Data Deletion
Operator: Epigos Ltd (“we”, “us”)
Product: PingChange
Contact: hello@pingchange.com
This page explains how you can request deletion of personal data associated with PingChange, what we delete, what we may retain, and how long the process typically takes. It complements our Privacy Policy and Terms of Service.
1. Who can request deletion?
You may request deletion if:
- You have a personal account, or
- You are an authorized administrator of an organization account, or
- You are acting on behalf of a user with appropriate legal authority (for example a guardian or estate representative).
We must verify your identity before deleting data, to prevent malicious erasure requests.
2. How to request deletion
Email hello@pingchange.com with:
- Subject:
Data deletion request - Your full name and the email address associated with the account
- Whether the request is for a personal account or organization/workspace (include workspace name if applicable)
- Any alternative emails you may have used to sign in
- Whether you are requesting full account deletion or specific categories (for example profile only, while retaining billing records per law)
We may ask follow-up questions or request proof of account control (for example a confirmation link, signed statement, or administrator approval for shared workspaces).
EU/UK users: You may also refer to GDPR/UK GDPR Article 17 in your message; we will respond within statutory timelines (typically one month, extendable where complex).
3. What we typically delete
After verification, we will delete or irreversibly anonymize personal data that is no longer needed for a lawful purpose, including:
- Profile — name, email on the account, avatar, preferences (where not legally required)
- Service configuration you controlled personally — personal monitors, personal tokens, personal notification endpoints (where technically separable)
- Derived operational data tied solely to your personal identity (for example personal support tickets)
Organization accounts: Deleting a single member may not delete all historical artifacts if the organization must retain them for legitimate business purposes (audit trails, incident response). Organization administrators should coordinate workspace-level deletion or export before removing users when required by internal policy.
4. What we may retain (exceptions)
Even after a valid deletion request, we may retain certain records where:
| Reason | Examples |
|---|---|
| Legal obligation | Tax, invoicing, accounting records; regulatory inquiries |
| Establishing/defending legal claims | Abusive behavior investigations, unpaid invoices, litigation holds |
| Security & integrity | Tamper-evident logs with minimized personal data |
| Aggregated/de-identified data | Metrics that can no longer identify you |
When retention is required, we limit access and minimize personal data to what is necessary.
5. Backups and propagation
Production data may exist in encrypted backups for a limited period. We will ensure deletion from active systems promptly; residual copies in backups are aged out on a documented rotation schedule (often 30–90 days, subject to infrastructure design).
6. Third parties
We use subprocessors (hosting, auth, email, payments, error monitoring, AI inference, queue workers). We instruct vendors to delete or anonymize data on our request where contractually required. Payment processors may retain payment records under their own legal duties—contact them separately if needed.
7. Timelines
- Acknowledgment: within 5 business days for most requests
- Completion: typically within 30 calendar days; up to 60 days where requests are complex or involve organization hierarchies
- Compliance with law: if your jurisdiction provides a specific deadline, we follow the stricter requirement where it applies
We do not charge a fee for good-faith requests unless they are manifestly excessive or repetitive (as permitted by GDPR and some U.S. state laws).
8. U.S. state rights
Residents of certain U.S. states may have deletion rights under state privacy laws. Submitting a request to hello@pingchange.com initiates our review under both GDPR (where applicable) and U.S. frameworks. If we deny a request in whole or part, we will explain why and how to appeal where required.
9. Contact
Epigos Ltd — PingChange
hello@pingchange.com
For general privacy matters, see the Privacy Policy.
This page describes our operational practices and is not legal advice.