Alamora
Privacy
What Alamora records, what it keeps in your browser, and the third parties that get to see you: the ad vendors, and the game publishers whose frames you play inside.
Who is responsible
Alamora is operated by operator legal name — to be completed by the site operator of operator postal address — to be completed by the site operator, which is the controller of the personal data described here. Privacy requests go to privacy contact email — to be completed by the site operator; see Contact for the other routes in.
What is collected, and why
Your account
An email address, a password (stored only as a hash, never in a readable form), a handle, a display name, an optional bio and profile title, and a date of birth. The date of birth is an age gate rather than a profile field: registration is refused below 13, and an account under 16 is created without direct messages or voice. The age is recalculated from the stored date on every request rather than frozen into a flag, and the birth date is never published on a profile.
If you sign in with a third-party provider instead of a password, that provider tells us the identifiers it chooses to release and we store the tokens needed to keep the link working. We do not receive your password from them.
What you write
Posts, replies, clips, guild messages, direct messages, reactions, pins, ratings and the reports you file. Guild channel history is capped at the most recent 500 messages per channel and notifications at the most recent 40 per person; older rows are deleted as new ones arrive. Pinned messages are exempt from that trim, because a pin is a deliberate act and a retention rule that silently deleted one would be a bug rather than a policy.
Direct messages are stored in plain form on the server and are not end-to-end encrypted. They are private between the two accounts in the thread, and they are readable by the operator — a moderator acting on a report about a message can see it. Do not use them for anything you would not put in an email.
What you do
Play sessions — which title, when it opened, when it closed and how many seconds of it the server was willing to credit. The browser sends a heartbeat while a game is open; it never sends a duration, and a session nobody closes is closed by a server-side sweeper. Also: favourites, library entries, recently played, quest progress, achievement unlocks, purchases in the coin shop, follows, blocks and mutes, and one row in an economy ledger for every XP or coin award. Leaderboards are computed from those rows.
What you send through the contact form
The name, email address, topic and message entered on the contact page are stored as a row on our server, together with your account id if you were signed in when you sent it. It is kept until the request has been dealt with, is read only by whoever handles it, and is not passed to any of the vendors named below. Sending it does not create an account or set a cookie.
Technical records
Each sign-in creates a session row holding the IP address and user-agent string of the browser it was created from, so an unfamiliar session can be recognised. The API keeps short-lived counters in Redis for rate limiting and for who is currently online. If error reporting is configured on a deployment, unhandled errors are sent to Sentry, which receives a stack trace, the URL and, for a signed-in visitor, the account id. Content Security Policy violations are posted to an endpoint on this site that records the blocked URL and the directive that blocked it.
What is kept in your browser
A session cookie once you sign in — that is what keeps you signed in, and there is no session cookie for a signed-out visitor. Beyond it, exactly two keys, both written by this site and readable only by it:
alamora-settings-v1in local storage — four interface preferences (theme, interface motion, sounds, and whether Alie is chatty). It exists because the theme has to be applied before the first frame is painted, which is earlier than any server round trip can answer. For a signed-in account the same four are also stored server-side.alamora-splash-v1in session storage — a single flag meaning “this tab has already seen the boot animation”. It is discarded when the tab closes.
Cookies and local storage lists these again alongside what the advertising and game frames set on their own.
Advertising, and the vendors behind it
Alamora is funded by display advertising served through Google AdSense. When advertising is enabled on a deployment, the following Google properties are contacted by your browser and may read or write cookies and similar identifiers in it:
pagead2.googlesyndication.com— the AdSense tag itself, which requests and renders the units;googleads.g.doubleclick.netandtpc.googlesyndication.com— ad delivery and the frames the creatives render inside;fundingchoicesmessages.google.com— Funding Choices, Google’s consent management platform, which presents the consent dialog and records your answer.
Google uses cookies and device identifiers to serve and measure advertising, and may personalise what you are shown based on activity across sites that use its ad products. What it collects, and the controls over it, are described in Google’s “How Google uses information from sites that use our services” and in Google’s privacy policy. You can opt out of personalised advertising by Google at My Ad Center, and reopen the consent dialog from the cookies page.
Ad units are never placed inside, over or against the edge of a game frame, and there is no advertising interposed between you and a game you have asked to play. That is a policy decision, and it is enforced in the code that owns the slot positions.
Advertising is off unless a deployment has been given a publisher account. Where it is off, none of the hosts above are contacted at all: the ad script is absent from the page rather than present and idle, so there is no third-party request and nothing to consent to.
Games and their providers
Each game page identifies its provider. Publisher embeds load a document from that provider’s domain inside a frame, and external games open the provider’s website in a new tab. The built-in catalog includes Famobi and GameMonetize; additional games and cover images may come from other configured providers. Hosted browser builds run from Alamora’s game asset directory.
When your browser loads a third-party game, its publisher controls that game. In particular:
- it can set its own cookies and storage, which we cannot read, control or clear from here;
- it runs its own advertising, including the spot that often plays before a title starts. That inventory is sold by the publisher. We cannot skip it, shorten it or remove it, and the stage says so on screen while it happens rather than letting a black frame read as a fault;
- it receives your IP address and user-agent, as any site your browser connects to does;
- it is governed by its own privacy policy, not this one.
What we do on our side of that boundary: the frame is loaded with a no-referrer policy, so the publisher is not told which Alamora page you came from, and no account information — your handle, email, id or session — is passed into it. Nothing crosses back out either, which is also why Alamora has no score, level or result for any game.
Voice chat exposes your IP address to the room
Guild voice is peer-to-peer. Establishing a call requires the participants’ browsers to exchange candidate network addresses through a STUN server, and those addresses — which include your public IP — are visible to the other people connected to the same voice channel, not only to us. That is inherent to how WebRTC works and is not something a setting on this site can switch off. Voice is unavailable to accounts under 16, and joining a channel is always an explicit act.
Who else sees any of this
Other users see what you publish: your handle, avatar, bio, profile title, level, achievements, posts, clips, guild messages and your position on a leaderboard. They do not see your email address, your birth date, your direct messages, your block or mute lists, or your session records.
Beyond that, data reaches only the vendors named above, the infrastructure providers that host the database and the application, and anyone we are legally required to disclose it to. It is not sold.
How long it is kept
Account data is kept while the account exists. There is no self-service delete button yet — the settings menu’s “Clear local data” only clears this browser’s theme and cached query state, and it says so — so deletion is done by asking: privacy contact email — to be completed by the site operator. When an account is deleted, the rows that hang off it — sessions, posts, messages, clips, progress, ledger entries — go with it by database cascade.
Guild channel history and notifications are capped as described above and roll off on their own. A specific retention schedule for server logs, session records and moderation history is retention schedule, to be set by the operator — to be completed by the site operator.
Your rights
Depending on where you live, you may have the right to see a copy of your data, correct it, have it deleted, object to or restrict certain processing, take it elsewhere, and complain to a supervisory authority. Write to privacy contact email — to be completed by the site operator from the address on the account, or from one you can prove controls it. The applicable law and supervisory authority for this service are governing law and authority — to be completed by the site operator.
Children
Alamora is not for children under 13, and registration is refused below that age. We do not knowingly collect personal data from anyone under 13; if you believe a child has an account, tell us at privacy contact email — to be completed by the site operator and it will be removed.
Changes
Material changes to this page will be announced in the app before they take effect. The date at the top is the last revision.