Privacy Policy

Clayo hosts help documentation. This policy covers two audiences: people with a Clayo account (“customers”), and people who read a docs site or use a support widget that a customer publishes with Clayo (“readers”). We collect the minimum needed to run the service, we don’t sell data, and we don’t run advertising trackers on any Clayo surface.

• Account: your email address, a display name, and an optional profile photo. If you sign in with Google, we receive your name and email from Google - nothing else.
• Session: a cookie that keeps you signed in. It’s essential to the service, not used for tracking.
• Team: the email addresses you invite to your projects, used to send and manage the invitation.
• Product usage: how you use the Clayo site and dashboard - pages viewed, clicks, and session recordings (with everything you type masked) - linked to your account email so we can help you and improve the product. This runs only on our own site, never on your docs site or widget.
• Error reports: when something breaks in the app, a technical report of the error is collected so we can fix it. Reports don’t include what you typed or your API keys.
• Content: the articles, project settings, and logos you publish. Public content is public by design - that’s the product.
• OpenAI API key (optional): stored encrypted, used only to serve your projects’ AI features, and never shown again after you save it. You can replace or remove it at any time.

Readers don’t have accounts, and we don’t identify or track them across sites. On docs sites and widgets we host for a customer, we process:

• Questions to the AI assistant: the question text and the AI’s answer are stored for 30 days so the site owner can see what their docs failed to answer, then deleted. Questions are sent to OpenAI to generate the answer - under the site owner’s API key, or Clayo’s own key while the site owner is within the included allowance. Don’t type personal or sensitive information into a docs assistant.
• Search queries: processed to return results; not stored as a per-reader history.
• Aggregate read counts: daily totals per article (e.g. “this page was read 12 times”). No reader identity, no advertising cookies, no cross-site tracking. Our product analytics never run on docs sites or widgets.
• Error reports: if a docs page or widget breaks in your browser, a technical report of the error is collected so we can fix it. It doesn’t include what you typed or identify you.

For this data, the site owner is responsible for their readers; Clayo processes it on their behalf.

To provide and improve the service: signing you in, hosting and serving your docs, answering readers’ questions, showing site owners how their docs perform, and sending transactional email (sign-in codes, team invites). We don’t sell personal data, and we don’t use your content or your readers’ questions to train AI models.

Clayo runs on third-party infrastructure: cloud hosting, a managed database, file storage and delivery, and an email delivery service - each processing data only to provide their service to us. AI answers and search embeddings are generated by OpenAI, product usage analytics are processed by PostHog, and error reports are processed by Sentry, each as described above. We don’t share personal data with anyone else unless the law requires it.

• Reader questions and AI answers: deleted after 30 days.
• Account data and content: kept until you delete the content, the project, or your account.
• Aggregate read counts: kept as statistics; they contain no personal data.
• Product usage events: kept for 12 months; session recordings and error reports for 30 days.

You can update your name and photo in the app, delete articles and projects (which removes their content), and remove your OpenAI key at any time. To access, correct, or delete personal data - or to ask anything about this policy - email support@clayo.com. If you’re a reader with a question about a specific docs site, contact that site’s owner first; we’ll help either way.

If this policy changes, we’ll post the new version here with a new date. Material changes to how we handle data will be called out, not slipped in.