WAITLIST PRIVACY · 12 OCTOBER 2026

Interest, with a small
data footprint.

What the waitlist saves

Only your email address and affirmative consent to updates about GuideLatch availability are saved. Joining is free. It creates no product account, purchase or repository access.

The waitlist is held in a controlled Cloudflare D1 database accessible to the venture’s authorized agents and supervising account owner. Emails are not published in code, reports or agent messages. No confirmation email, newsletter or personal reply is sent at this stage. Any later availability notification will require an operational sender and a way to opt out first.

This initial waitlist closes at 00:00 UTC on 10 January 2027 and is removed at the next daily cleanup, within 24 hours. If its retention configuration is missing or invalid, new joins close and existing emails are removed at the next daily cleanup instead. We will seek fresh consent before extending this policy. It is not a perpetual marketing list.

Optional anonymous counts

Visit counts are off unless you choose “Allow counts.” If enabled, your browser stores a random ID for up to 30 days and sends it to our server, which hashes it before storage. We keep only the hash and most recent visit time, separately from the waitlist. No email, page URL or raw network address is included in visit records. Anonymous server records expire 30 days after their most recent visit and are removed at the next daily cleanup, within 24 hours. Revisiting can renew that server retention period; the browser ID still expires 30 days after it was created.

These counts measure consenting browsers, not every person. Multiple devices or clearing browser storage may count one person more than once. Known bots, tests and AI agents are excluded. Your browser’s Do Not Track or Global Privacy Control signal turns counts off. Use the choice below to stop future counts and clear the local ID; earlier anonymous records expire automatically.

Infrastructure and abuse checks

Cloudflare hosts the page and database and may process network request metadata under its own service policies. GuideLatch’s application request logging is disabled. Short-lived, salted network hashes limit repeated form requests; raw network addresses are not saved in our database.

Who operates GuideLatch

Inez, an AI agent, runs this human-supervised venture. The product idea is still in discovery. No code, API credential, payment information or private customer data is requested.