Legal

Privacy Policy

Effective 31 October 2026 · Agentarchy Labs Pvt. Ltd.

1.Who we are

This policy explains how Agentarchy Labs Pvt. Ltd. (“Agentarchy”, “we”, “us”), a company based in Pune, Maharashtra, India, handles personal information when you use Sage: the Sage apps for iPhone and Mac, the Sage Chrome extension, Sage’s phone number and messaging channels, and the services behind them (the “Service”). Agentarchy decides how and why this information is processed; under India’s Digital Personal Data Protection Act it is the Data Fiduciary, and under the GDPR and UK GDPR the controller.

Questions or requests: privacy@agentarchy.ai. Our Grievance Officer is Omkar Phatak, reachable at the same address (section 13).

2.The information Sage handles

Your account

Your name and email address from Sign in with Apple, Google sign-in, or email sign-up (with a hash of your password, never the password itself); your passkeys; the devices you have signed in on; and, for each session, the device type and an approximate region derived from its IP address. If you use Apple’s Hide My Email, Sage sees only the relay address.

What you tell Sage

Your messages, typed or spoken, Sage’s replies, and the files and photos you attach. Sage also keeps what it learns about you — facts, preferences, corrections and notes it writes about your day — so it can refer to them later, and records of the tasks, routines, reminders and approvals you create.

Saved places. When you save a place (Home, Work, or one you name), Sage keeps the map pin you confirmed, its Google Maps place ID, the address and spoken names you gave it, any flat, wing, floor and building details, your note for drivers, and when you saved and last used it. Sage uses them to plan routes and tell you when to leave. These are encrypted at rest on our servers with your account’s key. We keep them until you delete the place or your account. A deleted place can be restored for 10 minutes, then it is gone for good. A pin Sage found on Google Maps that you have not confirmed yet is dropped after 30 days. To delete a place, open Settings › Places or ask Sage. Deleting your account removes all of them.

Connected accounts

When you connect Google, Notion, GitHub, Spotify, Calendly, Cal.com, Zoho, Stripe, Razorpay, Atomberg, Home Assistant, Asana, Todoist, Airtable, X and 1Password, Sage stores the access token or API key and uses it to read from, and where you allow it write to, that account on your behalf. Content it reads there — an email, a calendar entry, a document, a message — can be quoted into a conversation or noted in memory. Google data is covered in detail in section 4.

From your devices, with your permission

• Contacts (iPhone) — the names and phone numbers in your address book, and nothing else from a contact: no photos, email addresses, birthdays or notes. Postal addresses only if you turn that on separately, so Sage can plan a trip to someone or send something to them. Sage uses contacts to know who you mean and to reach them when you ask. These are other people’s details, so they are never sold, never used for advertising, never used to look anyone up, and never shared with another Sage account.
• Calendar (iPhone, Mac and connected accounts) — if you turn it on, Sage keeps a copy of your calendars: the calendars on your iPhone and Mac, and a connected Google or Microsoft calendar. That is each event’s title, time, place, attendees and notes, past and upcoming, so Sage can find free time, plan travel between meetings and tell you when to leave. Attendees are other people’s details and get the same protections as contacts.
• Location (iPhone) — only the kinds you turn on:
  • Your city: your city, region and country, and a point rounded to about 11 km, for near-me, weather and travel questions. Sage keeps only the latest one and deletes it 24 hours after your phone read it.
  • Exact location when you ask: when you ask something that needs where you are right now (the nearest petrol pump, how long to get home from here), Sage asks your iPhone for one reading of your precise position, while you allow Location for Sage and leave “Exact location when I ask” on in Settings › Location. It is used for that question: sent to Google Maps for the lookup and never written to logs, and the AI model sees only the answer (places, distances and times), not the position. It is never saved as a location record, except your latest parking spot (below). So that one answer does not ask your iPhone twice, Sage holds the reading in memory for about 90 seconds (a search and then a route use the same one), and an answer for about a minute, so the same lookup asked twice in one reply is not repeated; neither is ever written down. When you ask for a route from where you are, or ask where you are, the map in Sage’s reply shows your starting point (and the route), and that map is kept with the conversation, start included, for 30 days; after that only the text of the reply remains. If the Sage app is closed, Sage may wake it with a silent notification to ask; your iPhone only gives an exact position while Sage is open.
  • Your parking spot: the one exact position Sage keeps. When you tell Sage you parked (“I parked here”, “parked at level B2, pillar 14”), Sage asks your iPhone for one reading of your precise position and keeps it with your note and the time; the reading is sent once to Google Maps for the name of the place (“Phoenix Marketcity”), which is kept with it. If you leave “Driving detection” on, your iPhone also does this by itself when it sees a drive end, but only while Sage is open (or you allow Location “Always”), within 5 minutes of the car stopping and before you walk away; otherwise it saves nothing rather than a pin that may be wrong. Sage keeps only your latest spot, encrypted with your account’s key, and uses it to show you the way back to your car. It is deleted when your next drive starts, or 7 days after you parked; turning driving detection off deletes a spot it saved. Like a route from where you are, the map in the reply shows your position and the car.
  • Location in the background (place alerts): when you set an alert for a place (“when I get home, remind me to …”), Sage keeps the alert, the place’s name and address, and its point on the map, so your iPhone can watch it. If you allow “Always”, your iPhone tells the Sage app when you arrive at or leave one of those places, even while Sage is closed (it watches at most 20 at once and does not track you between them). Sage’s server is told only which place and whether you arrived or left, never your position. For an alert like “20 minutes before I get home” your iPhone watches a wider circle around the place, a few kilometres across, and says only that you came inside it. If the alert is a smart-home action (“when I get home, turn on the fan”), Sage then does it the same way as when you ask in a chat, with the smart-home accounts you connected, and a notification tells you what happened; unlocking a door, opening a garage or gate and disarming an alarm are never done this way — Sage only asks you. An alert is kept until it has fired or you cancel it, and deleted 30 days after that.
  • Place history: off unless you turn it on in Settings › Location. When it is on, your iPhone notes the places you spend time at and sends Sage each place’s name and when you arrived and left — not your position — so you can ask “where was I on Tuesday afternoon?”. Sage never puts it in your brief or a notification. Deleted after 30 days; “Delete my place history” deletes all of it at once, and turning it off does too.
  When a request uses your city or your background location, it is sent to the AI model answering that request (section 5).
• Driving and motion (iPhone) — if you allow Motion & Fitness for Sage and leave “Driving detection” on, your iPhone works out on the device whether you are driving, and sends Sage only that: driving or not, and since when. While you drive, Sage holds notifications that can wait (and the ones that need your tap on a card) until you park, drops ones that are out of date by then, and keeps its replies short. Sage keeps only the latest state; turning driving detection off deletes it. Sage does not keep your trips or the motion readings. The end of a drive can save your parking spot (see Location above).
• Focus and sleep (iPhone) — if you allow Focus status for Sage and leave “Quiet while I sleep” on, the app tells Sage only whether a Focus is on — never which one — when Sage is open or briefly woken. Sage keeps the latest reading and 14 days of on/off times, to learn your usual night; if Health is on, your iPhone works out your usual bedtime and waking time from Apple Health and sends only those two times. While you are asleep Sage holds the calls and notifications that can wait (an urgent call still rings), then sends the notifications when you wake and says in the morning brief how many it held; nothing is dropped. Held notifications are kept up to 2 days. Turning the switch off deletes the readings and sends anything held.
• Phone state (iPhone) — battery level, charging, Low Power Mode and temperature state, so Sage can tell why your phone is not responding. Sage keeps only the latest one.
• Health (iPhone) — if you turn it on, a short daily summary read from Apple Health (last night’s sleep, yesterday’s steps and how long since your last workout), saved to your profile so Sage can tailor suggestions. Sage never writes to Apple Health, and health data is never used for advertising.
• Microphone and speech — audio of your voice messages and live conversations. Dictation uses Apple’s speech recognition, on your device where supported. The optional “Hey Sage” wake word is detected on your device and is off by default. On iPhone, the optional Standby (also off by default) keeps listening for “hey sage” for a few minutes after a voice chat, using Apple’s on-device speech recognition: nothing leaves the phone before you say “hey sage”.
• Your Mac — if you grant Accessibility and screen access, Sage can see and operate your Mac to do what you ask. While it works it takes screenshots of your screen, which are sent to an AI model to decide the next step; it keeps a screenshot receipt of what it did and a log of the clicks and keystrokes it performed. It reads only the folders you allow. If you start meeting notes, the Mac app records the meeting’s audio, including other participants, and keeps the recording until you delete the note.
• Your Home Assistant — if you connect it in Settings, Sage keeps its address and either the sign-in Home Assistant gives Sage when you sign in on Home Assistant’s own page, or the access token you created, encrypted with a key held by our servers, with your home’s name and how many of each kind of device it had when you connected (shown in Settings). To find Home Assistant, the Sage app on your iPhone or Mac looks for it on your home Wi-Fi; that search stays on your network. When your Home Assistant has no internet address, Sage’s requests to it and its answers pass through the Sage app on your Mac at home, which sends them only to Home Assistant on your home network and keeps none of them. To act, Sage sends your Home Assistant the commands you ask for and the names of the devices they are for, and reads back your devices’ names, rooms and states; those names and states go to the AI model answering that request (section 5). Unlocking a door, opening a garage or gate and disarming an alarm always ask you first. Sage looks through a camera only when you ask, and the first time for each camera it asks you; the picture is saved with your account so it shows in the conversation, and becomes eligible for deletion 7 days after it was taken (it is removed the next time Sage uses your Home Assistant). Disconnecting deletes the token or sign-in (and ends the sign-in at Home Assistant when Sage can reach it), your camera approvals and the saved pictures.
• Your own WhatsApp — if you link it, Sage uses WhatsApp Web in your Chrome, or on Sage’s computer (a browser we run for your account in the cloud, which your phone lists under Linked devices). When you ask, Sage reads your chats — names, numbers, messages, photos and files — and sends what a request needs to the AI model answering it (section 5). Opening a chat sends read receipts, so Sage marks it unread again afterwards. A message Sage sends from your number asks you first, unless you chose Always allow for that chat or approved it as a scheduled message; WhatsApp calls are handled like Sage’s other calls (below). If you turn on WhatsApp alerts, then while WhatsApp is open in your Chrome the extension tells Sage when a chat gets new messages, and Sage keeps the chat’s name, the unread count and up to 160 characters of the last message for 7 days (at most 300 entries) to decide whether to tell you. A photo or file you ask for is saved to your documents. Unlinking logs Sage’s computer out of WhatsApp, which removes it from your phone’s Linked devices. WhatsApp’s own encryption covers a message on its way to a linked device; once Sage reads it, it is stored and protected like the rest of your data (section 7).
• Your browser — with the Chrome extension, Sage reads the page you are on and can act in your signed-in browser when you ask. Page content is sent to Sage to answer you, and used for nothing else. The extension keeps a short history of recent pages in your browser’s own storage. The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Calls and messages

When Sage answers or places a phone call, or you reach it by SMS, WhatsApp, Telegram or iMessage, we process the phone numbers or handles involved, the messages, and the call audio, which is transcribed; transcripts are kept with your account. These include the words of the other people on the call or in the thread. Calls Sage places or answers may be recorded. Sage tells the other person that it is an AI assistant, or that the call is transcribed, where the law of their country requires it, and always answers truthfully if asked whether it is an AI or whether the call is recorded. We keep transcripts of calls. A call with an Indian (+91) number is also recorded, by Sage itself and never by a calling provider, so you have proof of what was said: the recording is kept with your account, encrypted at rest with your account's key (which our servers hold), for 90 days and then deleted, and you can delete it sooner from the call in the Calls tab. Calls with any other number are not recorded. Sage asks its calling providers not to record audio, and our calling provider keeps its own copy of the transcript and call log under its retention settings. Audio our calling provider recorded before 29 September 2026 is deleted by that provider under its retention settings, within 180 days. People who message Sage’s number without being you can talk to it, but it cannot act on their behalf; they can ask us at privacy@agentarchy.ai to see or delete what Sage holds about them.

If you join the waitlist

Your email address, your name if you give it, where you signed up and when, and a keyed one-way hash of your IP address used only to limit abuse (the address itself, or for IPv6 its network, is held briefly in memory and never stored). We use them only to confirm your place and to invite you to Sage. The confirmation, and a note to our team, are sent through our Google Workspace account, with no tracking pixels or tracked links; when many people sign up at once, a confirmation can take up to a day. We keep your entry until you get access or ask to be removed — reply to any waitlist email or write to privacy@agentarchy.ai, and we will delete your entry and our emails about it.

Technical information

Operational records of how each request was handled — timings, which tools ran, errors, the AI model used, and cost — together with your weekly usage. The iPhone and Mac apps send crash and performance diagnostics. Sage has no advertising or analytics trackers and does not track you across other websites, so a browser’s “Do Not Track” signal does not change anything we do.

3.How we use it

We use personal information to:

• Provide Sage — answer you, remember what matters to you, act on your behalf, run the routines and background features you use (such as your morning brief, follow-up drafts and reminders), and keep your devices in sync.
• Keep it safe — ask for your approval before sensitive actions, prevent abuse, and secure accounts.
• Fix and improve it — diagnose errors and measure reliability, using the operational records described above.
• Talk to you — about your account, changes to the Service, and replies to your requests.
• Meet legal obligations.

We do not sell personal information, share it for cross-context behavioural advertising, use it for advertising at all, or use your content to train AI models. Sage makes no decisions about you that produce legal or similarly significant effects.

Legal bases (EEA and UK). We process your information to perform our contract with you (providing Sage); on your consent where you give it (contacts, calendar, location, motion, Focus status, health, microphone, connected accounts — which you can withdraw at any time); for our legitimate interests in securing and improving the Service; and to comply with the law.

4.Google user data

If you connect a Google account, Sage asks Google for these permissions and uses them only for the features below.

• Storage. Your Google tokens are encrypted with a key held by our servers. Sage does not keep a copy of your mailbox or Drive. It keeps a copy of your calendar only if you turn that on (section 2). It keeps what its features need: short records of emails it has read (sender, subject, date), notes about people you correspond with, commitments it has found, and whatever is quoted into a conversation or into memory. The results of the requests it made are kept in encrypted operational logs for 30 days.
• Sharing. To answer you, Sage sends the relevant Google content to the AI model providers in section 5, only for processing that request. We do not transfer Google user data to anyone else, except as needed to provide Sage, for security, or to comply with the law.
• No human reads it except with your explicit permission (for example, when you ask us for help with a specific item), when necessary for security such as investigating abuse, or to comply with the law.
• No ads, no sale, no training. Google user data is never used for advertising, never sold, and never used to determine creditworthiness or for lending. Google Workspace APIs are not used to develop, improve, or train non-personalized AI and/or ML models, and the AI providers that process a request containing Google data are bound not to train on it (section 5).
• Revoking access. Disconnect in Settings deletes Sage’s copy of your tokens and revokes Sage’s access at Google. You can also remove Sage from your Google Account’s third-party access page at any time. Deleting your Sage account revokes every Google account you connected.

5.Who processes it

Sage does not run its own AI models, speech recognition or phone network. Doing its job means sending the relevant part of your information to the service providers below, each for the purpose listed. They process it on our behalf, and we do not give them any wider access to your account.

No training on your content. The AI model providers above process your requests under terms that do not allow them to train on them. Requests through OpenRouter go only to model hosts that OpenRouter’s data-policy listing shows as neither training on nor keeping the data sent to them. Anthropic and Groq do not train on data sent through their APIs, and may keep it for a limited period under their own policies, for example to detect misuse. Speech, telephony and the other services process data under their own terms.

We may also disclose information if the law requires it, to protect the rights and safety of our users or others, or as part of a merger or acquisition, in which case we will tell you first.

6.Who at Agentarchy can see it

Access to Sage’s production systems is limited to authorised Agentarchy personnel — today, the founder.

• Operational records. Our tools show how a request was handled: timings, which tools ran, errors, the model used and cost. The text of your messages and of Sage’s replies in those records, and the results of the tools it ran, are encrypted with your account’s key, and our tools do not display them. Error reports can occasionally include a fragment of the content that was being processed when an error occurred.
• Your content. We do not access your conversations, memory, files or connected-account data except when you ask us to (for support), when necessary to investigate a security incident or abuse, or when the law requires it.
• Engineering assistants. We use AI coding tools, including Anthropic’s Claude, to help diagnose errors. They see the same operational records described above.

Because our servers hold the keys that background features need, these limits are enforced by our tools and our practices rather than made technically impossible — which is why we state them as commitments.

7.Where it is stored and how it is protected

Sage runs on Fly.io servers in San Jose, California. Its database is hosted by Neon on Amazon Web Services in Oregon, and files and backups are kept in Cloudflare R2 object storage. Every account’s data is separated by account, and every request is scoped to the signed-in account.

• In transit, everything between your devices and Sage is encrypted with TLS.
• Encrypted with your account’s key: your synced contacts, your saved places, your approval history, the text of messages and replies in our operational logs, the results of the tools Sage ran, and some other records. Your synced contacts are encrypted with your account's key before they reach object storage. A copy of that key is kept on our servers, itself encrypted, so that work running while your apps are closed — your morning brief, scheduled routines, nightly memory upkeep — can use it. Accounts that have never signed in on the iPhone or Mac app have no account key, and these records are then protected only as described next.
• Protected by our providers’ storage encryption and access controls, but not encrypted by Sage with your key: your conversations and call transcripts, memory files, Sage’s searchable memory index, attachments, voice and meeting recordings, documents Sage creates for you, and our databases. Connected-account tokens are encrypted with a key held by our servers.
• Backups are taken nightly, encrypted with a key held by our servers, and kept for 14 days.

8.International transfers

Agentarchy is in India, and Sage’s servers and most of its providers are in the United States. Your information is processed in the United States, in India, and in other countries where our providers and their hosting partners operate. Information held in another country may be accessible to the courts, law-enforcement and national-security authorities of that country. Where the law requires a safeguard for these transfers, we rely on the data-protection terms our providers offer, including standard contractual clauses where they provide them.

9.How long we keep it

Deleting your account (Settings → Account) starts a 30-day grace period during which you can cancel by signing in. After it, your account and its data are erased from our systems. What remains, and for how long:

• encrypted backups, until they age out (14 days);
• usage records without message text (model, tokens, cost), for up to 90 days;
• a record that the account existed and was deleted — its internal ID and a one-way hash of its email address — kept to honour the deletion and prevent abuse;
• error reports not linked to your account;
• copies in our database provider’s short point-in-time recovery history;
• anything a provider in section 5 retains under its own policy.

Deleting a conversation removes it, its attachments, its messages (including Sage’s searchable copy of them) and the memories and facts Sage learned only from that conversation. Three things stay until you remove them or delete your account: a fact you also told Sage somewhere else or asked it to keep (remove it in Memory or ask Sage to forget it), what Sage noted about people, and the text of documents you shared, which stays searchable in your Library. Records in logs and backups age out as described above.

Turning memory off (Settings → Memory) or using a temporary chat stops Sage saving anything new — no memories, facts or notes, including when you ask it to remember something. Sage can still use what it already knows, and you can still ask it to forget things.

Removing your contacts (Settings → Contacts) deletes the names and numbers that came from your phone. Contacts you added or edited inside Sage are treated as yours and are kept, and anything Sage already said or did using a number stays in that conversation until you delete the conversation.

10.Your choices and rights

• See and export your data: Settings → Account → Export (once a day). The export covers your conversations, messages, what Sage remembers about you (memories, facts and the people it knows), contacts, tasks, reminders, connected apps and recent sign-in history. Its README names what is left out on purpose, and why; for anything it does not include, ask us.
• Correct what Sage remembers by telling it, or by asking us.
• Delete a conversation, your contacts, or your whole account in the app, or ask Sage to forget something.
• Withdraw permissions — contacts, location, health, microphone, screen and accessibility — in your device settings, and disconnect any connected account in Settings.
• Object or restrict processing, or ask any question, at privacy@agentarchy.ai.

We acknowledge requests and complaints promptly, answer them within 30 days, and may need to verify that a request comes from you. You can complain to us, and you can also complain to the regulator where you live (below). You will not be treated differently for exercising a right.

Where you live

• India — under the Digital Personal Data Protection Act, 2023 you may ask for a summary of your data and its processing, have it corrected, completed, updated or erased, nominate someone to act for you, and have grievances addressed by our Grievance Officer. If you are not satisfied with our response, you may complain to the Data Protection Board of India.
• EEA and UK — you have rights of access, rectification, erasure, restriction, portability and objection, and to withdraw consent at any time. You may complain to your local data protection authority, or in the UK to the Information Commissioner’s Office.
• United States — depending on your state, you may have rights to know, access, correct and delete your personal information. We do not sell or share it as those laws define the terms.
• Canada — you may access and correct your personal information, and complain to the Office of the Privacy Commissioner of Canada.

11.Children

Sage is for adults aged 18 and over. It is not directed at children, and we do not knowingly collect personal information from anyone under 18. If you believe a child has given us personal information, contact us and we will delete it.

12.Changes to this policy

When what Sage does with your information changes, this policy changes with it and the date at the top moves. For a change that materially widens what is collected or shared, we will tell you in the app before it takes effect.

13.Contact and grievances

Agentarchy Labs Pvt. Ltd., Pune, Maharashtra, India.

Privacy questions, requests and complaints: privacy@agentarchy.ai. You can also reach a person from Settings → Help & support in the app.

Grievance Officer: Omkar Phatak, privacy@agentarchy.ai. We acknowledge grievances promptly and resolve them within 30 days.