Last updated August 2026
Requesting deletion (Settings → Privacy → Delete my account) schedules erasure at least 48 hours later, as required by DPDP Rule 8(2). You can cancel any time before then. When it runs:
| Data | Retained while | After account deletion |
|---|---|---|
| Profile (name, email, phone, bio, avatar) | Account is active | Erased; minimal registration record kept 180 days (see above) |
| Messages you sent | Conversation exists, or until you delete a message individually | Content scrubbed; conversation and other participants' messages remain |
| Files you uploaded | Until you delete it, or the account is deleted | Database record and physical file both removed |
| Meetings you hosted | Indefinitely (no auto-expiry currently) | Meeting record and other participants' data survive; your identity as host becomes an internal reference only, no longer publicly attributed |
| Contacts & contact requests | Until either party removes it, or an account is deleted | Removed |
| Notifications | Indefinitely — no automatic pruning is currently implemented | Removed with the account |
| Active sessions | Until logout, password change, or expiry | Removed with the account |
| Consent records | Permanently — this is a compliance record, kept even after account deletion (see Privacy Policy) | Survives; contains no re-identifiable data once the account is gone |
| Audit/access logs | Minimum 1 year, no shorter, per DPDP Rule 6/8 | Survives, actor reference anonymized |
| WebRTC signaling data (call setup) | Transient — automatic cleanup is an optional cron job, not enabled by default (see project's INSTALL.md) | Removed with the account regardless |
| Password reset / verification tokens | 1 hour to 7 days depending on type, then unusable — automatic row cleanup is an optional cron job | Removed with the account regardless |
Both are self-service, from Settings → Privacy:
Something not covered by these tools? Contact our Grievance Officer.