Data Deletion Instructions
Effective date: July 21, 2026 · Version 2.0
Any person whose data Kepla holds may have it deleted, at any time, free of charge, without giving a reason. This page defines the exact process, verification, scope, and timelines we are bound to.
1. How to submit a deletion request
- Email support@getkepla.com with subject "Delete my data."
- Send the request from the email address associated with your Kepla data, or state that address in the message. If your request concerns a connected Instagram account, include the Instagram username.
- An authorized agent may submit on your behalf with written proof of authorization.
2. Verification, how we prevent fraudulent deletions
- If the request comes from the associated email address, that control of the mailbox is itself sufficient verification. No documents are required.
- If the request comes from a different address, we will send a one-time confirmation email to the associated address and act only on confirmation, so that a stranger cannot delete (or probe the existence of) your record.
- We never ask for government ID, passwords, or payment for a deletion request. Anyone claiming otherwise in our name is fraudulent.
- If we cannot verify a request after reasonable attempts within 14 days, we will decline it and say why.
3. Scope. What gets deleted
What a deletion request covers, data type by data type.
| Data | Included in deletion |
| Waitlist record (name, email, studio details, position, referral codes) | Yes, permanently removed |
| Survey answers | Yes, permanently removed |
| Attribution data tied to your record | Yes, permanently removed |
| Demo interaction logs linked to you | Yes, permanently removed |
| Instagram-derived setup data (if you connected) | Yes, permanently removed |
| Emails you exchanged with us in our inbox | Deleted on request |
| Aggregated/de-identified statistics that cannot identify you | Not applicable, contains no personal data |
| Minimal record of the deletion request itself | Retained solely as evidence of compliance |
4. Timelines, binding commitments
- Acknowledgement: within 72 hours of receiving your request.
- Deletion from production systems: within 30 days of verification (typically within days).
- Encrypted backups: purged on rotation within a further 30 days; backup copies are never restored to production without re-applying pending deletions.
- Written confirmation: sent to you when production deletion is complete.
- Referral counts derived from your signup are recalculated so no personal trace remains.
5. Instagram users, additional controls
- You can revoke Kepla's access yourself at any time in the Instagram app (Settings → Security → Apps and websites → Remove Kepla). Revocation stops all data access immediately.
- Revocation alone stops future access; emailing us as above additionally deletes previously derived data from our systems under the timelines in Section 4.
- Where Meta transmits a data-deletion signal for your account to our app, we honor it under the same timelines without requiring a separate email from you.
6. Effects of deletion
- Deletion is irreversible. Your waitlist position and referral credits cannot be restored; rejoining later places you at the end of the list.
- You will receive no further emails from us after deletion, except the single confirmation of completion.
- If you only want to stop emails but keep your place in line, reply "unsubscribe" to any email instead of requesting deletion.
7. No retaliation, no conditions
Deletion requests are honored without fees, without conditions, and without any degradation of how we would treat you if you later return. We will never require you to create an account, complete a survey, or state a reason to exercise this right.
8. Complaints
If you believe we mishandled a deletion request, reply to any of our emails or write to support@getkepla.com with subject "Privacy complaint". Complaints are reviewed by the founder personally. EU/UK residents may additionally contact their data-protection authority.
Full details on what we collect and why: Privacy Policy.