How your customer data flows through Cockato
When a customer joins a loyalty programme powered by Cockato, the merchant acts as the data controller and Cockato acts as the data processor under GDPR Article 28. This distinction is critical: the merchant decides what data to collect and why, while Cockato processes that data strictly according to the merchant's instructions and the terms of the Data Processing Agreement.
What data is collected
Cockato enforces data minimisation by design. A typical loyalty card stores only the customer's name, email address or phone number, and their reward balance (stamps or points). No location data, device fingerprints, or behavioural profiles are collected. This aligns with GDPR Article 5(1)(c) — data must be adequate, relevant, and limited to what is necessary.
Where data is stored
All customer data is hosted on Supabase infrastructure within AWS ap-southeast-2 (Sydney, Australia). Each merchant's data is logically isolated at the database level through tenant-scoped row-level security policies. Data is encrypted with AES-256 at rest and protected by TLS 1.3 during transit.
How long data is retained
Customer data is retained for the duration of the merchant's active subscription. When a merchant closes their account, all associated customer data is permanently deleted within 30 days. Customers can also request individual erasure at any time via the self-service deletion portal, with processing completed within 72 hours per GDPR Article 17.
Sub-processors
Cockato discloses all sub-processors in the DPA. The primary sub-processors are:
- Supabase Inc. — Database hosting and authentication (AWS Sydney)
- Stripe Inc. — Payment processing for merchant subscriptions
- SendGrid / Twilio — Transactional email and SMS delivery
No customer data is shared with advertising networks, data brokers, or any third party beyond these essential service providers.