Last updated: 2026-09-10
Deposits & Partial Payments: Privacy Policy
1. Who we are
Deposits & Partial Payments (“the App”) is operated by:
- Kainabinoids GmbH
- Registered address: Carabelligasse 5/Haus 56, 1210 Wien, Österreich
- Firmenbuchnummer: FN 607246i, Handelsgericht Wien
- UID: ATU80796845
- Contact: hello@sitething.at
- Managing director / Geschäftsführer: Kai Juszko
- Data Protection Officer (Art. 13(1)(b)): We are not legally required to appoint a Data Protection Officer and have not done so; our processing is not on a scale or of a nature that triggers Art. 37 GDPR. Direct any data-protection questions to the contact above.
We are an Austrian company; the App is distributed through the Wix App Market.
2. Our role under the GDPR
When a merchant installs Deposits & Partial Payments on its Wix account, that merchant is the data controller for the data the App processes on its behalf. The App acts as a data processor under Article 28 GDPR, processing data solely to provide the deposit and balance-collection service and only on the controller’s documented instructions (the installation and the deposit rules and reminder schedule the merchant configures).
A Data Processing Agreement (Auftragsverarbeitungsvertrag) under Art. 28 GDPR applies to every controller and is incorporated by reference into the App’s terms. See our Data Processing Agreement.
3. What data we process, and why
The App stores a small operational ledger so it can track each deposit and collect the balance later. It is built for data minimization: the App stores no buyer personal data — no buyer names, no email addresses, no card or payment details. Those stay inside the merchant’s Wix account.
| Data | Source | Purpose | Stored? |
|---|---|---|---|
| Wix order id + order display number | Wix order webhooks | Identify the order the deposit belongs to | Stored in the App’s database |
| Deposit total, balance owed, currency, due date, status | Wix order + the merchant’s deposit rule | Track the open balance and when it is due | Stored |
| Payment-link id and URL | Generated via Wix Payment Links | Let the merchant collect the remaining balance | Stored |
| Merchant deposit rules (percentage or fixed, per product or store-wide) and reminder schedule | Set by the merchant in the App dashboard | Decide the deposit amount and when reminders go out | Stored (config only) |
| Installation record (instance id, installed/uninstalled timestamps) | Generated on install/uninstall | Run the App per merchant and govern deletion | Stored |
| Per-installation reachability verdict (the verdict and its reason code, the HTTP status behind it, a consecutive-night streak, the time the current run of unreachable nights began, and the time of the last check) | Generated by the App’s nightly reachability check against the Wix API | Govern deletion when an installation or a site no longer exists | Stored (one record per installation, deleted with it) |
| Webhook event id + receipt time; per-order reminder state | Generated by the App | Prevent processing the same event or sending the same reminder twice | Stored (operational, rolling) |
| Buyer contact id (a Wix contact UUID) | Wix order (buyerInfo.contactId) | Passed to Wix Automations at reminder time so Wix sends the email | Not stored — used transiently at send time and discarded |
Order ids and order numbers are Wix order identifiers, not buyer personal data. The App never reads or stores the buyer’s name, email address, or payment details.
Reminder emails are sent by Wix, not by us. When a balance reminder is due, the App hands the buyer’s Wix contact id (a UUID) to Wix Automations, which sends the email from within the merchant’s own Wix account. The buyer’s email address and name never reach the App.
We do not process payment data: Wix handles all checkout, balance collection (via Wix Payment Links), app billing, tax, and payment.
We do not use analytics or advertising trackers, and the App sets no cookies.
No automated decision-making. The App carries out no automated decision-making or profiling that produces legal or similarly significant effects within the meaning of Art. 22 GDPR. It calculates a deposit amount from the merchant’s rule and tracks the resulting balance.
4. Legal basis
We process the above as a processor on the documented instructions of the controller (Art. 28 GDPR). The controller’s own legal basis for using the App is typically the performance of its contract with its customer (Art. 6(1)(b)) — taking a deposit and collecting the balance — or its legitimate interest in managing made-to-order and high-ticket sales (Art. 6(1)(f)).
5. Sub-processors
To deliver the service we use:
- Cloudflare, Inc.: the App’s backend runs on Cloudflare Workers and stores the ledger and configuration in Cloudflare D1 (SQLite), provisioned in the EU region (created with EU jurisdiction, region EEUR / Zurich). Cloudflare is our only external sub-processor. Cloudflare Inc. is US-headquartered; to the extent any access from outside the EEA occurs, it is governed by Cloudflare’s Data Processing Addendum and the EU Standard Contractual Clauses. See Cloudflare’s privacy policy and sub-processor list.
The App also operates on the Wix platform (Wix.com Ltd.), where the merchant’s order and customer data already reside. Reminder emails are sent by Wix Automations and balances are collected via Wix Payment Links — both within the merchant’s own Wix account, under the merchant’s existing relationship with Wix. Wix is the platform the merchant already controls, not a sub-processor we introduce.
A current sub-processor list is maintained at Sub-processors and in our Data Processing Agreement. We will inform controllers of changes to sub-processors in line with the DPA.
6. Data location and transfers
The App’s ledger and configuration are stored in Cloudflare D1 in the EU region (EEUR / Zurich). Order and customer data otherwise remain in the merchant’s Wix account. We do not transfer personal data outside the EU/EEA for our own purposes; where access by Cloudflare from outside the EEA cannot be excluded, it is covered by Cloudflare’s Data Processing Addendum and EU Standard Contractual Clauses.
7. Retention
- Configuration (deposit rules, reminder schedule): kept until the App is uninstalled or the setting is removed.
- Order ledger (deposit/balance state): kept while the App is installed so balances can be tracked and collected.
- Webhook dedupe and reminder state: kept as a rolling operational record.
- Buyer content: never retained (the App stores no buyer name, email, or payment data at all).
On uninstall, the App immediately stops processing and marks the merchant’s data for deletion; all stored ledger and configuration data is then hard-deleted within 30 days of the App being removed, or of an installation being confirmed as no longer existing, by an automated daily purge. A site can be deleted without the App ever being uninstalled, so the App checks reachability nightly and flags installations that stop existing; once one is confirmed gone, the same 30-day deletion clock starts. There is no buyer content to recover because none was ever stored.
8. Security
- The App stores no buyer PII — data minimization by design (order ids, amounts, due dates, and merchant config only).
- Per-merchant isolation: every row is partitioned by the Wix installation id (
instanceId); a token is minted per installation (OAuth client-credentials, instance-scoped). - Incoming Wix webhooks are signature-verified first (RS256) and rejected if unverified; duplicate events are ignored.
- Configuration and balance endpoints are guarded by a constant-time shared secret that fails closed if the secret is unset, and reject the request before any database access.
- Secrets (app credentials, the Wix public verification key, the route secret) are held in Cloudflare’s encrypted secret storage, never in source code.
- All connections use TLS in transit. Access to Wix data is limited to the minimum eCommerce scopes required (no “Manage Stores” scope).
9. Data subject rights
Every individual has the following rights under the GDPR:
- the right of access (Art. 15),
- the right to rectification (Art. 16),
- the right to erasure (Art. 17),
- the right to restriction of processing (Art. 18),
- the right to data portability (Art. 20),
- the right to object to processing (Art. 21), and
- the right to withdraw consent at any time (Art. 7(3)).
Because we act as a processor, individuals should direct these requests to the controller (the merchant whose Wix account is used). We assist the controller in fulfilling such requests as required by Art. 28(3)(e). Because the App stores no buyer personal data, most such requests are fulfilled by the merchant directly within Wix; we assist with the order-level ledger data the App holds without undue delay. As stated in section 3, the App performs no automated decision-making under Art. 22, so no related right is engaged.
10. Supervisory authority
Controllers and data subjects may lodge a complaint with a supervisory authority. In Austria this is the Datenschutzbehörde (DSB), Barichgasse 40-42, 1030 Wien: dsb.gv.at.
11. Contact
Questions about this policy or the App’s data handling: hello@sitething.at.
12. Changes
We will update this page when the App’s data handling changes and note the date above.