Privacy
Arcanaeum tracks which of Skyrim's books you have read and collected. This page says what it stores about you, why, where, and for how long, and how to get a copy of it or have it deleted.
Last updated
Who runs this site
Arcanaeum is an unofficial fan project run by bduffin. For requests regarding your data, email privacy@arcanaeum.app.
What is collected
Browsing without signing in stores nothing about you in the site's database. You can sign in with GitHub or with your email address. Either way, it stores:
- Your email address, when your account was created, and when you last signed in.
- If you sign in with GitHub, from your GitHub account: your name, username, profile picture address and GitHub account number, and whether GitHub reports your email address as verified.
- If you sign in with your email address: when you confirmed it, and any profile details sent when the account was first registered. The site's own form sends none, but software calling the sign-in service directly can; they are stored, and never shown on the site.
- An email address typed into the sign-in form, as soon as a code is sent to it, before it is confirmed. If it is never confirmed, it is deleted within two days of the last code sent to it.
- The one-time code emailed to you, stored as a hash rather than as the code itself, until it is used or replaced.
- For each device you are signed in on, when it signed in and when it was last used. The network address and software name recorded with it are the site's own server's, not your device's, because the server is what signs you in and keeps you signed in.
- For each GitHub sign-in, a short-lived record while it completes, which can hold the access GitHub grants the site to sign you in. It is deleted within two days.
- The books you mark as read or collected.
- Your choice of whether your collection is public or private, once you make it.
What is not collected
No analytics, advertising or tracking of any kind, and no payment details. Nothing is sold, rented or shared for marketing.
Why
To sign you in, which includes emailing you sign-in codes, and to keep what you save about the books. Nothing else.
Who handles it, and where
- Supabase runs the database and sign-in, in the United States, which is where your data is stored.
- Vercel hosts the site, in the United States and across its global network.
- GitHub is one way to sign in.
- Resend sends the sign-in codes by email, from the United States. It receives your email address and the code. Its open and click tracking are off, so it does not record when you read the email.
- Cloudflare runs the site's domain and forwards email sent to its addresses.
- Google's Gmail holds email about requests, in two mailboxes: the project's own, and the developer's personal inbox, which receives a forwarded copy of every message sent to the site.
Cookies
Only the ones signing in needs: session cookies that keep you signed in; cookies used during a GitHub sign-in itself, which hold only random values and are deleted when GitHub sends you back, or when you next sign in or out if you leave partway; and, while you sign in by email, one holding the email address your code was sent to, so that the address never appears in a web address. That one is sent only to the sign-in page, and lasts 10 minutes or until you sign in.
How long it is kept
- Your account and everything you have saved: until you ask for it to be deleted, when it is removed from the database straight away.
- Each signed-in device's record: until you sign out on that device, or on every device at once from Settings, or until it has gone about 90 days unused, when it is deleted and that device is signed out.
- An email address that is never confirmed: within two days of the last code sent to it.
- Sign-in records: at most two days.
- Sign-in emails: Resend keeps a log of each one it sends, including your address and the code, for 30 days. It expires on its own; deleting your account does not remove it.
- Request logs, which can include your IP address: up to 1 day at Supabase and 1 hour at Vercel. They expire on their own rather than being deleted with your account.
- Backups: there are none.
- Email about a request: kept for 12 months after the request is answered, in the project's mailbox, as the record that it was handled. The forwarded copy in the developer's personal inbox is deleted when the request is answered. Deleted mail stays in Gmail's trash for 30 days before Gmail removes it.
What is public
When you first sign in, you are asked whether your collection should be public or private. Public is selected to start with, and you can change your choice at any time in Settings, in the menu under your name at the top of the page. Until you choose, your account is treated as private.
- Private: nothing. No one else can see your collection, or even that your account exists.
- Public: anyone can see that your account exists and that it is public, identified by a random number the site gives your account, not by anything from GitHub or your email address, along with its username if it has one. Anyone can also list the public accounts.
Either way, your collection itself is visible only to you for now. Public collections are planned, and this notice will say what they show before they appear.
Your choices
- Ask for a copy of your data, or for its deletion, by emailing privacy@arcanaeum.app. The reply goes to the email address on your account, to confirm the request came from you before anything is done, and the request is answered within one month. An account that signs in by email can be confirmed only through that mailbox.
- A copy of your data holds what is stored about you in the site's database, except one-time codes and the access GitHub grants during sign-in, which are credentials rather than information about you. For an account registered by email, it can include profile details sent when it was first registered.
- Make your collection public or private at any time, in Settings.
- Sign out at any time, on this device, or on every device at once from Settings.
- If you sign in with GitHub, revoke the site's access to your GitHub account, in GitHub's settings under Applications, then Authorized OAuth Apps.
Changes
This notice is updated before any change to what is collected or made public, and the date at the top says when it last changed.