Updated: 5 October 2026
Privacy at Aion2Builds
This page explains which data Aion2Builds uses and which information is public. Reading guides and builds does not require an account.
Optional performance measurements
Measurements start only after consent in “Help make the site faster” at the bottom of the page. Our own endpoint stores aggregate LCP, INP and CLS values by UTC day, language, page category and small or large screen. It does not store nicknames, accounts, IP addresses, full URLs, visit identifiers or device details. No measurement cookies or external analytics service are used. Consent is stored locally and can be withdrawn in the same panel; DNT/GPC disables measurement. Statistics older than 30 days are excluded and removed when the dashboard is read or during further collection. Withdrawal stops future measurements; anonymous sums cannot be attributed to a player. Build confirmations store review type, patch, date, version fingerprint and the reviewer’s internal identifier, which is not public.
Google sign-in
With your permission, Google provides an account identifier and verified email address. We use these to create your account, preserve access to your builds, and identify votes. We do not request access to Gmail, Google Drive, or your contacts. New Google accounts use “Daeva” as their default public nickname. Your Google profile name and photo are not automatically published on builds.
Existing ChatGPT accounts
ChatGPT sign-in remains a separate way to access builds saved with that account. Google and ChatGPT accounts are not automatically merged, even if they use the same email address.
Guides, progress and followed builds
Player guides, their images, sources and author nicknames become public when published. Images also become public when attached to a published guide and cannot be removed from the library while public content still uses them. Guide drafts are stored locally in your browser. Build preparation checklists and followed builds are stored in D1 for your account and are not public. Updates to followed builds appear on the site; we do not send update emails. A published build history contains earlier saved versions; editing does not remove previous content from its history. Deleting a build also deletes its history, related progress and follow records.
Builds and votes
Published builds, descriptions, character choices, source links, and author nicknames are public. Account data, builds, and vote associations are stored in Cloudflare D1. We display vote totals publicly, not voters’ email addresses. We do not add your account email to a build. Do not include private information in public descriptions.
Reports and moderation
D1 stores the report reason and explanation, the reporter’s identifier and nickname, an excerpt of the reported content and author details needed for moderation. Reports and decision history are accessible only to authorized moderators. The reported excerpt remains in the history after content is edited or deleted. Hiding content and banning accounts restrict public access; they do not delete all records. Contact us about report data.
Screenshots and annotations
Uploaded images are stored in Cloudflare R2 and their metadata in D1. A new screenshot is accessible only to its owner until it is attached to a published build. Published images can be reused in other players’ build copies and remain public while any published build references them. You can permanently delete unused images from your screenshot library when no published build uses them. Deleting a local draft does not delete its server images. Remove visible private information before uploading a screenshot. JSON exports contain image identifiers and annotations, but do not include the image files themselves.
Drafts and device preferences
Build drafts, favorites, language, and reading preferences are stored in your browser’s localStorage. These are not automatically published builds. Clearing the site’s browser data can delete them. JSON export lets you keep your own copy of a draft.
Sign-in cookies
Sign-in uses essential session cookies. An Aion2Builds session lasts up to 30 days and may be renewed while you use the site. Short-lived cookies protect the return from Google. Signing out ends the session. The account system may store technical session data, such as IP address and browser information, to operate sign-in and limit abuse.
Providers and technical statistics
The site runs on OpenAI Sites and Cloudflare infrastructure. Google sign-in is also subject to Google’s policies. The Grindveil advertisement is a static link without tracking pixels or external advertising scripts. Clicking opens a separate website with its own policies. We do not add third-party analytics scripts. Hosting providers may process technical logs and traffic statistics to operate and secure the service.
Deleting data and contacting us
You can delete your own build after signing in. To request deletion of your account and related data, contact the email address below. We may ask you to confirm that the account belongs to you. Do not send passwords or sign-in codes. You can remove local drafts and preferences through your browser’s site-data settings.