Privacy policy

1. Information we process

Participants can ask without signing in. We process a hash of a random participation token, the chosen nickname and language, questions, votes, reports, attachments, and limited timezone, platform, viewport and browser details needed for reliability. The participant screen does not ask for a name or email.

Operator accounts may include an authentication email, workspace role, project and session settings, API-key hashes and usage records, and webhook delivery state. Raw API keys and webhook signing secrets are shown only once after creation.

2. Why we use it

• Receive anonymous questions, deduplicate votes, review content, and provide answers and reports
• Prevent abnormal repetition, harmful content and security incidents
• Store attachments privately and provide short-lived access links
• Operate project metrics, APIs, webhooks and recovery

3. Retention and deletion

Project data is kept until the operator deletes the project or account. On deletion, linked private files are queued and retried before question metadata is removed. Incomplete upload reservations and temporary API retry records are removed regularly after they expire.

Account and workspace information is retained as needed to provide the service and meet legal obligations. If deletion affects other members or project records, ownership transfer or workspace-deletion confirmation may be required.

4. Service providers and transfers

The deployment operator may use infrastructure providers such as Supabase for authentication, databases and file storage, and Vercel to run the web application. Actual processing regions and subprocessors depend on the deployment's contracts and project settings.

5. Rights and contact

Operators can delete project data and deactivate resources in the admin area. Send access, correction, deletion, restriction or privacy requests to cleverlywittyapps@gmail.com. For participant requests, include the project link, question text and approximate submission time when possible.