Where your data lives
The Allcora platform and its database run on Amazon Web Services in the Europe (Ireland) region. Slack messages, if you connect Slack, go to Slack, and billing details are held by Stripe. Production is a separate AWS account from our testing environment. Point-in-time backups of the database are kept, and the production database is protected against deletion.
What Allcora collects
For each AI request or usage period, Allcora records the time, vendor, model, tool, token counts, cost, the key, workspace or project it came from, the person's email address where the source reports it, and any engagement tags. It also keeps the people in your firm (name, email, roles and sign-in activity), your clients, engagements, budgets and decisions, and the audit log.
What it never stores
Allcora never stores prompts, responses, documents or code. The Anthropic and OpenAI connections read usage and cost reports only. The Allcora CLI doesn't switch on Claude Code's prompt logging, and Allcora keeps only the per-request usage and cost from the telemetry it receives. The Allcora API refuses records with fields that could carry content, such as prompt, messages or response.
Your keys and credentials
Vendor and gateway keys are stored in AWS Secrets Manager, as a separate secret for each firm, and are never shown again after you save them. The database and every secret are encrypted with an AWS KMS key that Allcora manages for the platform, rotated every year. Allcora ingestion keys are shown once; revoke any key you no longer use on the Usage sources page.
Access control
- Each person belongs to one firm, and everything they see is limited to that firm and to what their roles allow.
- Sign-in only works from a verified email address, and passwords are at least 12 characters.
- Removing someone ends their sign-in sessions and app access straight away. Ingestion keys belong to the firm, so rotate any key they held.
- The sign-in service and the APIs sit behind AWS WAF, a web application firewall.
- Approval links in emails are signed, personal to one approver, single-use and expire after 72 hours.
Audit log
Org admins and Finance owners can open the Audit log to see who did what and when: engagements created, budgets changed, top-ups approved or rejected, thresholds edited, rules and sources added, people invited or removed, months exported and locked, and terms accepted. Budget changes carry the reason given. Use Export CSV to keep a copy.
Budget suggestions Beta
Where Suggest a budget is available and you use it, the description you write is processed by Claude on Amazon Bedrock through an EU inference profile, so it is processed within the EU. Under Bedrock's terms, AWS doesn't use it to train models. Allcora keeps the description with your firm's data. Leave client names out; the form doesn't need them.
Your data, your requests
Org admins and Finance owners can export monthly chargeback figures and the audit log as CSV. For your usage records or other data, or to close your account and have your data deleted, contact us and we will confirm what's held and act on it. How we handle personal data is set out in the privacy notice.
Last reviewed 29 October 2026, Allcora platform version 15.