Privacy Policy

CrowdTicks is an independent community project. For privacy requests, email contact@crowdticks.com.

Depending on how you use the site, CrowdTicks may process:

• Account data: email address, a password stored by Supabase Auth (we do not see your plaintext password), and Google profile details if you sign in with Google.
• Profile data: username, display name, and bio.
• User-generated data: predictions (including direction, targets, thesis, and settlement fields), comments, likes, follows, and watchlists.
• Security data: Cloudflare Turnstile tokens and server logs that may include IP address, user agent, and request metadata.

CrowdTicks does not ask for precise location and does not run third-party advertising pixels.

Usernames, predictions, theses, comments, like counts as shown on the site, and settled track records — including leaderboard rows — are visible to anyone who can load the page, whether or not they have an account. Treat a call as a public statement. Watchlists and email addresses are not shown as public profile fields.

We use this information to:

• Run accounts, sessions, and settings.
• Publish, settle, and score calls, and to build leaderboards.
• Operate social features (comments, likes, follows, watchlists).
• Protect the service against abuse and technical abuse.

CrowdTicks does not sell personal information to data brokers.

CrowdTicks relies on other companies to operate:

• Supabase — authentication and the PostgreSQL database, on Supabase's infrastructure.
• Vercel — application hosting.
• Cloudflare Turnstile — bot checks on sign-in and sign-up.
• Google — OAuth sign-in, when that option is enabled.

The TradingView chart widget may set its own cookies or similar storage in your browser. CrowdTicks does not control that widget.

CrowdTicks uses cookies and similar storage for authentication and session continuity. Turnstile may set its own storage as part of the bot check. There is no separate cookie policy at this stage.

Account and profile data are kept while the account exists. Public predictions are part of the community record. If you ask us to delete your account, we will remove or lock the login and profile, and we will anonymize your public predictions (for example by detaching them from your username) rather than erase the historical calls. That keeps settlement history and leaderboards from being hollowed out by deletions. Comments may be removed or anonymized with the account. Server logs are kept only as long as needed for security and operations.

Account deletion is currently handled by writing to the contact address above. Self-serve deletion is not built yet.

You can review and update display name and bio in Settings. You can ask, via the contact email, to see the personal data we hold, to correct it, or to delete your account as described above. CrowdTicks does not run a full GDPR request portal. We will still try to honor reasonable requests.

CrowdTicks is not directed at anyone under 18. We do not knowingly collect personal information from children.

Hosting and authentication run on cloud infrastructure that may be located in the United States and other countries. If you use CrowdTicks from elsewhere, your information may be processed in those locations.

This policy may change. The date at the top of this page is the current version. Continued use after a change means you accept the updated policy.

Privacy questions: contact@crowdticks.com.