Data Processing Agreement (summary)
Last updated: [Effective date]
This document is a draft
01Overview
This page summarises the Data Processing Agreement (“DPA”) between [Company legal name] (“RefundMind”) and each business customer (“Customer” or “merchant”). It covers personal data about the merchant’s own customers (“End Customers”) that RefundMind processes when providing the service. It is written to meet KVKK Article 12 and, where applicable, GDPR Article 28.
02Roles of the parties
- The Customer is the data controller (veri sorumlusu) of End Customer personal data it imports, syncs or receives in RefundMind. It decides why and how that data is processed.
- RefundMind is the data processor (veri işleyen) and processes that data only on the Customer’s documented instructions.
- For data about the Customer’s own Users and for our marketing-website visitors, RefundMind is a separate controller under its Privacy Policy; that data is outside this DPA.
03Subject matter, duration, nature and purpose
| Item | Details |
|---|---|
| Subject matter | Provision of the RefundMind service: managing returns, refunds, exchanges, store credit and related customer communication. |
| Duration | For the term of the agreement, plus the period needed to delete or return data afterwards. |
| Nature of processing | Collection by CSV import, Shopify sync and inbound email; storage; organisation into cases; display to authorised Users; sending and receiving email; calculation of return statistics and an advisory risk level; anonymisation and erasure. |
| Purpose | Solely to provide, secure and support the service for the Customer, following its instructions as expressed through its configuration and use of the product. |
04Data subjects and categories of personal data
Data subjects: the Customer’s End Customers (shoppers who placed orders or requested a return, refund, exchange or store credit) and people who email the Customer’s support address through RefundMind.
| Category | Examples |
|---|---|
| Identity and contact | Name, email address, phone number (optional), external platform IDs (for example Shopify customer ID). |
| Order data | Order number, dates, items, amounts, currency, payment method label, fulfilment status, tracking numbers. |
| Case data | Return, refund, exchange and store-credit reasons, item condition, inspection results, amounts, statuses. |
| Communications | Inbound and outbound email (sender name and address, subject, body) and attachments such as images, PDFs and office documents. |
| Derived data | Return statistics and an automated risk level or segment based on return history (advisory only; a human approves every resolution). |
| Notes and imports | The Customer’s free-text notes; CSV import files and row-level import error reports that may contain the raw CSV row. |
RefundMind does not store structured postal addresses or process payment card data. The service is not designed for special categories of personal data; the Customer should not upload such data, although End Customers may include anything in free-text messages or attachments.
05RefundMind’s obligations as processor
Instructions
We process End Customer data only on the Customer’s documented instructions — the agreement, and the Customer’s configuration and use of the service — unless the law requires otherwise, in which case we will inform the Customer where legally permitted. We will tell the Customer if we believe an instruction infringes data-protection law.
Confidentiality
Everyone at RefundMind who can access End Customer data is bound by confidentiality obligations and accesses it only as needed to provide and support the service.
Security
We maintain the technical and organisational measures listed in Section 7.
Sub-processors
The Customer gives general authorisation for the sub-processors in Section 8. We impose data-protection obligations on each sub-processor that are no less protective than this DPA and remain responsible for their performance. We will give the Customer notice before adding or replacing a sub-processor, and the Customer may object on reasonable data-protection grounds; if we cannot resolve the objection, the Customer may terminate the affected service.
Assistance with data-subject requests
If an End Customer contacts us directly, we will forward the request to the Customer and not respond ourselves except on the Customer’s instruction. The service lets the Workspace owner erase an individual End Customer immediately, and we will provide further reasonable assistance where needed. We honour Shopify’s mandatory privacy webhooks (customer data requests, customer redaction and shop redaction); a customer-redaction request triggers the same anonymisation automatically.
Personal data breaches
We will notify the Customer without undue delay after becoming aware of a personal data breach affecting End Customer data, with the information then available (nature of the breach, categories and approximate number of people and records affected, likely consequences and measures taken), and will support the Customer in meeting its own notification obligations — including the obligation under KVKK to notify the Personal Data Protection Board within 72 hours.
Impact assessments and consultation
We will provide reasonable information to help the Customer carry out data-protection impact assessments and any prior consultation with an authority.
Deletion or return at the end of the service
On termination, the Customer may request an export of its data. Workspace data is then deleted or anonymised within [Account data deletion period after termination], and backup copies roll off after [Backup retention period], unless the law requires us to keep it.
Audits and information
We will make available the information reasonably necessary to demonstrate compliance with this DPA and allow audits by the Customer or an independent auditor it appoints, on reasonable prior notice, during business hours, subject to confidentiality and no more than once a year unless required by an authority or following a breach.
06The Customer’s obligations as controller
- Have a valid legal basis for the End Customer data it brings into RefundMind and for its instructions.
- Give End Customers the privacy notices required by KVKK Article 10 and other applicable law, including that a service provider processes their data on its behalf.
- Respond to End Customer requests under KVKK Article 11 or the GDPR, using the tools the service provides.
- Set an appropriate retention period for its Workspace and keep User roles and access up to date.
- Make and remain responsible for all final decisions on returns, refunds, exchanges and store credit.
07Security measures
RefundMind maintains the following measures:
- Encryption in transit (TLS) for all traffic to the product app, marketing site and our providers.
- Encryption at rest provided by our hosting provider (Supabase on AWS).
- Multi-tenant isolation: PostgreSQL Row-Level Security on every workspace table, so one workspace cannot read another workspace’s data.
- Role-based access control enforced in the database — for example, only owner/admin and finance-approver roles can approve or complete refunds, only owner/admin and support-agent roles can send customer emails, and viewers are read-only.
- An append-only style audit log of actions taken in each workspace (who acted, in which role, what changed, and when).
- Private file-storage buckets; attachments are served only through short-lived signed URLs that expire after 15 minutes.
- Signature verification on incoming webhooks (Shopify HMAC; Resend/Svix signatures).
- Server-only secrets: service keys are never sent to the browser, and Shopify access tokens cannot be read by app users.
- Idempotent background jobs with health monitoring and alerting.
- Provider-managed backups, retained for [Backup retention period].
- Passwords are handled by Supabase Auth and are never stored in plain text by RefundMind.
08Sub-processors
RefundMind uses the following sub-processors for End Customer data:
| Provider | Service | Data involved | Location |
|---|---|---|---|
| Supabase, Inc. (USA) | Database, authentication, file storage and background jobs for the product app; storage of marketing-form submissions. | All account, workspace and end-customer data held in the product; sign-in events (including IP address and user agent); demo and contact form submissions. | Production project hosted on AWS in eu-central-1 (Frankfurt, Germany). |
| Netlify, Inc. (USA) | Hosting, content delivery network, server-side rendering and serverless functions for the product app and marketing site. | Request data (IP address, user agent, requested URLs) and data passing through the app in transit. | Global infrastructure; may process data outside the EU and Türkiye. |
| Resend — Plus Five Five, Inc. (USA) | Delivery of outbound and transactional email, and receipt of inbound email, for merchants’ customer communication. | Recipient and sender addresses, message content, attachments and delivery events. | Sending region eu-west-1 (Ireland), delivered over Amazon SES infrastructure. |
Not a sub-processor: Shopify. If the Customer connects its own Shopify store, data flows between the Customer’s store and RefundMind on the Customer’s instruction (scopes: read_products, read_customers, write_orders, write_returns), and refunds are issued through the Customer’s own store. Shopify’s processing is governed by the Customer’s agreement with Shopify.
RefundMind does not currently use any AI/LLM provider, payment processor, CRM, or error-tracking or session-replay tool to process End Customer data.
09International transfers
End Customer data is stored in the EU (AWS eu-central-1, Frankfurt) and email is sent from the EU (eu-west-1, Ireland). Our sub-processors are US companies, and our hosting provider may process request data outside the EU and Türkiye, so transfers abroad occur.
For transfers under KVKK Article 9 we rely on the standard contractual clauses published by the Personal Data Protection Board, which we put in place with our sub-processors and notify to the Personal Data Protection Authority within five business days of signing. Where the Customer is acting as data exporter under the GDPR, we rely on the European Commission’s Standard Contractual Clauses or the EU–US Data Privacy Framework, as applicable to each sub-processor. Where KVKK requires the Customer, as controller, to sign a standard contract with RefundMind for a transfer, we will do so on request.
10Retention and anonymisation tools
The service gives the Customer built-in controls to meet storage-limitation duties:
- Automatic anonymisation of End Customer personal data by a daily job once a retention period has passed since the customer’s last related case closed — 24 months by default, configurable by the Workspace owner between 6 and 120 months.
- Anonymisation clears names, emails, phone numbers, notes and external IDs; removes email subjects and bodies, sender details, attachments and raw import rows of eligible cases; and queues stored attachment files for deletion. Non-personal aggregates (counts, amounts, return rates, product statistics) are kept for reporting.
- Customers with an open case, or with order or case activity inside the retention period, are not anonymised. Unmatched inbound emails older than the period are also scrubbed.
- Immediate erasure of a single End Customer by the Workspace owner; Shopify customers/redact requests trigger the same process.
- Every anonymisation run and erasure is recorded in the Workspace’s audit log.
11Contact and requesting the DPA
To request the full DPA, the standard-contract documentation, or to ask about sub-processor changes, email [Privacy contact email] or write to [Company legal name], [Registered address] (KEP: [KEP address]). Data protection contact person: [Data protection contact person].