Trust centre
What we have in place to keep your data safe, and what we are still working on.
Certifications and reports
Updated 30 October 2026
- Cyber Essentials: Planned. The UK government's baseline certification. Planned before VAT returns are sent live.
- Cyber Essentials Plus: Planned. The independently tested level, after Cyber Essentials.
- ISO/IEC 27001: Planned. An information security management system, certified by an accredited body.
- ISO/IEC 27701 and ISO/IEC 42001: Planned. Privacy information management, and management of AI: to be considered once ISO/IEC 27001 is held (FR-TRU-09).
- SOC 2 Type II: Planned. An independent auditor's report on our controls over time, offered to customers under a non-disclosure agreement once issued.
We will show each certificate or report here once it is issued, and not before.
From our records
Reading our records.
Where your data is stored and processed
Updated 30 October 2026
Your data is stored and processed in London (Amazon Web Services, eu-west-2). The AI features run on Amazon Bedrock in the EU, and e-invoicing through Recommand in the EU; a business's owner can choose UK only in Settings, Security, which turns both off. The details are in our privacy policy.
Sub-processors
Updated 15 November 2026
Every company that processes customer data for us, and where. A new one is added here, with where it works, before it processes any data.
- Amazon Web Services: Hosting the app and API, the database (Aurora PostgreSQL), files, sign-in (Cognito), email (SES), queues and logs. Where: UK: London (eu-west-2).
- Amazon Bedrock (Amazon Web Services): AI: reading receipts, suggesting categories, the assistant and the unusual spending scan. Where: EU: called from Ireland on the EU inference profile, which runs only in EU regions; the assistant's search index is made in London. Off for a business that chooses UK only.
- Amazon Bedrock web grounding (Amazon Web Services): The assistant's web search, after GOV.UK: the topic searched for, in a few words, never your conversation, figures or details. Where: US: offered only in US regions. Off for a business that chooses UK only.
- Amazon Bedrock AgentCore (Amazon Web Services): The assistant: running it, its calculations and its reading of GOV.UK; keeping each person's conversation for 30 days and what it learns from them; scoring a sample of its answers. Where: UK: London (eu-west-2); its memory and scoring models run within the EU. Off for a business that chooses UK only.
- Recommand (BRBX BV, Belgium): E-invoicing: carrying the e-invoices a business sends and receives over the Peppol network, listing it in Peppol's directory, and checking the identity of whoever registers the business (through its own provider, Didit). Where: EU and EEA, under a UK addendum to the EU's standard contractual clauses. Only for a business that has joined Peppol; off for a business that chooses UK only.
- Meta Platforms Ireland (WhatsApp): WhatsApp messages PactTax sends and receives for a business through AWS End User Messaging: PAM by WhatsApp for people who link their number, receipts asked for and sent, and reminders to customers who opt in. Where: Meta's WhatsApp Business terms; messages may be processed outside the UK, including the US under the UK extension to the EU-US Data Privacy Framework. Off for a business that chooses UK only.
- Stripe: Subscriptions, and card, Pay by Bank, Direct Debit and Tap to Pay payments of your invoices, into your own Stripe account. Where: As described in Stripe's terms.
- TrueLayer: Read-only bank connections; payments a business instructs from its own bank account, and the payee name check, where it has bank payments on. Where: UK.
- Google Analytics (Google): Analytics, only if you accept analytics cookies: pages visited and what is clicked. Where: US, under the UK extension to the EU-US Data Privacy Framework.
- Microsoft Clarity (Microsoft): Analytics on our public pages only, if you accept analytics cookies: heatmaps and recordings with typing hidden. Where: US, under the UK extension to the EU-US Data Privacy Framework.
Not sub-processors, but they see your data at your direction:
- Xero, QuickBooks Online, FreeAgent, Sage and Pandle: Only when you connect one to move your books to PactTax: PactTax reads from it. Where: Your provider's own terms.
- Shopify, Amazon, eBay and Etsy: Only when you connect a sales channel: PactTax reads your orders, fees and payouts from it, read-only. Where: Your channel's own terms.
- Microsoft 365: Only when a council connects it: PactTax saves the released public committee papers to the SharePoint site or OneDrive the council chose, as the signed-in officer. Where: The council's own Microsoft 365 tenant and terms.
- AWS Marketplace (Amazon Web Services EMEA SARL): Only when you buy PactTax through AWS Marketplace: AWS bills you, with VAT, as the marketplace operator, and tells PactTax which AWS account subscribed, to which plan and when it changes or ends. PactTax tells AWS nothing about your books. Where: AWS's own terms, as an independent controller.
- HMRC and Companies House: The returns and accounts you file, which they receive in law. Where: UK.
How PactTax uses AI
Updated 30 October 2026
What PAM, our assistant, does and does not do, the model it uses, where it runs, what it sees and how a person stays in charge are in how we use AI.
HMRC and Companies House recognition
Updated 30 October 2026
Each kind of filing needs its own recognition. PactTax sends a return live only once it is recognised; until then it prepares it, or sends it to the test service.
Loading the current status…
Service status
Updated 30 October 2026
Whether PactTax is working now, and anything we know is wrong, is on our status page.
Reporting a security issue
Updated 30 October 2026
Found a security weakness? See how to report a security issue. We acknowledge a report within one business day. Our security contact is also at /.well-known/security.txt.
Penetration testing
Updated 30 October 2026
Our test environment is penetration tested every quarter by an automated tester (AWS), signed in as three kinds of customer and trying to reach one from another. The first full test ran on 26 October 2026. Each finding is checked, fixed and tested again. An independent penetration test by a specialist firm has not yet been done; we will publish its summary here when it has.
Signing in
Updated 30 October 2026
You can sign in with a passkey: your fingerprint, face or device PIN, with no password to type. An authenticator app is the alternative. We never send sign-in codes by text message. Anyone who can file returns or move money must use a passkey or an authenticator app.
Software Security Code of Practice: our self-assessment
Updated 31 October 2026
How we meet each principle of the UK government's Software Security Code of Practice, reviewed every year. Last reviewed 31 October 2026.
Secure design and development
- 1.1 Follow an established secure development framework: Partly met. Every change is reviewed and passes a quality gate with static analysis (Semgrep, Bandit) and infrastructure checks (Checkov) before it ships. A written mapping to a named framework such as the NCSC's is still to be done.
- 1.2 Manage third-party components and their risks: Met. A software bill of materials (CycloneDX) is made for each build, and dependencies are scanned for known vulnerabilities (Trivy, pip-audit) in the build.
- 1.3 Test software and updates before distribution: Met. Unit, integration and end-to-end tests run in the pipeline, and a release goes to a test environment before production.
- 1.4 Apply secure by design and secure by default principles: Met. Passkeys or an authenticator app for anyone who files or moves money, encryption at rest and in transit, least-privilege roles, and AI that only proposes.
Build environment security
- 2.1 Protect the build environment from unauthorised access: Met. Builds run in AWS CodeBuild under roles scoped to each pipeline, with no long-lived keys; secrets are scanned for (Gitleaks) on every change.
- 2.2 Control and log changes to the build environment: Met. Pipelines are defined as code and changed only through reviewed change sets; AWS CloudTrail logs every change.
Secure deployment and maintenance
- 3.1 Distribute software securely: Met. PactTax is delivered as a service over HTTPS only; the mobile apps are distributed through the app stores.
- 3.2 Implement and publish a vulnerability disclosure process: Met. Published on this page and at /.well-known/security.txt.
- 3.3 Detect, prioritise and manage vulnerable software components: Met. Builds fail on high and critical findings in dependencies and container images, and findings are fixed by severity.
- 3.4 Report vulnerabilities to relevant parties: Partly met. We report a weakness found in another vendor's component to that vendor. A written procedure for when and how is still to be published.
- 3.5 Provide timely security updates, patches and notifications: Met. As a service, fixes reach every customer when deployed; customers are told of anything they must do on the status page and by email.
Communication with customers
- 4.1 Specify the support and maintenance level provided: Partly met. Support hours and response times are on the contact page; a service level for each plan is still to be published.
- 4.2 Give at least one year's notice before support ends: Met. A public API version or operation that is to go carries Deprecation and Sunset dates at least a year ahead.
- 4.3 Make information available about notable incidents: Met. Incidents and their root-cause reports are on the status page, and affected customers are told directly.
Accessibility
Updated 30 October 2026
We are working to WCAG 2.2 AA. What works, what does not yet, and how to tell us is in our accessibility statement.
Data protection
Updated 30 October 2026
The reviews the Data (Use and Access) Act 2025 asks of us. A review is a draft until our data protection lead signs it off. Questions and requests about your data: pacttax@rinegansolutions.com.
- Automated decisions (reviewed 30 October 2026, draft). The privacy notice now describes the safeguards and how to use them, and names the features they apply to. The safeguards in each feature are PRD FR-PAM-15, built with PAM's governance layer.
- Recognised legitimate interests (reviewed 30 October 2026, draft). Reviewed each legitimate interest in the privacy notice (security, fraud prevention, HMRC's fraud prevention headers, fixing faults, waitlist emails). Each stays on ordinary legitimate interests with its balancing test. A recognised legitimate interest would be relied on only to answer a lawful request from an authority to detect or prevent crime, or to safeguard someone at risk, and each such disclosure would be recorded.
- Cookies and the analytics exemption (reviewed 30 October 2026, draft). Reviewed the cookies on the privacy page. The cookies needed to sign in and keep a session safe stay exempt. Analytics stay off unless a person accepts them: Google Analytics and Microsoft Clarity are run by third parties, so PactTax keeps asking for consent rather than relying on the exemption.
- Subject access requests: reasonable and proportionate searches (reviewed 30 October 2026, draft). The procedure: confirm who is asking; export everything PactTax holds for the person from every table that is theirs, found the same way erasure finds it, with their files (Settings, Your data, or by staff on request); then search the support inbox and the staff console's records for their name and email. Each request is logged with the date it arrived, what was searched and the date it was answered, within one month.
- Data protection complaints (reviewed 30 October 2026, draft). A complaint form on the privacy page, open to anyone. Each complaint is acknowledged by email at once, with its date and reference; staff record each step and send the outcome from the staff console, and the whole handling is kept.
To complain about how we use your data, use the complaint form.