June — Privacy Policy

Version 1.0 · Effective 23 July 2026

This policy explains what personal data June collects, why, who it goes to, how long we keep it, and what you can do about it.

Data controller: L'Atelier Gege LLC (Лателиэр Гэгэ ХХК), a company registered in Mongolia. Contact for privacy matters: hello@gege.mn.

It applies to june.gege.mn, June's mobile apps, her HTTP API, and her MCP server (the "Service").

We process personal data under the Law of Mongolia on Personal Data Protection and, where it applies to you, the EU/UK GDPR (see Section 11).

1. The short version

• June is an assistant for personal and professional life, so she holds genuinely personal material: your conversations, your calendar, your contacts, and facts she remembers about you.
• We do not use your data to train AI models. We do not sell it. We run no advertising, no analytics, and no third-party tracking of any kind.
• To answer you and act for you, we send the relevant parts of your data to Google's Gemini API, and we run on Cloudflare. Both are outside Mongolia. That cross-border transfer is inherent to how the Service works.
• Our staff can technically read your data, and will do so only when needed to support you or fix a fault.
• You can export your data and delete your account.

2. What we collect

We collect only what June needs to work. Nothing here is bought from data brokers or inferred for advertising.

2.1 Account and identity

From your Google sign-in: your name, email address, profile picture, Google account identifier, and the session and authentication records that keep you signed in.

2.2 What you tell June

• Conversation history — every message you send and June sends back, in one continuous thread, together with the tool receipts and outcome notes attached to each turn (what June did, whether it worked, what error came back).
• Memory profile — durable facts June saves about you: preferences and habits, people and relationships, projects and work context, logistics such as working hours and addresses. Facts you correct are marked superseded rather than erased, so the history of what June believed stays auditable.
• Tasks and notes — titles, plans, notes, due dates, tags, and links.
• Sticky notes — short-lived items you ask June to hold, including any code or reference you put in them.
• Reminders and schedules — the reminder text, its recurrence, your timezone, and a delivery record for each firing.

2.3 From accounts you connect

• Google Calendar — events, times, titles, participants, and free/busy, for calendars you authorise.
• Google Contacts — display, given and family names, email addresses, phone numbers, organisation, job title, photo, birthday, and notes, for contacts you sync. This is other people's personal data that you bring in; see Section 4.

2.4 Generated by using the Service

• Activity log — a record of each action June performed for you: which action, whether it succeeded, the error code if not, and when.
• Usage counters — daily message counts and token tallies, used for fair-use limits, billing, and understanding cost.
• Settings — your timezone, autonomy preferences, and similar.
• Files — documents, exports, and attachments June stores for you.

2.5 Credentials and technical data

• OAuth tokens for the accounts you connect, including refresh tokens so June can act while you are away.
• Technical request data — IP address, user agent, timestamps, and request logs generated by our infrastructure provider for security, abuse prevention, and debugging.

We do not collect or store your payment card or bank details — see Section 8.

3. Sensitive personal data

Some of what you may tell June counts as sensitive personal data («эмзэг мэдээлэл») under Mongolian law and as special category data under the GDPR: information about health, sex life or sexual orientation, religion or beliefs, political views, ethnic origin, genetic or biometric data, or criminal matters — plus, in practice, precise home addresses and financial account details.

How June handles it:

• She will never save such a fact proactively. She saves it only when you explicitly ask her to remember it.
• Any such save is flagged as sensitive with a stated reason, shown to you in the chat, and is one click to remove.
• She is instructed to refuse to store credentials, passwords, API keys, and recovery codes, and to point you to a password manager instead.
• Honest limitation: facts marked sensitive are stored in our database in plain text, like all other memory content. They are protected by our infrastructure provider's encryption at rest and by our access controls — but not by any additional application-level encryption. Do not give June anything whose exposure you could not tolerate.

Our legal basis for processing this category is your explicit consent, given by asking June to remember it. You can withdraw that consent at any time by deleting the memory.

4. Other people's data

June holds information about people who are not our users — your contacts, calendar guests, email recipients. When you bring that data in, you are responsible for having the right to do so, and we process it on your instructions to provide the Service to you. We do not use it for any other purpose, do not build profiles of those people, and do not contact them except when you instruct June to.

5. Why we process it, and on what basis

We never use your data to train AI models, sell or rent it, use it for advertising or profiling, or share it for anyone else's marketing.

6. AI processing — what goes to Google

This is the part people most want to know, so we state it plainly.

To answer you or act for you, we send Google's Gemini API the parts of your data needed for that turn: your message, recent conversation history, relevant memory facts, the definitions of the tools June can call, and any data a tool returned (for example, the calendar events she just read).

• Google processes this under Google's Gemini API terms. We use the paid API tier, whose terms exclude using inputs and outputs to improve Google's models.
• Google's servers are outside Mongolia.
• We use a main model for the assistant loop and a smaller model for internal work such as tidying your memory profile.
• We do not send Google more than the turn needs, but we cannot guarantee any particular piece of your data will never be relevant to a turn.

If you are not comfortable with this, do not put the material into June.

6a. Google user data — Limited Use

June's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Concretely, data we obtain from Google Calendar and Google Contacts through the scopes you approve is used only to provide and improve the user-facing features you asked for. We do not:

• transfer it to others, except as needed to provide those features, for security purposes, or to comply with the law;
• use it for advertising, ad personalisation, or any marketing purpose;
• use it to train generalised AI or machine-learning models. Where a model is involved in producing a response for you, it is Google's Gemini API on the paid tier, whose terms exclude training on inputs and outputs (see Section 6);
• allow humans to read it, except with your explicit consent for a specific issue, where necessary for security or to comply with the law, or where the data is aggregated and anonymised.

The scopes June requests, and the reason for each, are listed on our home page and in Section 5 of the Terms of Service. You can withdraw any of them at any time from June's settings or from your Google Account permissions.

7. Cookies and tracking

We use only the cookies necessary to sign you in and keep your session.

We run no analytics, no advertising pixels, no session recording, and no third-party trackers. This is a deliberate product decision, not an oversight: June handles personal material and we do not want third parties in that path.

8. Who we share data with

We use a small set of providers. Each acts on our instructions or as an independent controller for its own narrow purpose.

We also disclose data where legally required — to a court, regulator, or law enforcement body acting under valid Mongolian legal process — and, if we are ever party to a merger or sale of assets, to the acquirer, with notice to you and no reduction in the protection of this policy.

We will publish updates to this list before adding a provider that receives your personal data.

9. International transfers

Your data is stored and processed outside Mongolia. Cloudflare and Google operate global infrastructure; your conversations, memory, tasks, contacts and files live on their servers, and prompts are processed by Google in its data centres abroad.

Mongolian law requires your consent for cross-border transfer of your personal data. By creating an account and using the Service, you consent to this transfer. It is not optional — the Service cannot function without it, so if you do not consent, please do not use June.

For users in the EEA or UK: these transfers rely on the providers' Standard Contractual Clauses and equivalent safeguards, and on the necessity of the transfer to perform our contract with you.

10. How long we keep it

We keep data for as long as needed for the purpose it was collected for, and no longer.

Being straight with you: automatic scheduled pruning is a design commitment we are still implementing. Today, deletion happens when you ask for it or when you delete your account. We will tighten this table once the automated jobs are running, and will not weaken it.

11. Your rights

Under the Law of Mongolia on Personal Data Protection you have the right to:

• know what data we hold about you and how it is processed;
• access it and get a copy;
• correct it if it is inaccurate or incomplete;
• delete it, and to have processing stopped;
• withdraw consent you previously gave, including for sensitive data and for cross-border transfer — noting that withdrawing transfer consent means we cannot continue providing the Service;
• complain to the competent Mongolian authority if you think we have handled your data unlawfully. Mongolia does not have a single dedicated data protection authority; oversight is shared, and complaints about the handling of personal data can be made to the National Human Rights Commission of Mongolia (https://en.nhrcm.gov.mn) or to the Ministry of Digital Development, Innovation and Communications.

If you are in the EEA or UK, you additionally have the rights to restriction of processing, to data portability in a machine-readable format, to object to processing based on legitimate interests, and not to be subject to solely automated decisions with legal or similarly significant effects. We do not make such automated decisions about you. You may complain to your local data protection authority.

How to exercise any of these: email hello@gege.mn, or use the export and delete controls in June's settings. We respond within 30 days. We may ask you to verify your identity first.

12. Deleting your data — what actually happens

We would rather be precise than reassuring.

• Deleting a memory removes it. Facts June has superseded (replaced with a newer version) are kept as history until you delete your account, so the record of what she believed and when stays honest.
• Deleting a task moves it to trash first, so you can undo it. It is removed for real when you empty the trash or delete your account.
• Deleting your account erases your conversations, memory, tasks, reminders, contacts, files, settings, activity log, and stored tokens. We keep only what law requires us to keep — principally billing and tax records.
• Backups. Deleted data can persist in our infrastructure provider's backups and replicas for a short period until those roll over. It is not restored to the Service.
• Data already sent to third parties — a calendar event June created, an email she sent, a prompt Google processed — is outside our control and is not recalled by deleting your account.

13. Who at our company can see your data

Our staff can technically access the data stored by the Service. Access is limited to what is needed to support you or investigate a fault, restricted to personnel who need it, and subject to confidentiality obligations.

We do not browse user data out of curiosity, and we do not read your conversations for product research. If a support issue requires us to look at your data, we will tell you where we reasonably can.

We cannot honestly claim your data is unreadable to us — the Service is not end-to-end encrypted, because June must be able to read your data to work.

14. Security

• All traffic runs over TLS.
• Data at rest is encrypted by our infrastructure provider.
• OAuth tokens are held in a scoped token layer, are never written to logs or error messages (only provider names appear), and are revocable by you.
• We request the narrowest OAuth scopes that make a feature work, and ask for new ones incrementally rather than up front.
• Content that June ingests from tools — calendar invites, files, emails — is treated as untrusted input, never as instructions. This is enforced in the action layer, so a malicious calendar invite cannot make June act or plant a memory.
• Access to production systems is limited to personnel who need it.

No system is perfectly secure. If a breach affects your personal data, we will notify you and the competent authority as the law requires, without undue delay.

15. Children

The Service is for adults. It is not directed at anyone under 18, and we do not knowingly collect data from anyone under 18. If we learn that we have, we will delete the account and its data. If you believe a minor is using June, contact us.

16. Changes to this policy

We may update this policy. For material changes we will give at least 30 days' notice by email or in-app before they take effect, and the new version will carry a new effective date. Where a change requires your consent under Mongolian law, we will ask for it rather than assume it.

17. Contact

Questions, requests, or complaints about your data:

L'Atelier Gege LLC (Лателиэр Гэгэ ХХК), registered in Mongolia Privacy contact: hello@gege.mn Web: https://june.gege.mn

We aim to answer within 30 days.