Cliodo
English
English Tiếng Việt Español Português (BR) Français Deutsch Bahasa Indonesia ไทย 日本語 한국어 简体中文 हिन्दी

Privacy

What information a room needs to work, and how it is handled.

Information used to run a room

A host can add a room title, decision options and timing settings. Guests can submit their responses, and the host can lock a shared outcome. These details are stored so the room can display the responses and final result.

Guests and accounts

Guests can open a room link without creating an account. They may provide an alias and submit availability or option responses and comments. Hosts can add a room title, options and timing settings, then lock a shared outcome. Hosts may sign in with email or choose Google sign-in; the service receives the email and basic identity information needed for that sign-in.

The app uses room-scoped session cookies to authorize host and participant access. A signed-in host session is also kept in browser storage. These support account and room operation; they are separate from marketing analytics.

Who operates Cliodo

Cliodo is operated by Nguyen Dinh Quoc, an individual in Vietnam. For privacy questions, use the contact address below.

Analytics and room content

Private app pages are not tracked, and the app analytics tracker is disabled. Public marketing pageviews are sent to the shared hosted GoatCounter service with the canonical Cliodo path and an empty referrer; query strings and URL fragments are omitted. The site uses GoatCounter's standard aggregate settings: counts may be grouped by browser, operating system, approximate location, language and screen width. Individual pageview logging is off.

GoatCounter's published privacy policy says it keeps the IP address and User-Agent in memory for up to eight hours to recognize repeat visits, but does not store the IP address or full User-Agent in its database. Its hosted service stores data on Hetzner servers in Finland and Germany and is operated from Ireland. Cliodo does not send room titles, aliases, responses, comments, capability tokens or room links to GoatCounter.

Retention and service providers

An unlocked room expires 30 days after the later of its deadline or the end of its search window. Its detailed room data is retained for a further 90 days after expiry, then reduced to an aggregate-only tombstone. Detailed locked-outcome data is retained for 365 days after locking, then reduced to a tombstone. Participant session tokens expire no later than room expiry or 30 days after creation. Tombstones retain room state, lock time and response count—not aliases, responses or comment text.

The production Supabase project stores its primary data in Singapore (ap-southeast-1) and provides database, authentication and realtime services. Cloudflare Pages serves the public sites and same-origin API façade; backend operations use Supabase Edge Functions. Google receives sign-in information only when a host chooses Google sign-in; the app requests the OpenID Connect openid, email and profile scopes. The [email protected] inbox is hosted by Zoho Mail in the US, as confirmed in its account settings.

When general product-support messages are submitted through the Cliodo Contact channel, the separate Contact service handles them. Contact stores conversation messages in Cloudflare D1 and optional attachments in Cloudflare R2, sends operator notifications to Telegram, and may use Resend for email notifications or replies if you provide an email address. Contact begins cleanup after 180 days without conversation activity; cleanup may remain pending if an external deletion cannot be confirmed. Provider backups, email logs and copies already delivered to Telegram recipients may persist under those providers' practices. This channel is triage-only and has no response-time commitment.

For public provider information, see the Supabase Data Processing Addendum, Supabase subprocessor list, Cloudflare Data Processing Addendum, GoatCounter privacy policy, Google privacy policy, Zoho Global Privacy Policy, Telegram privacy policy and Resend privacy policy. This summary names the services directly used by Cliodo; it is not a complete account-specific inventory of every provider subprocessor or processing location. Contact-specific provider regions are not independently confirmed here. Provider-side retention and transfer practices are described in their current notices and may change.

Self-service account deletion is planned but is not available yet. There is no published fixed retention period for account or authentication records. You can send an account or privacy request to [email protected], but the inbox currently only receives requests: there is no self-service or full-deletion process, no published request-handling procedure and no response-time commitment. Sending a request does not automatically delete data.

Contact

The Cliodo Contact conversation is the general product-support channel; it is triage-only and has no response-time commitment. For privacy or account requests, email [email protected]. That inbox currently only receives requests; there is no published identity-verification or request-handling process, no self-service deletion and no response-time commitment. Sending a request does not automatically delete data.

Open the Cliodo Contact conversation

Pricing Privacy Terms of Service