Privacy policy

What we need

You can browse public questions without an account. When you sign in, Clerk provides an account identifier, authentication state, and some account details you choose to share. Your account can store progress, favorites, Track Preferences, and submissions.

How we use it

We use data to provide the catalogue, sync your state across devices, protect the service from abuse, and review community contributions. We do not sell your data or use it for behavioral advertising.

Service providers

Authentication is provided by Clerk, the Node backend runs on Vercel, and the frontend is hosted on Cloudflare Pages. The backend talks to the database on the browser’s behalf; the browser does not connect to the database directly. Submissions may be sent to GitHub for review.

Public contributions

A contribution you approve for publication may become public after review and can include your display name, content, and submitted references. Do not send personal information you do not want published.

Retention and deletion

We keep data while it is needed to provide the service or complete moderation work. To request correction or deletion, open an Issue in the project repository without posting sensitive information.

Security and updates

We use reasonable access controls and operational practices to protect data, but no internet service can promise absolute security. We may update this policy as the service changes and will publish the current version here.