Data deletion

In the same browser session that created the link, use Remove request and confirm. A successful removal makes the public GetPaid URL unavailable and deletes its request record and removal-capability record from the request store.

If the creator no longer has the removal token, the request remains readable until its 7-day expiry. The request and its server-side removal record are then deleted automatically. Deleting a message or browser-history entry does not remove a still-active server request.

Open the public Sorry Receipt, paste your private code, choose Check my contribution, then Withdraw my counts. This works without the original request link or an account. It removes the public row and its counts from the current sums. The accepted total remains; a removed contribution is not restored by retrying it.

Request deletion and contribution withdrawal are separate actions. Keep your code if a response is interrupted and check the stored result again; an empty lookup is not a promise that an in-flight submission was cancelled. There is no owner-assisted recovery for a lost code, and copied images cannot be recalled.

Individual rows and removal hashes expire 30 days after the run closes. Only the bounded aggregate summary remains afterward. Clear site data to remove the separate localStorage code; closing a tab alone does not clear it, and clearing it does not withdraw a public contribution.

After removing an active request, or once it has expired, clear site data or close the browser session to remove GetPaid sessionStorage entries and demo receipts. Clearing browser storage first can remove the only deletion token; it does not remove an active public request.

Operator credentials for GetPaid Social are separate from product request data. The operator can delete the ignored local social environment file and revoke the corresponding platform authorization in that platform's settings.