Version 2026-08-03-v1
Subprocessor Register
Last updated: 3 August 2026
This register identifies provider categories used to deliver, secure, support, and bill for HisaBooks. It should be read with the Privacy Policy, Security Overview, and any customer data-processing terms.
1. What a subprocessor is
A subprocessor is a third-party provider engaged by AARK to process Customer Data or personal data so HisaBooks can provide the Service. Some providers process data as independent controllers for their own legal, security, fraud, billing, store, or platform purposes. Those roles are noted where relevant.
2. Current register
| Provider or category | Purpose | Data handled | Status and notes |
|---|---|---|---|
| Stripe | Checkout, recurring subscriptions, payment status, hosted invoices, payment-method management, fraud prevention, disputes, and refunds. | Billing contact, payment status, subscription identifiers, invoice and checkout references. Complete card numbers and CVC are handled by Stripe. | Confirmed integration. Stripe may act as payment processor and, for certain payment, fraud, dispute, and legal activities, an independent provider. |
| Expo push notification service | Routes mobile push notifications where the user grants permission. | Expo push token, notification payload, app and device routing metadata. | Confirmed mobile integration. Applies only when mobile notifications are enabled. |
| Google Android platform services | Android app distribution, push delivery, operating-system services, and store compliance. | Device, install, account, push routing, diagnostic, and store metadata handled under Google policies. | Confirmed for planned Android release and Google Play compliance. |
| Production hosting, database, and backup provider | Hosts the web application, app API, database, files, logs, queue jobs, and backups. | Workspace data, account data, uploaded files, logs, backup contents, and security metadata. | Active provider category. The exact live provider and locations are maintained in AARK's production vendor register and can be shared with customers where relevant. |
| Transactional email provider or configured SMTP service | Sends verification, password reset, billing, privacy request, security, and workflow emails. | Email address, name, company code where needed, message content, and delivery metadata. | Active provider category. The active sender, domain-authentication, retention, and access evidence are maintained by AARK. |
| Domain, DNS, CDN, and security-edge providers | Routes traffic, protects availability, terminates TLS, provides DNS, or performs edge security and anti-abuse checks where configured. | IP address, request metadata, TLS/security logs, DNS records, and anti-abuse signals. | Active provider category. Only providers enabled for the live service are treated as active for this row. |
| Apple platform services, if iOS is released | App distribution, push delivery, operating-system services, and store compliance. | Device, install, account, push routing, diagnostic, and store metadata handled under Apple policies. | Future/conditional. Applies only if an iOS release proceeds. |
| Professional advisers and support contractors | Legal, accounting, tax, security, incident response, customer support, and audit assistance. | Limited account, billing, support, security, privacy-request, or workspace excerpts needed for the engagement. | Conditional. Access must be need-to-know, approved, time-limited, and covered by confidentiality or data-processing obligations. |
3. Customer-selected recipients and integrations
When a Customer or authorised user sends an invoice, exports a report, shares a public link, downloads a PDF, prints a document, imports data, or connects a future integration, that recipient or integration is chosen by the Customer. Customer-selected recipients are not subprocessors engaged by AARK for all customers, but they may process data at the Customer's direction.
4. Provider changes
We may add or replace providers to operate, secure, support, or improve the Service. Material production changes should be recorded on this page before or promptly after the change, depending on urgency. Customers with a signed data-processing agreement may receive additional notice rights if their agreement provides them.
Customers may raise a good-faith data-protection objection to a material provider change. AARK will review the concern and decide whether it can be addressed through information, safeguards, alternative configuration, suspension of the affected feature, cancellation of the affected service, or another commercially reasonable path.
A provider must not be added for behavioural advertising, session replay, analytics, AI processing, or broad support access until the Privacy Policy, Cookie Notice, data inventory, consent flow, and customer notice obligations are reviewed.
5. Contact
Send subprocessor questions or objections to support@hisabooks.com. Include your company code and the provider or processing activity you are asking about.