Data Processing Agreement
This agreement applies when Submoving processes personal data on behalf of a customer, mostly the data of the customer’s own clients held in its Stripe accounts. It is part of the Terms of Service and needs no signature: accepting the Terms accepts it.
- You (the customer) are the controller; Submoving is the processor.
- We process your Stripe data only to provide the features you use, on your instructions.
- Security measures, subprocessors and breach rules are listed below.
- When you leave, we delete your data within 30 days.
1. Parties and scope
This agreement is between the business that accepted the Terms (the “Customer”, controller) and , registered under , with its registered office at , (“Submoving”, “we”, “us”) (the “Processor”). It applies to personal data the Processor processes for the Customer while providing Submoving, and follows Article 28 of the EU General Data Protection Regulation (GDPR).
The Processor’s representative in the European Union (GDPR art. 27) is Enzo Lanne, 365 chemin du clos de digne, 83440 Fayence, France, contact@lannetech.com.
2. The processing
| Subject matter | Providing Submoving: dry-runs, migrations, backups and restores, analytics, search, dispute management and alerts. |
|---|---|
| Duration | As long as the Customer uses the service, then until deletion under section 9. |
| Nature | Reading data from the Customer’s Stripe accounts, storing encrypted backups, computing statistics, and writing to Stripe when the Customer launches an action. |
| Data subjects | The Customer’s own customers and contacts present in its Stripe accounts. |
| Personal data | Names, email addresses, phone numbers, billing addresses, Stripe customer and subscription IDs, plans, amounts and billing dates, payment status, dispute details and evidence. Full card numbers are never accessible to the Processor: they stay with Stripe. |
| Special categories | None intended. The Customer should not store such data in Stripe fields. |
3. Instructions
The Processor processes the data only on the Customer’s documented instructions: these terms, and the actions taken in the app by the Customer’s workspace. It tells the Customer if it believes an instruction breaks data protection law. It doesn’t use the data for its own purposes.
4. Confidentiality
Everyone at the Processor who can access the data is bound by confidentiality and accesses it only when needed to provide or support the service.
5. Security
The Processor applies the technical and organisational measures in Annex A and keeps them up to date with the state of the art.
6. Subprocessors
The Customer authorises the subprocessors in Annex B. The Processor gives them the same data protection obligations as in this agreement and remains responsible for them. It informs the Customer at least 30 days before adding or replacing one; the Customer may object on reasonable grounds and, if no solution is found, end the service with a refund of prepaid fees for the remaining period.
7. Assistance
The Processor helps the Customer, as far as it reasonably can, to answer requests from data subjects, to carry out data protection impact assessments, and to meet its security obligations. Many requests can be handled by the Customer directly in Stripe or in Submoving.
8. Personal data breaches
The Processor notifies the Customer without undue delay, and within 48 hours of becoming aware of a breach affecting the Customer’s data, with what is known: what happened, the data and people concerned, likely consequences and the measures taken. It shares updates as it learns more.
9. Return and deletion
The Customer can download its backups at any time. When the Customer disconnects a Stripe account or closes its workspace, the related data (keys, backups, off-server copies) is deleted within 30 days, unless the law requires keeping it.
10. Audits
The Processor makes available the information needed to show compliance with this agreement, and allows audits by the Customer or an independent auditor it appoints, with 30 days’ notice, at most once a year unless a breach occurred, at the Customer’s cost and without access to other customers’ data.
11. International transfers
Personal data is transferred outside the European Economic Area only with appropriate safeguards, such as the European Commission’s Standard Contractual Clauses or an adequacy decision.
12. General
Liability under this agreement follows the limits in the Terms of Service, except where the law forbids it. If this agreement and the Terms conflict on data protection, this agreement prevails. It is governed by the law of .
Annex A — Security measures
- Encryption at rest: Stripe API keys and backups are encrypted with AES-256-GCM, using separate derived keys; the master key is kept outside the database and can be rotated.
- Encryption in transit: HTTPS (TLS) for all traffic to the app and to Stripe.
- Off-server copies of backups are encrypted before upload.
- Access control: sign-in with password (hashed with scrypt); sessions stored as hashes and limited to 30 days; owner and member roles; destructive actions limited to owners and confirmed by typing.
- Least access: restricted Stripe keys recommended; write access used only for actions the Customer launches.
- Safety by design: a backup before every migration and restore; pilot runs, an emergency stop and rollback for migrations.
- Retention: backups kept only for the period the Customer chooses; deleted on disconnection.
- Monitoring: failed backups, broken keys and failed migrations raise alerts.
Annex B — Subprocessors
| Subprocessor | Purpose |
|---|---|
| Hosting the application and database | |
| Encrypted off-server copies of backups | |
| Sending account and alert emails |
Stripe is not a subprocessor of Submoving for this data: it is the Customer’s own provider, which the Customer instructs Submoving to connect to.