Privacy Policy — Facturette
Version 1.0 — effective 2026-08-07 This is an English translation provided for information. The French version of this policy is the only authoritative text.
1. Who we are
Facturette is a Shopify app published by:
| Publisher | Alexandre TRAN (EI) (Entrepreneur individuel) |
| French company number (SIREN) | 833695190 |
| Registered address | 62 Avenue Edouard Millaud, 69290, Craponne, France |
| Data protection contact | [email protected] |
| Website | https://facturette.minhan-tran.fr |
Facturette automatically generates Factur-X invoices (PDF/A-3 + EN 16931 CII XML) compliant with French law and, within the merchant's monthly plan allowance, files B2B invoices to the accredited e-invoicing platform (Plateforme Agréée).
2. Our role: processor, not controller
The merchant operating the Shopify store is the data controller for their customers' data. Facturette acts solely as a processor under Article 28 GDPR: we process personal data only on the merchant's documented instructions, expressed by installing the app and configuring it.
We never use the merchant's customer data for our own purposes — no marketing, no profiling, no resale, no model training, no commercial analytics.
The terms of this processing are set out in the Data Processing Agreement, provided to the merchant on request, which forms part of the contract entered into at installation.
3. What we process, and why
3.1 Merchant and store data
| Data | Purpose | Legal basis |
|---|---|---|
*.myshopify.com domain |
Identify the store (multi-tenant isolation) | Performance of contract |
| Admin API access token | Read orders to produce the invoice | Performance of contract |
| Merchant legal identity: legal name, SIREN/SIRET, VAT number, address | Mandatory invoice particulars, seller side | Merchant's legal obligation |
| Numbering prefixes and format, legal footer text | Invoice configuration | Performance of contract |
| Subscription tier (free / paid) | Billing the app through Shopify | Performance of contract |
The access token is encrypted at rest (ASP.NET Core Data Protection, with keys persisted in the database rather than on the instance disk).
3.2 The merchant's customers' data
We request access to three protected fields, and only three:
| Field | Why it is indispensable |
|---|---|
| Name (first, last) | Buyer identity — a mandatory particular of a French invoice (Code de commerce art. L441-9; CGI Annex II art. 242 nonies A). An invoice without the buyer's identity is legally void. |
| Address (lines, postcode, city, country) | Billing address — mandatory; it also determines VAT territoriality (domestic, intra-EU or export). |
| The consumer buyer's electronic address on the invoice (BT-49, required by the French rule BR-FR-12): it is the only electronic address a consumer has. For a business buyer the SIREN serves as the address and the email is not used on the invoice. For a B2B invoice or credit note filed with the accredited platform, Facturette sends the buyer a "deposit notification" (number, date, amount including VAT, seller name, platform name): it states facts only, attaches no invoice and contains no link. The address is read from Shopify at send time and is neither stored nor logged. For a B2C invoice, Facturette sends the buyer no email. The invoice download link asks the buyer to confirm their order's email address: Facturette keeps only a fingerprint of it (a SHA-256 hash), never the address itself, next to the invoice file and deleted with it. |
Phone number is deliberately not requested. A French invoice does not need it. Requesting a field we have no use for would breach the data minimisation principle.
We also process the order data needed for the calculation: line items, quantities, prices, discounts, shipping, VAT rates and amounts, currency, payment date, the Shopify order and customer identifiers, and where applicable the business customer's SIREN (entered by the merchant or the customer, used to route B2B versus B2C).
3.3 What we do not store
The raw body of a Shopify webhook is never retained. An orders/paid body carries the
customer's name, address and email; we store only a SHA-256 digest, which is enough to guarantee
idempotency (never invoicing the same order twice) while retaining no personal data at all.
No customer personal data appears in our application logs.
4. Retention periods
Our retention model is deliberately short: the merchant, not Facturette, holds the long-term archive. The ten-year invoice retention obligation is theirs, and we do not duplicate it.
| Data | Period |
|---|---|
| Invoice file (PDF/A-3 + XML) | 30 days after issue, then automatically deleted. This window lets the merchant download their invoices; Facturette never sends the invoice by e-mail. Exception: a document whose filing with the approved platform was refused because the buyer is not yet registered in the directory, or whose filing is still under way, is kept for up to 90 days after issue, so that it can still be filed once the buyer has registered. |
| Fingerprint of the buyer's email address | Deleted with the invoice file it protects (the same 30 days, or 90 days in the exception above) |
| Personal-data-free invoice metadata (number, order identifier, amounts per VAT rate, XML digest, timestamps) | Duration of the installation |
| Merchant legal identity and settings | Duration of the installation |
| Webhook idempotency ledger (digests, no personal data) | Duration of the installation |
| Access token | Erased immediately on uninstall (Shopify revokes it) |
| All store data | Erased on receipt of the shop/redact webhook, which Shopify sends 48h after uninstall |
The merchant downloads and keeps their invoices themselves, within 30 days of issue. The PDF and the XML are available from the app's "Invoices" page during that window, then deleted. Facturette never emails the invoice and attaches no copy to the Shopify order; the link published on the order, which the merchant may insert into a Shopify notification, expires with the document. For a B2B invoice or credit note filed with an approved platform (Plateforme Agréée), Facturette sends the merchant and the buyer a "deposit notification" when the platform has received the document and, for SUPER PDP, when it has accepted it: its purpose is to inform the buyer that the invoice was filed; no invoice is attached and it contains no link. The buyer's email address is neither stored nor logged: it is read from Shopify at send time. A B2B invoice filed with an approved platform is also held by that platform, under its own terms, which does not release the merchant from their retention obligation.
5. Where data is hosted
Data is stored in Switzerland, a country whose level of protection the European Commission has recognised as adequate. Requests transit Cloudflare's global network (a US company) without being stored there; emails are delivered by the provider named below, from the location shown:
| Sub-processor | Role | Location |
|---|---|---|
| Oracle Cloud Infrastructure | Database (Autonomous Database) and application server | Switzerland — eu-zurich-1 region |
| Cloudflare | TLS termination, network protection, request routing | Global network; transit only, no invoice data stored |
| OVH SAS | Delivery of emails addressed to the merchant (welcome, setup reminders, refused-filing alerts, deposit notifications) and of "deposit notifications" addressed to the buyer of a B2B invoice; no invoice is attached | Union européenne (France) |
| SUPER PDP | Filing B2B invoices to the accredited platform, if the merchant chose this platform | France |
| iopole | Filing B2B invoices to the accredited platform, if the merchant chose this platform | France |
Switzerland is not a member of the European Union or the EEA, so hosting there is a transfer to a third country within the meaning of Chapter V of the GDPR. That transfer relies on an adequacy decision of the European Commission (Art. 45 GDPR), adopted on 15 January 2024 under the GDPR: personal data may be transferred from the EU and the EEA to Switzerland without additional safeguards. Standard Contractual Clauses are therefore not required.
Cloudflare, a US company, acts only as transit, without storage. That transit relies on the European Commission's adequacy decision of 10 July 2023 on the EU–US Data Privacy Framework (Data Privacy Framework), provided the importer is certified under it, and otherwise on Standard Contractual Clauses (Art. 46 GDPR). The email provider is located in the European Union or the EEA, in a country covered by an adequacy decision, or bases its transfer on a Chapter V GDPR mechanism (Standard Contractual Clauses or the Data Privacy Framework) shown in the table above.
An adequacy decision is a living instrument, reviewed periodically by the Commission. Should it be suspended or repealed, or should the hosting location change, this policy will be updated and merchants notified before the change takes effect.
The accredited platform case
For B2B invoices only, the invoice is transmitted to the merchant's accredited platform using the merchant's own credentials. This transmission is the merchant's legal obligation under French B2B e-invoicing rules, not a transfer of data for our benefit. Facturette holds no account on the platform and is not a party to the tax filing.
One platform at a time, and the merchant picks it. Facturette can talk to SUPER PDP and to iopole; a store connects one of them, and invoices are never transmitted to the other. Changing platform replaces the connection, so at any moment only one of these two sub-processors receives anything at all for a given store.
Filing is not reserved to a paid plan. Every plan files; what differs is how many filings a month. Past that number the invoice is still issued and kept as usual — only its transmission waits for the merchant to change plan.
6. Security
Measures actually implemented:
- Encryption in transit: HTTPS/TLS for all public access; mTLS (Oracle wallet) to the database; HTTPS to the Shopify API and to the accredited platform's API. The application service is not publicly exposed in cleartext — it listens only on the loopback interface, behind Cloudflare [TO CONFIRM: production binding verified as loopback-only].
- Encryption at rest: Transparent Data Encryption on the Oracle Autonomous Database, backups included; access tokens carry a second, application-level layer of encryption.
- Minimisation: three protected fields requested, phone excluded; webhook bodies never retained; no personal data in logs.
- Tenant isolation: every request is scoped to the store derived from a verified session token or an HMAC-validated webhook — never from a client-supplied parameter.
- Environment separation: development and production data live in distinct database schemas under distinct credentials.
- Secrets: never in source control; environment variables in production.
Our incident procedure is described in the security incident response policy, available on request.
7. Data subject rights
The merchant's customers exercise their rights (access, rectification, erasure, restriction, objection, portability) with the merchant, who is the controller.
We assist the merchant through the Shopify mechanisms provided for this purpose:
customers/data_request— a request for access to a customer's data. We record the request and the number of invoice documents still held for that customer's orders. Nothing is returned automatically: the merchant downloads those documents from the "Invoices" page while they are retained (§4), and we assist on written request.customers/redact— the customer's personal data is deleted. Given the 30-day retention window (§4), there is usually nothing left to erase by the time the request arrives.shop/redact— all store data is erased after uninstall.
Questions about this processing: [email protected]. You may also lodge a complaint with the French supervisory authority, the CNIL (www.cnil.fr).
8. Cookies and trackers
Facturette's admin interface renders inside the Shopify admin and uses no analytics, advertising or profiling cookies. Authentication relies on Shopify session tokens, sent with each request and not stored in a cookie.
9. Changes
Any material change to this policy is notified to installed merchants before it takes effect. The version date appears at the top of this document.