Privacy Policy
This policy explains what personal data Aurelia Spes Limited, a company registered in England and Wales (company number 17299015), registered office: 44 Henderson Way, Kempston, Bedford, England, MK42 8NP ("we", "us") collects when you use Aurelia Spes, why, and your rights. We are the controller of that data under the UK GDPR and the Data Protection Act 2018. Questions: Founder@aureliaspes.com.
What we collect
| Data | Why | Lawful basis |
|---|---|---|
| Name, email address, password (stored only as a one-way hash) | To create and secure your account and email you about it | Contract |
| Your declaration that you are 18 or over, and your country. Your date of birth is checked when you enter it and is not stored | To confirm you are 18 or over before we contract with you | Contract |
| Account type, company name and use case (business accounts) | To show the right plans and checks | Contract |
| Strategy code, settings and data you submit; the reports and backtests produced | To provide the analysis and keep your history | Contract |
| Subscription status, plan and invoices (card details are held by Stripe, never by us) | To take payment and keep accounting records | Contract; legal obligation |
| Usage counts, IP address and request logs | To enforce plan limits, prevent abuse and keep the service secure | Legitimate interests |
| The partner link you arrived from, if any | To know which partners introduced customers and pay them their share | Legitimate interests |
| Team membership: which plan your account uses, and who owns it | To share a firm's plan and its credits across named colleagues | Contract |
| Your credit history: each credit granted, spent, refunded or refilled, with the time and what it paid for (no code or report content) | To show you where your credits went, settle any dispute and keep accounting records | Contract; legal obligation |
| Your light or dark display choice | So the website and app look the way you chose on every device | Contract |
| Name, email, account type, company, the partner link you came from, and plan, payment and cancellation events, copied to our customer records (see "Our customer records" below) | To manage our relationship with customers: support, billing questions, renewals and complaints | Contract; legitimate interests |
We do not sell your data, and we do not use it for advertising.
If you are on somebody else's plan
A firm can buy one plan and give colleagues their own sign-in. You join a team only by accepting an invitation to it. Being invited, or signing up with the invited address, does not join you. Once you accept, the person who owns the plan can see the checks you run on it while you are a member: the strategy name, when you ran it, the language and files, the verdict, and your name and email beside it. They can open those reports in full and download their evidence packs. That is deliberate: it is the record the firm has to keep about its own algorithmic trading, and it is why the plan is theirs and not yours.
They cannot see anything else about your account, and they cannot see checks you ran before you joined or after you leave. You can leave a team at any time in Your team; your account and your own past reports stay yours, and the plan stops applying to you.
Our customer records
We keep our own customer records (a CRM) on the company's own computer, not with an outside provider. It holds the contact details and account events listed above, never your strategy code or the content of your reports. It is reached only from our own devices over a private network, protected by a passkey, and every view and change is recorded. The website keeps the events it passes to it for up to 30 days. When you delete your account, the website removes your details from those events at once and tells the CRM, and we erase your record there within one month.
The evidence record on a report
Every report carries a record of how it was produced: the rule-set version, the engine and model, the verdict rules applied, the name and email of the account that ran it, a SHA-256 checksum of the code submitted and a SHA-256 checksum of the report itself. The checksums are one-way: the code cannot be reconstructed from them. We keep this so that a report in a compliance file can be shown, years later, to be the report that was issued and to name the version of the checks that produced it.
Who processes it for us
- Stripe: payments, invoices and the billing portal, for subscriptions bought on this website.
- Apple: payment, billing and renewals for subscriptions bought inside the iPhone or iPad app. Apple is the seller for those, handles the payment itself under its own privacy policy, and tells us only that a subscription exists, which plan it is for, and when it renews or ends. We never receive your card details from Apple.
- Our hosting provider: runs the servers and stores the database.
- Resend: sends account emails (confirmation, password reset).
- Anthropic: when the full analysis is switched on, the code you submit is sent to Anthropic's API to produce the compliance report.
Some of these providers are based in, or use servers in, the United States. Where data leaves the UK, each transfer relies on the safeguards in that provider's data processing terms: the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, or the UK Extension to the EU–US Data Privacy Framework where the provider is certified under it. Email us and we will send you a copy of the safeguards for any provider. Anthropic's handling and retention of the code it receives is set out in its own commercial terms and privacy policy; we use it only through its API.
How long we keep it
- Account data, reports and backtests: while your account is open. Deleting your account deletes them, with one exception: checks you ran as a member of a firm's team, on the firm's plan, are the firm's records. They stay on the team owner's record, shown as run by you as you appeared on the team, because the firm is required to keep them (SYSC 9.1). The firm is responsible for those records from then on.
- Payment and invoice records: six years after the end of the financial year they relate to, because UK tax law requires it. After you delete your account they no longer carry your name or email.
- Free credit: if you delete your account, we keep a one-way fingerprint of your email address and the number of free credits it used, for twelve months from your last free credit. It cannot be read back as your address (it can only confirm a match if the same inbox signs up again) and it is not linked to anything else. It stops deleting and re-registering, or signing up under an alias of the same inbox, from restarting the free credit (legitimate interests: preventing abuse).
- Credit history: while your account is open; deleting your account deletes it. Payment records for credits you bought are kept as payment records (above).
- Customer records (CRM): while you are a customer and for up to six years afterwards for accounting and complaints, or erased within one month of your deleting your account, except what we must keep as payment records.
- Server logs: up to 30 days.
- Password-reset and email-confirmation links: until used or expired (30 minutes and 24 hours).
Your rights
You can ask to see, correct, delete, restrict or export your data, and you can object to processing based on legitimate interests. You can delete your account yourself in the app (Account → Delete account). For anything else, email Founder@aureliaspes.com. We reply within one month.
If you are unhappy with how we handle your data, you can complain to the Information Commissioner's Office at ico.org.uk. We would appreciate the chance to put it right first.
Cookies and storage
The web app keeps your sign-in session in your browser's local storage. We don't use advertising or tracking cookies. Stripe sets its own cookies on its payment pages to prevent fraud.
Children
Aurelia Spes is for people aged 18 and over. We do not knowingly collect data from anyone younger.
Changes
If we change this policy in a way that matters, we will tell you by email or in the app before the change applies.