Aurelia · UK GDPR

Privacy Policy

This policy describes how Aurelia Ltd (“Aurelia”, “we”, “us”) processes personal data when you use our autonomous financial operations platform. Last updated: March 2026.

Summary We process personal data to run accounting automation, bank-connected feeds, AI-assisted classification, and (where you instruct us) HMRC Making Tax Digital submissions. You have rights under UK GDPR including access, correction, erasure, and complaint to the ICO.

1. Who we are

Aurelia is a UK-based financial technology company providing software for autonomous financial operations and accounting automation for small and medium-sized enterprises. For UK data protection law, we act as the data controller for personal data processed in connection with our website, marketing, and the operation of our SaaS platform, except where we act as a processor strictly on your documented instructions (for example, under a data processing agreement for your organisation’s end-user data).

If you use Aurelia on behalf of a business, your organisation may also be a controller for employee and customer data you upload. In that case, both your organisation’s privacy notices and this policy may apply to different elements of processing.

TopicDetail
Legal entityAurelia Ltd (United Kingdom)
Privacy inbox[email protected]
Data protection[email protected] (or privacy inbox where no DPO is appointed)
PostalAs published on our website or provided on request for formal notices

2. Data we collect

We collect and process categories of personal data proportionate to delivering the service and meeting our legal obligations. The table below is illustrative and may vary depending on your subscription, integrations, and configuration.

CategoryExamplesTypical source
Identity & contactName, work email, phone (if provided)Registration, support tickets
Account & companyCompany name, role, tenant identifiersSignup, workspace settings
Financial & transactionInvoices, receipts, ledger lines, VAT attributes, bank transaction metadataUploads, feeds, platform use
Bank connectionTokens/consents, account identifiers (not passwords), transaction descriptionsAuthorised open banking / aggregator APIs
TechnicalIP address, device, browser, session logsInfrastructure, security monitoring
Usage & analyticsFeature usage events, crash diagnostics (where enabled)Product analytics (see Cookies)
Credentials We do not ask you to share your bank login password with Aurelia for standard integrations. Access is established through regulated or contractual APIs and token-based consent flows offered by your bank or authorised provider.

4. How we use data

We use personal data to deliver and improve the platform, including:

  • Provisioning and securing user accounts and organisational workspaces.
  • Running ingestion pipelines, reconciliation workflows, and AI-assisted classification with human oversight where configured.
  • Generating audit trails, compliance checks, and management information you configure.
  • Communicating service messages, security alerts, and (where permitted) product updates.
  • Training and evaluating models only as described in our agreements and privacy documentation — we minimise use of personal data for model development and apply contractual and technical controls.

Automated processing may suggest categories, flags, or draft filings. You or your authorised users remain responsible for reviewing outputs before reliance, particularly where submissions have legal or financial consequences. We design workflows to surface confidence indicators and escalation paths where CPA review is enabled.

We do not use your confidential accounting data to market third-party financial products to you without clear disclosure and, where required, consent. Product improvement analytics are aggregated or pseudonymised where feasible.

Human review Where your organisation requires human sign-off for specific thresholds (e.g. high-value journals, sensitive vendors), configure approval rules in the product. Policy defaults do not replace your internal control framework.

5. Financial data & HMRC

Where you connect financial sources or upload accounting documents, we process that data to perform bookkeeping automation, VAT calculations, and — if you enable it — submissions via HMRC’s Making Tax Digital (MTD) APIs.

HMRC processing is performed as your filing agent only where you authorise the submission. You remain responsible for reviewing returns and ensuring underlying records are accurate. We log technical events associated with API calls as part of service operation and auditability.

ActivityData involvedNotes
MTD VAT (example)VRN, return payloads, obligation referencesTransmitted per HMRC API specifications
Authentication to HMRCOAuth tokens where applicableStored and rotated under security standards
Evidence & logsSubmission IDs, timestamps, error codesSupport troubleshooting and audit

6. Third parties

We share personal data with categories of recipients where necessary:

  • Infrastructure & SaaS subprocessors — cloud hosting, databases, logging, email delivery, observability.
  • HMRC — when you instruct filings through official APIs.
  • Banks and open banking providers — to maintain authorised connections.
  • CPA / professional partners — where you enable escalation or review workflows.
  • Professional advisers — lawyers, insurers, auditors under confidentiality.

We require subprocessors to meet appropriate security and data protection terms. A current list may be provided on request or published on our website.

7. International transfers

Your data may be processed in the UK and the European Economic Area. If we transfer personal data outside the UK, we implement safeguards such as the UK International Data Transfer Agreement, the UK Addendum to the EU Standard Contractual Clauses, or reliance on adequacy regulations, as applicable.

Where subprocessors store encrypted backups in multiple regions for resilience, we assess transfer risk, document transfer mechanisms, and require subprocessors to notify us of legally binding requests for access that may affect personal data. You may request a summary of material subprocessor locations relevant to your workspace by contacting the privacy inbox.

Transfers to the United States or other jurisdictions without an adequacy decision are not undertaken without appropriate safeguards and, where required, supplementary measures assessed in line with ICO guidance. We periodically review our transfer register when vendors or product architecture change.

Transfer summary Primary processing is intended to remain UK/EEA-centric. If you require UK-only processing for a specific deployment, discuss enterprise options with our team — availability may depend on product tier and technical feasibility.

8. Retention

We retain personal data only as long as necessary for the purposes above and to meet legal, regulatory, and contractual requirements. Indicative periods:

Data typeIndicative retentionRationale
Active account profileDuration of contract + short wind-downService delivery
Accounting / tax records in workspaceUp to 7 years (or as required)UK tax / company law norms
Security & access logs12–24 monthsIncident response, forensics
Marketing consents & listsUntil withdrawn + minimal residualConsent lifecycle
BackupsOverlapping backup cyclesDisaster recovery

9. Your rights

Subject to exemptions, you have the following rights under UK GDPR in relation to personal data for which we are controller:

RightWhat it meansHow to exercise
AccessObtain confirmation and a copy of your personal dataEmail [email protected]
RectificationCorrect inaccurate or incomplete dataAccount settings or privacy inbox
ErasureRequest deletion where applicablePrivacy inbox (subject to legal holds)
RestrictionLimit processing in certain casesPrivacy inbox
PortabilityReceive structured, machine-readable data you provided (where applicable)Privacy inbox / export tools
ObjectionObject to processing based on legitimate interests or direct marketingPrivacy inbox / unsubscribe
Withdraw consentWhere processing is consent-basedConsent controls / privacy inbox
Automated decisionsInformation about solely automated decisions with legal/similar effects (if any)Privacy inbox

We will respond within one calendar month in most cases (extensions may apply for complex requests). We may need to verify your identity before disclosing data.

10. Security

We implement appropriate technical and organisational measures including encryption in transit, access control, least-privilege administration, vulnerability management, and staff training. No system is perfectly secure; if we become aware of a personal data breach that must be notified, we will follow applicable legal requirements.

Organisational measures include role-based access to production systems, background checks for roles with elevated access where permitted by law, and confidentiality commitments in employment and contractor agreements. Technical measures include network segmentation, secrets management, and monitoring for anomalous access patterns.

Customers are responsible for safeguarding their own credentials, configuring strong authentication where offered, and promptly revoking access for departed staff. We recommend periodic review of integration permissions and API keys associated with your workspace.

Control areaExamples
EncryptionTLS for data in transit; encrypted storage at rest for primary databases (as configured)
AccessMulti-factor options for administrators; audit logs for privileged actions
AvailabilityBackups and disaster recovery procedures tested on a schedule
AssuranceThird-party assessments and penetration tests as appropriate to roadmap

11. Cookies & analytics

We use cookies and similar technologies for essential operation (e.g. session security, load balancing context), preferences, and — where you consent — analytics to understand product usage. You can control non-essential cookies via our cookie tool (where provided) and your browser settings.

TypePurposeLegal basis
Strictly necessarySecurity, authentication stateLegitimate interests / essential
FunctionalRemember preferencesLegitimate interests or consent
AnalyticsAggregated usage metricsConsent where required

12. Children

Aurelia is intended for businesses and adults with authority to bind an organisation. We do not knowingly collect personal data from children under 16. If you believe we have done so, contact us and we will take steps to delete the information.

13. Changes to this policy

We may update this Privacy Policy to reflect legal, regulatory, or product changes. We will publish the revised version with an updated “Last updated” date. Where changes are material, we will provide additional notice (for example by email or in-product banner).

14. Contact & complaints

For any privacy question or request, contact [email protected]. If you are not satisfied with our response, you may complain to the Information Commissioner’s Office (ICO), the UK supervisory authority:

ICO Website: ico.org.uk/make-a-complaint
Helpline: 0303 123 1113