How June handles your data.

The short version

Your saved journal is stored on your devices and, when available, synced through your private iCloud database. June does not keep a separate server-side database containing your complete diary. AI features, analytics, diagnostics, purchases, attribution, and scheduled calls still require specific data to be processed by the services described below.

Journal storage

Journal entries, June's saved notes about you, search history, and photo references are stored in June's database on your device. Synced journal data uses your private iCloud database. The current chat thread, call-capture work in progress, and search embeddings remain local to the device.

June uses an iCloud-derived identifier when an iCloud account is available and an install-scoped identifier otherwise. These identifiers let the app connect the correct devices, schedules, limits, purchases, and service requests without a separate email-and-password account.

AI processing

A live voice call sends the conversation audio and context directly from your device to Google Gemini Live. June's Cloudflare service issues the short-lived connection token. Text used for semantic search embeddings is also sent to Google Gemini through that service.

Chat messages, home prompts, call transcripts used to write summaries, and recent-entry context are sent through June's Cloudflare service to OpenRouter and the model provider selected for that feature. A chat voice note is sent for transcription, and the local audio clip is removed after successful transcription. Photos or other media you deliberately attach may also be processed for the requested feature.

Google, OpenRouter, and their downstream model providers process these requests under their own terms, privacy policies, and retention controls. June does not make a separate promise here about how those providers train models or retain submitted content.

June's service data

June's service runs on Cloudflare. It processes request content, an account or install identifier, App Attest security data, rate-limit counters, and error information. To schedule calls it also stores your selected call time and timezone, push notification tokens, device registrations, and recent-call state in a per-user Cloudflare Durable Object.

This operational state is not a copy of the complete journal, but prompts and journal excerpts you send to an AI feature pass through the service while the request is handled.

Analytics and diagnostics

June uses PostHog for product analytics, session replay, diagnostics, server logs, and AI observability. Data can include app and device metadata, feature interactions, an account or install identifier, warning and error details, model and token usage, and the content of AI inputs and outputs. In particular, AI traces for chat, home prompts, and call summaries can include prompts, responses, recent-entry context, and the call transcript submitted for summarization.

Media bytes are removed from June's AI-observability traces, although text derived from that media and surrounding conversation content may still be present. Development and test builds do not send production analytics.

Purchases and attribution

Apple processes App Store downloads and payments. June uses RevenueCat to manage products, trials, subscriptions, entitlements, paywall activity, and selected usage attributes connected to the June identifier.

June also uses Apple advertising attribution and the Meta SDK to understand campaign and purchase performance. Meta may receive app activation, registration, subscription, and device-attribution signals. Access to Apple's advertising identifier depends on the permission choice presented by iOS. June does not show third-party ads inside the app and does not sell personal information.

Retention and your choices

The in-app Delete everything control removes June's per-user Cloudflare state, wipes the journal and chat data on that device, and asks iCloud to propagate the journal deletion to your other devices. Deleting only the app may leave synced data in iCloud and data already processed by service providers.

PostHog, Google, OpenRouter, downstream model providers, RevenueCat, Cloudflare, Meta, and Apple retain information according to their own settings and policies. For a privacy question or a request concerning information controlled by June, use Settings → Problems & Suggestions or email contact@talkjune.com.

A note for younger users

June is made for adults and isn't intended for children.

Changes to this policy

When June's data practices change, the current policy will be posted here with an updated date.