Privacy · Effective 18 September 2026
Privacy and cookies
This policy explains what information Erya processes when you browse the archive, create a reader account, or send information through the site.
Reader accounts and saved preferences
Supabase provides Erya’s authentication and database services. A reader account uses your email address and authentication data managed by Supabase. Titles you track, adaptation votes, news choices, muted authors, and your saved light or dark theme are linked to your Supabase user ID so those choices can follow you across devices.
Information you submit
Title suggestions and correction reports contain the catalog information, explanation, and supporting links you enter. Contact messages contain your name, reply email, topic, subject, and message. Erya stores these records in Supabase so moderators can review them, respond where appropriate, maintain the catalog, and investigate abuse. Please do not submit private or sensitive personal information.
Security and anti-spam information
Public submission, correction, and contact forms use Cloudflare Turnstile for human verification. Turnstile receives the verification token and technical information needed to assess the request, including the request IP address. Erya also combines the request IP address and browser user-agent with a private salt, stores only the resulting one-way hash for rate limiting, and removes rate-limit records older than 24 hours when the rate limiter runs.
Automated content screening
The text in title suggestions and contact messages is sent to OpenAI’s moderation API for automated safety screening. A title suggestion that is flagged, or cannot be screened, is quarantined for moderator review rather than published automatically. Screening supports site safety and does not replace human moderation. Correction reports are not sent to OpenAI by the current implementation.
Cookies and local storage
Supabase uses essential authentication cookies to maintain signed-in reader and administrator sessions. Erya stores your light or dark theme in browser localStorage and in an erya-theme cookie with a one-year lifetime so the correct theme can be applied when a page first loads. For signed-in readers, the theme is also saved to the account in Supabase. These preferences are used for display, not advertising.
Analytics
Erya uses Cloudflare Web Analytics and Umami Cloud on the production website to understand aggregate site traffic and usage. Umami records information such as visited pages, referrers, browser, operating system, device, screen size, language, and approximate location. Umami uses the request IP address to derive location information but does not store the IP address, and its analytics do not use cookies. Netlify hosts the application, while Cloudflare provides delivery, security, analytics, and Turnstile services; these providers process ordinary web-request information needed to deliver, measure, and protect the site. Erya does not include advertising or behavioral-advertising scripts, and no affiliate tracking system is currently implemented.
Other service providers
Resend sends operational notification emails to the site administrator when forms need attention. Erya’s server requests book-cover search results and cover images from Open Library, then serves available cover images through Erya’s own image endpoint. Erya serves its website fonts from its own deployment rather than making your browser request them from Google. External source links take you to third-party websites only when you choose to follow them, and those sites have their own privacy practices.
Retention and your choices
Account data and saved reader preferences remain while your account is active. Signed-in readers can use the “Privacy & data” section of the account page to download a JSON copy of their account details and saved reader data, or permanently delete their Supabase authentication identity and linked reader preferences. Rate-limit fingerprints are removed after 24 hours. Automated moderation reasons are retained for no longer than 90 days; active administrator or editorial reasons may remain while a case is unresolved. Resolved or deleted contact messages and resolved correction reports are retained for up to 12 months after their last review or resolution, then deleted. Accepted factual adaptation and catalog information may remain indefinitely after transient moderation or contributor metadata is removed. Catalog submissions, corrections, and contact messages are not linked to reader account IDs and therefore require separate review through the privacy contact route when applicable.
Questions and requests
Use the contact page and select “Privacy or data request.” This policy will be updated when Erya’s data practices or service providers materially change.