Security at RootSpend

1. 1You paste it and can test it with a read call before you save.
2. 2It is encrypted with Fernet: AES 128 encryption, signed with HMAC SHA256. A tampered value refuses to decrypt.
3. 3It is stored encrypted next to your tool, never in plain text.
4. 4It is used in memory only while a sync runs, then thrown away.
5. 5It never comes back No screen, API, export or log returns it. AI keys show a masked hint, nothing more.
6. 6You stay in control Replace it or disconnect the tool at any time.

• In production, the server refuses to start without a valid encryption key, so it can never fall back to storing keys in plain text.
• Error messages from vendors are scrubbed of every credential before anything is logged.
• RootSpend only calls each vendor’s own addresses. For example, it won’t follow an Azure link to any host other than management.azure.com.

Each table that holds company data has this rule, straight from our database setup. A request that doesn’t say which company it is for sees nothing at all, and a write for the wrong company is refused by the database, not just skipped by our code.

ALTER TABLE tools ENABLE ROW LEVEL SECURITY;
ALTER TABLE tools FORCE ROW LEVEL SECURITY;

CREATE POLICY tenant_isolation ON tools
  USING      (org_id = NULLIF(current_setting('app.current_org_id', true), '')::uuid)
  WITH CHECK (org_id = NULLIF(current_setting('app.current_org_id', true), '')::uuid);

• FORCE means the rule applies to RootSpend’s own database user too, not just to everyone else.
• Background jobs, like syncs and analyses, run inside the same rule, one company at a time.

{
  "currency": "USD",
  "period": { "start": "2026-09-28", "end": "2026-10-27", "days": 30 },
  "totals": { "spend": 18158.42, "change_pct": 4.6 },
  "tools": [
    { "id": "t1", "name": "Snowflake", "connector": "snowflake",
      "category": "Databases", "spend": 7906.10, "change_pct": 2.4,
      "people_with_spend": 14 }
  ],
  "services": [
    { "id": "s1", "tool": "t1", "name": "ANALYTICS_WH", "spend": 3120.50,
      "active_days": 30, "period_days": 30, "daily_variation_pct": 8.2 }
  ],
  "teams": [ { "name": "Data", "spend": 3688.00, "change_pct": 6.1 } ],
  "daily_spend": [ { "day": "2026-10-27", "spend": 612.40 } ]
}

• Names from your tools are sent as data the AI is told never to follow, so text hidden in a resource name can’t give it orders.
• The AI never writes an amount. It writes placeholders, and RootSpend fills in every figure from your data.
• Each finding must cite the exact spend it is about. Anything that cites spend that doesn’t exist is dropped, and no saving can be bigger than what you really spend.
• Links and markup are stripped from its answer before anyone sees it.
• It can’t change anything in your tools. People decide, and RootSpend measures the result 14 days later.
• AI spend is capped. Each request reserves its worst case cost before it is sent, so an allowance can’t be overrun.
• An admin chooses RootSpend AI, your own Anthropic, OpenAI or Gemini key, or off.

• Costs per person stay off until an owner turns them on for the organization.
• Even then, only roles allowed to see people can view them. Everyone else sees teams and tools.
• People data is never sent to the AI analyst.

• Passwords are hashed with bcrypt. Nobody can read them, including us.
• Sign in, sign up and password reset allow 5 attempts a minute from one address, which stops password guessing.
• Your session lives in a secure, httpOnly cookie that scripts on the page can’t read. Signing out or changing your password ends it.
• In production the sign in cookie only travels over HTTPS.
• Roles decide who can view costs, manage budgets, connect tools or see people.

1. 1

   On the list

   Only emails on a list kept on the server can open the console. No button in the app adds anyone.

2. 2

   Second factor

   A code from an authenticator app, which can’t be reused.

3. 3

   30 minutes

   Console sessions end after 30 minutes, or when the person signs out.

• Inside your organization, staff can only look. Anything that would change your data is refused.
• Every visit is written to your own audit log, as platform_admin.viewed.

• tool.connected
• tool.reconnected
• tool.deleted
• budget.updated
• alert_rule.created
• group.people_set
• member.updated
• invitation.created
• ai.settings_updated
• ai.key_deleted
• recommendation.marked_applied
• org.exported
• platform_admin.viewed

Keys are never written to the audit log, not even masked.

• Owners can export everything at any time: every table that holds your organization’s data.
• The export leaves out your connector keys, and drops any field that looks like a secret.
• Deleting an organization removes every one of those tables in one go, after you type its exact name.

• No cookies, no analytics and no advertising trackers.
• Served only over HTTPS, with strict security headers.
• The contact form is delivered by Web3Forms straight to our inbox. We don’t add you to any list.