Data Processing Addendum
Last updated: November 1, 2026
1. Purpose and Scope
This Data Processing Addendum ("DPA") forms part of the Terms of Service between scriptsCanFly by Simon Laube, Bifangstrasse 4, 5610 Wohlen AG, Switzerland ("we", "us", the "Processor") and the Merchant (the "Controller"). It governs the processing of personal data of the Merchant's customers that we process on the Merchant's behalf when operating their shop on the Platform, in accordance with Art. 9 of the Swiss Federal Act on Data Protection (FADP) and, where applicable, Art. 28 of the EU General Data Protection Regulation (GDPR).
For data where we determine purposes and means ourselves (e.g. the Merchant's own account data, platform analytics, invoice numbering, transactional emails we are legally required to send), we act as an independent controller; that processing is described in our Privacy Policy and is not subject to this DPA.
2. Subject Matter of the Processing
- Categories of data subjects: the Merchant’s shop customers, newsletter subscribers (including those the Merchant adds or imports with their agreement), recipients of gift cards, visitors who asked to be told when a product is back in stock, visitors who asked a question about a product, visitors who wrote in the shop’s chat or sent its contact form, and visitors of the shop
- Categories of data: contact details (name, email, phone), billing and delivery addresses, order and subscription data, payment status (never full card details), customer account data, saved carts and wishlists (for guests under a random identifier), product reviews, back-in-stock requests (email address and the product variant), questions about products (the question, the asker’s name and email address, the Merchant’s answer), chat conversations (the messages, the page and language, and the email address and name a visitor leaves), contact form messages (name, email address, phone, subject, message and the Merchant’s reply), gift card recipients (name, email address, the buyer’s message and the delivery day), pictures a buyer uploads with a product the Merchant asks one for (the picture, its file name and a smaller copy, kept while their order is open and deleted 90 days after it was completed, cancelled or refunded, or seven days after the upload when no order took them), aggregated visitor statistics without cookies (page and product views, cart and checkout events, referrer, UTM parameters, device type, under a random identifier kept for one visit only), communication related to orders
- Purpose: hosting and operating the Merchant’s shop — storing orders and customers, sending order-related emails in the Merchant’s name, generating invoices and credit notes, providing customer accounts, the shop’s chat and forms, and the dashboard assistant, which reads the data an answer or a task of the Merchant needs
- Duration: for as long as the Merchant’s shop exists on the Platform, plus statutory retention periods
- Where the Merchant connects their own Brevo account for newsletters: on the Merchant’s instruction we keep the email addresses of the Merchant’s confirmed newsletter subscribers in a list in that account, remove from it whoever leaves the Merchant’s list, take back the unsubscribes, spam complaints and undeliverable addresses Brevo reports, and create and send the Merchant’s newsletters there. Brevo processes this data under the Merchant’s own contract with Brevo and is not our sub-processor; disconnecting Brevo ends our access, and the data in the Brevo account stays with the Merchant
- Copies of the emails sent in the Merchant’s name about orders, shipments, review requests, credit notes, subscription invoices and gift cards, which the Merchant can read in the dashboard, are kept for 12 months after sending and then deleted; emails with sign-in codes or links are not copied
3. Our Obligations as Processor
- We process the data only to operate the Merchant’s shop as described in the Terms and this DPA, and otherwise only on the Merchant’s documented instructions given through the Platform’s features
- We ensure that persons authorized to process the data are bound by confidentiality
- Our staff open the Merchant’s dashboard, where the Merchant’s customers’ data can be seen, only while the Merchant has granted support access, in the account settings or with a support ticket, and only for the period the Merchant chose there; the Merchant can end it at any time. Granting it is a documented instruction under this DPA. Each time our staff open the dashboard under it, we record who opened it, the reason given, when it started and ended, and the kind and time of each change our staff make there, never its content; we notify the Merchant by email when it is opened and again with a summary of those changes when it ends, and the Merchant can read the record in the account settings; while our staff are in the dashboard, they cannot make payments or refunds, change the Merchant’s plan, credits, domains or Stripe connection, or change the Merchant’s password or account
- We implement appropriate technical and organizational measures (encryption in transit, access controls, row-level tenant separation, backups)
- We assist the Merchant, insofar as reasonably possible, in responding to data subject requests and in meeting their security and notification obligations
- We notify the Merchant without undue delay after becoming aware of a personal data breach affecting their customers’ data
- When the Merchant deletes a shop that never sold anything, we delete its customer data with it. When the Merchant terminates the account, we delete the customer data of the Merchant’s archived shops: customer accounts with their logins, saved carts and wishlists, chats, contact requests, product questions, reviews, the newsletter list and its connections, review email opt-outs, back-in-stock requests, email copies and visitor statistics are deleted, and names and addresses are removed from the customer list and from gift cards. Orders, customer subscriptions, invoices and credit notes, with the details on them, remain for the statutory retention period for bookkeeping records (10 years from the end of the financial year, Art. 958f Swiss CO) and are deleted after it. Before terminating the account, the Merchant can download the orders and the invoices with credit notes in the dashboard; afterwards our support hands out copies on request. Database backups are overwritten automatically after their fixed period
- We make available the information reasonably necessary to demonstrate compliance with this DPA
4. Sub-Processors
The Merchant authorizes the use of the following sub-processors for the processing described above:
- Supabase (database, authentication, file storage)
- Vercel (hosting and content delivery)
- Stripe (payment processing on the Merchant’s own Stripe account)
- Resend (transactional email delivery)
- OpenAI (AI-assisted content and image generation, the AI answers of the shop’s chat, the dashboard assistant, which passes the customer data an answer needs, and checking uploaded pictures for prohibited content; where the Merchant uses these features; not used to train OpenAI’s models)
- fal.ai (AI film generation from pictures the Merchant chooses, where the Merchant uses the film feature)
- Google (sign-in with Google for customer accounts where the customer chooses it; the shops’ Google Fonts are delivered from 10mShop’s own servers, so visitors’ browsers do not contact Google for them)
- Pexels and Unsplash (stock photos and videos; their services are queried when the Merchant or the AI searches stock media, and visitors of a shop receive the media through 10mShop’s servers, so their browsers do not contact Pexels or Unsplash)
- Lorem Picsum (placeholder images while a design still shows one, delivered through 10mShop’s servers)
These providers may process data outside Switzerland or the EU/EEA; where they do, transfers are safeguarded by adequacy decisions or standard contractual clauses. We will inform Merchants of intended changes to this list (e.g. via the Platform or the date at the top of this page); if a Merchant objects to a new sub-processor on reasonable data protection grounds and no solution is found, the Merchant may terminate their account.
5. The Merchant's Obligations as Controller
- The Merchant is the controller of their customers’ data and responsible for the lawfulness of the processing, including a valid legal basis and their own privacy policy
- The Merchant handles their customers’ data subject requests; we assist as described above
- Instructions to us are given through the Platform’s features (e.g. deleting a customer, exporting data); instructions beyond the Platform’s functionality require a separate agreement
6. Liability and Final Provisions
The liability provisions of the Terms of Service apply. In case of conflict between this DPA and the Terms regarding the processing of the Merchant's customer data, this DPA prevails. This DPA is governed by the same law and jurisdiction as the Terms.