Privacy Policy

Klynt (“Klynt”, “we”, “us”) operates klynt.one, a project truth layer that connects to tools like Slack and Figma, collects meaningful changes, and keeps a current state of your project. This Privacy Policy explains what information we collect, how we use it, and the choices you have.

By using Klynt, you agree to the collection and use of information in accordance with this policy. If you do not agree, please do not use the Service.

Depending on how you use Klynt, we may process:

• Account information — email address and authentication credentials when you register or log in
• Project data — projects you create, their names, settings, and the facts, interpretations, and conflict detections the Service derives for them
• Contact information — name, email address, and message content when you email us
• Waitlist information — email address if you join the beta waitlist
• Usage and device data — aggregated analytics such as pages visited, referrer, browser type, and general location (country/region)
• Technical logs — IP address, request timestamps, and error logs retained briefly for security, abuse prevention, and service reliability

When you connect an integration, you grant Klynt access to parts of that workspace so it can detect meaningful project changes. Currently:

• Slack — messages and events in the channels you select, including message text, author names, and timestamps
• Figma — file activity such as version saves, comments, and related file metadata (file names, user handles)

To keep these connections working, we store the OAuth access and refresh tokens issued to Klynt. These tokens let the Service read from the connected sources until you disconnect the integration.

Content from connected services is processed to detect project events and update project state. We do not use it for advertising, and we do not sell it.

We use collected information to:

• Collect events from connected tools and maintain your project's current state
• Operate, maintain, and improve the Service
• Respond to contact and support requests
• Send waitlist confirmations and product updates you opt into
• Monitor performance, debug issues, and prevent abuse
• Comply with legal obligations

To interpret what changed and why it matters, event content from your connected sources is sent to our AI provider (Anthropic) for automated interpretation. The output — event classifications, facts, and detected conflicts — is stored with your project data.

We do not use your connected workspace content to train our own models, and our AI provider processes it under its own data handling terms for API usage.

Where applicable data protection laws require a legal basis, we rely on:

• Contract / service delivery — to provide the Service you signed up for, including processing the workspace data you connect
• Legitimate interests — to secure, improve, and measure the Service in a way that respects your privacy
• Consent — where required for optional communications such as waitlist and product emails

When you connect a workspace on behalf of a team or company, you are responsible for having the authority and any required notices or consents to share that data with Klynt.

Your account, project, event, and derived data are stored in our database (hosted by Supabase) while your account is active.

Disconnecting an integration stops further collection from that source. Previously collected events and derived facts may remain until you delete the project or ask us to delete your data. OAuth tokens are removed when an integration is disconnected or the project is deleted.

Contact form submissions and waitlist emails are retained only as long as needed to respond, operate the Service, or meet legal requirements. Server logs are kept for a limited period for security and diagnostics.

We share information only with service providers that help us operate Klynt:

• Vercel — hosting and application delivery
• Supabase — database and authentication
• Anthropic — AI interpretation of project events
• Resend — transactional and waitlist email delivery

These providers process data on our behalf under contractual safeguards and only for the purposes described in this policy.

We may also disclose information if required by law, to protect our rights or users, or in connection with a merger, acquisition, or sale of assets, with appropriate notice where required.

We use essential cookies required for authentication and for the Service to function. We use privacy-focused analytics (Vercel Analytics and Speed Insights) to understand usage in aggregated form.

You can control cookies through your browser settings. Disabling essential cookies may prevent sign-in and other core functionality.

Depending on your location, you may have rights to access, correct, delete, or restrict processing of your personal information, or to object to certain processing. You may also have the right to lodge a complaint with a supervisory authority.

To exercise these rights, email hello@klynt.one. We may need to verify your request before responding.

Klynt is not directed to children under 16 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided us personal information, please contact us and we will take appropriate steps to delete it.

We may update this Privacy Policy from time to time. The “Last updated” date at the top of this page indicates when the policy was last revised. Material changes will be posted on this page. Continued use of the Service after changes become effective constitutes acceptance of the updated policy.

Questions about this Privacy Policy? Email hello@klynt.one.