Security and privacy

This page answers what you would ask before letting June into your mail, files and code: who can see what, where your sign-ins are kept, and what leaves June. The privacy policy is the legal text and names every service provider.

Your account

You sign in on June's sign-in page; June never stores your password. There is no button to delete your account yet: see your data below.

Who sees your chats

• Your own chats are yours. Other people, including your organizations' members, do not see them.
• An organization's chats and projects are visible to every member of that organization. The exception is Slack: a direct message with June, and a thread in a private Slack channel, are seen only by the people in them. Leave the organization and you stop seeing its chats.
• A share link makes one conversation readable by anyone who has the link (see below).

Your connections

When you connect a tool on the Integrations page, its password or token is stored encrypted on June's servers.

• The code June runs never sees it. For GitHub and ownCloud, June's sandbox holds no password or token at all: your sign-in is added to its requests to that service on the way out.
• The one exception is Tailscale. June's sandbox joins your tailnet as one of your devices, so it holds that device's key while it runs (Tailscale).
• June reaches only what the account you connected reaches, within the permissions you granted. Each integration's page says what June may read and change.
• A step that needs your confirmation, such as creating a calendar event, sending a Teams message or sending an email, runs only after you approve it on a card in a chat on the web, in the app or in Slack, exactly as the card shows it, once. Only the person whose message led to it can approve it. Everywhere else June turns it down, and nothing is created or sent (how).
• A connection from your Integrations page works in your private chats and every organization you're in unless you mark it Personal only; one made inside an organization stays there (personal or organization). In a shared thread, June uses the connections of the person it is answering (whose sign-in June uses).
• Disconnect on a connection's row removes it, and June stops using it at once. Some providers also list June as an app with access to your account; remove it there too if you want the provider to forget the grant.

What reaches the model

To answer, June sends the conversation and the context it needs (memories, files you attached, results from your tools) to the model that runs the reply, only to produce that reply:

• your ChatGPT plan, if you connected it: OpenAI;
• your Claude plan, if you connected it: Anthropic;
• an API key you or your organization added: that key's provider;
• otherwise June's default model, currently an OpenAI model.

An organization can set one funding source that pays for every turn in it; then that source's provider gets the organization's conversations. Models and who pays says which model runs a reply.

Share links

A share link is a public, read-only copy of one conversation: anyone with the link can read it, and the files and images in it unless you switch them off. June's tool steps and reasoning are left out, shared pages are kept out of search engines, and deleting the link ends access at once. Share a conversation covers frozen and live links, attachments and deleting a link.

Memory

June remembers facts, preferences and decisions from your conversations so you do not repeat yourself. The Memory page lists what it saved. Forget a memory there and June stops recalling it; the memory's history is kept, but it does not come back on its own. In an organization's chats and in Slack channels June uses that chat's own memory, never your personal one, and keeps personal facts out of it. Your personal memory and Soul are yours alone; a memory saved in an organization's project shows to everyone in the organization. See Memory and shared chats.

Analytics

June uses product analytics and error reports to find what breaks, hosted in the EU. Session recordings mask everything you type and leave out chat content and attachments.

Your data

Your account, conversations, attachments and the encrypted sign-ins of your connections are stored with the hosting providers the privacy policy names. June uses them to run the service, answer your support requests, keep the service secure and make it more reliable.

June keeps your data as long as it needs it to run your account, unless the law requires it to keep some longer. To have your account and its data deleted, use the contact in the privacy policy.