Skip to content
Zuperbase
FeaturesFor firmsSecurity
Sign inRequest early access

Zuperbase Data Processing Agreement

Version 1, effective 17 Nov 2026

This agreement ("DPA") covers personal data that a customer puts into Zuperbase. The parties are:

  • The customer: the organisation or accounting firm whose owner accepts this DPA at sign-up or later in settings. The customer is the controller. In Indian law it is the Data Fiduciary.
  • TrueAxis Private Limited, CIN U70200HR2026PTC144463, of 406, Pabana Hassanpur, Assandh, Karnal, Haryana 132040, India. TrueAxis is the processor. In Indian law it is the Data Processor.

This DPA forms part of the Zuperbase Terms of Service. If the two conflict about personal data, this DPA wins.


1. Why this DPA exists

  • India. Under the Digital Personal Data Protection Act, 2023, section 8(2), a Data Fiduciary may use a Data Processor only "under a valid contract". This DPA is that contract.
  • UK and EU. The UK GDPR and the GDPR, Article 28(3), list what a controller–processor contract must say. This DPA covers each item, and Annex 4 maps them.
  • UAE. The UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) expects a processor to act on the controller's instructions and to keep data secure. This DPA does that.

2. Words used

  • Personal data: any information about an identifiable living person. It includes "digital personal data" under the DPDP Act.
  • Customer personal data: personal data in the customer's Zuperbase organisation or firm, which TrueAxis processes for the customer. Annex 1 describes it.
  • Sub-processor: a company that TrueAxis uses to help process customer personal data.
  • Breach: a personal data breach, meaning any unauthorised processing, or any accidental disclosure, access, change, loss or destruction of customer personal data.
  • Data protection law: every data protection law that applies to the processing. That includes:
    • the DPDP Act and DPDP Rules, 2025, as their provisions come into force;
    • section 43A of the Information Technology Act, 2000 and the 2011 rules on sensitive personal data, while they apply;
    • the GDPR and UK GDPR;
    • the UAE PDPL.

3. Roles

  1. The customer is the controller (Data Fiduciary) of customer personal data. TrueAxis is the processor (Data Processor).
  2. Accounting firms. For data about a firm's clients, the firm is the controller. If the client holds its own Zuperbase organisation, the client is the controller of that organisation's data, and the firm is a user whom the client has invited.
  3. Account data. TrueAxis is the controller of account data about users: sign-in, billing, support and logs. The Privacy Policy covers that data, not this DPA.
  4. Customer's own AI key. If the customer connects its own AI provider key, that provider is the customer's own choice. The customer deals with that provider directly. It is not a TrueAxis sub-processor.

4. The customer's duties

The customer confirms that:

  • it has a lawful basis, or consent where needed, for every piece of personal data it puts into Zuperbase;
  • it has given any notices that the law requires to the people whose data it uploads;
  • its instructions to TrueAxis comply with data protection law;
  • it remains responsible to those people and to regulators under data protection law. This follows section 8(1) of the DPDP Act, under which the Data Fiduciary stays responsible for processing done on its behalf;
  • it keeps its own statutory records, such as GST, tax and company records, for as long as the law requires, and exports them before it asks for deletion.

5. TrueAxis's duties

5.1 Process only on instructions

  • TrueAxis processes customer personal data only on the customer's documented instructions. Those instructions are:
    • this DPA and the Terms;
    • the customer's settings and actions in Zuperbase, including approvals and autonomy levels;
    • any other written instruction the customer gives that TrueAxis accepts.
  • The same applies to transfers to another country.
  • If a law requires TrueAxis to process data in any other way, TrueAxis will tell the customer first, unless that law forbids it.
  • TrueAxis will tell the customer at once if it believes an instruction breaks data protection law.
  • TrueAxis will not:
    • use customer personal data for its own purposes;
    • sell it;
    • use it to train AI models;
    • combine it with another customer's data.

5.2 Confidentiality

Everyone at TrueAxis who can access customer personal data is bound to keep it confidential, by contract or by law. Access is given only when needed, and it is logged.

5.3 Security

  • TrueAxis takes the technical and organisational measures in Annex 2. They meet:
    • Article 32 of the GDPR and UK GDPR;
    • section 8(5) of the DPDP Act and rule 6 of the DPDP Rules;
    • rule 8 of the 2011 sensitive personal data rules.
  • TrueAxis may improve these measures. It will not lower the overall level of protection.

5.4 Sub-processors

  1. The customer gives TrueAxis general written authorisation to use the sub-processors in Annex 3.
  2. TrueAxis will give at least 30 days' notice before it adds or replaces a sub-processor, by email to the owner and in the published list.
  3. The customer may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, the customer may close the affected service. It gets a pro-rata refund of prepaid fees for that service, by credit note.
  4. TrueAxis puts each sub-processor under a written contract with data protection duties at least as strict as this DPA's, including on security.
  5. TrueAxis remains fully liable to the customer for each sub-processor's work.

5.5 Helping with people's rights

  • TrueAxis will help the customer answer requests from people who use their rights: to see, correct, complete, update, erase or move their data, or to object, nominate or complain.
  • Most requests can be handled by the customer directly in Zuperbase, through search, edit and export.
  • If a request comes to TrueAxis directly, TrueAxis will pass it to the customer within 5 working days and will not answer it alone, unless the law requires it to.
  • Under the DPDP Rules, the customer must answer within 90 days. TrueAxis will help in time for the customer to meet that limit.

5.6 Breaches

  1. Notice. TrueAxis will tell the customer without undue delay, and in any case within 48 hours, after it becomes aware of a breach affecting customer personal data.

  2. What TrueAxis will say, as far as it knows at the time:

    • what happened, including its nature, extent, timing and location;
    • the kinds and rough number of people and records affected;
    • the likely consequences;
    • the steps taken, or proposed, to limit harm and to prevent it happening again;
    • whom to contact at TrueAxis.

    TrueAxis will send updates as it learns more.

  3. Why 48 hours. The customer may have to:

    • tell the Data Protection Board of India within 72 hours under rule 7(2) of the DPDP Rules, once in force;
    • tell its UK or EU supervisory authority within 72 hours under Article 33 of the GDPR and UK GDPR;
    • tell affected people without delay.

    The 48 hours leave the customer time to do so.

  4. CERT-In. Where the CERT-In directions of 28 April 2022 apply to TrueAxis's own systems, TrueAxis will also report the incident to CERT-In within 6 hours.

  5. Help. TrueAxis will help the customer with its notices to regulators and to affected people. TrueAxis will not notify affected people itself unless the customer asks or the law requires it.

5.7 Other help

Where it can, given the information it holds, TrueAxis will help the customer with:

  • data protection impact assessments and prior consultation, under Articles 35 and 36 of the GDPR and UK GDPR;
  • any assessment the customer must do as a Significant Data Fiduciary, if the Indian government notifies it as one.

5.8 Accuracy

Zuperbase applies deterministic checks to accounting entries. However, the customer decides what is posted. Section 8(3) of the DPDP Act puts the duty to keep data complete, accurate and consistent on the Data Fiduciary. TrueAxis will help by fixing any error in the service that harms accuracy.

6. Deletion and return at the end

  1. When the customer asks to delete its organisation or firm, or the Terms end:
    • TrueAxis sends the owner a full export of customer data by email, and makes it available to download from the dashboard;
    • the customer has 30 days to cancel the deletion;
    • after 30 days, TrueAxis deletes customer personal data, including copies held by sub-processors;
    • backups are overwritten within 14 days.
  2. What may be kept. TrueAxis may keep data only where a law requires it, and only for as long as that law requires. In that case it keeps the data confidential and does nothing else with it. Examples:
    • DPDP Rules, rule 8(3). From when it comes into force, it requires processing logs, traffic data and related personal data to be kept for at least 1 year from the processing. This covers processing done by a Data Processor.
    • CERT-In directions. They require system logs to be kept for 180 days.
  3. TrueAxis will confirm deletion in writing if asked.
  4. The customer's statutory record-keeping duty stays with the customer. For example, section 36 of the CGST Act requires GST records to be kept for 72 months after the due date of the annual return.

7. Showing compliance and audits

  1. On request, TrueAxis will give the customer the information needed to show that it meets this DPA. That includes its security summary and any independent audit reports or certificates it holds.
  2. If that information is not enough, or a regulator requires it, the customer may audit TrueAxis, or appoint an independent auditor who is bound to confidentiality. Audits work like this:
    • the customer gives at least 30 days' written notice;
    • no more than once in any 12 months, unless a breach or a regulator requires more;
    • during business hours, without disrupting the service or seeing other customers' data;
    • at the customer's cost.

8. Transfers outside India

  1. Customer personal data is hosted on servers in India.
  2. UK and EU data. TrueAxis does not yet serve customers established in the UK or the EU. This section applies if it does. Where the GDPR or UK GDPR applies to the customer, sending data to TrueAxis in India is a restricted transfer. The parties agree to the following:
    • EU: the Standard Contractual Clauses in Commission Implementing Decision (EU) 2021/914, Module Two (controller to processor), are incorporated into this DPA. The customer is the data exporter and TrueAxis is the data importer. These choices apply:

      • Clause 7 (docking clause): included;
      • Clause 9: Option 2 (general authorisation), with the notice period in section 5.4;
      • Clause 11: the optional redress wording is not included;
      • Clause 13: the supervisory authority of the customer's EU representative or establishment;
      • Clause 17: the law of the EU Member State that TrueAxis names, by notice, before it first serves a customer in the EU;
      • Clause 18: the courts of that Member State.

      Annexes 1 to 3 of this DPA serve as the Annexes to the Clauses.

    • UK: the UK International Data Transfer Addendum issued by the Information Commissioner is incorporated. It applies to the EU Clauses above, with the tables completed from this DPA.

    • If the Clauses or the Addendum conflict with this DPA, the Clauses or the Addendum win.

  3. Sub-processors abroad. TrueAxis will not move customer personal data out of India, except to sub-processors listed in Annex 3 with suitable safeguards in place, or on the customer's instruction.
  4. India. TrueAxis will follow any restriction the Indian government notifies under section 16 of the DPDP Act or rule 15 of the DPDP Rules.
  5. UAE. For UAE customers, the customer instructs TrueAxis to transfer the data to India to provide the service. The customer is responsible for making sure that the transfer meets the cross-border conditions of the UAE PDPL.

9. US customers

Where a US state privacy law treats TrueAxis as a "service provider" or "processor", TrueAxis:

  • processes customer personal data only to provide Zuperbase;
  • does not sell or share it, or use it for cross-context behavioural advertising;
  • does not keep, use or disclose it outside the direct business relationship with the customer;
  • does not combine it with other data, except as that law allows;
  • will tell the customer if it can no longer meet these duties.

10. Liability

The limits in the Terms of Service (section 20) apply to this DPA. They do not limit either party's liability to a person whose data is affected, where data protection law does not allow such a limit.

11. Term, law and courts

  • This DPA lasts as long as TrueAxis processes customer personal data. Duties that by their nature continue, such as confidentiality and deletion, survive its end.
  • This DPA is governed by the laws of India. The courts at Karnal, Haryana have jurisdiction. This is subject to section 8, where the EU Clauses and the UK Addendum set their own law and courts.
  • TrueAxis may update this DPA to follow changes in the law. It will give 30 days' notice of any change that reduces the customer's protection. If the customer does not agree, it may close its account.

Annex 1: Details of the processing

Item Details
Subject matter Providing Zuperbase: bookkeeping, invoicing, bills, bank reconciliation, reports, tax workings (drafts), payroll calculations and practice management
Duration While the customer's organisation or firm exists, plus the 30-day cancellation window and backup cycle in section 6, plus any period the law requires
Nature of processing Storing, organising, reading, classifying (including with AI where the customer turns it on), calculating, displaying, exporting, emailing on the customer's instruction, backing up and deleting
Purpose Only to provide Zuperbase to the customer and to keep it secure
People whose data is processed The customer's own customers, vendors and suppliers, and their contact persons. The customer's employees and contractors (payroll). The customer's owners, directors, partners and shareholders. Users invited by the customer. For accounting firms: the firm's clients and their contacts, employees and related persons
Types of personal data Names, addresses, emails, phone numbers. Tax identifiers such as GSTIN, PAN, VAT number or TIN. Bank account details shown on documents and statements. Invoice, bill and payment details. Payroll data: salary, deductions, statutory numbers such as PF, ESI, NI or SSN where entered, and attendance where used. Uploaded documents such as invoices, receipts and bank statements. Notes and messages in the platform
Sensitive data Financial information such as bank account details counts as "sensitive personal data or information" under the 2011 IT rules. The service is not designed for health, biometric or other special category data. The customer should not upload such data unless the law requires it, for example statutory payroll deductions that reveal it

Annex 2: Security measures

TrueAxis keeps these measures in place.

  1. Encryption: TLS (HTTPS) for all traffic. Customers' own AI keys, connection secrets and email content waiting to be sent are stored encrypted by the application. The database accepts connections only from the server itself.
  2. Access control:
    • one login per person;
    • per-user permissions set by the owner;
    • two-step sign-in available;
    • staff access through a separate admin surface, limited to people who need it, and logged.
  3. Separation of customers: row-level isolation by organisation in the database. Each AI call runs only on one organisation's data.
  4. Logs and monitoring: an audit trail of user and bot actions, and security logs kept for at least 180 days (CERT-In) and, once the rule applies, 1 year (DPDP Rules, rule 6(1)(e) and rule 8(3)). Logs are reviewed for unauthorised access.
  5. Continuity: the database and documents are backed up every night and kept for 14 days. Backups can be read only by the server's administrator account.
  6. Secure development: an automated test suite, code review, and no customer data in test environments.
  7. People: confidentiality duties for staff, and security training.
  8. Suppliers: written contracts with sub-processors that include security duties, as rule 6(1)(f) of the DPDP Rules requires.
  9. Incidents: a documented process for incidents and breaches, including the notice times in section 5.6.
  10. Documentation: a written information security programme and policies, as rule 8 of the 2011 sensitive personal data rules requires.

Annex 3: Sub-processors

TrueAxis keeps this list current. It gives 30 days' notice of changes (section 5.4).

Category Sub-processor Location of processing What it does When it is used
Hosting Amazon Web Services (AWS), Mumbai region (ap-south-1). Later, another hosting provider in India, to be named with notice India Servers, database, document storage, backups Always
DNS Cloudflare Global network Points web addresses to TrueAxis's servers. Customer data does not pass through it Always
Email delivery Microsoft 365 (Microsoft Corporation) Microsoft's data centres for TrueAxis's Microsoft 365 tenant Sends emails the customer triggers, such as invoices to its customers or reminders, and system emails When emails are sent
Payment gateways Razorpay, Stripe, PayU, PhonePe India, and other countries for Stripe Take subscription payments from the customer to TrueAxis only. They see the payer's details, not the customer's books Only when the customer pays TrueAxis
AI model provider Anthropic PBC United States Reads documents and suggests classifications or drafts. Under its commercial terms it does not train on this data and keeps it only for a limited period Only when the customer uses TrueAxis's managed AI key. Not used when the customer uses its own key

Annex 4: Where each legal requirement is met

Requirement Section of this DPA
GDPR / UK GDPR Art. 28(3): subject matter, duration, nature, purpose, data types, data subjects Annex 1
Art. 28(3)(a): documented instructions, including transfers 5.1, 8
Art. 28(3)(b): confidentiality 5.2
Art. 28(3)(c): Art. 32 security 5.3, Annex 2
Art. 28(3)(d) and 28(2), 28(4): sub-processors 5.4, Annex 3
Art. 28(3)(e): help with data subject rights 5.5
Art. 28(3)(f): help with Arts. 32–36 5.3, 5.6, 5.7
Art. 28(3)(g): delete or return at the end 6
Art. 28(3)(h): information and audits; telling the controller about unlawful instructions 7, 5.1
Art. 33(2): processor tells the controller about a breach 5.6
Arts. 44–46: transfers 8
DPDP Act s.8(2): processor only under a valid contract 1, whole DPA
DPDP Act s.8(1): Data Fiduciary stays responsible 4
DPDP Act s.8(5) and Rules r.6(1)(f): security, with contract provision 5.3, Annex 2
DPDP Act s.8(6) and Rules r.7: breach intimation 5.6
DPDP Act s.8(7)(b): Data Fiduciary causes the processor to erase 6
DPDP Rules r.8(3): 1-year log retention, including by processor 6.2, Annex 2
DPDP Act s.16 and Rules r.15: transfers outside India 8.4
IT Act s.43A and SPDI Rules r.8: reasonable security practices 5.3, Annex 2
CERT-In directions (28 April 2022): 6-hour reporting, 180-day logs 5.6, 6.2
ZuperbaseZuperbase

Accounting that keeps your books clean from day one. Zuperbase is a product of TrueAxis Private Limited.

Contact: support@zuperbase.co

Product

  • Features
  • For firms
  • Security
  • About
  • Contact
  • Sign in

Legal

  • Terms
  • Privacy
  • Cookies
  • Data processing

© TrueAxis Private Limited