Privacy Policy

Book waitlist. When you join, we collect your first name, last name, and email address. We record when you joined, whether a confirmation was sent, and whether you unsubscribed. We use these records to confirm your signup and send the book launch announcement. Announcement delivery records can include delivery status and an email-provider message identifier.

Field Guide access. We process your email address and entered access code to check eligibility and send verification or sign-in links. We keep access-request records, including whether access was accepted, and reader-account and code-redemption records. Entered codes in access-submission records are encrypted.

Reader assessments. For readers signed in with an email-linked account, unfinished assessment answers and the current section are saved so you can resume. Completed answers, including any optional written reflections you provide, are saved with scores, result category, and completion date to support your progress history. Retakes add a new result rather than replacing earlier results.

Messages to us. If you email us, we receive the information you include so we can respond. Please do not include access codes, sign-in links, or unnecessary confidential information in a privacy request.

Assessment answers and results are not published or displayed to other readers. Reader-facing access to saved work is restricted to the signed-in account. Optional written reflections are not required; avoid including confidential information about other people or customers.

Private does not mean inaccessible to authorized technical operators or service providers that maintain the service. Assessment reflections are not stored in shared-browser local storage; supported resumable drafts are saved on the server and associated with your reader account.

We process technical request information to operate and protect the site. Application request logs include the request method, URL path, response status, and request identifiers. Rate limiting uses a keyed value derived from an IP address to limit repeated attempts. Hosting and delivery providers also process technical information needed to provide their services.

Access controls and security measures help protect information, but no internet service can guarantee absolute security.

The site uses authentication cookies to keep readers and administrators signed in. Logging out clears the relevant authentication cookie. Your browser settings may let you block or remove cookies; blocking authentication cookies can prevent protected Field Guide features from working.

The site supports Replit website analytics when enabled, including traffic measurements such as page views, referrers, countries, browsers, and devices. It also supports custom worksheet-download events that record the worksheet identifier, file format, and whether a download succeeded or failed. These custom events do not include email addresses, access codes, or assessment answers.

We use Google Tag Manager to manage website measurement tags, including Google Analytics when configured by the site owner. Google receives technical connection information when the container loads. Tags configured through the container may use cookies and process browser, device, and usage information. Our integration loads the container on public production pages and supplies public-page events with query strings and fragments removed from page URLs and referrers limited to their origin. It does not supply names, emails, access codes, assessment answers, or protected reader-page events. The owner controls the tags and their triggers in Google Tag Manager. Browser privacy tools may let you block measurement.

The site loads fonts from Google Fonts. Your browser requests those resources from Google, which receives technical connection information.

We use Postmark to deliver verification, sign-in, waitlist, and book launch emails. Delivery requires sharing the destination email address and message content with Postmark. We use Replit hosting, database, and private file-storage services to operate the website and provide the Field Guide.

Authorized site administrators can manage reader access and view or export access submissions and waitlist entries. Service providers process information needed to deliver and maintain their services.

Field Guide access-submission records are scheduled for deletion after 365 days. Expired authentication-session and rate-limit records are scheduled for cleanup.

Reader accounts and completed assessments are retained to support reader access and progress history, without automatic deletion for inactivity. They can be removed through a verified, owner-approved deletion request. Sign-in token records are scheduled for cleanup 30 days after their expiry; this does not remove reader access.

Waitlist and announcement delivery records are eligible for owner review 365 days after unsubscribe or confirmed launch delivery, using the latest relevant event. This is a review threshold, not an automatic deletion deadline. Pending or uncertain sends are excluded. Approved cleanup removes names and resolved delivery details while retaining a minimal email suppression record so the address is not added back to announcements.

On whole-account deletion, matching buyer codes are retired rather than made reusable. Their redemption markers remain without the reader email address.

Saved assessment drafts are replaced as you save changes and removed when you discard them or complete the assessment. Signing out or unsubscribing does not by itself delete your stored account or assessment history.

Provider logs, backups, and admin-exported copies are separate from application cleanup and require separate handling. We cannot promise deletion from copies outside the application's control. Contact us to discuss those copies and any limits on your request.

You can stop book launch announcements using the unsubscribe link provided with the announcement, or contact us for help. Unsubscribing does not change your Field Guide access. Requested verification and sign-in emails are separate from book announcements.

Supported reader accounts can discard an unfinished assessment draft and export a summary of completed assessment scores. That summary is not a complete export of all personal information.

Email hello@everybodyin.ai to request access to, correction of, or deletion of your personal information. For deletion, we send a fresh, single-use confirmation link to the email concerned. The confirmation page explains the requested scope: assessment data only, waitlist data, or the whole reader account. You must explicitly confirm; opening the email link does not delete information. The owner reviews and separately approves deletion. Whole-account deletion ends Field Guide access; assessment-only or waitlist deletion does not.

If you no longer control that email address, contact us for manual review; supplying an email address alone is not proof of identity. Incomplete deletion-request records expire after 30 days. Completed requests retain a minimal operational record of the scope, dates and approval reference, without the email address or confirmation token. A minimal email suppression record and retired code-redemption records may remain as described above. The rights available and any limits on a request depend on applicable law.

We will post changes to this policy here and update the date shown on this page.

For privacy questions or requests, contact Digital Ignitor, LLC at hello@everybodyin.ai.