Privacy Policy

Effective date: October 1, 2026 · Last updated: October 1, 2026

June processes your documents and emails inside your own browser, and we do not receive, store or read them. This Privacy Policy explains what limited information we do handle when you use June, the AI legal assistant available at june.ambiency.ai (the "Service").

The Service is operated by MB Ambiency, a company registered in Lithuania under company code 307536078, with its address at 1 Savanoriu av., Vilnius, Lithuania ("we", "us", "our"). For questions, contact team@ambiency.ai.

How June is built

June runs client-side: its code executes in your browser, and your browser talks directly to the services you connect (such as Gmail, Google Drive and Docusign). Contract drafts, emails, files and the knowledge June builds about your company are kept in your browser and in your own connected accounts. They are not sent to or stored on our servers. To generate drafts, your browser sends the relevant text directly to Google's Gemini models on Vertex AI.

Category What it includes Where it goes
Account information Your name, email address and profile picture from Google Sign-In Our authentication provider (Google Firebase), to let you sign in
Google user data Gmail messages and settings, and Google Drive files you choose to sync Processed in your browser; relevant text is sent directly to Google's Gemini models on Vertex AI to generate output; never sent to us
Other connected services Data from Docusign, Slack, Asana or Jira that you connect Processed in your browser only; never sent to us
Content you add Templates, playbooks, policies and approval rules Stored in your browser or your own connected storage
Technical data IP address, browser type and request logs from our hosting provider Our hosting provider, for security and reliability
Communications Emails you send us, such as support requests or demo bookings Our email system

We do not use advertising cookies or sell any personal information. We may use anonymized, aggregated usage data, such as which features are used, error reports, and browser and device type, to understand how June is used and to improve it. This data does not identify you and never includes the content of your emails, documents or files.

How June uses your Google data

June runs inside your own browser, and it works with your Gmail and Google Drive only after you approve it on Google's consent screen. This data stays between your browser, your Google account and Google's Vertex AI. We never have access to it.

Permission (scope) Why June needs it
Basic profile and email (openid, email, profile) To sign you in and show which account is connected
Read Gmail (gmail.readonly) To find counterparty details and contract requests in your inbox
Create Gmail drafts (gmail.compose) To prepare follow-up and signature emails as drafts for you to review and send
Google Drive To read the templates and contracts you sync to June, and save drafts and signed copies

June never sends an email on its own. It creates drafts, and by default a person must approve any message before it goes to a counterparty.

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. In particular:

How we use and share information

We use the limited information we hold to run your account, keep the Service secure, answer your messages and tell you about important changes. We do not sell personal information or share it for advertising.

We rely on these service providers, each bound by data protection terms:

We may also disclose information if the law requires it, to protect rights and safety, or to a successor in a merger or acquisition, with notice to you.

Storage and retention

June keeps your working data (drafts, extracted details, company memory) in your browser's local storage and in your connected accounts. You can delete it at any time by disconnecting an account in June, clearing site data in your browser, or revoking access at myaccount.google.com/connections.

We keep account information for as long as your account is active and delete it within 30 days after you ask us to close it. Hosting logs are kept for up to 30 days.

Security

Connections to Google and other services use encrypted HTTPS and OAuth, so June never sees your passwords. Access tokens stay in your browser. No method is perfectly secure, so please keep your device and browser protected.

Your rights

If you are in the European Economic Area, the UK or another region with similar laws, you can ask us to access, correct, delete, restrict or export your personal information, and you can object to how we process it. Our legal bases are performing our contract with you and our legitimate interest in running a secure service. You may also complain to your local data protection authority. To make a request, email team@ambiency.ai; we reply within 30 days.

If we transfer personal information outside the EEA, we use safeguards such as the European Commission's Standard Contractual Clauses.

Children

June is a business tool and is not intended for anyone under 18. We do not knowingly collect information from children.

Changes to this policy

We will post any changes on this page and update the date above. If a change is significant, we will tell you by email or in the app before it takes effect.

Contact

MB Ambiency, 1 Savanoriu av., Vilnius, Lithuania · team@ambiency.ai