Privacy.

What we collect (v0)

Nothing. CrowLingo does not run analytics, does not set tracking cookies, does not embed third-party trackers (Facebook Pixel, Google Analytics, Mixpanel, etc.), does not fingerprint your browser, and does not log IPs beyond what the hosting platform (Vercel) records for routine operations like DDoS protection.

Cookies

CrowLingo does not set its own cookies. Vercel, our hosting platform, may set short-lived operational cookies (for example, edge-routing or rate-limit) — those are not under our control and don't carry user-identifying data. See Vercel's privacy policy for specifics.

What we will collect later (and how we'll tell you)

The roadmap (see /frontier) includes features that will collect data — citizen-scientist audio uploads (v3) and an optional newsletter (v2+). Before either of those goes live, this page gets updated with:

• Exactly what data is collected (file metadata, email, etc.)
• Why we need it
• How long we keep it
• Who we share it with (we won't sell it, period)
• How to delete or export your data

We'll also publish the change in the deployment commit log on GitHub so the diff is auditable.

What our AI / dev access tools track

When AI agents or search crawlers hit our endpoints (/llms.txt, /sitemap.xml, etc.), Vercel logs the request in routine operational logs. We do not retain, analyze, sell, or share those logs.

Children's privacy

CrowLingo is intended for the educated curious public. We do not knowingly collect any data from anyone — children included — because we collect no data in v0. If features that change this land later, COPPA compliance is part of the design constraint.

Your rights

Because we don't collect personal data, there's currently nothing to access, correct, port, or delete. If that changes, this page will tell you how to exercise GDPR/CCPA/etc. rights.

Questions

contact@kymatalabs.com for privacy-specific questions. contact@kymatalabs.com for everything else.