Privacy Policy

Sign-in and your account

ÆDRE requests only the openid, email, and profile scopes. After you choose Google sign-in, we use Google's stable account identifier to find or create your ÆDRE account. We also receive your email address, whether Google marks it verified, your name, and a profile image URL. We store the Google identifier and the available profile fields alongside an internal ÆDRE user ID and account timestamps in Cloudflare D1. An explicitly unverified email is not saved as your account email.

These details let us recognize the same account on later visits and show basic information on the Account page. We do not request access to Gmail, Drive, Contacts, or Calendar. The authorization code and ID token are processed during sign-in; ÆDRE does not store Google's access token, refresh token, or raw ID token in its database.

You can also sign in with email. In that case we store your verified email address as a sign-in identity attached to your internal ÆDRE user ID — email is a way in, not the account's identity key. To send and confirm the sign-in code, we create a short-lived verification transaction holding the email address, a keyed code verifier, its purpose (login, registration, or account linking), a validity window, and an attempt counter. A code works once, expires for authentication after ten minutes, and is allowed only a few verification attempts; the code itself is never stored in readable form.

Inside your Account you may explicitly link supported sign-in methods — for example adding Email sign-in to an account that started with Google. Linking is always an explicit, authenticated step: ÆDRE never merges accounts or identities merely because email addresses match.

ÆDRE may also store records of access rights (entitlements) tied to your internal user ID. Each such record holds the access right's key, its source category and source reference, its status, any validity window, and timestamps. These records govern what an account may access; they contain no payment data.

Sessions and cookies

When you sign in, ÆDRE sets a Secure, HttpOnly, SameSite=Strict session cookie so the site can recognize your browser. The database stores a hash of the session token, the associated internal user ID, a CSRF value, and session timestamps. A session has a maximum validity of 30 days. Signing out revokes that ÆDRE session and clears its cookie; it does not sign you out of Google.

A Google sign-in attempt also creates short-lived server-side state, including a PKCE verifier and nonce. This state can be used only once and expires for authentication after 10 minutes. Consumed and older expired records are removed during successful later sign-in activity, rather than by a scheduled deletion job. Email sign-in verification transactions similarly become unusable after ten minutes or first use; their rows remain for the time being as diagnostic history, holding no usable code.

Site analytics

On the production site, ÆDRE uses first-party analytics to count page views and approximate browser-tab sessions. The browser sends the page path without query or fragment, an external referrer's hostname when present, and a broad viewport category. Cloudflare request metadata supplies a country code. The database holds aggregate counters, not an individual event log. ÆDRE's analytics does not store raw IP addresses, user-agent strings, cookies, or persistent visitor identifiers.

Analytics does not send events when your browser reports Global Privacy Control or Do Not Track. A tab-only sessionStorage flag helps avoid counting the same open tab as a new session on every page.

Services, storage, and security

Google supplies the sign-in service. Cloudflare serves the site and stores ÆDRE account, session, and aggregate analytics records in D1. These providers process information to deliver their services and may operate in countries other than yours. ÆDRE does not sell Google account information or use it for advertising.

Transactional authentication email — the sign-in codes — is delivered by Resend. Resend receives the destination email address, the message itself (the code and its expiry), and the delivery metadata required to deliver it. Resend does not receive your Google profile data, the account database's contents, or entitlement records.

Sign-in is handled over HTTPS. ÆDRE checks Google's signed identity response and uses server-side session revocation, a hashed session token in storage, and cookie and CSRF protections. No internet service can guarantee absolute security.

Retention and data requests

While your ÆDRE account exists, its records remain for as long as the site needs them to work. This covers the account record, its linked Google and Email sign-in identity records, any entitlement/access records, and the sign-in verification transactions described above — including ended (revoked or expired) entitlement occurrences, which are kept while the account exists for audit and correct access evaluation. When the canonical account itself is deleted, its Email sign-in identity record, its account-bound linking transactions, and its entitlement records are deleted with it; other record classes, if any ever exist, may carry their own legally required retention — none do today. There is no automatic account deletion control today. Sessions stop working when they expire or are revoked, though their database rows are not currently removed by a scheduled job. Aggregate analytics counters have no fixed deletion schedule.

To request review, correction, or deletion of your account information, email the official channel listed on our Contact page:

support@aedre.space

Such a request covers your ÆDRE account record, its linked Google and Email identity records, its sessions, and its entitlement/access records; the aggregate analytics counters hold no per-account records to remove. We may need to confirm that the request concerns your account before acting. You may also stop using Google or Email sign-in and sign out of your ÆDRE session at any time. A request to ÆDRE does not delete your Google account or Google's own records.

Changes to this policy

We may update this page as the site changes. The date above shows the latest published revision. Questions about this policy can be sent to:

support@aedre.space