Axioma Professional Accounting

Data Processing Agreement

Version dpa-2026-09-02

Effective Date: September 2, 2026 Last Updated: September 2, 2026

This Data Processing Agreement ("DPA") is entered into by and between Quantum Quake Innovations ("Axioma," "Processor," or "Service Provider") and the customer entity agreeing to the Axioma Terms of Service ("Customer" or "Controller").

This DPA supplements and forms an integral part of the Axioma Terms of Service available at https://axiomapr.app/terms ("Agreement"). In the event of any conflict between this DPA and the Agreement, this DPA shall govern with respect to the Processing of Personal Data.


1. Definitions


2. Roles and Processing Instructions

2.1 Role of Parties. The parties agree that with respect to Customer Personal Data, Customer acts as the Controller (or Business) and Axioma acts as the Processor (or Service Provider).

2.2 Documented Instructions. Axioma shall process Customer Personal Data solely: (a) to provide, secure, and maintain the Service under the Agreement; (b) in accordance with the documented instructions of Customer; and (c) as required by applicable laws to which Axioma is subject.

2.3 CCPA/CPRA Service Provider Terms. Axioma certifies that it does not and will not:

2.4 Customer Compliance. Customer represents and warrants that it has established and will maintain all required legal bases, notices, and authorizations required under Applicable Privacy Laws to transfer Customer Personal Data to Axioma for the processing operations contemplated under the Agreement.


3. Sub-processors

3.1 Authorized Sub-processors. Customer provides general written authorization for Axioma to engage the third-party infrastructure providers listed in Schedule 2 (and published at https://axiomapr.app/subprocessors).

3.2 Sub-processor Commitments. Axioma shall bind each Sub-processor to written obligations no less protective of Customer Personal Data than those set forth in this DPA. Axioma remains fully liable to Customer for the performance of each Sub-processor.

3.3 Notification of Sub-processor Changes. Axioma shall update its sub-processor directory at https://axiomapr.app/subprocessors, and shall send written notice to the account owner of each Customer, at least ten (10) business days prior to authorizing any new Sub-processor. Business days exclude Saturdays, Sundays and public holidays observed in the Commonwealth of Puerto Rico. Customer may object in writing on reasonable data protection grounds within ten (10) business days. If the parties cannot resolve the objection, Customer may terminate the subscription without penalty.


4. Technical and Organizational Security Measures (TOMs)

4.1 Security Safeguards. Axioma shall implement and maintain appropriate administrative, physical, and technical safeguards designed to protect Customer Personal Data against accidental, unauthorized, or unlawful destruction, loss, alteration, or disclosure, as detailed in Schedule 1.

4.2 Confidentiality. Axioma ensures that all personnel authorized to process Customer Personal Data are bound by statutory or contractual obligations of confidentiality.


5. Security Incidents and Personal Data Breaches

5.1 Breach Notification. Axioma shall notify Customer in writing without undue delay, and in any event within seventy-two (72) hours, after becoming aware of a confirmed Personal Data Breach affecting Customer Personal Data. Axioma becomes "aware" when its personnel confirm, following investigation, that a Personal Data Breach has occurred; the period runs from that confirmation. Where the full particulars are not available within that period, Axioma shall provide the information it holds and supply the remainder as it is established.

5.2 Remediation & Details. Axioma shall take prompt steps to mitigate the impact of any breach at its own expense. The notification shall describe the nature of the incident, the categories and approximate number of Data Subjects and records affected, and the remedial actions taken or planned.


6. Data Subject Rights & Audit Support

6.1 Assistance with Requests. Axioma shall provide commercially reasonable technical assistance, through the self-service capabilities of the platform or direct support, to enable Customer to respond to Data Subject requests (such as access, correction, deletion, or portability) under Applicable Privacy Laws. If a Data Subject submits a request directly to Axioma, Axioma shall promptly redirect the Data Subject to Customer.

6.2 Compliance Demonstrations. Upon Customer's written request no more than once per twelve-month period, Axioma shall provide documentation demonstrating its compliance with this DPA. If an independent audit is required, the audit will occur during regular business hours upon reasonable notice, subject to standard confidentiality agreements and at Customer's sole cost.


7. Return and Deletion of Data

7.1 Export Window. Following expiration or termination of the Agreement, Customer may export Customer Personal Data through Axioma's self-service export tools during the thirty (30) day export window defined in the Terms.

7.2 Permanent Deletion. Following the thirty (30) day export window, Axioma shall permanently delete, overwrite, or anonymize Customer Personal Data within sixty (60) days, except to the extent that retention is strictly required by applicable law or preserved within routine, encrypted disaster-recovery backups (which are overwritten in accordance with standard retention cycles).


8. International Data Transfers

8.1 Primary Processing Location. Customer Personal Data is stored and processed on secure cloud infrastructure located within the United States.

8.2 Standard Contractual Clauses (SCCs). Where transfers of Customer Personal Data from the EEA, the UK, or Switzerland to Axioma are subject to Chapter V of the GDPR, the parties incorporate the European Commission's Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914):


Schedule 1: Technical and Organizational Measures (TOMs)

  1. Access Controls: Passwords are stored only as salted cryptographic hashes (bcrypt); role-based access control (RBAC) is enforced on every API route through a three-layer check of authentication, permission and subscription entitlement; authentication tokens (JWT) expire eight (8) hours after issue and are not renewable, requiring re-authentication.
  2. Transmission Security: All traffic between browsers, the application server and the database is carried over HTTPS/TLS. The Service does not use cookies for authentication; the session token is held in browser local storage and presented in an application request header, and is scoped to a single origin under a Content-Security-Policy that restricts script execution to first-party sources.
  3. Data at Rest Security: Database records and backup archives are encrypted at rest by our managed database provider using AES-256, under that provider's published encryption practices.
  4. Tenant Isolation: Every table carries a company_id and every query is scoped to the requesting user's company. In addition, Row Level Security is enabled on all application tables in the production database with no permissive policies defined, so the database rejects any direct access outside the application's own authenticated connection.
  5. Business Continuity: The database and application hosts operate in a single United States region. Axioma does not currently subscribe to a contracted backup or point-in-time recovery service, and gives no warranty as to backup frequency, retention period or recovery point objective. Customers are directed to the self-service export tools and to the Customer Responsibility provision of the Terms (§5.6), which place the authoritative copy of the records with the Customer. Axioma will amend this Schedule, with notice, before offering the Service to the general public.
  6. Code Security: Dependencies are scanned automatically on every change to the main branch, on every pull request, and on a weekly schedule; a high-severity or critical advisory affecting the application server's runtime dependencies fails the build. Dependency updates are proposed automatically and reviewed. Production and development environments are strictly separated: the application selects its database by environment alone and deliberately ignores the production connection string outside production, so development work cannot reach customer data. Application secrets are held in the hosting provider's environment configuration and are not committed to source control; the server refuses to start with a missing or weak signing secret.

Schedule 2: Authorized Sub-processors

Sub-processor NameEntity & HeadquartersProcessing ActivityLocationEffective
Stripe, Inc.Stripe, Inc. (USA / Ireland)Payment processing, recurring billing, PCI-DSS compliant hosted checkout. Card details are collected on Stripe-hosted pages and are never transmitted to or stored by Axioma.United States / Global2026-09-02
Render, Inc.Render, Inc. (USA)Application server hosting (the Axioma API). Runs the Express application that serves every authenticated request. All categories of Customer Personal Data are processed in transit and in memory on this infrastructure.United States (Oregon)2026-09-02
Supabase, Inc. / Amazon Web Services, Inc.Supabase, Inc. / Amazon Web Services, Inc. (USA)Managed PostgreSQL database hosting, encryption at rest, automated backups. All Customer Personal Data is stored at rest here.United States (AWS us-west-2)2026-09-02
Vercel, Inc.Vercel, Inc. (USA)Static hosting and edge delivery of the browser application. Serves application assets only; does not execute the API and does not process Customer Personal Data.United States / Global Edge2026-09-02
Resend, Inc.Resend, Inc. (USA)Delivery of transactional email (password resets, user invitations, system notices) and, where the Customer uses the invoice email feature, delivery of invoice documents to recipients the Customer designates. Message content — including the recipient address, the Customer's business name and the invoice PDF — is transmitted to and processed by this provider. Messages are sent from an Axioma-controlled sending domain with the Customer's business name as the display name and the Customer's own address as Reply-To; the Customer's address is not used as the envelope or header sender.United States (us-east-1)2026-09-03

Ancillary third party (not a Sub-processor of Customer Personal Data). Axioma's public pages load typefaces from Google Fonts (Google LLC, USA), which receives the requesting browser's IP address in the course of serving those files. Google receives no account information and no Customer Personal Data.

Change history. Axioma maintains the current list of authorized Sub-processors, together with the effective date of each entry and a dated record of additions and removals, at https://axiomapr.app/subprocessors. Changes are published there in accordance with the advance-notice period in Section 3.3.

Notification of changes. Advance notice under Section 3.3 is sent by email to the account owner of every active Customer, without the Customer having to request it. The right belongs to the Customer, so it is not conditional on subscribing to anything. The notice states the Sub-processor, its processing activity and location, the date it may first process Customer Personal Data, and the date by which an objection must be received; it is sent in English and Spanish, and replies reach legal@axiomapr.app.

An account owner may decline these notices from their profile in the Service. Declining waives the advance notice to which that Customer is entitled under Section 3.3, and Axioma records the decision. Axioma also records the despatch of each notice to each recipient, which is the evidence available under Section 6.2.

Revision of 2026-09-02: Render, Inc. added (previously omitted); Resend, Inc. removed (not engaged); Vercel's processing activity corrected — it hosts the static frontend, not the API.

Revision of 2026-09-03: Resend, Inc. added as the outbound mail relay, resolving the bracket left open in the previous revision. The provider was selected and integrated on this date; the sending domain mail.axiomapr.app is verified on the account and messages are processed in the provider's us-east-1 region. This entry supersedes the 2026-09-02 removal, which recorded the accurate position at that time — Resend was not then engaged.

Advance notice (Section 3.3). This addition is subject to the ten-business-day advance-notice period. The entry carries its effective date above; publish it at https://axiomapr.app/subprocessors and notify Customers on the notification list before the provider begins processing Customer Personal Data in production, or delay the production cut-over until the period has run.