Visible in this tab
Dwell time, scroll depth, clicks, and coarse pointer activity can update the on-page demonstration in memory. They are not durable merely because the interface shows them.
PRIVACY BY ARCHITECTURE
What the site observes, remembers, and refuses to collect.
Eidos is a working demonstration of first-party digital marketing. That makes the boundary more important, not less: interaction can be visible in the current tab without automatically becoming a durable record.
Remembered only by choice
The site may remember your selected industry, role, and segment on this device when personalization is enabled. Otherwise those choices still work for the current session without persistent storage.
Measured only behind every gate
Measurement requires your analytics choice plus separate browser, server, and database switches. A credential or consent record alone cannot activate collection.
Withdrawal means cleanup
Turning measurement off removes its visitor ID, session ID, event-order counter, and acquisition context from this browser and requests deletion of associated first-party raw events whenever the hosted store is active.
The categories
Essential storage remembers the privacy decision so the site does not ask on every page.
Personalization remembers the audience selections you make in the top bar and carries explicit planning selections between sections in the current tab.
Measurement permits anonymous first-party events and any future consent-gated analytics integration.
What is not here
No advertising cookie, cross-site identity graph, purchased third-party audience data, or hidden email capture.
The public page remains usable when analytics, its database, or every optional choice is unavailable.
Raw first-party event retention is fixed at 90 days when collection is eventually activated.
Contact messages
The contact form asks for your name, email address, and message. Industry, role, and segment are optional text fields. Choices from the page are filled in for review and can be rewritten in your own words, cleared, or excluded before sending.
A submission includes the section you contacted Chris from and a received timestamp. It does not include browsing history, visitor identifiers, inferred interests, or marketing consent. Contact details are not sent to the analytics system.
Delivery and protection
When sending is enabled, Cloudflare Turnstile verifies the submission and Resend delivers it to Chris at chris@chrischerrydesign.com. Opening the enabled form loads the security check; its provider processes technical connection information for that check.
Submission limits use a keyed hash of your connection address and the attempt time in a separate Supabase security store. This store does not receive your raw address, message, name, email, or audience selections. It keeps at most 20 attempt records; expired records are removed when the next submission reaches the attempt check. Separate daily and monthly counters limit total email attempts. These protections are separate from optional analytics.
Messages are used to respond to your inquiry, not to subscribe you to a mailing list. They are retained in the email systems, not saved in the analytics database. The 90-day analytics retention rule above does not apply to correspondence. Email Chris to request deletion of a contact message.
If delivery or the required protections are not configured, the form cannot send. A direct email link remains available.