Homer

The Homeric Record

A permanent public record for those who wish history to know where they stood.

Policy

This page explains what information The Homeric Record collects, what is public by design, and how your data is handled. It reflects how the site actually works.

Signing is public by design

Signing the declaration creates a permanent, public entry in The Homeric Record. The name you submit, your signatory number, your public record page, and your placement within the Living Record are all public by design. Do not submit a name you would not want shown publicly.

Once submitted, a signature becomes part of The Homeric Record and cannot be edited, replaced, or withdrawn through the site. Signatory numbers and positions within the Living Record are permanent and are not reassigned. This does not prevent you from contacting us regarding your personal information or exercising any rights available to you under applicable law.

Email and claiming

An email address is collected only if you choose to claim your record. Claiming associates your email address with an entry that already exists from signing and allows us to send your confirmation. Your email address is never displayed publicly.

Claiming your record is free. No payment or purchase is required to claim a record.

Marketing is optional and separate

When claiming, you may optionally consent to receive email dispatches from the project. This option is unchecked by default and is entirely separate from signing and claiming. The transactional confirmation email you receive when claiming is not marketing email. Marketing dispatches are sent only to those who have explicitly opted in.

Service providers

To operate the site, we rely on a small number of service providers: Supabase for database services, Vercel for hosting and delivery, and Brevo for transactional email. Data necessary to operate The Homeric Record may be processed by these providers on the project’s behalf.

Analytics and cookies

With your consent, this site uses Google Analytics (Google LLC) to measure, in aggregate, how the site is used — which pages are visited, how visitors arrive, and on what kinds of devices. This helps us understand and improve the site. The legal basis is your consent, given through the cookie banner; analytics is never loaded before you accept it, and declining does not affect any function of the site, including signing and claiming.

When analytics consent is given, Google Analytics sets first-party cookies (named _ga and _ga_…) and processes usage data such as pages viewed, referrers, approximate location derived from your IP address, and device and browser information. This processing may take place on Google servers outside your country, including in the United States, under Google’s applicable data-transfer safeguards. We do not use analytics data to identify you.

The signature event is linked to Google Ads as a conversion. This means that when you have allowed Analytics, a successful signature causes Google to send a further measurement request to a second destination, pagead2.googlesyndication.com, in addition to the ordinary Google Analytics request. This happens even when advertising consent is denied. We describe it plainly rather than imply otherwise: denying advertising does not mean that no request reaches Google Ads infrastructure. What denying advertising does mean is that the request is sent cookieless and non-personalized — no advertising cookie is set or read, no advertising identifier is used, the request is not used for personalized advertising, and Google is signalled that advertising storage, advertising user data and advertising personalization are all denied.

That request is not anonymous, and we do not claim it is. Like the Google Analytics request beside it, it carries Google’s standard consented transport metadata: the consent signals themselves, the measurement identifier, the page URL and page title, device, screen and browser information, and client and session identifiers generated by Google Analytics.

What it does not carry is anything you submitted. No signatory name, signature number, email address, database identifier, claim token, or any other record data is attached to the analytics or advertising request as a custom parameter. The event is sent as a bare event name with no custom event parameters and no user properties of any kind.

Advertising consent is asked for separately and is denied unless you grant it. Granting it enables Google Analytics advertising features, known as Google Signals: advertising cookies, the building of remarketing audiences in preparation for future advertising, and personalized advertising. With advertising consent granted, the Google tag additionally contacts Google advertising endpoints, including stats.g.doubleclick.net and Google’s /ads/ga-audiences endpoint, and Google may associate that activity with a signed-in Google account where the account holder has allowed it. Without advertising consent, none of that happens: no advertising cookie, no advertising identifier, no personalization, and no audience building. The project may run advertising campaigns on Google and Meta platforms; the measurement described on this page is how their effectiveness is assessed. Analytics and advertising remain independent choices, and granting one does not grant the other.

With advertising consent, this site also uses the Meta Pixel (Meta Platforms, Inc.) to measure our advertising on Meta services such as Facebook and Instagram. The pixel is never loaded before you grant Advertising in the cookie banner: without that grant, no Meta script runs, no Meta cookie is set, and no request of any kind is sent to Meta. When you have granted it, the pixel sets first-party cookies (_fbp, and where applicable _fbc), records page views, and reports a conversion event when a signature is accepted. This processing may take place on Meta servers outside your country, including in the United States, under Meta’s applicable data-transfer safeguards.

The signature conversion event sent to Meta carries none of what you submitted: no signatory name, signature number, email address, database identifier, or claim token. Beyond Meta’s standard consented transport metadata, its only attached value is a randomly generated event identifier that maps to nothing in our records and exists solely to prevent the same signature being counted twice. Withdrawing advertising consent stops all further Meta measurement and deletes the Meta cookies.

You can withdraw or change your choice at any time through “Privacy choices” — the shield beneath the copyright line in the footer of every page. On rejection or withdrawal, analytics and advertising features stop and existing Google cookies (_ga, _ga_… and _gcl_…) are deleted. Your consent choice itself is stored on your device as a strictly necessary preference.

Permanence and moderation

The permanence of the public Record is an intended part of the project. Entries are not ordinarily edited, replaced, or removed after submission. The project nevertheless retains the authority to moderate, redact, or remove content where reasonably necessary, including in cases of misuse, abuse, impersonation, legal obligation, or other exceptional circumstances.

Your requests

You may contact the project to request information about personal data associated with your record or to make a privacy related request. Where applicable, requests concerning correction, deletion, or other rights will be handled in accordance with applicable law.

For privacy or data requests, contact lets@wokeodyssey.com.