Delete your LoveBox account

Request deletion without the app

The planned operator-assisted email route will not require reinstalling LoveBox or signing into the app. Servisite is the confirmed company name; full legal identity and contact details still need confirmation.

No verified deletion email address is available yet.

Once the operator supplies a monitored address here:

1. Email that address from the email associated with your LoveBox account.
2. Use the subject LoveBox account deletion and state: "Please delete my LoveBox account and its associated data."
3. Respond to the operator's mailbox-ownership confirmation. This protects you against someone else requesting deletion of your account.

Never send a password, sign-in token, identity credential or intimate information. Partner details are not needed. If you no longer control the account mailbox, request a manual identity review; deletion cannot proceed until ownership is safely established.

The operator must verify requests and follow deletion work to completion before this route is offered. This page has no form and sends no request itself. Email correspondence is handled by the operator and email providers.

Request deletion in the app

1. Open Settings, then Your data & choices, or open the Privacy & consent icon.
2. Choose Delete account.
3. Complete recent identity verification through the hosted sign-in flow or the purpose-bound email-code fallback, then confirm deletion. Never send that code to support.

When the server accepts the request, sharing stops and both accounts are unpaired. Deletion runs in the background; a requested/scheduled message does not mean erasure is already complete.

What is removed

The target deletion worker removes application personal data, device tokens, invitations and associated work, then deletes the Microsoft Entra External ID customer identity. Both signals and pairing pointers are cleared when the request is accepted. Your partner's separate account is not deleted.

An unverified signup cannot erase invitations by claiming another person's email. Requests about those invitations need separate mailbox verification and operator review.

Timing and remaining copies

Background work retries failures; actual scheduling and directory deletion must be verified before release. No fixed erasure deadline is promised. Minimal access-restricted identity tombstones prevent recreation by still-valid tokens until directory deletion, token lifetime and recovery retention are satisfied.

Provider-managed logs, backups and email records follow separate retention and are not instantly erased by the app. Seven-day database recovery retention is proposed, not verified; backups can hold earlier snapshots. Actual settings, tombstone retention and support-request retention must be finalized before release. Already delivered emails, screenshots and saved JSON exports are outside application cleanup.

The operator must explain completion and any legitimate remaining retention, and meet applicable legal response obligations. Read the privacy retention details.

Stopping sharing without deleting

Turning off your own signal, resetting both, unlinking or withdrawing consent is separate from account deletion. Unlinking and withdrawal end the pair and clear both signals; withdrawal leaves the account available for export or deletion. Uninstalling the app alone does not delete the account.