Privacy and A account

A account provides shared sign-in, profiles, friends and conversations for projects on andraz.org. It is operated by Andraž Čadež. For questions or data requests, contact andraz.cadez8@gmail.com.

Sign-in information

When you choose Google sign-in, we use your verified Google user identifier and display name to recognize your A account. Your display name appears in your profile and conversations. We request only the basic identity scopes openid and profile. We do not request or store your Google email address, access Gmail or Drive, or retain Google's access tokens after verifying your identity.

Other optional sign-in methods use the selected provider's verified identifier and the profile information needed for sign-in. Accounts are connected only through the account connection process; matching names or email addresses do not automatically merge accounts.

Local sign-in uses a username, a one-way password hash and expiring sessions. An optional email alias and recovery proof support local account recovery.

Email sign-in verifies your email address with an 8-digit code. We store a one-way hash of the code, bind it to the browser that requested it and expire it after 10 minutes. Resend processes your email address and the code to deliver the sign-in message from login@andraz.org. A verified sign-in email is stored as an account identity. Adding it to an existing account requires the account connection review.

Passkeys use your device or password manager to prove account ownership. We store the credential identifier, public key, security counter and device metadata, along with the name you choose and creation and last-use times. Your private key, device PIN, fingerprints and face data are handled by your device or password manager and are not sent to A account. You can manage passkeys in Email and passkeys.

Profile and conversation information

We store the profile details you choose, such as your display name, avatar, description, links and visibility settings. Friends, groups, invitations, messages, attachments and notification subscriptions support the features you use. We also store your conversation preferences, including pinned, archived, unread and muted states. Conversation access follows the account, participant and group permissions. Suggestions sent to the Suggestions channel are visible to the site owner.

Messages are not end-to-end encrypted. Device notifications are optional and require your browser's permission.

Hosting and security

OpenAI Sites and Cloudflare provide hosting, database and file storage, content delivery and connection security. Resend delivers email sign-in codes. The selected identity provider handles its sign-in screen. Cloudflare Web Analytics measures site visits and performance. Security checks use temporary hashed network and account identifiers to limit abuse.

Retention and your choices

Account data remains in the active database while the account exists. Sign-in sessions last up to 30 days. Approximate browser and device names and last-active times let you review and sign out your own sessions in Settings. We do not store raw device user-agent strings for this feature. Expired authentication records are removed during use, and security events older than 90 days are removed. Deleting a shared account removes its connected sign-in identities and associated data from the active account database.

You can edit your profile and visibility settings, manage connected sign-in methods and sign out from the account settings. For access, correction, export or deletion requests that you cannot complete in the interface, use the contact address above. Independent projects may also keep their own learning or game data, which is managed by those projects.