Cranberry

Privacy Policy

Last updated: October 3, 2026

Cranberry CRM (“Cranberry”, “we”) is a shared workspace for teams: a shared inbox, tasks, contacts and an activity log. This policy explains what information we collect, how we use, store, share and delete it, and the choices you have. If you connect a Google or Microsoft mailbox, the sections on those accounts apply to the data we receive from them.

1. Information we collect

Account information. Your name, your email address and/or phone number, your workspace name, and a one-way hash of your password (we never store your password itself).

Workspace content you or your teammates add. Contacts and companies, tasks and their assignments, tags, notes, files you upload to import contacts (we delete the file when the import completes; if an import is abandoned or fails, the file can remain in our storage until we remove it), and an activity log of actions taken in your workspace (entries about actions on an email (replying, forwarding, archiving, tagging and similar) can include that message’s subject; these are deleted with that mailbox’s data, but not later entries about a task created from one of those emails, which keep the title copied from the subject; see section 7).

Connected mailboxes. When you connect a mailbox, we store the credentials we need to reach it (an app password for IMAP/SMTP, or OAuth access and refresh tokens for Google or Microsoft), and we sync and store the mail needed to show it in the shared inbox (for Outlook mailboxes, mail from all of its folders; see section 4):

  • message headers (sender, subject, date, and the recipients and cc: for synced mail as the mail provider gives them to us, for mail sent from Cranberry as you entered them; see below), a short preview, and the message body (text and HTML);
  • attachment names, types and sizes. We do not store attachment contents;
  • replies and forwards sent from Cranberry, and the tags and archive state your team applies.

People added automatically from email. For mail we sync or send, we add the other people on it to your workspace’s People list, as follows, and link a message to one of them where there is one:

  • For mail you receive, the person added is its sender.
  • For mail the mailbox itself sent (anything we sync from the mailbox’s own address), the people added are those it was addressed to, and the mail is linked to the first of them. For a reply or forward sent from Cranberry, that is every To and Cc recipient. For other synced mail from the mailbox’s own address, such as a note to yourself, it is the recipients the mail provider gives us: all To and Cc recipients for Gmail mailboxes, but only the first To recipient for IMAP and Outlook mailboxes. For Outlook mailboxes this includes messages in Sent Items, Drafts, Junk and its other folders, so an unsent draft can count.
  • We store each person’s email address and, for senders, the display name the message gives. This includes automated and no-reply senders.
  • Not added: the connected mailbox’s own address (a send-as alias of it can be, because we do not know a mailbox’s aliases) and Blind-copied (Bcc) recipients.
  • When you first connect or reconnect a mailbox, the mail it syncs is only linked to people who already exist: it does not create new ones.

These may be people who have not signed up for Cranberry: your workspace is responsible for having a legitimate reason to hold their details. Anyone in your workspace can see and edit them.

Technical information. Session cookies that keep you signed in, a short-lived cookie used while you connect a mailbox, your IP address (used for rate limiting and sign-in protection; your IP address and browser details are also stored with your sign-in session record for as long as that session exists), and server logs kept by our hosting provider. We do not use advertising or third-party analytics trackers.

2. How we use it

  • To provide and operate the features you see: the shared inbox, tasks, contacts and activity log, including adding the people on your mail to your People list (see section 1).
  • To keep the service secure: sign-in protection, rate limiting, abuse prevention and fixing errors.
  • To communicate with you about your account and respond to requests.

We do not sell your data. We do not use it for advertising. We do not use your mail or other workspace content to train machine-learning or AI models.

3. Google user data

You can connect a Gmail account with a Gmail app password over IMAP/SMTP; we then handle it like any other mailbox (stored encrypted credentials and synced mail, deletable as described in section 7). You can also connect Gmail with Google sign-in (OAuth). When you connect that way, we ask for one Google permission: https://www.googleapis.com/auth/gmail.modify(“read, compose and send emails from your Gmail account; does not allow immediate, permanent deletion”). We use it only to do what the shared inbox shows:

  • read your messages and attachment details so your team can read them in Cranberry;
  • send replies and forwards that you or a teammate compose in Cranberry;
  • archive a message (remove it from your Gmail inbox) when you archive it in Cranberry;
  • use the sender and recipient addresses (and a sender’s display name) of those messages to add people to your workspace’s People list, as described in section 1. We do not use Google data for anything else.

We store the Gmail data listed in section 1 in our database so the inbox works and your team can read it. We do not delete or permanently remove anything in your Gmail account.

Limited Use. Cranberry’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. In particular:

  • We use Google user data only to provide and improve the user-facing features described above.
  • We do not transfer Google user data to others except as needed to provide those features (for example, to our hosting and database providers), for security or abuse investigation, to comply with law, or as part of a merger or acquisition with your consent where required.
  • We do not use Google user data for serving ads, and we do not sell it.
  • Our people do not read your Google user data unless you ask us to and give consent for specific messages, it is necessary for security purposes (for example, investigating abuse or a bug), it is necessary to comply with applicable law, or the data is aggregated and anonymized for internal operations.
  • We do not use Google user data to develop, improve or train generalized AI or machine-learning models.
  • We apply these limits to Gmail data however it is connected (Google sign-in or an app password).

4. Microsoft user data

If you connect an Outlook / Microsoft 365 mailbox, we ask for Microsoft Graph permissions to read your mail, send mail and archive it, to look up your basic profile (to learn the mailbox address), plus offline access so we can keep the mailbox synced. We handle that data exactly as described for Google user data above: only to provide the shared inbox (including adding the people on that mail to your People list, as described in section 1), never for advertising, sale or model training. Gmail and IMAP mailboxes sync only the inbox. Outlook / Microsoft 365 mailboxes sync mail from all of the mailbox’s folders (for example Sent Items, Drafts, Junk and Deleted Items), not only the inbox.

5. Who we share data with

We use a small number of service providers to run Cranberry. They process data only to provide their service to us:

  • Vercel — application hosting, server logs, and temporary file storage for contact imports.
  • Neon — our database, where workspace content and synced mail are stored.
  • Upstash — short-lived rate-limit counters and locks (these include IP addresses and workspace identifiers, not message content).
  • Google, Microsoft and your own mail provider — the mailbox services you choose to connect.

Everyone in your workspace can see the workspace’s shared content, including any connected mailbox, by design. We may also disclose information if required by law or to protect the rights, safety or security of our users and the service.

6. Security

Data is sent over encrypted connections (HTTPS/TLS). Mailbox credentials and OAuth tokens are encrypted by us (AES-256-GCM) before they are stored, passwords are stored only as salted one-way hashes, and every workspace’s data is separated from every other workspace’s in our application. No system is perfectly secure, but we work to protect your information and we limit who can access it. Our operators can see technical error records, which can include identifiers, mailbox addresses, and the text of error messages returned by mail providers (which can echo addresses such as a recipient); we do not intentionally put message bodies or subjects in these error records (subjects do appear in the workspace activity log described in section 1).

7. Retention and deletion

We keep workspace content and synced mail for as long as your workspace uses Cranberry. You control deletion:

  • Delete a mailbox’s synced data yourself. In Settings → Stored mail, anyone in your workspace can permanently delete a mailbox’s stored sign-in (credentials and tokens), every message we synced from it and the tags applied to those messages, the activity entries linked to those messages or the mailbox, most technical error records that name the mailbox, and its “recently viewed” entries. Deleting also disconnects the mailbox. It is immediate and cannot be undone, and it never deletes anything in the mailbox itself. Not deleted: tasks your team created from those emails stay (with their link to the email removed) and keep the title and description that were copied from the email, along with later activity about the task, and your workspace’s activity log keeps a record that the deletion happened (who, when, the address and how many messages). The people added from that mail are not deleted with it: they stay in your People list (move them to the Trash there, below). Disconnecting a mailbox stops syncing and removes your team’s access to it in Cranberry, but keeps its synced mail and its encrypted stored sign-in until you delete the mailbox’s data.
  • Delete people added from email. Anyone in your workspace can delete a person from the People list. That moves the person to the Trash: they disappear from your People list, searches and pickers, but their notes, tags, company memberships and the emails and tasks linked to them stay (marked “Person in Trash”), and anyone in your workspace can restore them. Nothing in the Trash is emptied automatically, and a workspace member cannot erase a person for good; to have a person erased permanently, email us and we will erase the person record, their notes, tags and company memberships, and remove the link from their emails and tasks (the emails and tasks themselves stay). Activity log entries about the person stay in your workspace’s activity log, including earlier ones that name them (for example when they were added or edited) and a record that you moved them to the Trash (who and when, with their name or address), except that when we erase a person we also clear the text of the activity entries linked to them. Mail from or to the address of a person in the Trash is linked to that person and does not add a second one; after a person is erased for good, new mail from or to the same address adds them again, as it would for anyone new.
  • Revoke Cranberry’s access. Deleting a mailbox’s data removes the credentials we hold. If you connected Gmail with Google sign-in, we also ask Google to revoke Cranberry’s access at that moment (unless another Cranberry workspace also holds a mailbox for the same Google address, in which case we leave Google’s access in place, because revoking it could cut that one off too). We record the outcome in your workspace’s activity log, and we tell you if Google could not confirm it or we left it in place, in which case remove it yourself at myaccount.google.com/permissions (you can also do this at any time). For other connections, deleting does not cancel them at your provider: if you connected Gmail with an app password, delete that password at myaccount.google.com/apppasswords; for Microsoft sign-in, remove it at account.live.com/consent/Manage (personal accounts) or myapps.microsoft.com (work or school accounts). You can do this at any time.
  • Delete your account or workspace. Email us at the address below and we will delete your workspace and its data within 30 days. Deleted data may remain in our database provider’s backups for a limited time before it ages out.

8. Your choices and rights

You can ask us to access, correct or delete your personal information, or to send you a copy of it, by emailing us. Depending on where you live (for example, the EEA, UK or California) you may have additional rights under local law, and we will honor them. Within a workspace, any member can edit or delete the workspace’s contacts, tasks and tags. If you are not a Cranberry user but your details appear in a workspace (for example because you emailed one of its mailboxes), you can email us at the address below and we will help you with a request to access or remove them.

9. Cookies

We use only essential cookies: a session cookie that keeps you signed in, and a short-lived, single-purpose cookie that is set while you connect a mailbox with Microsoft sign-in or Google sign-in and is cleared when you finish (or expires after 10 minutes if you do not). We do not use advertising or analytics cookies.

10. Where data is processed

Our providers may process data in the United States and other countries where they operate. By using Cranberry you understand your information may be transferred to those countries.

11. Children

Cranberry is a business tool and is not directed to children under 16. We do not knowingly collect their personal information.

12. Changes to this policy

We may update this policy. If we make a material change we will update the date above and, where appropriate, notify workspace members. Using Cranberry after a change means you accept the updated policy.

13. Contact

Questions, privacy requests or deletion requests: hi@cranberrycrm.com.