DRAFT. Not a legally binding text. A lawyer has to review this before launch, and the placeholders have to be replaced.
Privacy (draft)
This text describes what the early Ready4Bots site actually does. It is not legal advice and not a finished privacy policy.
Who is responsible
[Name and address from the legal notice]. While those are still placeholders, this notice is only a draft.
Waitlist
If you join, we store your email, an optional company URL, the status pending or confirmed, a hash of the confirmation token, and the timestamps. The token itself is not stored. Only the link in the confirmation email sets the status to confirmed. Without mail sending, the entry stays unconfirmed.
Bot-Ready-Check
You enter a public URL. Our server fetches that page and a fixed list of public paths (robots.txt, llms.txt, sitemap, Agent Card, OpenAPI, MCP, bot-ready.json). We store the report: URL, level, points, findings. We do not store the full page. We refuse private networks, credentials in the URL, and unusual ports.
What we do not store
No account, no payment data, and no analytics cookies from us. The IP address is used only briefly in memory to limit requests. It is not written into the waitlist or the report.
Who else sees it
Hosting can run on Vercel. If DATABASE_URL is set, the records live in Postgres at whichever provider that string points to. Confirmation email is sent only when RESEND_API_KEY and WAITLIST_FROM_EMAIL are both set, then via Resend. Without those variables, addresses are not sent to an email provider.
How long
Until you ask for deletion, or until we replace this draft with a binding retention period. Locally, without a database, the records sit in a JSON file on the machine that runs the app. On Vercel, without DATABASE_URL, nothing is stored.
Your rights
Access, correction, deletion, restriction, portability, and objection under the GDPR, plus a complaint to a supervisory authority. To delete an entry, write to [insert contact@example.com] once that address is published in the legal notice.