# Privacy and browser storage

This is a description of the current implementation, not a policy for an unlaunched paid service.

Saved app identifiers and appearance preferences stay in browser storage. They do not sync across devices. Removing this site's browser data removes those preferences.

When Google sign-in is enabled, the authentication service stores the Google account identity, name, email address and avatar with server-side account and session records. An HttpOnly session cookie identifies the browser session. Browser preferences are separate from the signed-in identity. Signing in does not grant paid membership. Google applies its own privacy practices during sign-in. Provider configuration and deployment are required before public sign-in is available.

Production document pages on asoer.app load the Umami tracker at https://umami.sofxcking.cool/script.js for page views and client-side route changes. The tracker is restricted to the asoer.app hostname. It excludes query parameters and fragments from the recorded page URL. The /api/auth/* callback returns a server response and does not render the document shell. asoer.app adds no account identifiers or credentials as custom analytics properties. This integration notice does not describe Umami's referrer handling, request metadata or retention.

The Agents links open third-party websites with a shared, public question. They do not include searches, saved items, profile details, credentials or local server addresses. Third-party services apply their own terms and privacy practices. No chat API request is made by asoer.app.

[Reading guide](https://asoer.app/agents/index.md)