Privacy Policy

Kay Growth(“the Service”) analyses a merchant’s own commerce data and returns customer analytics to that merchant. This policy explains what we access, why, how long we keep it, and how to have it deleted.

Who the parties are

The merchant who connects a store is the data controllerfor their customers’ personal data. We act as a data processor, processing that data only to provide the Service to that merchant, on their instructions.

What we access

When a merchant connects Shopify, we request read-only access to four scopes:

• read_orders: order history, values, dates, refunds and line items.
• read_all_orders: the same order data reaching further back than 60 days. Shopify treats older orders as a separate permission; the analytics need a full purchase history to establish a customer’s buying rhythm, so a 60-day window would make churn and reorder predictions meaningless.
• read_customers: customer name, email, city, state, postal code, and marketing-consent status.
• read_products: product titles, types and prices, used to classify purchases.

We never request write access and never modify a merchant’s store. If a merchant connects Klaviyo, we store the API key they provide in order to sync audience segments back to their own Klaviyo account.

What we derive

The data is used to compute per-customer analytics: purchase-behaviour metrics, an advocacy score, churn and next-purchase predictions, and segment membership. The pricing ring is derived from each customer’s own order history (full-price versus discounted purchases), and area type from the postal code only. We do not attempt to identify individuals beyond the records the merchant already holds, and we do not buy or merge in third-party personal data.

How it is stored and isolated

• Data is stored in Convex, a managed database hosted on Amazon Web Services in the United States.
• Each workspace’s data is isolated: every request is checked against the signed-in user’s membership and role in that workspace (owner, analyst or read-only) before any data is returned.
• Access credentials (Shopify tokens, Klaviyo keys) are stored separately from the analytics data and can only be read by our server-side systems. They are never sent to a browser.
• All traffic is encrypted in transit (TLS), and our database provider encrypts stored data at rest.
• Our scoring engine runs on a server we operate with Hetzner in Germany. It processes store data in memory during a scoring run and writes the results to the database.

Who we share it with

We do not sell personal data and we do not share it with third parties for their own purposes. Data is processed only by the providers that run the Service, acting as sub-processors:

• Convex (on Amazon Web Services): database and sign-in.
• Vercel: hosts the web application.
• Hetzner: hosts our scoring engine.
• Resend: sends service email (sign-in codes, invitations, digests) to the merchant’s staff.
• Klaviyo: only when a merchant connects their own Klaviyo account and starts a sync. Customers who have consented to marketing in Shopify are sent to that merchant’s own Klaviyo account.

Retention and deletion

• Analytics are recomputed on each run; each run replaces the previous results.
• Uploaded order-export files are deleted as soon as the file has been processed.
• Disconnecting a source deletes the stored access credential immediately. When the app is uninstalled from Shopify, the stored Shopify token is deleted immediately and we stop accessing the store.
• We implement Shopify’s mandatory compliance webhooks. On shop/redact we delete the store’s customer records, its scoring history, segment lists, connection and credentials; the merchant’s account and logins are kept. On customers/redact we delete the named customer’s records, including their entry in any saved segment list.
• A merchant may request deletion of their workspace and all associated data at any time by contacting us.

Data-subject requests

Because we act as a processor, an individual’s request to access or erase their data should be directed to the merchant whose store they purchased from. We support merchants in fulfilling those requests, including via Shopify’s customers/data_request webhook, which we record and act on for the merchant.

Contact

For privacy questions, data-deletion requests, or to exercise any right described above, see the support page for how to reach us.