Policies and account deletion

Configure documents in the panel

In Authentication → Terms and privacy, the owner configures Terms of Use, Privacy Policy and account-deletion information. Each document can use text hosted by the platform or the operator’s own public HTTPS page.

Enter the responsible operator, privacy contact and the providers and retention practices that actually apply to your service. Editable templates are a starting point for review; they do not guarantee legal compliance or store approval.

Draft, review and publish

Saving creates a draft. Review and publish it separately so clients can use the published version. Supported clients obtain the published policies from the server, allowing policy changes without rebuilding the application.

Interface language selection does not automatically translate the operator’s legal text. Review any multilingual policies yourself. An external page must remain publicly accessible; when its material content changes, update the published policy version too.

For the user

Policies are available at sign-in and in Privacy and account. The user can request deletion from Profile → Privacy and account → Delete account, or the published browser request route. Signing out or uninstalling the app is not deletion.

The deletion flow explains its consequences and asks the user to confirm account ownership. The result includes the request status; media cleanup may still be pending. Certain transaction and required operational records can remain as described in the operator’s published policy. Do not promise that every record is erased immediately.

Prepare your own release

Provide accurate service information, accessible policy pages and a functioning deletion process before submitting your branded application. Review the actual enabled SDKs and providers when completing store disclosures. Buying the source or changing a logo does not guarantee acceptance by an app store.