--- title: "Privacy Policy — Coline" description: "What Coline collects, why, who we share it with, and the choices you have across the app, Kairo, Code, Mail, Upstream and the developer platform." url: https://coline.app/privacy --- # How Coline handles your data. This policy explains what Coline collects, why we collect it, who we share it with, and the choices you have. It covers coline.app, the Coline desktop and mobile apps, Kairo, Coline Code, Coline Mail, Upstream and upstream.codes, the API, SDKs and app platform, and our other sites. Last updated: October 11, 2026 ## Who we are Coline is operated by Coline Technologies, Inc., a Delaware corporation (“Coline”, “we”, “us”). We run Coline from British Columbia, Canada. When you use Coline for yourself, we are the controller of your personal information. When an organization sets up a team workspace, the organization controls the content in that workspace, and we process it on the organization’s behalf as its processor and service provider under our [Data Processing Addendum](https://coline.app/dpa). We remain responsible as a controller for account, billing, security and usage data. Our privacy officer is accountable for this policy and can be reached at [privacy@coline.app](mailto:privacy@coline.app). ## Information you give us **Account details.** Your name, email address, handle, password or sign-in method, avatar, time zone, profile details and preferences. If you sign in with Google, GitHub or Microsoft, we receive your name, email address and profile picture from that provider. **Workspace content.** What you and your teammates create or upload: messages, channels, threads, reactions, files, docs, notes, sheets, taskboards, comments, calendar events, emails, contacts, code, repositories, issues, change requests and reviews. **Calls.** Who joined a call and when. If someone turns on recording or transcription, the audio, video and transcript of that call. **Kairo and agents.** Prompts, attached files, conversation history, workspace content that you or an agent bring into a request, generated outputs, tool calls, memories, agent briefs, routines, goals and feedback. **Payments.** Your plan, billing contact, billing country, and subscription and invoice history. Card details go directly to our payment processor. We never see or store full card numbers. **Developer data.** Apps, manifests, store listings, API keys, OAuth clients, webhooks, app secrets, SSH keys and Git credentials. We store keys, tokens and credentials hashed or encrypted. **Public profile.** On upstream.codes: your handle, display name, bio, website, avatar, pinned repositories, the organizations you choose to show, and your public contribution activity. **Programs and support.** Information you send to join a program (for example, your GitHub account and student status), support requests, bug reports and product feedback. ## Information we collect automatically **Usage and device data.** IP address, browser and device type, operating system, app version, pages and screens viewed, features used, clicks, referring pages, approximate location derived from your IP address, and the time and length of visits. **Session replay.** In the Coline web and desktop apps, our analytics tool records how pages render and how you interact with them. Replays can include text shown on screen and what you type into text fields. Password fields are always masked, replays never include network request headers or bodies, and sign-in tokens are removed from page addresses before they are recorded. We use replays to find bugs and fix confusing flows. **Logs and diagnostics.** Server logs, request IDs, errors, console messages, performance timings and crash information. **Presence.** Whether you are online, typing, or viewing a channel or document, so teammates can see it in real time. **Cookies.** See “Cookies and similar technologies” below. ## Information from other sources **Integrations you connect.** When you connect a service such as Gmail, Google Calendar, Microsoft Outlook, GitHub, Linear, HubSpot, Salesforce, Pipedrive, Notion or a Model Context Protocol (MCP) server, we receive the data you authorize, such as emails, calendar events, contacts, repositories, issues or records. We use it only to provide the features you turned on. **Your organization.** Workspace admins may add your name and email address when they invite you, assign you a role, or set up your account through single sign-on. **Other users.** Teammates may mention you, share content with you, or add you to a call, room or thread. **Service providers.** Our payment processor tells us whether payments succeed. GitHub may confirm whether you qualify for a program, such as student status, when you apply. ## People who don’t use Coline Some of the data we process is about people without a Coline account: people who email a Coline Mail address or receive email from one, guests who join calls or Connect rooms, people invited to a workspace, and people named in workspace content or public repositories. We process it on behalf of the user or organization that controls it. If a sender turns on read status in Coline Mail, we record whether the images in an email were loaded and roughly when. We don’t store the recipient’s IP address or device details for this, and we try to ignore loads by mail security scanners and privacy proxies. ## How we use information - Provide Coline: run your account and workspaces, store and sync content, deliver messages, mail, calls and notifications, and run Kairo, agents, Code machines, Upstream and the apps you install. - Keep Coline secure: sign you in, enforce workspace permissions, detect abuse, spam and fraud, and investigate incidents. - Fix and improve Coline: debug problems, measure performance, see which features are used, and test changes. - Bill you: process payments, apply plan limits, credits and usage, and prevent payment fraud. - Talk to you: send account, security, billing and service messages, answer support requests, and send product news, which you can unsubscribe from at any time. - Meet legal obligations: respond to lawful requests, enforce our terms, and keep required records. We don’t sell your personal information, we don’t share it for cross-context behavioral advertising, and we don’t show ads in Coline. ## Legal bases in the EEA, UK and Switzerland **Contract.** To provide the service you signed up for, including the AI features you use, the integrations you connect and payments. **Legitimate interests.** To secure Coline, prevent abuse, understand usage, fix bugs, improve the product and communicate with customers. We weigh these interests against your rights, and you can object. **Consent.** For optional analytics on upstream.codes and anywhere else we ask for it. You can withdraw consent at any time. **Legal obligation.** To keep tax and accounting records, respond to lawful requests and meet other legal duties. ## Kairo and AI features When you use Kairo, crew agents, Tab completions, AI search, code review or other AI features, we send the relevant content to AI model providers to generate a response. That can include your prompt, conversation history, attached files, and workspace content that you or an agent bring into the request. **Agents read where they work.** Kairo and crew agents can read the channels, threads, DMs and documents they are part of, limited to the permissions of the person they act for. A crew agent set to reply when it’s useful reads new messages in its channels to decide whether to answer. Agents can save memories from conversations so they can help you later. **Upstream.** Repository owners can turn on AI code review and issue triage, which send change requests, diffs, issues and comments to AI model providers. Triage can flag likely spam. **Web search and browsing.** When Kairo searches the web, we send the search query to a search provider. When Kairo opens a web page, it loads the page from Coline’s servers, not from your device. **No training.** We don’t use your content to train AI models. Our AI model providers process it only to return results to us, not to train their own models. **Quality monitoring.** We log AI requests and responses, including limited amounts of prompt and output text, in our analytics tools to debug errors, measure speed and cost, and improve quality. **Your own API keys.** If you add your own API key for an AI provider in the Code editor, requests made with that key go directly to that provider under your agreement with them. **Automated decisions.** We don’t make decisions about you based solely on automated processing that have legal or similarly significant effects. ## Cookies and similar technologies We use cookies and local storage for these purposes: - Essential: keeping you signed in, completing sign-in, password reset and single sign-on, protecting against cross-site request forgery, remembering share links you open, and authorizing Code previews. Coline doesn’t work without these. - Preferences: your time zone, theme, layout and active workspace. - Analytics: product analytics and session replay in the Coline app. On upstream.codes, analytics run only after you agree to them, and never when your browser sends a Do Not Track or Global Privacy Control signal. The Coline desktop app stores your settings, and its built-in browser keeps history and bookmarks on your device. History isn’t saved for private tabs. Search suggestions in the built-in browser come from the search engine you choose. Our marketing pages are hosted by Framer, which collects basic visit statistics. You can block or delete cookies in your browser settings, but you need essential cookies to sign in. ## How we share information **Service providers.** Companies that host, store, secure and process data for us, including cloud hosting, database, file storage, email delivery, calls, payments, sign-in, analytics and AI model providers. They may use the data only to provide services to us. See our [list of subprocessors](https://coline.app/subprocessors). **Your workspace.** Members and admins of your workspaces can see content and profile information according to workspace roles and sharing settings. Admins can manage, export and delete workspace content and member accounts. **Public content.** Anything you make public is visible to anyone, including public repositories, profiles and contribution activity on upstream.codes, published pages and files, and share links. Public repositories can be cloned and forked, and copies can remain after you delete or hide the original. **Integrations and apps.** Services you connect and apps you or your admins install receive the data you authorize. Their own terms and privacy policies govern how they use it. If you mirror or sync a repository with GitHub, its contents are copied to GitHub. **People you communicate with.** Recipients of your messages, emails, invitations and call links. **Legal and safety.** When we believe disclosure is required by law, or needed to protect the rights, safety or property of our users, the public or Coline. Where the law allows, we try to notify affected users first. **Business transfers.** As part of a merger, acquisition, financing, reorganization or sale of assets. This policy continues to apply to information that is transferred. **With your consent.** In any other case where you ask us to or agree. ## International transfers Coline is operated from Canada, and our main infrastructure is in the United States. Our providers also process data in other countries. When we transfer personal information out of the EEA, UK or Switzerland, we rely on an adequacy decision where one applies, or on safeguards such as the European Commission’s Standard Contractual Clauses and the UK International Data Transfer Addendum. ## Retention We keep personal information while your account is active and as long as we need it to provide Coline. Some specifics: - Workspace content stays until you or your admins delete it, or until the workspace is deleted. - Coline Code agent execution logs are deleted after 7 days, and Code machine operation records after 30 days. - App execution logs are deleted after 30 days. An uninstalled app’s data is deleted 30 days after it was uninstalled. - Deleted content can remain in backups for a limited time until the backups expire. - We keep billing, tax, security and audit records for as long as the law requires, or as long as we need them to resolve disputes and enforce our agreements. When you delete your account, we wait 14 days so you can change your mind, then delete or de-identify your personal information unless we need to keep it for one of these reasons. Content you created in a team workspace stays with that team and shows as from a deleted user. ## Security We use technical and organizational measures to protect information, including encryption in transit, encryption at rest by our storage providers, encrypted secrets and credentials, hashed API keys and tokens, permission checks on every workspace request, isolated sandboxes for running code, rate limiting, and restricted staff access. No system is perfectly secure. If a breach affects your personal information, we’ll notify you and regulators as the law requires. ## Your rights and choices Depending on where you live, you may have the right to: - access the personal information we hold about you and receive a copy in a portable format; - correct inaccurate information; - delete your information; - object to or restrict some processing, including processing based on legitimate interests; - withdraw consent where we rely on it; - complain to your local data protection authority. You can update most account details and delete your account in Settings, and workspace owners can delete a workspace from its settings. To exercise any other right, email [privacy@coline.app](mailto:privacy@coline.app). We’ll verify your identity and respond within the time the law requires, usually within 30 days. If your data is in a workspace controlled by an organization, we may refer your request to that organization. **California.** California residents have the right to know, access, correct and delete their personal information, to opt out of its sale or sharing, and to limit the use of sensitive personal information. We don’t sell or share personal information as California law defines those terms, and we use sensitive personal information, such as account credentials, only to provide the service. You can use an authorized agent to make a request, and we won’t discriminate against you for exercising your rights. In the past 12 months we collected these categories of personal information, from the sources and for the purposes described above: identifiers, customer records, commercial information, internet and device activity, approximate location, audio and visual information (such as call recordings and avatars), professional information, and inferences (such as agent memories). We disclosed each category for business purposes to the service providers described in this policy. **Canada.** You can access and correct your personal information and withdraw consent, subject to legal and contractual limits. You can complain to the Office of the Privacy Commissioner of Canada or, in British Columbia, to the Office of the Information and Privacy Commissioner. **EEA, UK and Switzerland.** You can complain to the data protection authority where you live or work. **Email.** You can unsubscribe from product news with the link in those emails. We’ll still send messages about your account, security and billing. ## Children Coline isn’t meant for children. You must be at least 13 years old to use Coline, or older if the law where you live requires it (16 in some EEA countries). If we learn that we collected information from a child under that age, we’ll delete it. Email [privacy@coline.app](mailto:privacy@coline.app) if you think that happened. ## Changes to this policy We’ll post updates on this page and change the “Last updated” date. If a change is material, we’ll tell you by email or in the app before it takes effect. Privacy questions and requests Email [privacy@coline.app](mailto:privacy@coline.app) for privacy questions and requests, and [security@coline.app](mailto:security@coline.app) to report a security vulnerability.