Privacy Policy
We collect only the minimum lead fields and basic funnel events. We do not put sensitive content in analytics payloads.
On lead and waitlist forms we limit collection to what you submit (such as name, email, company, and stated use case).
Product analytics and scroll or page metrics are sent only if you opt in to analytics cookies in the cookie banner. Essential cookies are always used for session and security.
Cookies
- Essential cookies keep you signed in, protect the service, and remember locale where needed. They cannot be turned off from the banner.
- Analytics cookies (for example PostHog and our first-party `/api/analytics/events` pipeline) load only when you enable Analytics in the cookie banner. They help us understand which pages, locales, and CTAs perform best.
- Marketing cookies are reserved for future campaigns; you can leave them off. We do not use them for targeted ads in this build.
- You can change your mind by clearing site data for this origin or using the banner when we surface it again after a policy update.
Data retention (summary)
- GaiaLynk retains product data by class (for example conversation messages, audit-oriented logs, invocation receipts, and scheduled orchestration history). Default periods in production are placeholders aligned with our internal matrix until legal approves final commitments—typically on the order of one year for ordinary conversation text in many environments, with longer windows where compliance requires.
- When data ages out it may be archived and removed from normal in-product views. Exports and self-serve history reflect in-retention material unless a separate policy applies.
- Account deletion requests are handled through support; some records may be anonymized or retained where law mandates. The Help Center article *How long is data kept?* mirrors this summary in plainer language.
User-generated content, reporting, and moderation
- In multi-participant conversations you may report another participant’s user messages that violate acceptable-use or safety rules. Reports include a reason and optional detail for review.
- Space owners and administrators may hide a message after review; other members then see a standard placeholder instead of the original text. Hidden messages remain governed by retention and audit policies.
- Misuse of reporting (for example coordinated harassment through false filings) may itself violate policy and lead to enforcement.