Data deletion instructions
What a request removes, what we keep and why, and how to ask. This is the same information §8 of /privacy states — this page is its canonical, standalone location.
- HOW TO ASK
- /contact, or the grievance route on /privacy
- RESPONSE
- within one working day
- WHAT THIS COVERS
- your personal data — not public listing evidence
What is deleted, and what is kept — and why
| What | On a deletion request |
|---|---|
| Enquiry details you gave us — name, phone, email, brand — from /talk, /contact or the free site audit form | Deleted. Ask and we confirm what was held and when it is gone; every enquiry also auto-deletes 180 days after it is sent, whichever comes first. |
| Data read through a connector you granted (Shopify, Meta Ads, Google Ads, GA4, Search Console — none live yet) | Deleted, once you ask. Revoking the connector itself stops new reads immediately; a separate request removes what was already read. |
| Your console login identity, if you hold one | Deleted. Authentication is held by Clerk; ask and we remove your identity from it. |
| Public listing evidence — prices, page captures and product observations, read from pages anyone can open | Kept. It is public record about a page, not personal data about you, and it is kept without expiry because a price history cannot be rebuilt later — the same line /security states about it. You can ask that a domain stop being read for future public surfaces (below); that does not erase what has already been captured. |
| Storefront audit history — Speed, SEO, AEO/GEO and commercial-hygiene readings, once a domain has been audited | Kept. It is a growing history tied to the domain, never overwritten or aged out, so a trend is measured against real past runs rather than a snapshot. The same suppression request below stops future audits; it does not remove past ones. |
How to ask
Use the form on /contact and say what you want deleted and which of the rows above it concerns — that reaches us today. India’s DPDP Act also gives you a right to a named grievance officer, published on /privacy; that field is not yet filled in, and the page says so rather than leaving you to find out by writing to nobody.
We will not ask you to prove a legitimate interest, and we will not route you through a support ticket system. If the data you are asking about is an enquiry record, it may already be gone — every enquiry auto-deletes after 180 days, and we will tell you if that is what happened.
A different request: stop a domain being read for future public pages
This is not a deletion request and answers a different question — should we keep reading this domain, not erase what you already hold. It uses the same suppression form /bot already publishes: “This does not delete what we already hold, and it is not instant — the fetcher checks this before its next crawl of the domain, not mid-crawl.” The same fence also stops that domain rejoining the weekly crawl the storefront audit rides on, so no new audit rows are added for it either — past rows stay, for the reason stated above.
Questions about what we hold, or a request to make?
Ask us directly, and you’ll hear back within one working day.