Back to Winknex

Legal

Privacy Policy

Winknex processes the data needed to authenticate users, save collaboration plans, prevent abuse, and deliver notifications. We try to keep collection narrow and use the data only to operate, protect, and improve the service.

Last updated: March 31, 2026

What We Collect

We collect basic account and access information such as email address, session identifiers, invite allowlist status, and security verification results tied to your account.

To operate Winknex, we store the work you submit in the product, including task requests, collaboration drafts, work plans, reflections, feedback, and integration metadata connected to external agents or local execution environments.

We also process limited security and preference data such as Cloudflare Turnstile results, necessary error and abuse-prevention logs, locale cookies, theme settings, and sidebar state stored in the browser.

How We Use Information

We use this information to authenticate users, save and present human-agent work splits, deliver notifications you enable, and keep the service secure, reliable, and manageable during invite-only operation.

When you use Winknex AI features, we send the necessary request content to the configured model providers so the service can generate drafts, recommendations, and other outputs.

Service Providers

  • Supabase for authentication, database storage, and session handling.
  • Cloudflare Turnstile for bot detection and abuse prevention.
  • Resend for optional notification emails.
  • Kimi, or DeepSeek when you explicitly configure it, for AI features when those providers are called.
  • LangSmith for observability only when tracing is explicitly enabled by the team.

Sharing and Retention

We do not sell personal information as a data broker. We share data only with the infrastructure and model providers needed to run Winknex.

We retain data for as long as needed to provide the service, secure the platform, debug incidents, and meet legal obligations. When data is no longer required for those purposes, we may delete, anonymize, or reduce retention.

Your Choices

You can adjust local browser preferences such as theme and language, disable optional notifications, and stop using specific integrations. Some account and workspace records are still required for core service operation while the account remains active.

Policy Updates

We may update this policy as Winknex changes. The current version will be posted on this page, and the effective version is identified by the last updated date above.