X0 Bot

Privacy Policy

Effective: November 6, 2026

X0 Bot (also referred to as "we", "our", "us") builds a voice-and-text keyboard that transcribes your speech, refines your writing, and helps you communicate, along with bots that can work for you in the apps you connect, and Spaces for sharing with family and friends. This Privacy Policy explains what personal information we collect through the X0 Bot iOS, Android and desktop apps, the keyboard extension and our website (x0bot.com), how we use it, and the choices you have.

By using X0 Bot, you agree to this Privacy Policy. If you do not agree, please do not use the app.

1. Information we collect

1.1 Account information

  • Email address (when you sign in with email or Apple ID)
  • Phone number (only if you choose phone sign-in)
  • Name (only if you provide it during onboarding or your Apple ID shares it)
  • Language preference and other in-app settings

1.2 Voice and text you send to X0 Bot

When you use voice input or the refinement feature, we transmit the audio or text you dictate to our servers and to the AI providers listed below in Section 3 for the purpose of transcription and refinement.

  • Voice recordings are processed transiently — sent to a speech-to-text provider, converted to text, and then discarded. We do not permanently store raw audio unless you specifically enable session history in Settings.
  • Text you dictate or refine is used to produce refined output and is saved to your history so you can review it later. You can turn history off, or delete it, in Settings.
  • Personality preferences (tone, vocabulary, personal dictionary) are stored so refinement can match your voice.
  • What you ask X0 Bot to do on your phone: the first 80 characters are kept for 30 days, so the You tab can show your recent requests, and your words for a day when a request failed having changed nothing, so you can try it again with one tap (see 11.4). Of what you ask Ask on your computer, none of your words are kept, apart from your Tasks list (see 11.4).

1.3 Purchase information

  • In the iPhone and Android apps, subscriptions are bought through the Apple App Store or Google Play, which take the payment. RevenueCat manages them for us: it knows your purchases by your X0 Bot account ID, and tells us which plan you have and until when.
  • On the web and in the desktop app, subscriptions are bought at x0bot.com/pay and paid through Razorpay. You enter your payment details on Razorpay's own checkout, and Razorpay collects what it needs to take the payment under its own privacy policy. We give Razorpay your X0 Bot account ID, so the subscription is linked to your account, and we keep the subscription's ID, its plan, the market it was sold in (India or elsewhere), its status and the dates it runs to.
  • Web subscriptions bought earlier through Paddle are handled by Paddle, which sold them, under its own privacy policy.

We never receive or store your card number, your bank details or your UPI PIN.

1.4 Device and diagnostic information

  • Device model, OS version, app version, language, timezone
  • Push notification tokens (via Apple Push Notification service / Firebase Cloud Messaging) — used to deliver notifications you have opted into
  • Advertising identifier — on Android, the device's advertising ID is read by Meta's SDK to tell whether an install came from one of our ads (see 1.6). You can reset or delete it in Android's settings. On iPhone, X0 Bot never asks for or reads the advertising identifier (IDFA), and shows no tracking prompt.
  • Crash reports and error logs (via Sentry, only if enabled) — used to diagnose and fix bugs
  • Usage events (via PostHog, only if enabled) — anonymous aggregate metrics about which features are used, to guide product improvements

1.5 Data you may choose to share via device permissions

The app requests OS-level permissions only when you activate a specific feature. If you deny a permission, the related feature is unavailable but the rest of the app functions normally.

  • Microphone — required for voice input. Audio is transient and never stored (see 1.2 above). Flow Sessions: when you start a Flow session, the microphone stays active in the background — iOS shows the recording indicator the entire time — so you can dictate directly from the X0 Bot keyboard without reopening the app. The session ends automatically after a period of inactivity (about 10 minutes by default) and you can end it at any time from Settings → End Flow session. Outside of an active Flow session or an explicit dictation, the microphone is off.
  • Photos — opened only when you pick a photo, video or file to send to a bot or share in a chat, and written to only when you choose to save a picture or video to your Photos. Only what you pick is sent. We never scan your library in the background.
  • Camera — used only when you choose to take a photo or video to use in the app.
  • Face ID / Touch ID / biometric authentication — used on your device to confirm it's you before a bot does something you approve. Biometric data never leaves your device.
  • Clipboard — read only when you paste into the app. We never read the clipboard in the background.
  • Not used: the app does not ask for your contacts, your device's calendars or reminders, your location, Bluetooth, motion and fitness data, your music library, or the system's speech recognition. Your calendar and to-dos in the app are its own, kept with your account.

1.6 Advertising measurement (Meta)

We advertise on Facebook and Instagram, and we tell Meta when someone gets and starts using X0 Bot, so we can see which ads work and show them to people likely to find X0 Bot useful. What Meta receives:

  • On our website (Meta's pixel): the pages you visit on x0bot.com, and a click on a download or app-store link, with your IP address, browser, and Meta's cookies (_fbp, _fbc). The pixel does not load if your browser sends Global Privacy Control or Do Not Track, or if your device's clock is set to a European time zone. It never loads on the payment page.
  • From the phone apps (Meta's SDK): that the app was installed and opened, and three milestones — that you created an account, switched the keyboard on, and made your first dictation.
  • From our servers (Meta's Conversions API): for the desktop app, that you created an account and made your first dictation; for any subscription bought on x0bot.com, that it started and its price. These carry your email address and phone number only as one-way SHA-256 hashes, and your account ID hashed the same way, which is how Meta matches them to someone its ads reached.

Each milestone is reported once, and only for accounts in their first week. Meta never receives anything you say, type or dictate, nor your history, settings or vocabulary. You can control how Meta uses this in your Facebook or Instagram ad settings, and you can ask us to stop reporting your account at privacy@x0bot.com.

1.7 Non-collection notice

  • We do NOT collect your typing outside of when you actively invoke the mic or refine actions.
  • The keyboard extension respects Apple's and Google's sandboxing — we do not read passwords, PINs, or content from secure text fields.
  • We do not sell personal information to third parties.
  • We do not share your content with third parties for their independent marketing.
  • We do not use your data to train third-party AI models.
  • CCPA notice: we do not sell personal information. The advertising measurement in 1.6 may count as "sharing" for cross-context behavioural advertising under California law; we honour Global Privacy Control as an opt-out of it on our website, and you can opt out for your account by emailing us.

1.8 Spaces: messages, shared things, reports and blocks

In Spaces you can message the people you invite and share things with them. We store your words and a copy of what you share (like a list, a plan, a trip, a note or a link) so the people in that chat or space can see it, until it is taken out or the space or your account is deleted. A photo or file you attach stays one of your files, kept as 1.9 says, and the people there open it through a link that works only for them. Only the people in that chat or space can see what is in it. A space's admin (the person who made it) can also see the messages members send to one person there, and the things members keep with Plan Ease, Notes, Travel bot and Xode, and can share any of those things with one person in the space or with everyone there, once the member has agreed to this ("The space's admin can see and share your work and messages here."). The member is not told each time the admin shares one of their things, and only the admin can stop a share the admin made. The admin can also move a member's Plan Ease events and add notes to their things; the member sees each change. Anyone a member or the admin shares one thing with can do the same with that thing. A space's bots can read what is shared there when someone in the space uses them (see 14.3); and our team sees it only when it is reported to us.

  • Your name there: people in your chats and spaces see you by a name made from your email address (the part before the @: meera.rao@… is shown as "Meera R."), or, if you signed in with a phone number, its last four digits.
  • Invites and codes: when you invite someone by email, we keep their address with the invite, to send them that invite and the space's code. The invite waits in X0 Bot for whoever signs in with that address. Anyone else who types the code only asks to join: the space's admin sees their name and lets them in, or not, and we keep the request.
  • A message to one person: in a space you can write to one person there. Only they, you and the space's admin see it.
  • Sharing from your bots: you can share one plan, note, trip or Xode project with one person in a space, or with everyone there; a space's admin can share a member's the same way. We keep its title and a line about it, whose it is and who shared it, so they can open it from their own bot, and the notes people add to it. It stops being shared when its owner leaves the space, or it is taken out.
  • Tasks, plans and payment requests: a task or plan you give someone is kept for the people it is for. A payment request keeps who asked, the payee's name and UPI ID, what it is for, who approved or declined it, and when it was marked paid (and an amount, where an older version of the app sent one). X0 Bot moves no money: approving opens your own UPI app with the payee filled in, and you enter the amount and your PIN there.
  • Activity: a space keeps a log of who joined, shared, asked and paid, which everyone in the space can see. Changes someone makes to another person's thing are not in it: they are notes on that thing.
  • Reports: when you report a message, something shared or a person, we keep the report: who sent it, who and what it is about, the reason, any note, and a copy of what was reported as it was then. It goes to our support team so it can be acted on within 24 hours, and is kept afterwards as a safety record, including after either account is deleted (without the account). The person reported is not told who reported them.
  • Blocks: we keep whom you blocked, and the name they had then, until you unblock them or delete your account.
  • Checked before it is posted: every message and shared thing is checked before anyone sees it, against a list of banned words and, if you agreed to AI processing (Section 3), by an AI moderation service (see Section 3). Hate, sexual content, threats and abuse are not posted. Nothing is kept from the check itself.
  • Reporting a bot's answer: you can report an answer a bot gave you. We keep the answer as you saw it with the report, to act on it the same way.

1.9 Files and photos you attach

When you attach a file or a photo (to a message to X0 Bot, to a bot, or in a chat or space), X0 Bot reads it once and keeps what it found, so it can answer from the parts that matter instead of sending the whole file each time.

  • What is kept: the file itself (and, for a video, a few still frames from it), stored with Cloudflare (R2) under your account; the text read from it, in pieces, with anything that looks like a password or key left out; and details such as its name, kind, size, pages or length. A photo's hidden details (EXIF and the like, which can include where and when it was taken) are removed before it is stored; a JPEG keeps only which way up it is.
  • For how long: 30 days from when it was first read (sending the same file again starts the 30 days again), unless you choose to keep it. Then the file, its text and its pieces are deleted. A photo or file you sent in a chat or space is one of these files, so once it is deleted it no longer opens for the others either. Deleting your account deletes all of them; to have one deleted sooner, email privacy@x0bot.com.
  • Who reads it: documents, spreadsheets, scanned PDFs and videos are read on our own servers, by software that makes no calls out to the internet. The speech in a recording or a video is turned into text by our speech-to-text provider. A picture (and up to three frames of a video) is described once by an AI model from our AI service providers (see Section 3). When you ask about a file, only the pieces that match your question go to the AI model that answers. Nothing in a file is ever run.

2. How we use your information

  • To provide the core features (transcription, refinement, keyboard, personality)
  • To do what you ask in the Google apps you connect, and nothing more (see Section 11)
  • To do what you ask in GitHub with Xode (Section 12) and in the other apps you connect (Section 13)
  • To run the bots you use and make, and to keep what they remember of you (Section 14)
  • To read the files and photos you attach (see 1.9)
  • To send the notifications and fill the widgets you choose (Section 15)
  • To authenticate your account and secure your data
  • To process subscriptions and manage entitlements
  • To improve the app through anonymous, aggregated usage analytics
  • To measure and improve our advertising on Facebook and Instagram (see 1.6)
  • To diagnose and fix crashes and bugs
  • To comply with legal obligations

3. Service providers we use

X0 Bot works with a small number of carefully chosen service providers to run the service. Each receives only what it needs for its part, uses it only to provide that part, and is bound, by its agreement with us or its own published terms, to protect your data with the same or equal protection as this policy and Apple's App Store rules require. We never sell your data to any of them.

  • AI services: understand what you say, type or share, and write the answer: speech-to-text, language models, image understanding, and the safety check on what is posted in Spaces.
  • Hosting and storage: your account, our database, and the files you attach.
  • Payments: the app stores and payment processors for subscriptions.
  • Notifications: the services that deliver notifications to your devices.
  • Apps you connect: Google, GitHub and other apps you choose to connect, which handle what X0 Bot reads or writes there under their own privacy policies.
  • Search and maps: web search and map services, which receive the words or places searched, never your account.
  • Diagnostics and ad measurement: crash reports, and, only if you turn them on or allow them, usage statistics and ad measurement.

Every provider, with what it does and a link to its own privacy policy, is listed in Service providers, which is part of this policy. We keep it up to date, and change its date whenever it changes.

AI services, and your permission

Much of X0 Bot works by sending what you give it to third-party AI services, and we ask your permission before anything is sent. The first time you open the app, a card on Home says what is sent, to whom, and why, with Agree and Not now. Until you tap Agree, nothing of yours is sent to an AI service, and the features that need one (bots, dictation, Ask, rewriting, notes from recordings) wait.

  • What is sent: the words you type or say to X0 Bot, your voice while you dictate or record, and the photos, files, screenshots or screen you choose to share with a bot, dictation or Ask. When you ask Keylessbord to rewrite, the text around your cursor in that field (never a password field).
  • Who receives it: the AI services listed in Service providers, each only for its part of the answer.
  • Why: only to give you what you asked for (an answer, a transcript, a rewrite, or a bot's work), and to check what you post in Spaces before it is posted (see 1.8). We do not sell it, and we do not send it for advertising.
  • Changing your mind: turn off Send to AI services in the app under You, Privacy. From then on nothing more of yours is sent. What was sent before is kept as Section 4 says, and you can delete it as Section 5 says.

4. Data retention

  • Voice recordings: transient. Deleted immediately after transcription.
  • History: kept by default so you can review it; you can turn it off in Settings. Stored until you delete it or your account.
  • Ask: what it reads off your screen, and any picture it sends, is not stored. See Section 10.
  • The record of your requests to Ask: how each one went (done, waiting for you, or stopped, and why), how long it took, how many steps and changes it made, and which AI model answered and what that cost. It is kept until you delete your account, and holds none of your words, except from your phone: the first 80 characters of what you asked, for 30 days; your words to try again with, for a day; and a question X0 Bot asks you back, with your request, for five minutes. See 10.4 and 11.4.
  • Google apps you connect: what X0 Bot reads in them is not stored, except the details of a change waiting for your OK. Your access to an app is kept until you disconnect it or delete your account; your Tasks list and its record of actions, until you delete your account. See Section 11.
  • Other apps you connect: the same as for Google apps. See Section 13.
  • Xode: your GitHub link, projects, jobs and what X0 Bot learned of your repos are kept until you remove the project, unlink GitHub in X0 Bot, or delete your account. A token from Sign in with GitHub is kept until you disconnect, delete your account, or leave it unused for 30 days. See Section 12.
  • Files and photos you attach: 30 days from when they were first read, unless you choose to keep them. See 1.9.
  • Bots: the bots you make, your chats with them (the last 200 turns with each) and what they remember of you are kept until you delete them or your account; activity entries older than 90 days are deleted whenever a new one is added. See Section 14.
  • Widgets and notifications: a widget's key lasts a day; the outcome of an answer given from a widget or a notification is kept for seven days. See Section 15.
  • Purchases: our record of a subscription is kept until you delete your account. See 1.3.
  • Account: kept until you delete it. When you choose Delete account in the app, your account and everything kept with it are deleted 7 days later. Until then nothing is removed and your bots stop working; sign in and choose Keep my account to keep it as it was. Where the app says deleting cannot be undone, it is deleted straight away. You can also ask for deletion without the app, by signing in with your email at x0bot.com/delete-account, which lists what is deleted and what is kept. Messages you sent in chats with other people stay in those chats for them, under the name you had; reports (see 1.8) are kept as a safety record; and the app stores and payment processors keep their own records of purchases.
  • Diagnostic logs: retained by Sentry / PostHog for up to 90 days per their standard retention.

5. Your rights

Depending on your region (GDPR, CCPA, and similar laws), you have the right to:

  • Access — request a copy of the personal information we hold about you
  • Correct inaccurate or incomplete information
  • Delete your account and associated data ("right to erasure")
  • Portability — export your data in a machine-readable format
  • Restrict processing in specific circumstances
  • Object to processing based on legitimate interests
  • Withdraw consent at any time: to sending what you give X0 Bot to AI services (You, Privacy, Send to AI services; see Section 3), and to optional processing (usage statistics in the same place, crash reporting, tracking)
  • Non-discrimination — we will not deny service, charge different prices, or provide a different level of service because you exercised any right (CCPA)
  • Automated decision-making — request human review of significant decisions made about you by automated systems. We do not currently make such decisions.
  • Authorized agent — you may designate an authorized agent to make requests on your behalf (CCPA)
  • Complaint — lodge a complaint with your local data protection supervisory authority if you believe we have not complied with applicable law (GDPR)

Deleting your account: in the app, under You, Delete account; or on the web, without the app, at x0bot.com/delete-account.

To exercise any of these rights, contact us at privacy@x0bot.com. We respond within 30 days (45 for CCPA requests, with a possible 45-day extension where permitted). We may request information to verify your identity before processing.

6. Data security

  • All communication with X0 Bot servers uses TLS (HTTPS).
  • Data at rest is encrypted by our infrastructure providers.
  • The keys that let X0 Bot into the apps you connect, and a token from Sign in with GitHub, are encrypted again (AES-256-GCM) before they are stored. A bot's API keys and a widget's key are stored only as one-way hashes.
  • Access to personal data is restricted to necessary personnel.
  • We follow industry-standard security practices, but no service can guarantee absolute security.

7. Children

X0 Bot is not directed at children under 13. We do not knowingly collect personal information from anyone under 13. If we learn we have, we will delete it.

8. International data transfers

X0 Bot is operated globally. Data may be processed in the United States and other countries where our providers operate. Where required by law (GDPR), we rely on Standard Contractual Clauses.

9. Keyboard extension privacy

The X0 Bot keyboard extension is a separate iOS/Android app extension with restricted sandboxing:

  • The keyboard only sends data to our servers when you explicitly invoke voice or refine actions.
  • Normal typing stays on-device and is never transmitted.
  • The keyboard cannot see content from secure text fields (passwords, PINs).
  • Full Access is only required for voice + refinement features that need network. Without Full Access, the keyboard still functions for regular typing.

10. Ask, on the desktop app

Ask is the helper in the X0 Bot desktop app for Mac and Windows. Tap its key twice and say something about the app in front of you ("where's Export?", "explain this chart"), and it points at the thing, explains it, or does a small job for you. It reads the screen when you call it up, and again after each thing it does for you, to see what changed.

Talking with X0 Bot. In the same app you can also have a spoken conversation: tap the key twice and talk, turn after turn, and X0 Bot answers out loud. It knows where you are (the app, the window and the page in front of you) so you can ask about it, and when you ask for something to be done, it hands that to Ask. Everything in this section applies to it too, with the differences in 10.2 and 10.3.

10.1 What Ask reads on your computer

  • The app in front of you, through the system's accessibility interface: its buttons, fields and the text in them. On a Mac this needs the Accessibility permission.
  • The whole page or document, not only the part on your screen, when your question is about it: through the accessibility interface where the app offers it, and otherwise by scrolling the window a screen at a time, reading each, and putting it back exactly where you were. Not while you are dictating.
  • The window's pixels, read into lines of text by your computer's own text recognition (Apple's Vision on a Mac, Windows' own OCR on Windows), on your computer. On a Mac this needs the Screen Recording permission (Screen & System Audio Recording on newer versions of macOS).
  • Where your text cursor is, while you dictate, so Ask's character can sit above it. That position never leaves your computer.

Some questions, like "where's Export?", are answered on your computer from what it read: your words still go to be turned into text (see 10.2), but nothing from your screen is sent.

10.2 What Ask sends to our servers

  • A text list of what is on the screen: for each button, field or piece of text, what kind it is, its label, a short value, whether it is checked, selected or greyed out, and a rough position (top left, centre, bottom right and so on), together with the lines of text read off the window's pixels, each with its rough position. Also the app's name (for a browser, with the site's name, taken from the end of the tab's title, as in "Chrome: Gmail"), which field your cursor is in, and the text you have selected, if any.
  • What you said: your spoken question, turned into text by the same speech-to-text providers as dictation and handled the same way (see 1.2); and, while Ask is working on a question, what it has done for it so far. With it go your language setting and your time zone (as its offset from UTC).
  • The names of your files, only when you ask Ask about them: when you ask Ask to find, sort or tidy files, your computer does the work, only inside your Downloads, Desktop and Documents folders, and never in system, app or hidden folders. For a question about your files, the file names, sizes, kinds and dates it needs are sent to the AI model that plans the answer; what is inside a file never leaves your computer, and X0 Bot does not store the names. Moving something to the Trash always asks first.
  • One picture, only when a question needs it: a picture of the part of the screen your question is about (the image or chart, or else the window), cut on your computer to below the window's title bar and a browser's tabs and address bar, where it finds them, and no more than 1,024 pixels on its longer side by default. Looking when it's needed is on from the start, so Ask does not stop to ask first; you can have it ask before every picture instead (see 10.5). Ask's card shows a note when a picture goes with a question.
  • In a spoken conversation, besides the above: the window's title and the page's address (never the part after "?" or "#"), the page reduced to its outline and the parts your question is about (at most about 4,000 characters), and the conversation so far. The answer is turned into speech by the providers in Section 3, and spoken on your computer.

10.3 What Ask never sends

  • The window's title, beyond a browser's site name (above), except in a spoken conversation (10.2). The tabs, headings and other text on the screen are listed as they are shown, even where one of them repeats the title.
  • Exact positions of anything on your screen. Only the rough position above leaves your computer.
  • Passwords and addresses: nothing in a password field; nothing in a browser's address bar, where Ask finds one; and never the part of a web address after "?" or "#", where links carry their one-time codes. Text you have selected is not sent at all if it contains such an address.
  • Anything from a sensitive app. Ask stops, and sends nothing from the screen, in an app or page whose name marks it as banking, payments, investing or crypto, tax, health, insurance, a wallet or a password manager; and our servers refuse a request that comes from such an app.

Private (incognito) windows. When you call Ask, the one key or a spoken conversation up in a private (incognito) browser window, it works there as anywhere else: it reads the window as in 10.1 and sends what 10.2 says. Nothing from a private window is kept after your request is answered: not in what X0 Bot keeps to understand you (10.6), not in your History (what you dictate there is written for you but not saved), and nothing is learned from it. A spoken conversation holds it in our server's memory only while the conversation lasts, for its follow-ups, as for any window. The record of each request to Ask (10.4) is kept as for any request: how it went, never your words or your screen.

10.4 Where a picture goes, and what is kept

  • A picture goes from our server to the AI model that answers the question, from our AI service providers, with a second and a third model ready if the first fails (see Section 3). It goes with the question and the text list above. Each provider handles it under its own privacy policy.
  • X0 Bot does not store the picture and does not log it. It is held in memory only while your question is answered. Our logs record that a picture went with a question, its size in bytes, whether it was of one image or the whole window, and which model and provider answered; never the picture or the text on your screen.
  • Ask writes nothing to your History. As with dictation, your usage counts the words Ask writes for you and the seconds you spoke, and we keep a count, in memory, of the pictures sent in the past day, for the daily limit.
  • X0 Bot keeps a record of each request to Ask on your computer: how it ended and why, how many steps it took and how long, how many things it changed, and which AI model answered and what that cost. It holds nothing you said and nothing from your screen.

10.5 On from the start, and how to turn it off

So that X0 Bot works fully without a row of switches to set, everything in this section is on from the moment you sign in to the desktop app: reading the app in front of you, reading the window's pixels, reading the whole page when your question is about it, and looking at the screen when a question needs a picture. The app does not ask you to allow each one; this section is where we tell you what each does. Your computer's own permissions still apply (below), and X0 Bot never sends anything listed in 10.3.

  • Pictures, for every app: in the X0 Bot menu (the menu bar on a Mac, the system tray on Windows), "Pictures sent without asking" → "Ask again for all of them" makes Ask ask before each picture: Allow once, Always for that app (where the app can be named), or Not now. Answer Not now and no picture is sent. An app you said Always to is listed in the same menu, where you can have Ask ask again for it.
  • When you sign out: every Always is forgotten, and the next person to sign in on that computer starts from the defaults above.
  • Altogether, on a Mac: macOS itself asks you, the first time, to allow X0 Bot under Accessibility and under Screen Recording; X0 Bot cannot allow them for you. Without Accessibility Ask cannot read an app's buttons, fields and text, and without Screen Recording it cannot see the window's pixels or take a picture of them; with both off, it reads nothing on your screen. You can turn either off at any time in System Settings → Privacy & Security.
  • Altogether, anywhere: quit the X0 Bot app, or sign out of it. Ask works only while the app is open and you are signed in, and only when you call it up.

10.6 What X0 Bot keeps to understand you

So that a follow-up works ("send it to Dev too") and "message Riya" goes through the app you use for her, X0 Bot keeps a short record about you, on our servers, and gives it with each request to Ask, to the one key and to a spoken conversation:

  • You: your name, language and time zone, and what you told your bots.
  • People: who you ask X0 Bot to message and through which app, how often, and when last (at most 30 people).
  • Your last asks: the last six things you asked in full, and a short line for the ones before; and what X0 Bot last did for you (an Ask's last words, a routine's last run).

It never keeps anything from a password field, from X0 Bot's own window, from a private window or a sensitive app (10.3), from a picture, or anything that looks like a password, a code or a secret; and never what you dictate into other apps. A spoken conversation itself is held only in our server's memory and forgotten after 30 minutes without a word. Turn off "Use what you've told your bots" in Settings → Privacy and nothing is kept or used; clearing what your bots know there clears this record and your conversations too. It is deleted with your account.

11. Google apps you connect

You can connect Google apps to X0 Bot: Google Calendar, Google Docs, Google Tasks, Google Sheets, Google Forms and Google Classroom. Then you can ask X0 Bot, on your phone or with Ask on your computer, to do things in them for you. You connect each app yourself, in Connected apps in X0 Bot: tap Connect, and Google asks whether to allow it. This section says what X0 Bot reads and changes in those apps, where that goes, what we keep, and how to end it.

11.1 What X0 Bot does in each app

Google asks you for an app's permissions only when you tap Connect on it, and X0 Bot connects only if you allow all of them. Signing in to X0 Bot with Google never asks for them. Connecting does not give X0 Bot your Google account's name or email address.

  • Google Calendar — reads your events (their titles, times, and guests' names and email addresses), when you are free or busy, and your calendar's time zone. It adds, moves or cancels an event when you ask. If the event has guests, Google emails them the invite, the new time or the cancellation.
  • Google Docs — makes a new Doc from your words, or from one of your X0 Bot meeting notes (its summary, key points and people, or its transcript if it has no summary). It does not read your Docs. Google lets it reach only the files X0 Bot made, never the rest of your Drive.
  • Google Tasks — reads your task lists and tasks. It adds a task, ticks one off or deletes one when you ask.
  • Google Sheets — makes a sheet, adds rows to one, or reads one back. Google lets it reach only the sheets X0 Bot made.
  • Google Forms — makes a form with your questions and publishes it, and reads the answers people send: the totals for each choice and the latest three answers. Google lets it reach only the forms X0 Bot made. Those answers are other people's, and everything in this section applies to them too.
  • Google Classroom — only reads: your classes, the classwork that is due and whether you turned it in (with your grade, once it is returned), and your classes' latest announcements. It never changes anything in Classroom.

Gmail and Google Maps are not connected apps. When you ask X0 Bot to write an email, it opens Gmail's own compose window with the email written, for you to check and send yourself. When you ask for directions, it opens Google Maps. X0 Bot has no access to either, and it reads none of your email.

YouTube is not a connected app either. When you ask X0 Bot to find a video, it sends only the words to search for to Google's YouTube Data API, with X0 Bot's own key (or, when it can't, opens YouTube's own search on your device). There is no sign-in, and nothing from your Google account is read or changed.

11.2 Only when you ask

  • X0 Bot reaches into a Google app only to do what you just asked for. It never looks around in your apps on its own, in the background or on a schedule.
  • Looking something up (your calendar, your tasks, a sheet, a form's answers, your classes) happens right away.
  • Changes wait for your OK. The first time X0 Bot makes a kind of change in an app (adding an event, adding a task), it shows you a card with the exact change, and nothing happens until you tap Approve; tap Not now, and nothing is done. Once you approve, X0 Bot makes that kind of change in that app without asking again. Deleting always asks, every time. You choose how far X0 Bot can go in each app (Can look, Can draft or Can send): at Can draft every change asks, and at Can look X0 Bot changes nothing.

11.3 Where your Google data goes

  • To the AI model that works out the next step. What X0 Bot reads in a Google app, at most 1,500 characters at a time, goes from our server with your request to the AI model that answers you, from our AI service providers, with a second and a third model ready if the first fails (see Section 3). With Ask on your computer, the text list of your screen goes with it (see 10.2). On every one of these requests, X0 Bot asks only for providers that do not collect it to train models. The providers handle it under their own privacy policies, which may let them keep it for a short time after X0 Bot has dropped it.
  • To you. X0 Bot's answer, and the card asking for your OK, are shown in X0 Bot on your phone or computer.
  • To Google. What you asked X0 Bot to write there: an event and its guests' email addresses, a Doc with your words or your meeting note, a task, rows in a sheet, a form's questions; and the words of a YouTube search (see 11.1). When you connect, X0 Bot also sends Google your X0 Bot account ID, which Google sends straight back so we know the sign-in is yours.
  • Nowhere else. When a change is waiting for your OK, the notification on your phone names only the app. Apart from Supabase, which stores what 11.4 lists, no one else receives your Google data.

11.4 What we keep

  • Your access to each app. The keys Google gives X0 Bot for an app ("tokens") are encrypted (AES-256-GCM) before they are stored, and kept until you disconnect that app or delete your account. If X0 Bot stops offering an app you connected, its keys are no longer used, and they are deleted when you delete your account, or sooner if you email privacy@x0bot.com.
  • Your Tasks list. For each request that used an app: the first 80 characters of what you asked, and short steps like "Google Calendar: list events", so you can see what X0 Bot did. Only you can see it in X0 Bot.
  • A change waiting for your OK keeps its details, which can include what X0 Bot read in Google to show it to you (an event's title, time and guests, or the name of a task, task list or sheet), until you tap Approve or Not now. Then they are deleted. If you never answer, they stay until you delete your account.
  • A record of each action: which app and action, whether it ran, failed or you said no, and when. It holds nothing that was read or written.
  • Your recent requests, on your phone. The first 80 characters of what you asked and how it ended, for 30 days, shown in Activity on the You tab; and, when a request failed having changed nothing, your words for a day, for Try again. Only you can see them in X0 Bot. How each request went (how it ended, how long it took, how many changes it made) is kept until you delete your account, without your words. None of it holds what X0 Bot read in your Google apps.
  • Nothing else. Apart from a change waiting for your OK, what X0 Bot reads in your Google apps is used for that one request and not stored, and we do not write it into our logs. On your phone, a question X0 Bot asks you back is kept with your request until your next request, and used with it only if that comes within five minutes, so your answer makes sense; then it is deleted. A question that comes after X0 Bot read something in a Google app is held only in our server's memory, since it may repeat what was read. Your calendar's time zone is held in memory too, and read from Google again at most once an hour.

11.5 Limited Use

X0 Bot's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain words:

  • X0 Bot uses your Google data only to do what you asked, when you ask.
  • The record X0 Bot keeps of your requests (see 11.4) says how each one went; it never holds your Google data.
  • We never sell it.
  • We never use it for advertising, and it is not part of the advertising measurement in 1.6.
  • X0 Bot does not use it to create, train or improve AI or machine-learning models.
  • No one at X0 Bot reads it, unless you ask us to (for example, to look into a problem you report), it is needed for security (such as looking into abuse), or the law requires it.

11.6 Disconnecting, and deleting what we keep

  • Disconnect an app in Connected apps in X0 Bot. X0 Bot deletes its stored access to that app right away and stops using it.
  • At Google's end: Google keeps one permission for all the Google apps you connect to X0 Bot. When you disconnect the last of them, X0 Bot also asks Google to revoke it. Until then, Google keeps X0 Bot's permission for every Google app you connected, including the one you just disconnected, though X0 Bot no longer uses it for that app. You can also remove X0 Bot yourself at any time in your Google Account (myaccount.google.com/connections), for example if Google could not be reached when you disconnected.
  • What stays after you disconnect: your Tasks list, the record of actions, and any change still waiting for your OK (see 11.4). They are kept until you delete your account. To have them deleted sooner, email privacy@x0bot.com.
  • Deleting your account deletes all of it: your access to your Google apps, your Tasks list and the record. It does not tell Google, so disconnect your Google apps first, or remove X0 Bot in your Google Account afterwards.
  • What X0 Bot made or changed in your Google apps (events, Docs, tasks, sheets, forms) is yours. It stays there until you change it in Google.

12. Xode and GitHub

Xode works on code in your GitHub repos: it reads a repo, makes changes on a branch of its own, and opens a pull request for you to review. You connect GitHub yourself, in X0 Bot. This section says what it can reach, what it does there, where your code goes, what we keep, and how to end it.

12.1 How it connects, and to which repos

  • The X0 Bot GitHub App. You install it on GitHub and choose which repos it can see: all of an account's repos, or only the ones you select. X0 Bot works only in the repos you then add as projects in X0 Bot. In an organisation's repos, or another person's, it works only where GitHub says you can write, and an organisation's owner may have to approve the install first.
  • What the App is allowed to do, as GitHub shows you when you install it: read and write a repo's contents (its files, branches and commits), its pull requests and its workflow files; read its GitHub Actions runs, checks and commit statuses, and its basic details; and, if the App asks for it, read its deployments, to show a preview link. It also has GitHub's Administration permission, which X0 Bot uses only to make a new repo when you ask for one. GitHub tells X0 Bot when a pull request, a review, a comment, a check, a status or a push changes in those repos, and when the App is uninstalled or loses a repo. The App is given no access to issues, to the repos' secrets, or to your GitHub account's own settings.
  • Sign in with GitHub, where X0 Bot offers it instead of the App: you sign in on GitHub, and X0 Bot receives a GitHub token of yours that can reach every repo you can (GitHub's "repo" and "read:user" permissions, and "workflow" only if you allow that too). X0 Bot still uses it only in the repos you add as projects, and asks GitHub whether you can still push before every change.
  • A new repo. When you ask X0 Bot to make a repo, GitHub asks you to confirm; the repo is made on your own account, with the name you gave, private unless you chose public, and added as a project.

12.2 What it reads and what it writes

  • It reads a project's files, branches, commits and pull requests, reviewers' comments on its pull requests, and what checks and CI say about them (with the end of a failing job's log). When you add a project, X0 Bot reads the repo to learn its layout, and reads the changed files again when its default branch moves.
  • It does on its own: makes a branch for a task (named tailzu/…), commits to that branch, opens a draft pull request, brings its own branch up to date with the default branch, and comments on its own pull requests. Its commits name the bot as their author and you as co-author.
  • It asks you first before it commits or pushes to any other branch (the default branch included), merges a pull request, marks one ready for review, closes one, deletes a branch, changes a workflow file, or adds a first file to an empty repo. A force-push, deleting the default branch, and a commit with something in it that looks like a password or key ask every time, with Face ID on your phone. For a project, you can answer "always" or "never" for an action that asks (except those three), and take it back at any time. When nobody is there to answer, the work waits for you.
  • It never deletes a repo, writes outside the repo, or works around GitHub's branch protection.
  • Pull requests you hand over. If you ask X0 Bot to look after a pull request, it may push fixes to that pull request's branch, answer reviewers' comments and keep one status comment up to date there, without asking each time.
  • Running commands. A step that needs a computer (installing, building, testing) runs on one of your own computers with the X0 Bot desktop app open (see 12.6); or on GitHub's own computers (GitHub Actions), in your repo. For that, X0 Bot makes a temporary branch (named tailzu-run/…) holding a small workflow, the step's commands and a script, and deletes it afterwards. It uses your account's GitHub Actions minutes, and in a public repo anyone can see that branch while it exists. You can tell X0 Bot not to use GitHub's computers. A computer that runs commands is given access that can only read the repo; X0 Bot commits the changes itself, under the rules above.

12.3 Where your code goes

  • To AI models. To do the work, X0 Bot sends your task, parts of your files, and what commands printed, to AI models from our AI service providers (see Section 3), chosen by the kind of work. X0 Bot asks only for providers that neither keep nor train on what they are sent, and names you to them only by a one-way hash, never your account ID. Each provider handles it under its own privacy policy.
  • To GitHub. What X0 Bot writes goes into your repo. Its pull requests include a log of what it did.
  • Secrets. Before anything is committed, kept in our records or put in a pull request, X0 Bot looks in it for passwords, keys and tokens. A commit with one asks you every time, and our records keep a note in its place. This check can miss things, so do not put secrets in your code.
  • Not into our logs. Nothing that was sent to the AI models, or came back from them, is written to our logs.

12.4 What we keep

  • Your GitHub link: for each install you link, the account it is on, whether it sees all or some of its repos, and your GitHub ID and username. With the App we keep no GitHub token: one is made when X0 Bot needs to act in a repo, lasts under an hour, and is held only in our server's memory. With Sign in with GitHub, your token is kept, encrypted (AES-256-GCM); it is never shown to anyone, and never given to the AI models or to a computer that runs commands.
  • Your projects: the repos you added; for each branch X0 Bot made, its name, the first 200 characters of the task it was made for, the commit it started from, its pull request and where it is in its life; the pull requests it looks after; your settings for each project; and the standing permissions you gave.
  • Jobs: the first 500 characters of each task, the commands run, the last 8 KB each one printed (with anything that looked like a secret taken out), how long they ran, what the job cost, and a log of what X0 Bot did. A job's record also holds the changes it was making and parts of the files it last read, so it can carry on, or go back a step, and keeps them after the job ends.
  • What X0 Bot learned of a repo: its files' paths, languages and sizes, the names of their functions and other parts, which files use which, a short summary of each written by an AI model, the text its screens show people (without anything that looked like a secret), its commands and conventions, and the names (never the values) of its settings. Not a copy of your files.
  • Talking about your code: a short running summary of each conversation (up to 2,000 characters) and the files and lines the last answer pointed to; and your answers to the questions a new project is asked.
  • Usage: per month, the GitHub Actions minutes X0 Bot used for you and whether your free minutes ran out, and what your jobs cost.

12.5 How long, and how to end it

  • All of 12.4 is kept until you remove the project, unlink GitHub in X0 Bot, or delete your account, and then deleted. Removing a project deletes its branches' records, its jobs and what was learned of it.
  • Unlinking in X0 Bot forgets the install and its projects here, but does not uninstall the App from GitHub: X0 Bot shows you the GitHub page where you do that. Uninstalling the App on GitHub, or taking a repo off it, removes them from X0 Bot as well.
  • Sign in with GitHub: disconnecting it in X0 Bot, deleting your account, or leaving it unused for 30 days revokes your token at GitHub and deletes it. You can also revoke it yourself in your GitHub settings, under Applications.
  • Deleting your X0 Bot account does not uninstall the App from GitHub; do that on GitHub.
  • What X0 Bot wrote in your repos (branches, commits, pull requests, comments and repos it made) is yours, and stays on GitHub until you change it there.

12.6 Xode on your own computer

Your own computer is quicker than a cloud computer and costs you nothing, so while the X0 Bot desktop app is open and you are signed in, Xode may run a job's commands (installing, building, testing, and a preview of a site it is working on) there. This is on from the start, for every project you add, without asking you each time; this section is where we tell you how it works.

  • What our server learns of your computer: while the app is open, a random ID made for this computer, the computer's name (as the system reports it, at most 80 characters), whether it may run work and is busy, and which projects it may run. These are held only in our server's memory, for about a minute after the app last sends them, and never written to our database. With each job it gets back what the commands printed (kept as in 12.4).
  • Where it works: in a folder of its own inside the app's data, from a read-only copy of the project's code, with a clean environment and a private home folder. It cannot see your passwords, keys or your other files, and it never changes your own copy of the project. X0 Bot commits the changes itself, on GitHub, under the rules in 12.2.
  • What it refuses: commands that need administrator rights (such as sudo), pushing to GitHub or publishing a package from your computer, and deleting your home folder. If Docker is installed, you can have it work inside a container as well.
  • When it stops on its own: it pauses when your battery is below 20% or Low Power Mode is on, and runs nothing while the app is closed.
  • What it keeps on your computer: a log of every command it ran, with anything that looked like a secret taken out, kept for 7 days and then deleted. "Xode activity…" in the X0 Bot menu (the menu bar on a Mac, the system tray on Windows) shows what it is doing and opens that log.
  • How to turn it off: untick "Use this computer for Xode" in the X0 Bot menu, and your jobs run on GitHub's computers or ours instead; "Stop" there ends what is running. In "Xode activity…" you can also keep a single project off this computer. Quitting the app or signing out stops it too.

12.7 Xode in the terminal

  • Signing in: xode login shows a short code; you approve it in the X0 Bot app. The terminal then gets a sign-in of its own, which works only for Xode (your projects, its chat and its jobs) and nothing else in your account. We keep only a one-way hash of it, with the computer's name, its system, when it was added and when it was last used (at most every ten minutes).
  • On your computer: the sign-in is kept in your system's keychain (macOS), its secret service (Linux), or else a file only your user can read (~/.config/xode). It is never printed or written to a log. Beside it, xode keeps which project each folder is and the last job there.
  • What it does there: while xode is open, your computer can run that folder's project's work, under the rules in 12.6. When a job ends, its branch is brought into the folder only if you have no uncommitted changes there; otherwise it tells you how, and changes nothing.
  • Removing it: xode logout, or Settings → Terminal sign-ins in the app, where each one is listed with a Remove button. A removed sign-in stops working at once, or within a minute everywhere.

13. Other apps you connect, and apps X0 Bot opens for you

Besides Google's (Section 11), X0 Bot can connect to other apps, for example Notion, Linear or Todoist. Which ones you can connect is listed in Connected apps in X0 Bot, and changes over time.

13.1 How they connect

  • You connect each app yourself: tap Connect, sign in on the app's own page, and allow X0 Bot there. X0 Bot then works in the app through the connection the app itself offers to AI assistants (its "MCP server").
  • Zapier connects with a private link you copy from your Zapier account instead. That link is a key to your account, and we treat it as one.
  • Where X0 Bot lets you add an app by its address, it treats that app as one nobody at X0 Bot has checked: anything it can do that is not plainly a read asks you first, and you choose for each of its actions whether it may run, asks first, or is off.

13.2 What X0 Bot does there

  • As with Google apps, X0 Bot uses a connected app only to do what you asked, or what a bot you use was asked (Section 14), when it is asked. Looking something up happens right away.
  • You choose how far X0 Bot can go in each app: Can look (it only reads), Can draft (every change asks first, and nothing can be sent, deleted or paid) or Can send. A new connection starts at Can send. At Can send, the first time X0 Bot makes a kind of change or sends something in an app, it shows you the exact change and waits for your yes; once you approve, it does that kind of thing in that app without asking again. Deleting and paying ask every time.
  • X0 Bot tells reading, changing, sending, deleting and paying apart from what each app says about its actions and their names. An app can describe its own actions wrongly, so check what a card asks you to approve.

13.3 Where the data goes, and what we keep

  • What X0 Bot reads in a connected app, at most 1,500 characters at a time, goes to the AI model that works out the next step, as in 11.3 (or, for a bot, as in 14.4). What you asked X0 Bot to write goes to that app. Each app handles your data under its own terms and privacy policy.
  • We keep the same as for Google apps (11.4): your access to each app (its keys, or Zapier's private link, encrypted with AES-256-GCM), your Tasks list, the details of a change waiting for your OK until you answer it, and a record of each action, which holds nothing that was read or written.

13.4 Disconnecting

  • Disconnect an app in Connected apps in X0 Bot: X0 Bot deletes its stored access to that app right away and stops using it. Unlike Google, the app is not told; to end X0 Bot's access at the app's end too, remove X0 Bot in that app's own settings.
  • Your Tasks list and the record of actions stay until you delete your account, as in 11.6. Deleting your account deletes all of it, but does not tell the apps.

13.5 Apps X0 Bot opens for you

Some apps are not connected at all. X0 Bot opens them on your device with something filled in, for you to finish there: a WhatsApp, Telegram or text message, an email in Gmail or a Threads post for you to send; a call for you to start; a UPI payment for you to check and pay in your own UPI app, with your own PIN; or directions in Google Maps, a ride in Uber, hotels on Booking.com, or a search on Amazon, Flipkart, YouTube, YouTube Music or Spotify. What was filled in goes to that app when it opens. X0 Bot has no access to those apps or your accounts there, and never sends or pays for you.

14. Bots

X0 Bot's helpers are bots. Xode, Keylessbord, Plan Ease and the Travel bot come with it, and you can make your own from a sentence. This section says what a bot can do for you, what we keep, and what others can see when you share one.

14.1 What a bot can do for you

  • Only what its skills allow: search the web and read pages, read the files you gave it, make pages and charts, answer questions about your code (only reading it), and use the connected apps you gave it. Changing code is Xode's own work (Section 12).
  • In a connected app, a bot follows the rules in 13.2: it reads right away, and nothing that changes, sends, deletes or pays happens until you say yes, unless you already allowed that kind of change in that app. A bot is told when something is waiting for you, so it does not say it is done.
  • A bot fills in a UPI payment for you to pay in your own UPI app; X0 Bot never moves money.
  • When a bot searches the web, the words it searches for go to search services, and it reads public web pages; the Plan and Travel bots send places to map services (see Section 3). Your account is not sent to them.

14.2 What we keep

  • The bots you make: name, purpose, your rules for it, its skills, the apps and files you gave it, its tone, and its spending limits.
  • Your chats with a bot: what you said and what it answered, up to the last 200 turns with each bot, until you clear the chat, delete the bot, or delete your account.
  • What a bot remembers of you: short facts it learned from what you told it (at most 40 a bot; never a feeling, your health, politics, someone else's details or anything secret) and a short running summary of your talks. You can read them, and forget one or all of them, in X0 Bot.
  • What all your bots use: a fact one of your bots learned is also kept once for all of them (at most 60), so every bot, Ask and Xode can fit their answers to you; a fact about your health, religion or caste, politics, money or sexuality is never kept this way. It is on unless you turn it off in Settings › Privacy, where you can also clear it; forgetting a fact in a bot forgets it here too, and it is in your data download and goes when you delete your data.
  • Activity: for each answer a bot gave you, which bot, the first 200 characters of what you asked, and what it cost; and for a payment you say you made, which bot filled it in, what it was for, to whom and how much. Entries older than 90 days are deleted whenever a new one is added.
  • API keys you make for a bot are stored only as one-way hashes, with their first few characters so you can tell them apart. What an app sends a bot with a key, and the bot's answers, are not written to our logs, and do not go into the bot's memory of you.

14.3 Sharing a bot

  • In a space: Plan Ease, Notes, Travel bot and Xode, and any other bot added to a space, read the latest things shared there, and what the space told its bots, whenever someone in the space uses them.
  • In Find a bot: if you list a bot there, other people see its name, colour, purpose, your rules for it, its tone and the apps it asks for, and your name as 1.8 says it is shown; anyone can add a copy, which becomes their own bot. They never get your files, its memory of you, its keys or its commands. Unlist it to take it down.
  • With a key: anyone who has one of a bot's API keys can ask that bot, and its connected apps then act for you, under the rules in 13.2. Revoke a key in X0 Bot to stop it.

14.4 Where a bot's work goes

  • A bot's work goes to AI models from our AI service providers (see Section 3), only to providers that neither keep nor train on what they are sent. With your message go the bot's rules, what it remembers of you, the parts of its files that match your question (at most 3,500 characters), and what a connected app or a web page returned.

15. Widgets, Live Activities, notifications and your Lock Screen

Some of X0 Bot can be seen without opening it, so anyone who can see your phone may see it too. You choose which of these you use.

15.1 What can appear

  • The Month widget (Home Screen, and the iPhone Lock Screen): how many words you used or have left this month, and your streak. Never your words.
  • The Flow Live Activity (iPhone Lock Screen and Dynamic Island), while Flow keeps the microphone ready: whether it is ready, listening or writing, and a count of the words so far. Never what you said. Until you finish setting X0 Bot up, a Live Activity may also show your next setup step.
  • From your people (widget): the latest from the people in your spaces and chats: who sent or shared something, the tasks and plans they gave you, and, on the Home Screen, the words of their messages.
  • Needs you (widget): a bot's question with its answers, a change in a connected app waiting for your yes, and the tasks given to you, with buttons to answer them.
  • On the iPhone Lock Screen, these two widgets show only a count ("2 new from your people"), and while the phone is locked (StandBy, Always-On) the words of messages and of Needs you are hidden. On Android they are Home Screen widgets, and show what they show to anyone who can see your Home Screen.
  • X0 (widget, Home Screen and iPhone Lock Screen): your bots at a glance: which are working and on what, what needs you (a bot's question with its answers, or a change waiting for your yes, with buttons), the last thing a bot finished and its pull request, your week's count, and a line about what changed. On the Lock Screen, and while the phone is locked, a change waiting in a connected app and a question a bot marks private show only that a bot needs you, never their words; a Xode's question shows its words.
  • The Bots at work Live Activity (iPhone Lock Screen and Dynamic Island), while a Xode job runs: the words of its task, its step, a question it asks you with its answers (only that it needs you, if the bot marks the question private), and when it ends, what it finished and its pull request.
  • Notifications, if you allow them: that a bot needs your answer or your OK (one for a connected app names only the app); how a Xode job is going, with the words of its task; a task or plan someone gave you, with its title; that someone messaged you (their name and the chat, not the message); the reminders you asked for; a daily summary, if you turn it on; and reminders about your words. Your phone's settings decide whether their words show on the Lock Screen.

15.2 Answering without opening the app

  • A widget's or a notification's buttons can answer a bot's question, say yes or no to a change waiting in a connected app (never a delete or a payment: those open X0 Bot), mark a task done, or send a reply to a message.
  • So that a widget's buttons work while the app is closed, X0 Bot gives your phone a separate key that can do only those things and lasts a day. It is kept on your phone (in the iPhone's Keychain, or the app's private storage on Android), and we keep only a one-way hash of it. Signing out revokes it.
  • We keep the outcome of each such answer for seven days, so a button pressed twice acts once.

15.3 Your choices

  • Widgets appear only where you add them, the Flow Live Activity only while Flow is on, and the Bots at work Live Activity only while a Xode job runs. Remove them as you would any other.
  • Choose which notifications X0 Bot sends, and its quiet hours, in X0 Bot ("What pings you"); turn notifications off, or hide their words on the Lock Screen, in your phone's settings.
  • Our servers send notifications through Expo's push service to Apple's and Google's (see Section 3). The Bots at work Live Activity is updated through Apple's push service directly, with a token your iPhone gives for that one activity; we delete it when the job ends.

16. Changes to this policy

We will update this policy when our practices change. We will bump the "Effective" date at the top and, for material changes, notify you in the app or by email.

17. Contact

Questions or requests: privacy@x0bot.com

This policy is available at https://x0bot.com/privacy. The version served by the app matches the version linked in App Store Connect.