Your privacy with Milo.
Updated October 11, 2026
Milo uses the information you share and the connections you enable to help with your requests.
The Milo waitlist
When you join the waitlist, we store your email address and signup details in private Vercel Blob storage to contact you about Milo access. Waitlist addresses are not published on this website or sent to the AI model. Repeat submissions update the existing signup. Joining the waitlist does not create a Milo app account.
Conversations and saved context
Your messages, task results, and saved memories are processed and stored by Milo’s backend so your conversation can continue across requests. Relevant conversation and tool results are sent to an AI provider to produce responses. Milo currently uses OpenAI models.
Images you attach
You can choose images, including screenshots, using the iPhone system photo picker and attach up to two to a message. Milo receives only the images you select through that picker, not access to your entire photo library. Selected images are resized and re-encoded as JPEG before they are sent with your message.
Attachments are stored with your chat history on Milo’s backend. Up to six recent attached images may be included in the conversation context sent to OpenAI so Milo can understand and respond to them. Sending an image does not automatically post it publicly or send it to another person. Chat messages and attachments are not end-to-end encrypted. Avoid attaching screenshots or images containing information you do not want Milo and its processing providers to receive.
Attachments follow the same stored-history and deletion controls as your conversations. Disconnecting a Google account does not delete attached images or other existing chat history. Use the contact instructions below to request deletion.
Connections you choose
Calendar and email connections let Milo access information covered by the permissions you grant. If you allow Contacts access, contact information can be synced to Milo’s backend to help find people you mention. Features that use phone authentication use Firebase.
Website logins saved in Milo are encrypted on the server and used for website sign-in. The saved passwords are not included in AI prompts. Website content and task results may be included.
Google Calendar and Gmail
When you connect Google Calendar, Milo reads the list of calendars available to your account and events from the calendars you enable. It uses event titles, times, locations, descriptions, and attendee information to answer scheduling questions and help create, change, or remove events at your request.
Connecting Gmail for sending lets Milo send the message you review and explicitly confirm. Inbox access is a separate connection option. With inbox access, Milo can search and read messages, conversation threads, and supported small text attachments to answer your requests and draft replies. If you separately enable email updates, Milo checks new inbox messages for important updates and possible replies. Connecting a calendar alone does not grant inbox access.
Relevant Google Calendar and Gmail content may be processed by OpenAI to answer your request, summarize an email, or prepare a draft. Google account identifiers, granted permissions, and encrypted access credentials are stored on Milo’s backend. Information included in conversations, task results, summaries, and drafts may also remain in your history.
Disconnecting Google
Disconnect a Google account in Milo’s Connections settings to remove its saved access credentials from Milo and request revocation at Google. You can also review and remove Milo’s access in your Google Account connections. Disconnecting does not delete your original Google Calendar events or Gmail messages, and it does not erase content already saved in Milo’s conversation history or backups. For a request to delete stored Milo data, use the contact instructions below.
Service providers
Milo’s backend is hosted on DigitalOcean. This website is hosted on Vercel. Connected services, AI providers, and browser infrastructure may process information needed to complete a request. These services also process operational information, such as network requests, according to their own policies.
Your controls
You can manage connections and saved memories in Settings and change device permissions in iPhone Settings. Disconnecting a service stops future access through that connection; it does not automatically erase information already saved in conversations.
Email sending requires your explicit confirmation. Avoid sharing information in chat that you do not want processed by these services.
Questions or deletion requests
During the beta, use Send Beta Feedback on Milo’s TestFlight page to contact the developer about access, deletion, or other privacy questions. See Support for instructions.
This website
We use PostHog to compare website wording and understand visits, button clicks, and completed waitlist signups. A random browser identifier keeps your experiment version consistent. We do not send your waitlist email address or form contents to PostHog, and session recording is disabled. Local development and explicit copy-preview links are excluded. Clear this site’s browser storage to reset your identifier. PostHog processes these website events; see PostHog’s privacy policy. Our hosting provider also processes requests and operational logs to deliver and secure the site.