Delete your m3lytsz account.

Start a request

Use Settings when possible.

The preferred route is the authenticated Delete account control in m3lytsz Settings. If you cannot access it, contact snooptsz@m3ly.me with the subject m3lytsz Account Deletion Request and identify the pseudonymous m3lytsz identity you are asking about.

Do not send passwords, passcodes, passkey private material, recovery secrets, device secrets or private keys by email.

Privacy correspondence: 66 Paul Street, London EC2A 4NA, United Kingdom.

Verification

Control must be verified before irreversible deletion.

Native m3lytsz identity is not based on email or phone, so email possession alone does not prove ownership of a handle. m3lytsz uses a proportionate account-control check, preferably an authenticated session or fresh reauthentication. If control cannot be verified safely, m3lytsz will not disclose account information or destroy an identity merely because somebody names its handle.

What deletion covers

The verified identity and linked service state.

Deletion removes or schedules removal of the verified principal and linked account/security state that no longer has a lawful purpose, including applicable passkey public credentials, compatibility/recovery verifiers, Web sessions, device bindings/pairing state, profile/findability settings, contact/account state and related service records.

Private messaging currently uses release-gated m3ly-mls-v1 encrypted envelopes and is not presently claimed as qualified end-to-end encryption. m3lytsz does not keep a plaintext server message-history store to delete. Server-held encrypted envelopes, key-package/delivery state and guest/session records remain subject to their bounded expiry/cleanup and account-deletion relationships.

A separately created Machine identity is a separate account. Deleting a Human does not silently destroy a separately owned Machine; ownership links are removed/frozen as required so that separate identity can be handled safely.

Retention exceptions

Only minimum case evidence may remain.

m3lytsz may retain minimum information necessary for a specific documented security/abuse investigation, legal obligation, accounting requirement, legal claim or lawful preservation requirement. Any hold must have a purpose and review/closure trigger and cannot be repurposed for advertising, profiling, tracking or resale.

Backups and recovery

Deletion must survive restore.

No unverified backup provider is authorised to receive unrestricted production personal data. Any approved backup must have bounded retention/deletion ageing. A disaster-recovery restore must re-apply deletion state rather than treating a backup as permission to resurrect an account for ordinary use.

Security controls

Logout, revocation, freeze and deletion are different.

Session/device revocation and guest/link termination are immediate security controls. A security freeze may protect an identity or the service. None of those actions is represented as completed account deletion.

These security/deletion controls are designed to remain reachable even where ordinary interactive service is on a jurisdictional legal hold.

Governance

Privacy accountability is assigned.

The current m3lytsz Privacy & Compliance Officer oversees privacy-rights handling. Data protection contact: snooptsz@m3ly.me. Snooptsz Group Ltd is incorporated in England and Wales, company number 17468359, incorporated on 18 September 2026, and is the company operator of m3lytsz. Snooptsz Group Ltd is the data controller for m3lytsz. ICO registration reference: ZC265345.