A simple privacy policy.
What this is
We’re a small team testing demand for a proposed service. The service is not available yet. We are not delivering work, operating a customer pilot, selling anything, or taking payments. A brand name is not a legal entity.
What the waitlist asks
We ask for your email and qualifying context: a public app or site URL, platform, business type, or a non-sensitive description of what is broken or what you would automate. These details help us understand interest and prioritize what to build. They are not a work order or permission to access private systems.
How we would use it
After a separately approved launch of this waitlist page, we would use your answers only to measure demand, prioritize development, manage the waitlist, and email you if early access opens. There is no confirmed launch date. Consent is limited to this waitlist and its opening notification, not unrelated marketing. Joining creates no purchase, service, or subscription.
No sensitive information
Please do not submit passwords, API keys, source code, logs, IP addresses, customer lists, customer information, or confidential business data. We do not need system access to measure interest.
Local preview and processors
This local preview uses no tracking cookies, advertising pixels, third-party analytics, or external fonts. Local submissions are intercepted in your browser: nothing is sent or saved by the site. If approved for publication with Forms enabled, Netlify would process waitlist submissions and hosting logs under its own terms. Only authorized people and necessary service providers should have access. Waitlist information would not be sold.
Proposed retention
The proposed retention is 90 days from signup or the last direct waitlist interaction, unless you request deletion sooner or legal needs require a different period. Continued participation beyond that would need a renewed choice. Provider backups may differ. This policy must be confirmed before public collection.
Leaving the waitlist
You may withdraw consent and request access, correction, or deletion using the contact or unsubscribe route published with the live waitlist. Every eventual opening email must include a simple opt-out. Those channels and email delivery are not configured locally and must be set up before real entries are collected. No opening email has been sent.