Privacy Policy

01Who we are, what this covers

ASIS is a voice-first life assistant for iPhone, and "ASIS" ("we") in this policy means the operator of the ASIS app and of asis.life. This policy covers the app, the service behind it, and this website. It is the data-handling half of an agreement whose other half is the Terms of Use.

For anything this policy leaves you wondering about — including who is responsible for your data and how to reach them — write to support@asis.life and a human answers.

02What ASIS collects

ASIS keeps a small number of record types, all of them text or numbers:

• Account. Signing in with Apple, Google, or an email link creates your account; ASIS keeps the account identifier plus the email address and name your sign-in provider shares. A random installation identifier, created on first launch and kept in your iCloud keychain, links the install to your account.
• Conversation. The text of what you said and what ASIS replied — transcripts — together with technical metadata such as the models used, token counts, and timing. Audio is never part of a transcript (section 04).
• Memories. The twelve-section dossier ASIS builds from what you tell it — the same entries you can read, edit, archive, or forget in the app — each with its source and, as evidence, a short quote of your own words.
• Plans. Your events, to-dos, and reminders, and any notes ASIS attaches to events from your calendars.
• Calendars and reminders. If you connect Google or Outlook, a mirrored window of those calendars (section 07). Apple Calendar events, and items from the Apple Reminders lists you connect, are read on the device and are not mirrored into the ASIS database.
• People on plans. Once you connect Apple Contacts in Settings, you choose the people you add to a plan in Apple's contact picker, or ASIS finds them in your contacts by the name you said. ASIS keeps that person's name and phone numbers on your iPhone only; they are not stored in the ASIS database.
• Subscription. Your plan and its state — active, expiring, renewed — connected to your App Store purchase. Payment details stay with Apple; ASIS never sees your card.
• Usage. A per-day measure of how much you used ASIS and per-session voice durations, so your plan's daily allowance can be applied.
• Reminder calls. So that ASIS can call you for a reminder you mark Important, each iPhone you sign in on registers with ASIS: a random identifier for that install, its model, its App Store country, and, where ASIS can call it, the push token Apple issues for calls. ASIS also keeps the times your Important reminders are due to ring, and a record of each call: the reminder's title, when it rang, and whether you answered, marked it done, or snoozed it.
• Device and diagnostics. The app's build number, your timezone and chosen language, a handful of setup-progress markers from onboarding, and crash or error reports if something breaks.

Just as deliberate is what does not exist: no advertising profile, no location history, no upload of your contact list or photos, no browsing data, no HealthKit access, and no tracking identifiers.

03How ASIS uses it

Each record type exists to do its job: transcripts and memories power a conversation that knows you; plan and calendar data let ASIS schedule real things; your iPhones' registrations and call records let ASIS call you for Important reminders; subscription and usage records apply your plan and its daily allowance; device and diagnostic data keep the service working and secure. That is the complete list of purposes — there is no advertising, no profiling for third parties, and no sale of data. ASIS also never uses your content to train AI models.

Where the GDPR or UK GDPR applies, the legal bases are: performance of a contract (running ASIS for you); consent (the microphone permission, calendar and reminder connections, names in conversations, notification permission, and health details you volunteer — each withdrawable at any time); legitimate interests (keeping the service secure, preventing abuse, fixing failures); and legal obligation where the law requires us to act.

04Your voice is never recorded

When you talk to ASIS, audio streams from your iPhone over an encrypted connection to the speech-to-text service — Soniox, with Deepgram as the backup (section 08) — which transcribes it live. Then it is gone. ASIS has no recording infrastructure: no audio file is ever written, kept for training, or replayable — by you or by us. What remains is text you can see; the transcript on your screen is the complete record of the conversation.

Replies travel the other way: ASIS's answer is generated as text and synthesized into speech by the voice services in section 05, and that audio is streamed to you, not stored. One detail worth knowing: to recognize the people, places, and plans in your life when you say them, ASIS sends the speech-to-text service vocabulary hints. Soniox receives the names of people and places from your memories and the titles and places of your upcoming ASIS events, to-dos, and reminders — never events from a connected Google or Outlook calendar. Deepgram, the backup, receives the first names from your People memories. If you allow names in conversations, both also receive the names of people on your plans.

05AI processing

ASIS thinks with large language models, and each model sees only what its task needs:

• Conversation and memory extraction run on DeepSeek's models: your current words, the conversation so far, the memories relevant to it, and a snapshot of your plans — including the titles, times, and locations of events from any calendar you have connected, and the titles, due dates, priority, notes, and list names of reminders from any Apple Reminders lists you have connected, and, if you allow names in conversations, the names of people you added to those plans. A China-based provider; see section 14.
• Briefings and conversation openers run on the conversation model above when the briefing involves only your own ASIS plans, and on Google's Gemini models whenever it involves events from a connected Google or Outlook calendar; they see the calendar, to-do (Apple Reminders included), and memory text those tasks involve.
• Memory judging — deciding what is worth remembering, and whether two memories are the same — runs on Google's Gemini models, which see the memory text those tasks involve.
• Backup models step in automatically when a primary model fails, receiving the same kind of content for that turn: Google's Gemini behind conversation, and Anthropic behind the other tasks.
• Quick checks on what you say during a conversation (whether you have finished speaking, and the punctuation of your captions) run on Google's Gemini models, which see your words for that turn.
• Reminder calls are conversations like any other, on the services above. ASIS's opening lines are written by the conversation model from the reminder's title and your first name, and Google's Gemini models read what you say on the call to tell whether you have already done it.
• Memory search uses Voyage AI, which turns memory text and search phrases into embeddings so ASIS can find what is relevant.
• Speech recognition — turning your voice into text as you speak — runs on Soniox's speech-to-text model, with Deepgram as the backup. Each receives the live audio and returns text; neither keeps the audio (section 04), and each also receives vocabulary hints from your memories, the names of people on your plans if you allow names in conversations, and, for Soniox, your upcoming ASIS plans.
• Speech synthesis — turning each reply into the voice you hear — runs on Soniox's text-to-speech model for most languages, and on Alibaba Cloud's Qwen text-to-speech model (Model Studio, Singapore) for Korean, Japanese, and Chinese, with Google's Chirp voices as the backup. Each receives only the text of the reply it speaks; the audio it returns is streamed to you and not stored.
• Memory review runs on Alibaba Cloud's Qwen model (Model Studio, Singapore). From time to time ASIS reads one category of your memories together — all of your routines, say — to find duplicates, contradictions, and matches with your timetable, so that outdated entries can be closed or put to you as a question. The model sees the memory statements in that category, the titles and times of your own recurring plans and near-term to-dos, and a few closely related memories from other categories — never health memories, memories marked private, or any conversation transcript. If Alibaba Cloud is unavailable the review is skipped; no backup model receives it.

These providers process your content to produce their output for ASIS — nothing else is sent to them, and section 08 lists them all. ASIS never trains AI models on your content. And because ASIS is an AI system, its output can be wrong; the honest limits of that are in the Terms of Use.

06Memory and sensitivity

Memory is the point of ASIS, so it comes with controls. Every memory is visible in the app with its source and evidence, and every one can be edited, archived, or forgotten — one at a time, or all at once with "Clear all memories" in Settings.

Editing a memory keeps its previous wording: each earlier version is stored for 180 days so a change can be reviewed or undone. After that the earlier version is reduced to when it changed, who changed it and why — its text, and the name of whom it concerned, are removed. Forgetting a memory, or deleting your account, removes its versions with it.

Sensitivity is handled automatically and can only tighten, never loosen. Entries that look like credentials or financial identifiers are marked private on sight; health-related entries are always at least "sensitive". Private entries stay out of conversation unless you yourself raise the topic, and health memories exist only because you chose to share them — ASIS never infers your health from your calendar, your routines, or anything else. Neither health memories nor private entries are ever sent for memory review (section 05).

One boundary stated plainly: clearing memories removes the dossier, but conversation transcripts remain until you delete your account (section 12).

07Calendar, reminder, and contact connections

Apple Calendar is read and written on your iPhone, with the calendar permission you grant iOS, and is not mirrored into the ASIS database. When you talk to ASIS or a briefing is composed, the relevant slice of your day — including device-calendar events — is sent to the server to do that work. You can turn Apple Calendar access off in ASIS Settings at any time without changing anything in iOS.

Apple Reminders works the same way, with the reminders permission you grant iOS: ASIS reads the lists you leave switched on in Settings and does not mirror them into the ASIS database. When you talk to ASIS or a briefing is composed, the reminders relevant to it — their titles, due dates, priority, notes, and list names — are sent to the server for that work, as device-calendar events are. ASIS changes your reminders only when you ask it to: ticking one off, editing one, adding one to a list you choose, or deleting one you explicitly ask it to delete. Alerts stay with the Reminders app; ASIS sends none of its own for them. You can switch lists off, or turn Apple Reminders off entirely, in ASIS Settings without changing anything in iOS.

Contacts. Once you connect Apple Contacts in Settings, you can add people to plans by choosing them in Apple's contact picker or by name, and ASIS looks them up on your iPhone. Their name and phone numbers are kept on your iPhone only; your contacts are never uploaded. If you allow names in conversations, the names of people on the plans ASIS is talking about — and, when ASIS asks which contact you mean, the names of the contacts that match — are sent with your request to the AI that answers you, and the names of up to 30 people on your plans go to the speech-to-text service so it hears them right. Phone numbers never leave your iPhone. ASIS never sends a message for you: it opens Apple's Messages app with the text, and you decide whether to send it. You can turn names off, or remove people from all plans, in Settings → Connection → Contacts, and turn Contacts access off in iPhone Settings. Because those names reach the AI, and ASIS's replies (kept in your conversation history) can mention them, ASIS's App Store privacy label lists Contacts.

Google and Outlook connect through each provider's own sign-in page; your calendar password never touches ASIS. ASIS requests these scopes, exactly: from Google, openid, email, calendar.events, and calendar.calendarlist.readonly; from Microsoft, openid, email, offline_access, and Calendars.ReadWrite. With that access, ASIS mirrors a rolling window of your calendars — 60 days back to 400 days ahead — onto its server, keeping each event's title, times, location, and notes so it can plan around your life and write events back. The mirror follows the source: events deleted at the provider disappear from ASIS on the next sync, which runs about every 20 minutes.

The OAuth tokens that maintain the connection are encrypted at rest with AES-256-GCM. Disconnect an account in Settings and its mirrored events are deleted and its tokens destroyed; for Google, ASIS also revokes its own access at Google. Microsoft offers no per-app revocation, so destroying the tokens is the whole story on our side — you can additionally remove ASIS from your Microsoft account's app permissions.

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

08The services that process your data

ASIS runs on a small set of processors, each with a defined job. These are the active processors, and there are no others:

• LiveKit — voice transport. Carries the live audio between your iPhone and ASIS; nothing is recorded.
• Deepgram — backup speech-to-text, and the speech-to-text service for app versions before 0.9.0. Receives your voice as you speak and returns text; the audio is not kept by ASIS. Also receives first names from your People memories, and the names of people on your plans (with names in conversations on), as vocabulary hints (section 04).
• DeepSeek — the language model behind conversation and memory extraction, and behind briefings and conversation openers that involve only your own ASIS plans. Receives what you say, the conversation so far, the memories relevant to it, and a snapshot of your plans, including connected-calendar event details, items from connected Apple Reminders lists, and, if you allow names in conversations, the names of people on your plans and of contacts that match a name you said. A China-based provider; see section 14.
• Google Cloud — the Gemini language models behind memory judging and behind briefings that involve a connected calendar, quick checks on your words during a conversation (whether you have finished speaking, your captions' punctuation, and on a reminder call whether you have already done it), the backup for conversation (including, if you allow names in conversations, the names of people on your plans and of contacts that match a name you said), the Chirp text-to-speech voices that back up the voice of ASIS (section 05), and the Google Calendar API if you connect Google.
• Soniox — speech-to-text and text-to-speech: it hears you, and it is the voice of ASIS in most languages. Receives your voice as you speak and returns text, and receives the text of each reply it speaks; processes both in the United States, keeps neither, and does not use them to train models. Also receives, as vocabulary hints, the names of people and places from your memories, the names of people on your plans (with names in conversations on), and the titles and places of your upcoming ASIS events, to-dos, and reminders — never events from a connected Google or Outlook calendar (section 04).
• Anthropic — backup language model for briefings and memory tasks, used automatically when a primary model fails.
• Voyage AI — memory embeddings and ranking, so ASIS can find the memories relevant to what you just said.
• Alibaba Cloud (Model Studio, Singapore) — the Qwen language model behind memory review, and the Qwen text-to-speech voice that speaks replies in Korean, Japanese, and Chinese (section 05). Receives the memory statements of one category at a time together with your timetable items, and the text of the replies it speaks; processes them in Singapore under its data-protection terms, and does not use them to train models.
• Neon Postgres — the primary database (United States) where your records live, encrypted at rest.
• Firebase (Google) — authentication only: verifying your Apple, Google, or email sign-in.
• Sentry — error monitoring for the app and the server. Receives crash and error reports — device model, OS and app version, stack traces — configured to exclude screenshots, message content, and personal detail.
• RevenueCat — subscriptions: connects your App Store purchase to your account. Sees your account identifier and purchase state, never your payment details.
• Fly.io — hosting for the ASIS servers (United States).
• Microsoft Graph — Outlook calendar access, only if you connect Outlook.
• Apple Push Notification service — delivers the call for an Important reminder to your iPhone. Receives your iPhone's push token for calls and, with each call, the reminder's title, when it is due, and codes that let your iPhone check the call is meant for it.

If a provider ever has to be replaced, a successor performing the same role under equivalent protections may take its place, and this list is updated with the change.

09What we never do

ASIS does not sell your personal information, does not share it for advertising, shows no ads, and does not track you across other companies' apps or websites — it never even asks for iOS tracking permission, because there is nothing to ask about. Your records are single-user by design: keyed to your authenticated account, never pooled, and readable by no other account.

Beyond the processors in section 08, data leaves ASIS in only two situations: if the law compels a disclosure, we disclose the minimum it requires; and if ASIS itself changes hands — a reorganization or acquisition — your data goes with the service only under this policy's obligations, and you will be told.

10Security

Everything moves over encrypted connections (TLS), and everything at rest sits in an encrypted database. Calendar tokens carry a second, application-level layer of AES-256-GCM encryption. Every record is keyed to the account identity proven by your sign-in token — never to anything the app merely claims — and row-level isolation enforces that boundary on every query. Server logs are deliberately content-free: they record technical events, not what you said. Sensitive actions, like deleting the account, require you to re-authenticate first.

No system is perfectly secure, and we will not pretend otherwise. If a breach ever affects your data, we will notify you and the authorities as the law requires. If you find a vulnerability, write to support@asis.life.

11How long data is kept

• Account, transcripts, memories, and plans are kept for as long as your account exists. ASIS does not auto-expire them — your assistant's memory is the product — and you can delete memories and plans at any time, or everything at once (section 12).
• Earlier versions of edited memories are kept for 180 days, then reduced to when, who and why. They go with the memory when you forget it.
• Mirrored calendar events live inside the rolling sync window and leave it as time moves or events are deleted; disconnecting an account deletes its mirror immediately.
• Reminder calls. The record of each call, and the iPhones registered for calls, are kept for as long as your account exists, like your plans. Signing out on an iPhone removes its push token, and the times your Important reminders are due to ring are cleared two days after they pass.
• Crash and error reports expire automatically on the monitoring service's schedule, about 90 days.
• Encrypted disaster-recovery backups of the database expire automatically within 30 days.

12Deleting your data

In the app, go to Settings and tap Delete Account. ASIS asks you to sign in again — deletion is worth being sure about — and then to type DELETE. One transaction then removes your records from the live database: memories and their observation history, transcripts and sessions, events, to-dos, reminders and calendar annotations, reminder-call records and the iPhones registered for calls, connected-calendar accounts with their mirrored events and tokens, subscription records, the usage ledger, and the account itself.

People you added to plans live only on your iPhone: Remove people from all plans, signing out, or deleting the app removes them.

After the deletion commits, ASIS revokes its Google calendar access at Google; Microsoft offers no per-app revocation, so ASIS destroys its token copies and you can also remove ASIS in your Microsoft account settings. The app then deletes your sign-in identity at Firebase. Residual copies in encrypted disaster-recovery backups expire automatically within 30 days.

Two practical notes. Deleting your account does not cancel the subscription — billing lives with Apple, so cancel it in your App Store settings as well. And deletion is permanent: there is no undo, and once the backup window has passed, nothing remains to restore.

13Notifications

Briefings, reminders, and heads-ups are composed on the server, then scheduled and fired locally on your iPhone — the notification you see at 7:00 was already sitting on your device, waiting for its hour. A reminder you set as an alarm rings as an iPhone alarm, set on your iPhone. The one thing ASIS sends from its server is a call: for a reminder you mark Important, ASIS's server sends a push through Apple's push service to each iPhone you have left on for calls, and the iPhone rings it as a phone call. The push carries the reminder's title, when it is due, and codes that let your iPhone check the call is meant for it. If you answer, it is a conversation like any other: your voice is not recorded (section 04). You choose which iPhones ring in Settings → Important reminders; signing out on an iPhone removes its push token. Every notification type has its own toggle in Settings, and the iOS notification permission is always yours to grant or revoke.

14Where your data lives

ASIS's servers and database run in the United States, so using ASIS means your data is processed there. The processors in section 08 operate where they operate — in the United States, with four exceptions: Apple's push service, which delivers a reminder call to your iPhone wherever it is; Microsoft Graph, which serves Outlook calendar access globally if you connect Outlook; Alibaba Cloud, which performs memory review and speaks Korean, Japanese, and Chinese replies in Singapore (section 05); and DeepSeek, a China-based provider that processes the conversation, memory-extraction, briefing, and opener text described in section 05. ASIS keeps no copy of your data in Singapore or China: each provider's input is processed there under its own data-protection terms and only its result comes back.

Wherever your data is processed for ASIS, it travels encrypted and is handled under this policy and our providers' data-protection terms. If you are in the EEA, the UK, or another region with data-transfer rules, transfers are made with the safeguards those rules recognize, such as standard contractual clauses where required.

15Your rights

Most rights are built into the product: every memory is readable, editable, archivable, and forgettable in the app; plans can be changed or deleted outright; the whole account deletes in section 12's one transaction. For anything else — a copy of your data in a portable format, a correction, a restriction, an objection — write to support@asis.life and we will respond within 30 days, verifying that the request really comes from you.

If you are in the EEA or UK, this includes your GDPR rights: access, rectification, erasure, restriction, portability, objection, and withdrawal of consent at any time — and if we let you down, the right to complain to your supervisory authority. If you are a California resident, you have the rights to know, delete, and correct; ASIS does not sell personal information and does not share it for cross-context behavioral advertising, and exercising your rights never earns you worse service.

If you are in Thailand, the Personal Data Protection Act gives you corresponding rights — access, correction, erasure, portability, objection, and withdrawal of consent — and the right to lodge a complaint with the Personal Data Protection Committee.

16Children

ASIS is for adults — the Terms of Use require users to be 18 or the age of majority — and it is not directed to children under 13. We do not knowingly collect data from children; if you believe a child has an account, contact us and it will be deleted.

17This website and the App Store

asis.life sets no cookies, runs no analytics, and makes no requests to anyone else's servers. Reading this site leaves no trace with anyone, including us. The only links out are the App Store and our own email address.

In the App Store, ASIS's privacy label is drawn from this policy, and the app's account-deletion requirement is met in full inside the app (section 12).

18Changes to this policy

If this policy changes, the new version is posted on this page with a new effective date at the top. For material changes we will give notice in the app or by email before they take effect.

19Contact

Questions about this policy, or about anything ASIS knows about you: support@asis.life.