SpendAssureData security
SpendAssure works with billing, usage and contract data. It never needs the content of what people ask AI tools. This page explains what we receive, what we never receive and how your data is protected.
Our commitments
- Read-only access. We do not change your systems or the configuration of your accounts with AI providers.
- No access to content. We do not process prompts or model responses, only data about usage, costs and billing.
- No external AI models. We analyse invoices and contracts without passing them to external AI providers.
- Connector inside your infrastructure. When access to provider APIs is needed, the connector runs in your environment, in read-only mode.
- Confidentiality and data protection. We use your data only for our work together, under an NDA and a data processing agreement within the meaning of the GDPR.
What we receive, and what we never receive
We receive
- AI vendor invoices and credit notes
- Usage and billing exports from provider consoles
- Contracts, order forms and price sheets
- Team or cost-centre lists, if you provide them
We never receive
- Prompts or model responses
- Provider administrator credentials or API keys
- Access that could change your systems or provider settings
Usage exports can include activity per user, for example to count inactive seats. Reports show teams rather than individuals, and groups of fewer than five people are not shown separately. If your policies require it, remove or pseudonymise user names before sending an export; seat counts by team still work.
The connector
A connector is needed only for budget alerts based on provider APIs. It is a small program that runs inside your infrastructure:
- It reads usage and cost data in read-only mode.
- Provider credentials stay in your environment. The connector reads them from environment variables or files on its host and never sends them to us.
- It opens outbound HTTPS connections only and listens on no inbound port.
- It sits outside the path between your applications and AI providers, so requests to AI services never pass through SpendAssure.
Where the workspace runs
We agree the deployment with you before a pilot. The SpendAssure workspace can be hosted by e.Lens, or run inside your own infrastructure from the same software, with the connector reporting to it rather than to us.
Because SpendAssure is read-only and outside the request path, your AI services do not depend on it. If SpendAssure is unavailable, your tools keep working and the limits configured at your providers stay as they are.
Current scope
Sign-in uses named accounts with roles for owners, analysts and viewers. Single sign-on with your identity provider is planned. We do not claim certifications such as ISO 27001 or SOC 2 for SpendAssure, nor exemption from DORA or other regulation. We answer security and procurement questionnaires as part of agreeing a pilot.
Website privacy
Website analytics, hosting logs and email enquiries are covered on the website privacy page. You can change the optional analytics choice in the footer.
Questions from your security team?
We are glad to go through the data flow, the connector and the paperwork with your security and procurement colleagues.
