Your Attance account and your data
These notes explain what the email sign-in and saved collections store. They supplement the operator’s general privacy information.
Who to contact
Attance is operated by IT-Beratung Dr. Brunzel. For questions about your account or your data, contact info@contextoid.com.
Your email and sign-in code
We store your email address and when your account was created. Your address identifies your account so that you can sign in on another device. It is not displayed publicly. You do not set a password.
When you request a code, we email it to the address you entered. The code is valid for ten minutes, works once, and must be entered in the browser where you requested it. The database keeps a protected verification value rather than the readable code. Incorrect entries and repeated requests are limited.
The sign-in emails are sent through Host Europe using the operator’s existing mail service. The mail provider processes the recipient address and email content to deliver the message. For now, the sender is Attance with the address info@contextoid.com.
Registering does not subscribe you to a newsletter or marketing emails.
Optional sign-in with Google
Where Google sign-in is offered, the account page loads Google’s sign-in component. Your browser connects to Google, which can receive network and browser information. When you choose to continue with Google, Google sends Attance a signed confirmation of your Google account identity, email address and verification status, and an organization domain where applicable.
We check that confirmation and store Google’s account identifier, the Google provider identifier and the time the connection was created, linked to your Attance account. A Google name or profile picture may be included in the confirmation; Attance does not store or use them. We do not receive your Google password or request access to Gmail, Drive, contacts or other Google account content. We do not keep Google access or refresh tokens.
We use these Google account details only to authenticate you and reconnect your saved collection. We do not use them for advertising or send your saved game progress to Google. A short-lived browser cookie and protected verification values prevent a sign-in confirmation from being reused in another browser. This verification expires after five minutes; repeated requests and invalid confirmations are limited.
You can continue using email codes. For some email addresses, we require an email-code sign-in before you can connect Google. The Google connection remains stored until your account data is deleted. You can manage consent in your Google Account; signing out of Attance ends the Attance session on this device.
Saved games and collections
Your account is linked to saved player collections in our existing games database. These can contain unfinished rounds, completed results, created tasks and invitations. When you register, existing guest progress from that browser can be attached to your account. If another collection already exists, it is retained separately so that one game does not overwrite another.
Some older games use separate player credentials. We store the credentials needed to reopen those games in encrypted form and link them to the appropriate collection. They are not part of public invitation links.
What stays on your device
A sign-in cookie keeps this browser connected to your account for up to 90 days. A short-lived cookie connects a requested code to its browser. Additional functional cookies protect requests and identify game progress. Signing out on a device ends its account session.
Games also keep local copies, drafts and pending saves in browser storage. Account collections are kept in separate storage areas. These copies can remain until you remove website data in your browser. Signing out preserves the server’s saved progress; clearing browser data can remove work that has not yet reached the server.
Retention and deletion requests
The account and its linked progress remain stored after you sign out or a sign-in expires. There is currently no automatic account expiry or self-service account deletion. To request access, correction or deletion, contact info@contextoid.com. We may need to verify that the account belongs to you.
To limit repeated code requests, we keep protected comparison values derived from the email address and network address, with request times. The account service does not store the readable network address in these records. Request records older than two days and code-verification records more than one day past expiry are cleaned up when subsequent code requests succeed. If there are no subsequent requests, those records can remain longer. An expired code or session cannot be used to sign in, even if its database record remains.
General server logs and backup handling are separate from these account records; the operator’s general privacy information also applies.