Retention and deletion

Ending a request

Completion, withdrawal or expiry ends public display of the request details and further access to its private fields. Your saved history can remain in your account until it is deleted. Deleting request content removes it and its access records from the application; the old public link stays reserved and shows an unavailable notice.

Ending access prevents further access through RippleEnd. It cannot erase information someone has already copied, downloaded, photographed, screenshotted or shared elsewhere.

Deleting an account

Use Account and privacy to export supported records or request deletion after fresh verification. Account deletion is separate from closing one request. Linked support, safety or review records can require a scoped review. A request marked “review pending” has not completed deletion. We confirm completion only after the supported deletion process succeeds.

Your policy responses and account settings are removed with the account. Export covers supported own records; contact us if you need assistance with other information concerning you.

Record-specific disposal targets

These periods guide manual review and deletion. Records are not automatically erased when a period ends. A due review is not a completed deletion.

Private request fields

Our target is to erase built-in and custom private fields 30 days after the earlier of request closure or expiry, subject to a specific review or hold. You can delete request content sooner using your account.

Ended request history

Our target is to erase saved request content and access records 90 days after the earlier of closure or expiry. The reserved public reference remains unavailable so the old link cannot be reused for another request.

Resolved routine support

Our target is 90 days after resolution for the case, replies and internal notes. Reopening stops that clock. Copies in our support mailbox need separate review.

Reports, moderation and review requests

Records needed for investigation and accountability remain while the matter is active. Our target is review and disposal 12 calendar months after final resolution. An unresolved appeal or active restriction prevents premature disposal.

Operational and security logs

Our targets are up to 30 days for routine logs and 90 days for security logs. Provider settings and necessary incident records require separate retention review.

Deletion records and backups

A minimal completion receipt is targeted for removal 90 days after confirmed deletion. Separate, restricted identifiers needed to prevent deleted data returning after a restore remain until every affected restorable copy has expired. Backup deletion follows provider rotation, not immediate erasure. We do not promise a fixed backup-erasure date.

Holds and recovery copies

A necessary hold must identify the record, reason and next review date. It does not justify keeping everything indefinitely. Live deletion does not immediately erase backups. Recovery must replay completed deletions and restrictions before restored data becomes accessible.