Account-linked data is retained while the account is active unless removed through available controls. Request deletion in More → Delete account or on the account deletion page, without installing the app. Verify ownership with your password or the available email verification method and confirm deletion.
An accepted request blocks the account while personal records, account-linked files, notification registrations, authored Community content and the Auth identity are removed. Failed cleanup remains pending and can be resumed; an incomplete request is not presented as complete.
Other current-version installations clear local account data when they next connect and detect deletion. Offline devices cannot be remotely erased. Unlinked public food catalog contributions and records held independently by other providers may remain.
While a deletion request is pending, its server record retains the account identifier, a random receipt hash, state and attempt timestamps so cleanup can resume. It is not marked complete until the required cleanup succeeds. Completion removes the account identifier from that receipt. The existing completion and pending-job procedures remove completed receipts that meet their age-based cleanup condition when those procedures run; this is not an exact removal deadline or proof of a current successful cleanup run.
Community publishing with in-app Bell notifications is active. Protected administrative approval and publication audit records are separate from ordinary profile and diary data.
The mobile publication audit retention update is installed, and minimization of future records has been explicitly enabled. New records on this path omit the actor account identifier and the published-content snapshot; request and post identifiers, hashes, timestamps, audience information and execution evidence remain. This reduces personal data; it does not make every retained field anonymous.
Historical protected records can still contain an actor identifier and content snapshot. Their retention or authorized disposition requires separate decisions and respects applicable holds. Audit erasure through account deletion has not been enabled. R4 approval records and other protected audit records are not automatically deleted when an account is deleted. Immutability supports accountability; it does not itself establish a legal requirement or justify indefinite retention.
Security and transport logs can contain IP addresses, request metadata and security events for operating and protecting the service. Cloudflare hosts this website; Supabase, Firebase/Google, the authentication email provider and the API hosting operator can hold separate operational records.
Database exports and provider backups can contain older account data. These separate copies are outside the account-deletion API. Provider log expiry, backup rotation and deletion controls after a restore have not been verified here. Installing the controlled mobile audit retention mechanism does not set an automatic expiry for historical records. No automatic erasure or fixed retention deadline for these copies is promised.
Google handles data retained by its services under its applicable policies; deleting a VEZVO account or changing UMP choices does not itself delete those provider records. Contact support@loxter.ai about retained data; a request does not itself guarantee erasure of a protected or provider-held copy.
