Privacy Policy

Last updated: 31 August 2026

Gilded Age is published by Gilded Age Ai LLC, Beta Building, Oficina 6, Próspera ZEDE, St. John's Bay, Roatán, Islas de Bahía 34101, Honduras. This policy explains what personal data we collect, why we hold it, how long we keep it, and what you can ask us to do with it. We keep collection to a minimum, and we do not sell personal data.

If you only want the short version: you can read the site without giving us anything. Everything below applies when you choose to sign up, comment, subscribe, apply to write for us, or contact us.

Who we are and how to reach us

Gilded Age Ai LLC is the data controller for the information described here. For any privacy question, including the requests described under Your rights, email [email protected], or [email protected] if you prefer. You can also write to us:

Gilded Age Ai LLC
Beta Building, Oficina 6
Próspera ZEDE
St. John's Bay, Roatán
Islas de Bahía 34101
Honduras

What we collect, and why

Reading the site. You do not need an account to read anything. We do not require you to identify yourself, and we do not build advertising profiles.

A reader account. If you create one, we store the email address you sign in with, and the profile you choose to fill in: a handle, a display name, and optionally a short bio, an avatar, and links to your own website, X or LinkedIn. Anything on your public profile page is visible to other readers, which is what it is for. Your email address is not shown publicly.
Lawful basis: performance of a contract, because we cannot give you an account without it.

Comments. We store what you write, when you wrote it, which article it was on, and the votes it receives. Every comment is automatically screened before it appears, and we keep the outcome of that screening (a visibility decision, a quality score used to order the thread, and a short reason) alongside the comment. A person can review and overturn any automated decision; email us if you think one is wrong.
Lawful basis: performance of a contract for the comment itself; legitimate interests for the screening, which exists to keep discussion usable and to keep unlawful content off the site.

The newsletter. When you subscribe we store your email address, the date and time you subscribed, the IP address the subscription came from, the page or form you used, and the exact wording of the consent you agreed to. We store that wording because consent means agreeing to something specific, and we should be able to show what that something was rather than ask you to take our word for it. We send you a confirmation email and add you to the list only when you click the link in it. If you never click, we do not send you a newsletter.
Lawful basis: consent.

Contacting us and enquiries. If you use the contact or advertising forms or email us, we keep your enquiry as a record (your name, email address, company if you give one, the subject and message, and the IP address it came from) together with a note of who dealt with it and when. We keep it for as long as it takes to respond and to keep a record of what was agreed.
Lawful basis: legitimate interests, namely responding to people who contact us.

Applying to contribute. If you apply to write for us, we collect your name, email address, a short biography, links you choose to give us, and the samples of your published work that you submit. We use an automated tool to read those samples and produce an assessment, which we store. It summarises the work and estimates how likely it is to be machine-generated. That assessment does not decide anything on its own. Every application is read and decided by a person, and you can ask us for the reasoning behind a decision, contest it, or ask a different person to look again.
Lawful basis: consent, and our legitimate interest in assessing people who ask to publish on the site.

Analytics. We use Google Analytics 4 to understand which coverage is read, and Cloudflare Web Analytics, which is served by our infrastructure provider. These tell us about pages and traffic patterns rather than about you personally, but Google Analytics does set cookies and Google processes the data on its own terms. See Cookies and your choice below.
Lawful basis: consent for Google Analytics. Cloudflare Web Analytics sets no cookies and runs on our legitimate interest in knowing which coverage is read.

Cookies and your choice

Google Analytics does not load until you say yes. On your first visit we ask, with Accept and Decline side by side and one click each. Until you choose, no analytics script loads, no request goes to Google, and no analytics cookie is set. Declining is not a lesser version of the site. Everything works identically either way.

You can change your mind at any time from the Cookies link in the footer, which also tells you which way your answer currently stands. Withdrawing takes effect immediately rather than on your next visit, and we expire the analytics cookies we can reach. It stops further collection; it cannot reach data Google has already received.

We ask again after twelve months rather than treating one answer as permanent.

Strictly necessary cookies are not part of this choice. If you sign in, the cookie that keeps you signed in is required for the site to work and does not need consent. You can only avoid it by not signing in.

Cloudflare Web Analytics sets no cookies and is not covered by the banner.

Who else handles your data

We keep the list short and we do not sell anything to anybody.

• Supabase: our database and sign-in provider. Stores accounts, profiles, comments and applications.
• Resend: our email provider. Sends sign-in links, newsletters, confirmations and enquiry notifications, and holds your address for as long as you are subscribed.
• Vercel and Cloudflare: hosting and network. They process the technical logs any website generates, including IP addresses, to serve pages and block abuse.
• Google Analytics: as described above.
• Anthropic: the provider of the automated screening described under Comments and Applying to contribute. Content submitted for screening is sent to their API and is not used to train their models.

Some of these providers operate outside the UK and EEA. Where they do, transfers rely on the standard contractual protections those providers publish.

How long we keep things

Why we keep the consent record after you unsubscribe. If you ask us to prove we were allowed to email you, we need the record of your consent to answer. Deleting it the moment you leave would destroy the only evidence that we did the right thing. It is kept minimal (your address, the timestamp, and the wording you agreed to) and it is deleted if you ask us to erase your data entirely.

Your rights

You can ask us to: give you a copy of what we hold; correct anything wrong; delete it; restrict or object to how we use it; or take it elsewhere in a portable form. Where we rely on consent, you can withdraw it at any time. Every newsletter has an unsubscribe link in its footer, and using it takes effect immediately.

Email [email protected], or write to the address under Who we are and how to reach us. We will respond within one month. If you ask us to erase your data, that removes you from our email provider's systems too, not only from our own records. You can also complain to your data protection regulator. In the UK that is the Information Commissioner's Office (ico.org.uk).

Changes

If we change this policy we will update the date at the top. If a change materially affects how we use data you have already given us, we will tell you directly rather than relying on you noticing.