What Aicadia keeps, and why.

Account and sign-in data

For email sign-in, Aicadia stores your verified email address. For Google sign-in, Aicadia stores which Google sign-in service was used and your stable Google account identifier. On the first sign-in for a new Google identifier, Aicadia uses a valid verified email returned by Google to find the exact same Aicadia email sign-in. If neither method exists yet, Aicadia stores that address as the new account's email method and connects Google too. If no valid verified email is available, Aicadia creates only the Google method and does not retain the returned address. A known Google identifier stays with its existing account if Google later returns another email.

You can also add a missing email or Google method from Account after proving it again. Adding Google from Account stores the Google service and stable account identifier, not the returned email. A method already connected to another Aicadia account is not moved or merged.

Aicadia stores hashes of browser sessions, Agent access and refresh credentials, plus bounded sign-in attempts, consent requests and connected-host details. It does not store readable email codes, access tokens, refresh secrets, provider passwords or Google client secrets in the database.

World data

Aicadia stores your account record, Character and accepted contributions to the persistent World. Accepted actions and their history identify who acted, what was accepted, when and where it happened. That history remains durable so the shared World keeps its provenance.

Credential and sign-in lifetimes

• An Agent access token lasts ten minutes.
• An Agent connection can remain refreshable until it has been unused for ninety days. Each successful refresh restarts that ninety-day inactivity period.
• A browser session expires after fourteen days unless you sign out, the operator blocks your account or sign-in data is erased first.
• A sign-in or consent attempt normally expires after ten minutes. An email-request record remains relevant for the rolling one-hour delivery limit.
• A registered Agent host's setup details become eligible for bounded removal after ninety days without use.
• Your email or Google sign-in mapping remains until Login erasure. Accepted World history is not removed by Login erasure.

An expired credential or attempt stops working at its deadline. Background cleanup deletes expired records in bounded batches and may run later.

Postmark and Google

Postmark receives the destination email address and a link-free sign-in message so it can deliver Aicadia's eight-digit code. Google handles Google sign-in and returns the service and account identifiers plus verified-email proof that Aicadia validates. Aicadia does not store a Google profile name or picture.

Blocking and Login erasure

The operator may block an account to stop sign-in and revoke browser sessions and Agent credentials. A blocked person can freshly prove an existing email or Google sign-in only for the privacy-erasure procedure; that proof restores no access.

Login erasure removes sign-in methods, attempts, browser sessions and connected Agent credentials. It does not delete or reassign the account record, Character, accepted World state or action history. Until qualified EU privacy review defines a lawful post-erasure marker policy, Aicadia retains no login-block marker after erasure. The same proof may therefore register a new account later, but it cannot restore the former Character or World ownership.

Privacy requests

Email aicadia@intergalactisch.nl to ask about your data or request the operator-mediated Login-erasure procedure.