Leaving the app?
Here are your options.

WHAT HAPPENS NEXT

A request is reviewed securely

The in-app request enters the app’s privacy-request workflow. A secure identity check is needed before an account can be erased, to protect members against impersonation. Email is an alternative contact route, not an automatic deletion tool.

The responsible team must confirm the handling outcome, any information retained and the reason. A proposed retention schedule is available below. Its owner, operational implementation and final approval remain outstanding.

Information covered by the request

• Private account information and sign-in identifiers.
• Community profile, avatar selection and preferences.
• Posts, replies, messages and related account links.
• Device tokens, notification choices and invitation/recognition records.
• Privacy-request, safety, moderation, audit and backup records, subject to the final retention and exception policy.

The proposed schedule below states the intended handling and exceptions. It becomes an operational commitment only after adoption and verification.

Proposed retention and deletion terms

Proposed terms for Seniorman Network CIC — 24 September 2026. These are purpose-based starting points for the adult community app, not statutory retention periods or a claim that automated deletion is already operating. They require controller adoption, safeguarding review and verified implementation before becoming effective.

Requests can be made using My account → Your information rights → Request deletion, or by emailing info@seniorman.co.uk. Proposed internal target: acknowledge within 5 working days and complete ordinary verified deletion within 30 days after verification, without delaying any shorter applicable legal deadline. Assess the response deadline from receipt under the applicable rules; verification is not permission to ignore a request. If lawful refusal, a permitted extension or limited retention applies, explain the reason and available complaint route. Do not describe the request button as immediate erasure.

Unverified registrations

Proposed period: 30 days after registration if verification is not completed.

Delete the incomplete account and associated registration data.

Active account and profile

Proposed period: While the account is active and needed. Review after 24 months without a sign-in; give 30 days’ notice before closing an inactive account.

On approved deletion, remove sign-in identifiers, private age information, profile and preferences from live systems within 30 days after identity verification, subject to any shorter applicable deadline.

Posts and replies

Proposed period: While published and useful to the community, with an annual necessity review.

On account deletion, remove the member’s contributions within the same deletion window. Keep only non-identifying thread placeholders; changing a name alone is not anonymisation.

Direct messages

Proposed period: 12 months from sending, or earlier under an approved deletion request.

Remove the departing member’s sent messages from live conversations within the account-deletion window. Retain only separately justified report evidence. Tell members about expiry before activating it.

Device tokens and notification delivery

Proposed period: Revoke on logout, invalidation or account closure; remove inactive tokens after 90 days. Delivery metadata: 30 days.

Delete tokens and unnecessary delivery records; retain no message bodies in push payloads.

Invitations, recognition and applications

Proposed period: While membership continues. Closed moderator applications: 12 months from the decision.

Remove personal referral links and recognition records with the account; retain only genuinely anonymous totals. A necessary staff-grant audit follows the audit schedule.

Blocks and routine moderation reports

Proposed period: Blocks while both accounts remain active. Closed routine reports and necessary evidence: up to 12 months from closure.

Delete expired records, unless a documented case-specific hold applies. Assess restrictions needed for an active safety case separately.

Safeguarding case records

Proposed period: Review every 6 months while open. Proposed default maximum: 24 months from case closure, subject to safeguarding-lead approval and any specific legal requirement.

Erase earlier when no longer necessary. Any longer retention needs a recorded lawful reason, limited scope, owner and next review date.

Staff access and security audit

Proposed period: 12 months from the event. General operational logs: 30 days.

Delete expired personal audit/log data through an authorised process; preserve only records covered by a documented incident or legal hold.

Privacy requests

Proposed period: Minimal request, verification outcome and decision record: 24 months from closure. Any identity-document copy: delete within 30 days after verification unless separately required.

Keep the decision trail, not a duplicate of exported/deleted content. Do not routinely request identity documents.

Backups

Proposed period: Proposed maximum rolling retention: 30 days, only once confirmed and configured for every relevant provider and copy.

Put deleted data beyond ordinary use until backup expiry. Replay deletions before a restored backup is returned to service.

Kels AI processing

Proposed period: No additional application-level archive of raw prompts or outputs. Published replies follow posts/messages; safety flags follow the relevant case schedule.

Model-provider logs and retention must be verified separately against the actual account settings and contract before these terms become effective.

Limited exceptions and legal holds

A hold must identify the specific records, lawful purpose, approving person, start date and next review date (no later than 90 days). Delete unrelated data on schedule. Release the hold when its justification ends and delete the affected data promptly, normally within 30 days. Safeguarding is not a blanket reason to keep all account data. Pseudonyms, hashed identifiers and detached account links can still be personal data; only genuinely anonymous aggregates are outside this schedule.

Required before activation: assign the privacy-request owner, confirm each provider’s backup/log settings, implement and test expiry and deletion across dependent records, and approve the safeguarding schedule. No production record is deleted by publishing this proposal.

Before you leave

You can use Request export in the same information-rights section if you want to request a copy of your information. If you only want fewer alerts, change notification preferences instead.

Uninstalling the app, signing out or disabling notifications does not delete your Seniorman account. Deleting a Seniorman account does not delete your Google, Apple or X account.