What we collect on the public site
Waitlist profile information you submit directly, such as name, email, company, role, and use case.
Basic site analytics through Plausible when enabled.
Privacy
Privacy should be clear before anyone connects real business data.
The public site and product should be explicit about what data is collected, what is connected, and what is intentionally outside scope.
Soft launchFounding accessBuyer-ready docs
Why this matters
Early buyers should not have to guess how the product is run.
Potsticker.AI should make its access model, privacy stance, and commercial boundaries obvious before a buyer ever has to book a call or email your team.
Clear boundaries for publishing, billing, and customer data.
A trust surface that matches the quality of the product itself.
Enough clarity for buyers, partners, and operators to move forward with confidence.
Security
Security
Platform protections, publishing boundaries, and operational safeguards.
Privacy
Privacy
How access, customer data, and account activity are handled.
Terms
Terms
The commercial baseline for using the product in a real business setting.
What the product can store when you use it
Project metadata, integration settings, queue state, incidents, subscriptions, analytics imports, and operator activity required to run the platform.
Only the systems you actively configure are turned on.
What we do not position the soft launch to do
We do not require your code to become public.
We do not frame this as anonymous consumer software; it is an operator product with deliberate onboarding.
We do not claim broad data portability or enterprise guarantees before those are fully hardened.
Ready to keep going?
Trust should feed the product path, not stop it.
Once the security, privacy, and legal basics feel clear, the next step should be obvious: watch the walkthrough or request launch access.
Next step