It is Chirp’s policy to respect your privacy. This Privacy Policy explains what information Rocket Source Ltd. (“Chirp”, “us” or “we”) collects when you use the Chirp shared inbox at https://app.teamchirp.io, the Chirp API and the website at https://teamchirp.io (together, the “Service”), how we use it, and when we share it. It applies only to information collected through the Service.
This Privacy Policy and our Terms of Service set out the rules for your use of the Service.
Who is responsible for your data
For the email, contacts and other content that a customer connects to Chirp, the customer’s organisation decides what is processed and why, and we process it on their behalf. For account details and information about how people use the Service, Rocket Source Ltd. is the controller. The Data processing section of our Terms of Service sets out our duties as the customer’s processor. It is part of every customer’s contract, and a signed copy is available by email.
Contact: Rocket Source Ltd., a company registered in England and Wales (company number 16517484), 38b Arbery Road, London, E3 5DD, [email protected].
The website
teamchirp.io is a static website and serves its own fonts. If you accept analytics, it loads Google Analytics to measure visits and interactions, such as page views, scrolls and outbound links. Google Analytics receives technical information about your browser and visit and sets analytics cookies. We use this information to understand and improve the website, not for advertising. You can reject analytics or change your choice using Analytics settings in the footer. We keep the choice in your browser’s local storage. Google Analytics event data is set to be retained for 14 months. Our hosting provider, Cloudflare, receives the technical data that every web request carries, such as your IP address and browser type.
Information in the app
Your account. Your name, email address, a hash of your password (scrypt; we never store the password itself), your time zone, your role (Admin, Agent or Viewer), your team, and your preferences for replies, triage and notifications. If you sign in or sign up with Google, Google sends us your name, your email address and the address of your profile picture. We store the name and the email address. We do not store the picture. We use the tokens that Google returns only to complete the sign-in, and we do not store them. If you sign in or sign up with Facebook, Meta sends us your name, your email address, the address of your profile picture and the identifier of your Facebook account. We store the name, the email address and the identifier. We do not store the picture. We use the token that Meta returns only to complete the sign-in, and we do not store it. For each sign-in, we store a session record with its expiry, your IP address and your browser’s user agent. An account is created by a sign-up or from an invitation; an invitation stores the invited email address, role and team, and expires after 14 days.
Connected mailboxes. An admin connects a mailbox with Google (Gmail) or with IMAP and SMTP.
- For Gmail, we store an OAuth refresh token and the mailbox address. Chirp copies every message in the mailbox, including spam and trash, so your team can work on it, and sends the replies your team writes.
- For IMAP, we store the username and password for the mailbox, and copy the inbox and the sent folder.
Refresh tokens and passwords are encrypted (AES-256-GCM) before we store them.
Messages and attachments. For each message, we store the sender, recipients, subject, body, dates and message identifiers, the list of attachments, and the original message file with its attachments. Messages are stored in our database and file storage, which our hosting and storage providers run for us.
Customer contact data. The people who write to your inboxes are identified by the name and email address in their messages. Chirp shows your team each sender’s past conversations. Admins can link an email address to a Stripe customer; we store that link.
Your team’s work. Assignments, statuses, snoozes, tags, internal notes, mentions, facts, saved views, automation rules and their run history, notifications, and a log of changes to each conversation.
Stripe. If an admin connects Stripe, we store a restricted API key for the customer’s own Stripe account, encrypted. When an agent opens the customer panel, Chirp reads that customer’s details, subscriptions and payments from Stripe and keeps them in memory for up to one minute. We do not store Stripe customer or payment data in our database, apart from the email-to-customer links above. Disconnecting Stripe deletes the key.
Linear. If an admin connects Linear, we store an OAuth token, encrypted, and the workspace name. When your team links a conversation to a Linear issue, we store the issue’s identifier, URL, title and state, and keep the state up to date. Chirp also adds a link back on the Linear issue: the conversation’s subject, the customer’s name or email address, the inbox name and a link to the conversation, with no message text. Removing the link in Chirp asks Linear to remove it from the issue. Chirp also asks Linear to remove these links when an admin disconnects Linear or deletes the workspace, and when a deleted conversation leaves Trash for good. When an agent links an issue, they can choose to post the customer’s latest message (up to 5,000 characters) as a comment on the Linear issue, with a link back to the conversation. Each inbox sets whether that choice starts on or off. Disconnecting Linear deletes the token and asks Linear to revoke it.
API keys. When you create an API key, we store its name, first characters, scopes, expiry, and a SHA-256 hash of the secret. We show the full key once and cannot show it again. We log each API request: the key, the method, the route, the conversation and the result.
Translation. Translation is off for each workspace until an admin turns it on in Settings → Integrations. We record who changes the setting, and when. When translation is on, Chirp sends the text of recent incoming messages that do not look English, and any message an agent asks to translate, to OpenRouter, which passes it to a language model (by default DeepSeek). Each request tells OpenRouter to use only model providers that do not store or train on the data. We store the translation with the message. When translation is off, no message text goes to OpenRouter. A workspace that used Chirp before this setting existed has translation on until an admin turns it off.
Remote images. By default, when you open an incoming email that is not marked as spam, your browser loads the remote images in it from the sender’s server, so the sender can see your IP address and when the email was opened; an admin can change this in Settings → Inboxes, so that the images of an email load only after a person selects Show images or allows its sender, and Chirp’s servers do not load these images.
Telemetry and logs. When telemetry is configured, we record traces and logs of requests, database queries and background jobs to find errors and slow pages, and send them to Axiom. Before anything leaves our servers, we keep only a fixed list of technical fields, remove message identifiers and email addresses from URLs, remove secrets from query text, and drop all error messages, because an error message can quote email content. Telemetry does not include the subject, body or attachments of any email.
Product analytics. When product analytics is configured, the app sends usage data to PostHog, in the EU, so that we can see which features people use: your Chirp user number, your workspace number and your role; events such as a sign-up, a connected inbox, a first reply, an invitation, a closed conversation, a new automation and a linked issue, with the number of the conversation or inbox; the names of the pages you open; and session recordings of the app. In a recording, every text and every field is masked before it leaves your browser, apart from Chirp’s own labels, and email frames and images are left out. A recording also lists the app’s own requests (address, timing and result, without their content); the address of a search request contains the text of the search. Apart from that search text, product analytics does not include your name, your email address, or the subject, body, sender or attachments of any email. PostHog sets no cookie and stores nothing in your browser. PostHog keeps a recording for 30 days.
Cookies. The app sets one session cookie when you sign in, to keep you signed in. It sets no analytics or advertising cookies. Your browser keeps your unsent reply and note drafts and your view preferences in its local storage, on your own device. The app serves its own fonts.
How we use information
We use the information above only to provide the Service to you and your team: to sync, show, search, organise and send email; to run the automations and integrations that your team sets up; to keep the Service secure; to find and fix errors; and to contact you about your account. We do not sell personal information, we do not use your email content for advertising, and we do not use it to train AI models.
Under UK data protection law, we rely on these legal bases: performing our contract with you or your organisation; our legitimate interests in running, securing and improving the Service; and meeting our legal obligations. We use website analytics only with your consent.
Google API Services: Limited Use
Chirp’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Chirp requests these Google scopes when an admin connects a Gmail mailbox:
| Scope | Why Chirp needs it |
|---|---|
https://www.googleapis.com/auth/gmail.readonly |
Read the mailbox’s messages and labels, so your team can see and answer them in Chirp. |
https://www.googleapis.com/auth/gmail.send |
Send the replies and new messages that your team writes in Chirp, from that mailbox. |
Google sign-in, when it is on, asks only for your basic profile and email address (openid, email, profile). It does not use the Gmail scopes.
Facebook sign-in, when it is on, asks Meta only for your public profile and email address (public_profile, email).
In particular, for data from Gmail:
- We use it only to provide and improve the user-facing features of Chirp that your team uses: the shared inbox, search, automations, the customer panel and translation.
- We transfer it to others only to provide those features, with your consent (for example, a customer message that an agent chooses to post to a Linear issue, or a message sent for translation after an admin of your workspace has turned translation on); for security purposes; to comply with applicable law; or as part of a merger, acquisition or sale of assets, after obtaining your explicit prior consent.
- We do not use it, or let others use it, to serve advertisements, to build user profiles for advertising, or to develop, improve or train generalised AI or machine-learning models.
- Our staff do not read it unless you give us permission for specific messages, it is needed for security purposes such as investigating abuse, it is needed to comply with law, or the data is aggregated and anonymised for internal operations.
Who processes your data
We share personal information only with the service providers below, and only as needed to run the Service. They process it on our behalf or, for services that you connect, on yours.
| Provider | What it does for Chirp | Data |
|---|---|---|
| Our hosting and storage providers | Hosting, database and file storage | Everything described above |
| Cloudflare | Hosting for the teamchirp.io website; storage of original message files, export files and database backups | The technical data of each web request; messages and attachments, exports, and backup copies of the database |
| Gmail sync and sending; Google sign-in; website analytics if you accept | Mailbox content; your Google profile; website visit and interaction data | |
| Meta | Facebook sign-in, if you use it | Meta learns that you sign in to Chirp; Chirp sends Meta no data from your workspace |
| Stripe | Your own Stripe account, read with your key | Customer email addresses sent in lookups |
| Linear | Your own Linear workspace | Issue searches; for each linked conversation, its subject, the customer’s name or email address and the inbox name; customer messages that agents choose to post as comments |
| Your email provider | The IMAP and SMTP server of a mailbox connected with a password | Mailbox content, and the replies your team sends |
| Axiom | Traces and logs, when telemetry is configured | Technical data, without email content |
| PostHog (EU) | Product analytics and masked session recordings of the app, when configured | User, workspace, conversation and inbox numbers; role; page names; masked recordings; the app’s request addresses, including search text |
| Plunk | Account email, when configured: verification, password reset and invitation messages | The recipient’s email address and the text of the message |
| OpenRouter and its model providers | Translation, when an admin has turned it on | The text of messages to translate |
Transfers outside the United Kingdom. Chirp’s servers and several of these providers are in the United States, so personal data is processed outside the United Kingdom. UK law allows a transfer to a country that UK adequacy regulations cover, such as the countries of the European Economic Area, or to a US organisation that is certified under the UK Extension to the EU-US Data Privacy Framework (the UK-US data bridge). For other transfers, UK law accepts a contract such as the UK International Data Transfer Addendum to the EU standard contractual clauses (the UK Addendum). This is what each provider’s own terms state:
- Cloudflare states that it complies with the Data Privacy Framework and its UK Extension. Its data processing terms also include the UK Addendum.
- Google states that Google LLC is certified under the Data Privacy Framework and its UK Extension.
- Axiom’s data processing terms include the UK Addendum.
- PostHog stores Chirp’s product analytics in the European Union (Germany).
- Plunk stores its data in the European Union (Germany). It delivers email through Amazon SES, under standard contractual clauses.
- Stripe, Linear and your email provider act under your own agreement with them. If you sign in with Facebook, Meta handles your Facebook account under its own terms with you.
To ask which safeguard applies to a provider that this list does not cover, email [email protected].
We also disclose information in response to a subpoena, court order or other governmental request, or when we believe in good faith that disclosure is reasonably necessary to protect the property or rights of Chirp, third parties or the public at large. We will not rent or sell personal information to anyone.
Security
We take measures reasonably necessary to protect personal information against unauthorised access, use, alteration or destruction. For example: mailbox tokens and passwords, the Linear token and Stripe keys are encrypted; passwords and API keys are stored only as hashes; the tokens from a Google or Facebook sign-in are not stored; each person sees only the inboxes that their workspace gives them access to; and telemetry leaves out email content.
How long we keep data
We keep your workspace’s data while your organisation uses Chirp. Your team can delete a conversation in Chirp: it moves to Trash, and after 30 days Chirp removes its messages, attachments and original files for ever. Chirp keeps a record without content (the message’s identifiers and a checksum), so the next sync does not copy the message again. Chirp has no other automatic deletion schedule. Deleting a conversation in Chirp does not change your mailbox, and deleting a message in your mailbox does not delete Chirp’s copy.
Export. An admin can export the workspace’s data at any time in Settings → Data. The export is a ZIP file with the conversations, messages, notes, tags, settings and members as JSON files, and the original message files. It leaves out passwords, tokens and API keys. Chirp keeps the file for 24 hours, and only the workspace’s admins can download it.
Deleting your account. Each member can delete their own account in Settings → Profile. Chirp deletes the sign-in, sessions, API keys, preferences, notifications and private views at once. The sign-in includes what Chirp got from Google or Meta: your name, your email address and the identifier of that account. The notes and replies that the member wrote stay with the workspace and show “Deleted user”. When an admin removes a member who belongs to no other workspace, Chirp deletes that account in the same way.
Deleting a workspace. An admin can delete the workspace in Settings → Data. Chirp deletes the workspace’s data and its members’ accounts from its database at once, with no grace period. A member who also belongs to another workspace keeps their account. It deletes the stored mailbox passwords, tokens and Stripe key, and asks Google and Linear to revoke its access. A job removes the original message files; it starts at once and runs again each hour until it is done. In normal circumstances, our database backups keep a copy for about 14 days. Chirp keeps a record of the deletion without content: the workspace’s number, the date, and counts. Before the deletion, Chirp asks Linear to remove the links that it added to your Linear issues. The mail in your own mailboxes is not changed.
When we close a workspace. If we end a workspace’s access, or an admin asks us by email to close it, we keep its data for 30 days, so that an admin can ask for an export, and then delete it as described above.
Deletion requests by email. To delete specific data, or if you cannot sign in, email [email protected]. We complete the deletion within 30 days after we confirm who you are. In normal circumstances, our database backups keep a copy for about 14 more days.
Your rights
Depending on where you live, you can ask us for a copy of your personal information, and ask us to correct it, delete it, restrict or object to its use, or move it to another service. A workspace’s admins can export or delete its data in Chirp, and each member can delete their own account, as described above. For anything else, email [email protected]. If an organisation’s workspace holds your data (for example, you emailed a company that uses Chirp), we will pass your request to that organisation. You can also complain to the UK Information Commissioner’s Office (ico.org.uk) or your local data protection authority.
You can revoke Chirp’s access to a Gmail mailbox at any time from your Google Account’s security settings.
Children
Chirp is a service for businesses and is not directed at children under 16.
Business transfers
If Rocket Source Ltd., or substantially all of its assets, were acquired, or in the unlikely event that it goes out of business or enters bankruptcy, user information would be one of the assets that is transferred or acquired by a third party. You acknowledge that such transfers may occur, and that any acquirer may continue to use your personal information as set forth in this policy.
Changes to this policy
We may change this Privacy Policy from time to time. We post each change here and update the date above. When a change is material, for example a new provider or a new use of your data, we also email the admins of each workspace at least 14 days before the change applies.
Contact
You can contact us about any privacy question at [email protected], or write to Rocket Source Ltd., a company registered in England and Wales (company number 16517484), 38b Arbery Road, London, E3 5DD.