# FAQ > Short answers to what people ask about June: training, who reads your chats, Slack, memory, who pays, deleting your account, email and more. Source: https://www.dearjune.ai/docs/faq Start here for a quick answer about privacy, memory, payment or a missed reply. Each answer links to the steps and limits; for a failure you are trying to fix now, use [Troubleshooting](/docs/troubleshooting). ## Is my data used to train models? June uses your data to run the service: to keep your account, process your messages and files, operate the tools you connect, answer support requests, secure the platform and improve reliability. Training models is not one of those uses in the [privacy policy](/privacy). To answer, June sends the conversation and the context it needs to the model that runs the reply, only to produce it. ## Can my organization read my chats? No, not your personal chats: no one in your organizations sees them, and admins get no extra access. An organization's own chats and projects are visible to every member, except a Slack direct message with June or a thread in a private Slack channel, which only the people in it see. See [who sees your chats](/docs/security-and-privacy#who-sees-your-chats). ## Why didn't June answer in Slack? In a channel, June answers only when you mention it, every time, even in a thread it already answered. When you did mention it: - **The workspace is not added to June:** June stays quiet. - **Your Slack account is not linked yet:** June sends you a direct message with a link. - **Nothing can pay** (no connected plan, no organization funding source): June sends you a direct message with a link to connect a model credential. - **You are a guest or from another organization:** June replies "June here is only for full members of this Slack workspace, not guests or people from other organizations." - **The channel is shared with another company:** June treats its threads as private, and the people from the other company get no answer. See [Use June in Slack](/docs/getting-started/slack). ## Why did June forget something? On the web and in the app, June brings into a reply the 8 memories that match your message best. When one is missing: - **It is not saved yet:** June saves a memory a while after a conversation goes quiet, or right away when you ask. - **Your message did not match it:** ask about it directly, or tell June again. - **It was forgotten** with **Forget** on the **Memory** page. - **It belongs to another place:** an organization's chats do not use your personal memory; in a Slack channel June saves facts to the channel or its project, never to a person; a thread in an organization's private Slack channel saves nothing. See [Memory](/docs/memory). ## Who pays for a reply or a schedule? The space's funding source, if it has one, pays for every turn there, schedules included. Without one, a reply runs on the asker's own plan or on June, and a schedule runs on the plan of whoever set it up, or on June when they have none. See [who pays for a turn](/docs/models#who-pays-for-a-turn). ## How do I delete my account? Ask through the contact in the [privacy policy](/privacy); June deletes your account and its data. There is no delete button in the app. ## Can June send email for me? Yes, from a connected Gmail account. June can send a new message or an existing draft; sending asks for approval by default. Review the sending account, recipients, subject, text and attachments on the card before approving. A saved approval permission can allow later sends without another card; see [Approvals](/docs/settings/approvals). Outlook and IMAP mailboxes support drafts only: you send those from your mail app. See [Mailbox](/docs/integrations/mailbox) for what each connection supports. A scheduled run of one of your [agents](/docs/agents) can also send through a sending (SMTP) connection if it was granted email sending, without a confirmation step. The **Integrations** page has no way to add that connection. ## Can I edit a memory? No. Choose **Forget** on the **Memory** page, then tell June the right version in the place where it belongs: a personal chat for your own facts, or the project chat for project facts. Forgetting leaves the original conversation and the memory’s history intact. See [forget a memory](/docs/memory#forget-a-memory). ## Does June know my time zone? No, June is not told where you are. Name the time zone when it matters; a reminder or schedule set without one runs in UTC. See [Follow-ups](/docs/follow-ups). > Example prompt: Remind me at 9:00 Berlin time tomorrow to call the bank ## Can June make images? Yes, on the web and in the app, when the reply runs on a ChatGPT plan; with any other model it cannot. See [Use your ChatGPT or Claude plan](/docs/models/your-plan). ## Can I use June in Claude Code or Codex? Yes. Connect Claude Code, Codex or another client to June, and it can use the connections of your personal space, not an organization's. A step that needs your approval gives you a link to approve it in June; once you have, the client reports what ran. See [June MCP](/docs/june-mcp#when-a-step-needs-your-approval). ## What happens when I leave an organization? Its chats and projects close to you at once, schedules you set up there stop, the work accounts you connected only for it are removed, and your personal connections stop working there. If you shared your plan with it, the plan stops paying; if that was its funding source, every reply there says the source can't pay because its owner left the organization, until an admin picks another in the organization's Funding section. See [leave an organization](/docs/organizations#leave-an-organization). ## Why didn't my schedule read my mail? A schedule June sets up from chat runs without your tools unless you asked for them. Ask June to turn on the `integrations` toolset for it (or `web`, `documents`, `terminal`), or list them under **Enabled toolsets** on the form. See [what a run can use](/docs/how-june-works/schedules#what-a-run-can-use). ## Why does a failing schedule keep running? June does not stop a schedule when its runs fail: it keeps running at its next times. The **Schedules** page lists it under what needs attention; open its history to see why, then fix it, **Pause** it or **Delete** it. See [the Schedules page](/docs/follow-ups#the-schedules-page). ## More help - [Limits](/docs/limits) lists every number in one place. - [Troubleshooting](/docs/troubleshooting) covers the common problems step by step. - [Support](/docs/support) to report a bug.