Data Processing Addendum
Last updated November 12, 2026
This Data Processing Addendum (“DPA”) forms part of the Terms of Service between you (the “Customer”) and Zesxai LLC, a Wyoming limited liability company, 1021 E Lincolnway #11080, Cheyenne, WY 82001, United States (“Processor”), and applies where we process personal data on your behalf in providing Axzura.
1. Roles
For personal data you put into your workspace — about your staff, clients and their contacts — you are the controller and we are your processor. For your own account and billing data, we are the controller, as described in the Privacy Policy.
2. Scope of processing
- Subject matter and duration: providing Axzura for as long as your workspace exists.
- Nature and purpose: storing, organising, retrieving, analysing with AI and transmitting data so the features you use work.
- Data subjects: your users, staff, clients, client contacts, and people who sign documents you send.
- Categories of data: contact details, business and contract information, invoice and payment records, employment records (attendance, leave, salary), document contents, e-signature evidence (name, signature, IP address, browser, time), and audio you choose to send to the voice assistant or meeting capture.
- You should not use Axzura for special-category data beyond what ordinary employment administration requires.
3. Our obligations
- We process personal data only on your documented instructions, which are these terms and your use of the product.
- Everyone we authorise to process it is bound by confidentiality.
- We apply appropriate technical and organisational measures, including encryption in transit and at rest, database-level separation of workspaces (row-level security), role-based access inside a workspace, and restricted administrative access.
- We help you respond to data subject requests; most can be handled directly in the product (export, edit, delete).
- We notify you without undue delay after becoming aware of a personal data breach affecting your data.
- We assist with data protection impact assessments and consultations where the law requires it, taking into account the information available to us.
- We do not use your workspace data to train AI models, and we do not sell it.
4. Subprocessors
You authorise us to engage the subprocessors listed below and on our subprocessors page. Optional subprocessors are only engaged when you use the matching feature, and pilot subprocessors only for a workspace that has the matching pilot feature switched on. We impose data protection terms on each subprocessor that are no less protective than this DPA, and remain responsible for their performance. We will update the list before adding a new subprocessor of customer personal data; if you object on reasonable data-protection grounds, tell us and, if we cannot address it, you may terminate the affected service.
Always involved
| Processor | Purpose | Data |
|---|---|---|
| Supabase | Database, authentication and file storage; stores conversations with Relay, the support assistant on this website | All workspace data, account details and uploaded files; Relay messages and any email you give Relay |
| OpenAI | AI answers, document reading, embeddings, transcription, realtime voice and images; Relay's answers on this website | The text, audio or files needed to answer a request, and messages sent to Relay; not used for model training |
| Vercel | Application and website hosting, scheduled jobs | Requests passing through the app and website, server logs |
| Resend | Transactional email delivery, including passing a Relay conversation to the team when you ask for a person | Recipient addresses and the content of system emails (reminders, invitations, invoices, signing requests, support handoffs) |
| Dodo Payments | Merchant of record for Axzura subscriptions; optional client payments | Billing name, email, country and payment details (held by Dodo, never by us) |
| Sentry | Error monitoring | Technical error reports, which may include identifiers and request metadata |
| PostHog | Product analytics inside the app | Anonymised usage events with identifiers and counts; never document or message contents |
Only when you use the matching feature
| Processor | Purpose | Data |
|---|---|---|
| Sign in with Google; Google Calendar for call booking when connectedWhen you sign in with Google or connect Google Calendar for booking | Your Google account email and name; free/busy times and the booked calls Axzura adds to your calendar | |
| Stripe | Client payment links on invoicesWhen you connect your own Stripe account to take invoice payments | Invoice amount and reference; your client's payment is handled by Stripe |
| Crisp | Live chat with a person inside the appInside the app only, when live chat is offered and you allow support cookies. The website's Relay assistant does not use Crisp | Messages you send to support and the email you give |
Only for pilot features, not generally available
These features are not part of the product most workspaces see. A processor here is involved only for a workspace that has the matching pilot switched on; for every other workspace it receives nothing.
| Processor | Purpose | Data |
|---|---|---|
| Google (Gmail) | Reading and sending mail from a connected Gmail inboxOnly when the Mail pilot is switched on for your workspace and you connect Gmail | Mail you ask Axzura to read or send |
| Twilio | Phone calls and SMSOnly when the calling or SMS pilot is switched on for your workspace | Phone numbers, call audio and message content |
| Fly.io | Voice call relayOnly when the calling pilot is switched on for your workspace | Call audio in transit |
| Apollo | Contact data syncOnly when the Apollo pilot is switched on for your workspace and you connect your Apollo account | Contacts and companies you choose to sync |
| Meta (WhatsApp) | WhatsApp messagingOnly when the WhatsApp pilot is switched on for your workspace | Messages and phone numbers in conversations you route to Axzura |
| Slack | Slack messagingOnly when the Slack pilot is switched on for your workspace and you connect Slack | Messages in channels you connect |
| Telegram | Telegram messagingOnly when the Telegram pilot is switched on for your workspace and you connect Telegram | Messages in chats you connect |
5. International transfers
We and most subprocessors process data in the United States. For transfers of personal data from the EU/EEA, the UK or Switzerland, the parties rely on the European Commission's Standard Contractual Clauses (Module 2, controller to processor, and Module 3 where applicable), with the UK International Data Transfer Addendum, which are incorporated by reference, or on another valid transfer mechanism.
6. Deletion and return
You can export your workspace at any time. When you delete your workspace it is locked at once and, unless its owner restores it within 14 days, we then delete the personal data in it, including stored files, except where the law requires us to keep it.
7. Audits
On reasonable written request, we will provide information necessary to demonstrate compliance with this DPA. Any audit beyond that is by agreement, at reasonable notice, and at your cost.
8. Contact
Data protection questions: privacy@axzura.io. If you need a countersigned copy of this DPA, email us.