Skip to content
kovnor

Kovnor privacy policy, in plain words.

Kovnor privacy in short: Attensira Technologies OÜ runs the Service, decides how account, billing and analytics data is used, and handles workspace content for the workspace. We never train AI models on your data and never sell it. Analytics run only after you accept them. The full policy below covers sharing, retention and your rights.

This page is the whole policy, not a summary of one. It names every provider that processes data and what each one does for Kovnor, and it keeps the rule the product already follows: private chats, private projects and unshared agents stay invisible to anyone outside them.

What holds today

  • We do not train AI models on your workspace content, your private chats or your files.
  • Product analytics hold only ids, fixed categories and counts, and run only after you accept them.
  • Actions that reach the outside world need a person's approval by default.

Last updated 15 October 2026

1. Who we are

Kovnor is built and run by Attensira Technologies OÜ, a company registered in the Estonian Commercial Register (EU). In this policy "Kovnor", "we" and "us" mean Attensira Technologies OÜ.

This policy covers kovnor.com, the web app at app.kovnor.com, the public API at api.kovnor.com and the MCP server at mcp.kovnor.com (together, "the Service").

Questions or requests: team@kovnor.com.

2. Our two roles

  • For your account, billing and our own analytics, we are the controller. We decide why and how that data is used.
  • For the content you and your agents put into a workspace, we act for the workspace. That content includes messages, files, memory, plans, tasks and tool actions. The workspace owner (usually your company) decides what goes in and who sees it, and we process it to run the Service for them. If you are a member of someone else's workspace, contact that workspace's owner about its content. Business customers can ask us for a Data Processing Agreement (DPA).

3. What we collect

Account data. Your name, verified email address, the workspaces (organizations) you belong to and your role in each (Owner, Admin, Member or Guest). Sign-in is handled by Clerk.

Demo requests. If you request a demo or join the waitlist with the form on kovnor.com: your name, work email, company, the job you describe if you do, the page you sent it from and the campaign tags (utm) you arrived with. We use them only to reply to you.

Workspace content. Everything created in a workspace:

  • messages in projects (group conversations with a goal) and in private one-on-one chats with agents
  • files (stored in our database, up to 10 MB each), artifacts, memory, skills, plans, tasks and automations
  • the work agents do on their cloud computers and the actions they take through your connected tools

Tool connection tokens. When you connect a tool (for example Gmail, X, LinkedIn, Instagram, Reddit, YouTube or a browser tool), the access tokens are stored by Composio or encrypted by us. We use them only to carry out actions in your workspace.

Your own AI provider keys. If you add your own Anthropic or OpenAI API key, we store it encrypted. Only that workspace's agents use it, and it is never shown again after you save it.

Usage and billing records. Credits granted, bought and used; plan; top-up and auto top-up settings; spending limits; invoices. Card details are handled by Stripe (through Autumn) and never reach our servers.

Audit log. A record of changes made in a workspace (who did what, when) so owners can see what happened.

Product analytics. Events about how the Service is used. These events contain only ids, fixed categories (enums) and counts. They never contain message text, file contents or keys. We use PostHog for this. Our servers record what happens in a workspace (for example that a task was created or a job finished), whatever you choose in the cookie banner. Your browser sends analytics (which pages and screens you use) only after you accept them in the cookie banner (see section 11).

Technical data. Standard request data such as IP address, browser type and timestamps, used for security, rate limiting and debugging. Server logs are kept for up to 30 days.

Error reports. When something breaks, our servers send PostHog an error report: the kind of error, where in our code it happened and the release, never message text, keys or email addresses. Your browser sends error reports only after you accept analytics in the cookie banner.

Push notifications. If you turn on browser notifications, your browser vendor's push service gives us a subscription address so we can send them.

4. Why we use it (and our legal basis under GDPR)

PurposeLegal basis
Creating your account, running workspaces, running agents and tools, sending service emails and notificationsContract: we need it to provide the Service
Billing, invoicing, tax and accounting recordsContract and legal obligation
Security, abuse prevention, rate limits, audit logLegitimate interest in keeping the Service and its users safe
Product analytics recorded by our servers (ids, enums, counts only)Legitimate interest in understanding and improving the product; you can object to it
Analytics in your browser (pages and screens used)Your consent, given in the cookie banner; you can withdraw it at any time
Answering support requests and refund requestsContract and legitimate interest

We do not sell personal data, and we do not use it for advertising.

5. AI models and your data

  • We do not train models on your data. Not on your workspace content, your private chats or your files.
  • To do their work, agents send relevant workspace content to AI model providers. Model calls on Kovnor's account go through OpenRouter or our self-hosted LiteLLM gateway to model providers including Anthropic and OpenAI. When you bring your own key, calls go to that provider on your key and fall under your own agreement with them.
  • Those providers' own terms apply to model calls.
  • Private chats stay private. A private chat is visible only to its participants. Its content is never used to answer anyone else's questions, and it does not appear in other people's search, mentions or inbox.
  • Coming soon: connecting a Claude Code or Codex plan. Each person would sign in on the vendor's own page, so Kovnor never sees their login. Connections would never be shared or pooled between people.

6. Actions agents take for you

Agents can draft content and, depending on your settings, act through your connected tools, for example by posting a reply. Actions that reach the outside world need approval by default. You can let an agent act without asking (earned autonomy), and you can take that back at any time. When an agent acts, the content goes to the platform you connected (for example X or LinkedIn) and falls under that platform's privacy policy.

7. Who we share data with

We use these service providers (subprocessors) to run Kovnor. Each one gets only what it needs for its job.

ProviderWhat for
ClerkSign-in, accounts, organizations (workspaces) and invitations
RailwayPostgres database, in the United States
VercelHosting the website, web app and API
RailwayHosting our core service and the model gateway (self-hosted LiteLLM)
BoatCloud computers that agents work on
OpenRouterKovnor's own AI model calls
Anthropic, OpenAIAI model calls, when you bring your own key or through our gateway
ComposioTool connections and the actions agents take through them
Autumn and StripeSubscriptions, credits, payments and tax
PostHogProduct analytics (ids, enums and counts only) and error reports; in your browser only after you accept it
Browser push services (e.g. Google, Apple, Mozilla)Delivering browser notifications

We may also disclose data if the law requires it, or to protect the Service or its users. If Attensira Technologies OÜ is sold or merged, data would transfer under this policy, and we would tell you first.

We keep this list current on this page, and tell workspace owners by email at least 30 days before a new subprocessor starts processing their content.

8. Transfers outside the EU

Several providers above are based in the United States or process data there. Where data leaves the European Economic Area, we rely on the EU–US Data Privacy Framework where the provider is certified, or on the European Commission's Standard Contractual Clauses.

9. How long we keep data

  • Account data: while your account exists, then deleted within 30 days of account deletion.
  • Workspace content: while the workspace exists, then deleted within 30 days of workspace deletion. Backups roll off within 30 days.
  • Tool tokens and provider keys: deleted when you disconnect the tool or remove the key, or when the workspace is deleted.
  • Billing records: kept as long as Estonian accounting law requires (7 years).
  • Audit log: 24 months.
  • Product analytics: 24 months.
  • Server logs: 30 days.

10. Your rights

Under the GDPR you can ask to:

  • access the personal data we hold about you, and get a copy of it
  • correct it
  • delete it
  • restrict or object to how we use it, including the analytics described above
  • receive it in a portable format

Workspace export and deletion. A workspace owner can ask us to export or delete an entire workspace. Until this is self-serve in the app, email team@kovnor.com from the owner's address and name the workspace. We will respond within one month.

You can also complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, www.aki.ee) or to the data protection authority where you live. We would appreciate the chance to sort it out with you first.

11. Cookies

  • Essential cookies keep you signed in (set by Clerk) and keep the app working. The Service doesn't work without them, so they are always on.
  • Analytics cookies (PostHog) help us understand product usage. They are off until you choose Accept in the cookie banner. If you choose Essential only, or your browser sends Do Not Track, analytics stay off. Your choice is stored in your browser, and you can change it at any time: in the app under Settings › General › Share usage data, and on this site with the Cookie settings link at the bottom of every page.

We don't use advertising cookies.

12. Security

Data is encrypted in transit. Provider API keys, and tool tokens we hold, are encrypted at rest. Access inside a workspace follows roles. Private projects, unshared agents and private chats are invisible to anyone outside them. Changes are written to an audit log. Sign-in, including two-factor sign-in, is handled by Clerk. No system is perfectly secure. If a breach affects your personal data, we will notify you and the authorities as the GDPR requires.

13. Children

Kovnor is a business tool and is not meant for anyone under 18. We don't knowingly collect children's data.

14. Changes to this policy

If we make a material change, we will tell workspace owners by email or in the app before it takes effect. The date at the top shows the latest version.

15. Contact

Attensira Technologies OÜ, Estonia. Email: team@kovnor.com.

Questions

Do you train AI models on my data?

No. Not on workspace content, private chats or files. Agents send the relevant content to AI model providers only to do the work you asked for, and on your own key under your own agreement with that provider.

When do analytics run?

Only after you choose Accept in the cookie banner. Essential only, or a browser that sends Do Not Track, keeps analytics off, and you can change the choice at any time from Cookie settings at the bottom of the page.

How do I get a workspace exported or deleted?

The workspace owner emails team@kovnor.com from the owner's address and names the workspace, until export and deletion are self-serve in the app. Section 10 of the policy covers it.

Book a demo

Tell Kovnor the outcome. It proposes the team.

Book a demo

20 minutes with the founder. We set your first goal together. Nothing sends without your OK.

Book a demo. On the call we set up your first goal and walk through a practice run before anything is sent.