Hypervoid: Invoice
Privacy policyTerms of serviceData processing addendum

Data processing addendum

Effective 16 October 2026 · Version 1.0-draft

Draft. Bracketed items and placeholder addresses are not final yet. They will be replaced with the details of the legal entity operating the app, and the addendum reviewed by counsel, before publication.

1. Parties and scope

This addendum ("DPA") forms part of the Terms of service between the merchant ("Controller") and [LEGAL ENTITY NAME] ("Processor") for Hypervoid: Invoice. It applies to personal data of the Controller's customers that the Processor handles to provide the app ("Customer Personal Data"). It is accepted when the Controller installs or uses the app. If this DPA conflicts with the terms, this DPA prevails for Customer Personal Data.

2. Details of processing (Annex I)

Subject matterGenerating, storing, printing, and sharing commercial documents from the Controller's Shopify data
DurationWhile the app is installed, plus the deletion periods in section 9
Nature and purposeRetrieval from Shopify, rendering into documents, storage of issued documents, customer download links, and handling Shopify privacy requests
Data subjectsThe Controller's customers and recipients of its documents
Categories of dataName, email address, phone number, billing and shipping address, company name and tax identifier, order contents and totals, order notes and line-item properties, Shopify customer and order identifiers
Special categoriesNone intended. The Controller must not place special-category data in order notes or templates.
FrequencyContinuous, triggered by the Controller's actions, automations and Shopify webhooks

3. Processor obligations

  • Process Customer Personal Data only on the Controller's documented instructions: these terms, the app configuration and settings the Controller chooses, and written requests. The Processor tells the Controller if it believes an instruction breaks data protection law.
  • Never sell or share Customer Personal Data, use it for its own purposes (including marketing, profiling or model training), or combine it with other data except as allowed for service providers under US state laws.
  • Ensure that personnel with access are bound by confidentiality and trained.
  • Implement the technical and organisational measures in Annex II.
  • Assist the Controller with data subject requests, data protection impact assessments and prior consultations, taking into account the nature of the processing.
  • Make available information needed to demonstrate compliance and allow audits as described in section 8.

4. Sub-processors

The Controller gives general authorisation to the sub-processors below. The Processor imposes data protection terms on each that are no less protective than this DPA and stays responsible for their performance. The Processor will give at least 30 days' notice, in the app and by email, before adding or replacing a sub-processor that receives Customer Personal Data. The Controller may object on reasonable data protection grounds; if no solution is found, the Controller may stop using the app and uninstall it.

Sub-processorPurposeLocation
Vercel Inc.Application hosting and compute; application logsUnited States (iad1)
Supabase Inc.Database, file storage (PDFs), job queuesUnited States (us-east-1)
Shopify Inc. and affiliatesPlatform on which the app runs; billing of app chargesGlobal

5. International transfers

Customer Personal Data is hosted in the United States. For transfers from the EEA, the parties incorporate the Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), Module Two (controller to processor), with: clause 7 docking clause included; clause 9 option 2 (general authorisation, 30 days' notice); clause 11 optional language omitted; clauses 17 and 18 governed by and resolved in [EU MEMBER STATE]; Annex I as section 2 above; Annex II as below; Annex III as section 4. For the UK, the International Data Transfer Addendum issued by the ICO applies; for Switzerland, the SCCs apply with references read as the Swiss FADP.

6. Data subject requests and Shopify privacy webhooks

Shopify sends privacy requests to the Processor automatically. The Processor handles customers/data_request by making a report of the documents it holds for that customer available to the Controller in the app for 7 days, customers/redact by deleting that customer's data (subject to section 9), and shop/redact by deleting all data for the shop. The target completion time is 24 hours and never more than 30 days. Requests the Processor receives directly are passed to the Controller without undue delay.

7. Personal data breaches

The Processor notifies the Controller (and Shopify) without undue delay, and within 72 hours, after becoming aware of a breach affecting Customer Personal Data. The notice describes the nature of the breach, the data and approximate number of people affected, likely consequences, and measures taken or proposed, and is updated as more is known. The Controller remains responsible for notifying authorities and individuals where required.

8. Audits

On written request, no more than once a year (or after a breach or a regulator's request), the Processor provides a written description of its security measures, its data inventory and the results of recent security assessments. Where that is not sufficient, an on-site or remote audit may be agreed with reasonable notice, at the Controller's cost, under confidentiality.

9. Deletion and return

The Controller can download its documents at any time. On uninstall, all Customer Personal Data is deleted when Shopify sends the shop deletion request (48 hours after uninstall); if that request never arrives, it is deleted 30 days after uninstall. Backups roll off within 7 days; if a backup is restored, completed deletions are re-applied.

Customer deletion requests and legal retention. The Controller chooses in the app (Settings, Data and privacy) what happens to issued invoices, credit notes and quotes when a customer asks to be erased. The default setting is "keep issued invoices required by law": the Controller instructs the Processor to keep those PDFs, which show the customer details printed on them, until the Controller's retention period for stored PDFs ends, because tax record-keeping law usually requires the Controller to keep issued invoices. The Processor then deletes them. Until then they are not available through customer links, are never regenerated from live data and are available only to the Controller. Issued documents already past the retention period are deleted straight away. With the "delete all" setting, every PDF for the customer is deleted straight away. In both cases all other stored documents for the customer are deleted, download links are revoked and the customer identifier is removed; document numbers, types, dates and totals are kept so numbering has no gaps. The Controller is responsible for choosing the setting that matches its legal obligations.

Annex II: technical and organisational measures

  • Encryption: TLS 1.2+ in transit with HSTS; AES-256 at rest for database, storage and backups; AES-256-GCM application encryption for access tokens and privacy-request contents with rotating keys.
  • Tenant isolation: every record keyed by shop, all queries scoped by shop, database row-level security denying public access, private storage buckets, automated cross-tenant tests.
  • Minimisation: order data is not mirrored; only fields used by a template are fetched; queues and logs carry identifiers only, and log entries are scrubbed of email addresses and phone numbers; expired download links deleted.
  • Access control: single sign-on and MFA for all staff tools; least-privilege roles; production access for named engineers only; quarterly access reviews; access removed within 24 hours of offboarding.
  • Logging: access log of document renders, prints, downloads, download-link use and privacy-request completion, retained 12 months.
  • Application security: verified Shopify session tokens and webhook signatures; sandboxed template rendering with no network access and JavaScript disabled; 60-second signed storage URLs behind revocable download tokens; keyed signatures on per-order links; rate limiting on public endpoints; automated tests in CI.
  • Resilience: managed backups with point-in-time recovery; health checks and structured error logs; documented incident response with twice-yearly exercises.
  • Separation of environments: separate Shopify apps, databases and hosting environments; production data never copied to lower environments.

Contact

[LEGAL ENTITY NAME], [REGISTERED ADDRESS] · privacy@invoicely.example

[LEGAL ENTITY NAME] · [REGISTERED ADDRESS] · privacy@invoicely.example

Hypervoid: Invoice is an independent app for Shopify merchants. It is not made by or affiliated with Shopify Inc.