Privacy policy
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 text reviewed by counsel, before publication.
1. Who we are and what this policy covers
Hypervoid: Invoice ("the app", "we", "us") is a Shopify app operated by [LEGAL ENTITY NAME], [REGISTERED ADDRESS] (registration [COMPANY REGISTRATION NUMBER]). Merchants use it to design templates and turn their orders, draft orders and refunds into invoices, packing slips, quotes, credit notes and similar documents, which they can print, download as PDF and share through download links.
This policy covers:
- Merchants who install the app, and their staff who use it;
- Customers of merchants whose details appear on documents. For that data the merchant is the controller and we are a processor (service provider) acting on the merchant's instructions under our Data Processing Addendum.
2. Data we handle
| Data | Source | Where it is kept | Why |
|---|---|---|---|
| Shop details: domain, name, contact email, currency, money format, time zone, locale, Shopify plan | Shopify Admin API | Our database | Running the app, rendering documents, service messages |
| Merchant content: templates, styles, settings, logos and assets, business details (legal name, tax number, address) | The merchant | Our database and private file storage | Producing the merchant’s documents |
| Staff user identifier (numeric Shopify user id, no name or email) | Shopify session token | Audit log | Security and accountability |
| Order data: line items, prices, taxes, discounts, shipping, payment status | Shopify Admin API, when a document is made | Not copied to our database except a minimal totals snapshot for issued documents; inside generated PDFs | Rendering; an immutable record of issued invoices and credit notes |
| Customer name, email, phone, billing and shipping address; order notes, line-item properties, company name and tax ID when a template uses them | Shopify Admin API, when a document is made | Inside generated PDFs (private storage) | Bill-to and ship-to details |
| Customer and order identifiers (Shopify IDs) | Shopify webhooks and Admin API | Our database | Linking documents to orders; privacy requests |
| Contents of privacy requests (customer email/phone, order IDs) | Shopify compliance webhooks | Encrypted in our database; deleted 30 days after completion | Fulfilling access and deletion requests |
| IP address of people opening a download link | HTTP request | Keyed hash only, in the audit log and rate limiter | Abuse prevention |
| Customer data-request reports (document list, links to stored PDFs) | Compiled by us when Shopify forwards a customer access request | Private file storage; deleted after 7 days | Giving the merchant the data to send to the customer |
What we deliberately do not do
- We do not keep a copy of merchants' orders. Order data is fetched from Shopify each time a document is made; webhook payloads are not stored.
- We fetch only the fields a template uses: a template without addresses never fetches addresses.
- Packing slips, pick lists and other non-legal documents are not archived by default. Bulk print files are deleted after 7 days.
- We do not sell personal data, share it for cross-context behavioural advertising, use it for marketing or profiling, or use it to train machine-learning models.
- We make no automated decisions with legal or similarly significant effects.
- We set no advertising or analytics cookies. The embedded app signs in with Shopify session tokens, not cookies.
3. Protected customer data and security
Shopify classifies customer names, emails, phone numbers and addresses as protected customer data. The app requests these fields only because they are printed on invoices, packing slips, quotes and credit notes. If a field has not been approved, it is left blank on documents. Safeguards:
- Encryption in transit (TLS 1.2+) and at rest (AES-256), including encrypted backups;
- Additional AES-256-GCM encryption of Shopify access tokens and of privacy-request contents;
- Strict tenant isolation: every record is keyed by shop, and cross-shop access is blocked and tested;
- Separate development, staging and production environments; production data is never copied to test systems;
- Production access limited to named engineers, with single sign-on, multi-factor authentication and quarterly access reviews;
- An access log of document renders, prints, downloads, download-link use and privacy-request handling;
- Application logs and job queues that carry identifiers only; log entries are additionally scrubbed of email addresses and phone numbers before they are written;
- A sandboxed template renderer with no network access, so templates cannot send data elsewhere;
- An incident response process (section 10).
4. Purposes and legal bases
- Providing the service to merchants (contract): rendering, storing, printing, sharing and numbering documents.
- Processing customer data for merchants: the merchant decides the legal basis (typically performing the sale and legal duties to issue invoices). We act only on the merchant's documented instructions.
- Security, abuse prevention and audit (legitimate interests; Shopify's protected customer data requirements).
- Billing: app plans are charged by Shopify. We receive plan and subscription status from Shopify, never card details.
- Service messages to merchants, such as usage and security notices (contract / legitimate interests).
- Legal compliance, such as responding to lawful requests.
5. Documents shared with customers
We do not contact a merchant's customers. Customers get documents through download links that the merchant adds to Shopify's own order notifications, or from their Shopify customer account.
6. Sub-processors
Merchants are told at least 30 days before we add a sub-processor that receives customer data, and may object.
| Sub-processor | Purpose | Data | Location |
|---|---|---|---|
| Vercel Inc. | Application hosting and compute; application logs | All data in transit through application functions; scrubbed logs (identifiers only) | United States (iad1) |
| Supabase Inc. | Database, file storage (PDFs), job queues | All stored data, including generated documents | United States (us-east-1) |
| Shopify Inc. and affiliates | Platform on which the app runs; billing of app charges | Data the merchant already holds in Shopify | Global |
7. International transfers
Data is hosted in the United States. For personal data from the EEA, the UK or Switzerland we rely on the European Commission's Standard Contractual Clauses and the UK Addendum, with the safeguards in this policy, as set out in the DPA.
8. Retention
| Data | How long |
|---|---|
| Issued documents (invoices, credit notes, quotes) as PDFs | The merchant’s retention setting, up to the plan maximum (Starter and Growth 3 years; Scale and Unlimited 10 years). Shorter periods can be chosen. This also applies after a customer deletion request unless the merchant chose “delete all” (section 9). |
| Other stored PDFs (for example packing slips) | The same retention setting; deleted straight away on a customer deletion request |
| Document records (number, type, date, minimal totals, neutral file name) | While the app is installed, to keep numbering gap-free |
| Customer data-request reports | 7 days |
| Download links | Until they expire or are revoked (the merchant chooses the expiry, which can be none), then deleted 30 days later; links shown in customer accounts expire after 10 to 20 minutes |
| Bulk print files | 7 days |
| Editor previews | 24 hours |
| Webhook delivery metadata (no contents) | 30 days |
| Privacy-request contents | Deleted 30 days after completion; a record that the request was handled is kept 3 years |
| Audit log | 12 months |
| Application logs (scrubbed, identifiers only) | Our hosting provider’s log retention period, at most 30 days |
| Database backups | 7 days, encrypted; deletions are re-applied if a backup is restored |
| All shop data after uninstall | Deleted when Shopify sends the shop deletion request (48 hours after uninstall). If that request never arrives, a safety net deletes the data 30 days after uninstall |
9. Privacy rights and Shopify privacy requests
Customers of a merchant should contact the merchant, who is the controller. Shopify forwards their requests to us and we act on them:
- Access (
customers/data_request): we compile the documents and stored PDFs we hold for that customer into a report. The merchant can download it in the app (Settings, Data and privacy, Customer data requests) for 7 days. We do not contact the customer directly. - Customer deletion (
customers/redact): we delete the customer's stored PDFs of non-legal documents (such as packing slips), revoke their download links, delete cached bulk files containing their orders, replace file names with neutral ones and remove the customer's identifier from our records. Issued invoices, credit notes and quotes are handled by the merchant's setting. By default ("keep issued invoices required by law"), because tax law usually requires the merchant to keep issued invoices, which show the buyer's name and address, their PDFs are kept until the merchant's retention period ends and are then deleted. Meanwhile they can no longer be opened through customer links or regenerated, and only the merchant can access them. Issued documents older than the retention period are deleted straight away. If the merchant chooses "delete all", every PDF for the customer is deleted straight away. Document numbers, types, dates and totals are always kept so numbering has no gaps. - Shop deletion (
shop/redact): all data for the shop is deleted from our database and file storage.
We aim to complete each request within 24 hours, and always within 30 days.
Merchants and their staff can ask for access, correction, deletion, restriction or portability of their personal data, or object to processing based on legitimate interests, at privacy@invoicely.example. Merchants can download their documents from the app at any time, one by one or with bulk export.
GDPR and UK GDPR
People in the EEA and the UK have the rights above and may complain to their data protection authority. EU representative: [EU ART. 27 REPRESENTATIVE, or a statement that none is required]. UK representative: [UK REPRESENTATIVE, or a statement that none is required].
California (CCPA/CPRA) and other US state laws
For customer data we are a service provider / processor to the merchant. We do not sell or share personal information, do not use sensitive personal information beyond providing the service, and do not combine it with other data except as the law allows service providers. Residents can exercise rights to know, delete and correct, without discrimination; authorised agents may act with proof of authority.
10. Security incidents
Our incident process covers detection, triage within one hour, containment, recovery and a post-incident review. If a personal-data breach affects a merchant, we notify the merchant and Shopify without undue delay and within 72 hours of becoming aware of it. Report security issues to security@invoicely.example.
11. Children
The app is a business tool and is not directed at children.
12. Changes
Changes are posted here with a new effective date. Material changes are announced in the app and by email to the shop contact at least 30 days in advance.
13. Contact
[LEGAL ENTITY NAME], [REGISTERED ADDRESS]
Privacy: privacy@invoicely.example · Support: support@invoicely.example