Spondo shows finance teams who is spending what on AI tools, on which projects, and turns it into month-end journals. It works from usage counts and project labels, never from what people type into their AI tools. It isn't a proxy: it doesn't sit between your staff and their tools, see network traffic or block a session.
What we collect, and what we never do
From each person's machine, Spondo receives:
- their work email (or Cursor user ID or GitHub username), to attribute spend to a person and their department;
- session ID and timestamp, cost, token counts and model;
- repository name, folder within it and branch, to match a session to a project (names only, never remote URLs or full paths);
- for Claude Code on Pro and Max, and Codex, the share of the plan's usage limit used.
Never collected: prompts, responses, code, file contents or names, full paths, git remote URLs, commit messages, terminal commands or credentials. Our telemetry settings never turn on content capture, and every data point is cut to an allowlist of the fields above before it's stored.
The only Spondo code on staff machines is a short shell script your team can read in full. An admin pushes it inline in the AI tool's managed settings, or IT through MDM, so nothing is downloaded. It sends one small message when a session starts and never blocks the session.
Access to your systems
Attributing usage needs no credentials at all, only an ingest token. Every other connection (AI billing APIs, Xero, Linear, Slack) is optional, asks for the narrowest access its job needs, uses a read-only key where the provider offers one, and can be revoked by your admin at any time. Spondo writes to one place only: draft manual journals in your accounting software, for your accountant to approve. It can't create, change or pay bills.
Where your data lives
All customer data, including uploaded invoices, is stored in the EU, in Render's Frankfurt region, on managed PostgreSQL with point-in-time recovery. Spondo has three sub-processors:
- Render hosts the application and database, and holds SOC 2 Type II. We can share its report.
- Resend, in its EU region, sends account emails such as password resets and sees only the recipient's address and the email.
- PostHog, in its EU cloud, records how people use the app and the errors it hits. Replays mask every input and all text on screen, and it knows users by an internal ID, never their email.
Spondo sends no customer data to any AI model. This website is separate from the product: it counts visits with Plausible, which sets no cookies, and enquiries from its forms go to our CRM, Attio.
How it's protected
- HTTPS (TLS 1.2+) on every connection.
- Passwords of at least 10 characters, stored hashed; optional two-factor with an authenticator app; rate-limited attempts. Or single sign-on (OIDC) through Okta, Microsoft Entra ID or Google Workspace.
- Third-party tokens, billing keys, single sign-on secrets and two-factor secrets encrypted with AES-256-GCM before they reach the database.
- Ingest tokens shown once and stored only as a SHA-256 hash, revocable instantly.
- Every record carries its organisation's ID, and every query is scoped to it.
- Only Spondo's two founders have production access, with MFA on their hosting, database and code accounts. They can't see inside your account unless your owner or admin turns on support access, for a set time; it's read-only and every view is recorded.
GDPR, retention and deletion
Under UK and EU GDPR, you are the controller and Spondo is the processor. Your data is used only to report and account for your AI spend: never sold and never used to train models. It's kept while you use Spondo, so past journals stay traceable, and deleted within 30 days of the contract ending, or sooner on request. We help with access and erasure requests, and sign our standard DPA or review yours.
Certification
Spondo doesn't hold SOC 2 or ISO 27001 yet. We're working towards SOC 2 Type I by the end of 2026, then Type II. Our full security and data handling paper, with the access each connection needs, is available on request.
Reporting a vulnerability
If you think you've found a security issue in Spondo, email security@getspondo.com, and please give us a chance to fix it before telling anyone else. Our security.txt has the same contact.