Privacy
The little room needs a real lock.
Félix can only feel like home if the lock is honest. This is a plain-language account of what OptimizeMyLife — operated by 9569-7173 Québec inc. — collects, how we use it, who helps Félix answer, and how we protect it. It says exactly what the product does, and nothing it doesn’t.
The little room needs a real lock: this page says what Félix keeps in memory, what stays on your device, what travels to AI engines so he can answer, and what we will never do with your words.
Effective August 13, 2026.
This page is the readable summary first; the complete, governing policy lives one step deeper: Privacy Policy (full version) — effective August 13, 2026. Privacy Officer : Maxime Jodoin, support@optimizemylife.ai.
Want to erase instead of read? The step-by-step deletion guide lives at Delete your data.
What Félix keeps close
The email you give us (waitlist or account) so we can reach you. Your account and billing status tied to your FOX key. Your conversations with Félix and the notes he keeps to remember what helps you. A push-notification token when you choose notifications. Your precise location, only for a request where you choose Share once (or the optional keep-my-position setting on the web and Telegram). A reported AI response only when you confirm a report. Course progress, exam results, certificates and setup preferences. Standard, anonymous hosting logs and aggregate analytics for page visits.
How we collect it
Directly from you — what you type to Félix, what you enter at signup or checkout, and the settings you choose. Some information (like basic device and log data) is recorded automatically when you use the site, the way any hosted web service works.
How we use it
To run the service: let Félix understand you, remember useful context, and answer well; to activate your account and process payments; to send you the messages you asked for; and to keep the service secure and improve it. We do not sell your data and we do not use your conversations to show you ads.
What stays in your browser
Some things stay in your browser or on your phone — course progress, exam results, certificates, setup preferences, and the profile photo you choose in the mobile app. That photo is not uploaded to us. Your Félix conversations and the memory he keeps are stored on our servers under your FOX key, because Félix needs them to remember you across devices. You can erase all of it — conversation, memory card and reminders — at any time.
Banking data
The bank connection is not open yet (coming soon); this clause describes how it will work once it opens. If you connect a bank, Plaid handles your bank sign-in; OptimizeMyLife never receives or stores those credentials. Félix gets read-only access to balances and transactions — never payments or transfers. The connection token is encrypted on our server under your FOX key, expires after 180 days unless you keep using the connection, and is deleted when you disconnect. If an incident risks your personal information, we will assess it, notify affected people when required, and follow Québec Law 25.
Félix Browser Bridge for Chrome
The extension needs access to ordinary http and https pages so it can work on the sites you choose. It can read page URLs and titles, selected and visible text, non-sensitive field labels and controls, and scroll position. While an ordinary web page is open, it keeps capped in-page ring buffers of recent visible console messages and request metadata (URL, method, status and timing — never request or response bodies). Buffering begins while the page is open; the extension displays those diagnostics only after you explicitly choose Console & network, and it never sends them in the background. “Compare tabs” reads the same context from your open web tabs only after you press it. A screenshot is captured only after you press Screenshot or give that voice command; it is shown temporarily and is not stored or sent in the background. The optional navigation path is off by default, stays in session storage and clears when the browser session ends. Page context, saved tasks, task values, site approvals, activity and safety logs, prepared-purchase amounts and budgets stay in local extension storage; settings may sync through Chrome when browser sync is enabled. Browser voice commands use Chrome’s built-in speech recognition: the extension receives the transcript and does not store raw microphone audio, while the browser or its speech provider may process the audio under its own terms. When you choose Ask Félix, the extension opens optimizemylife.ai and sends the current page URL, title, approval mode and a short domain-only path in that navigation request; the full captured page text remains local in version 0.4.1. The optional Félix Desktop bridge, added in version 0.4.0, links this extension to Félix Desktop, a separate companion program you install on your own computer. It does nothing unless you installed Félix Desktop and turned its bridge on there, and you can refuse it from the browser side at any time in the extension’s settings. When you click the camera beside the floating Félix, the extension answers with the structure of the page in front of you: its title, a visible heading, its address without query parameters, and the controls you can see with their label, kind and enabled state. It never sends a field’s value, never a password, payment-card or code field — those controls are dropped entirely, label included — and never an image. Since version 0.4.2, that same look also carries the page’s visible text, with every secret field’s own label and every ordinary field’s typed prose masked out before it leaves your device; version 0.4.1 and earlier sent structure only. One look per click. It travels over Chrome native messaging to Félix Desktop on your own device — never over the network from the extension itself. Félix Desktop then sends that look, and a screenshot when you took one, to Félix’s own servers to answer your question, only on that same click of the camera; neither is stored, only used to answer that one question. Panic mode refuses it like any other browser action, and the on-device activity log records that a look happened and whether it was answered — never the page’s address and never what was seen. Version 0.4.1 adds the one message the extension sends over that bridge without being asked: while Félix Desktop is connected and that same switch is on, whenever your active tab changes, navigates or renames itself, the extension announces that page’s title and its address without query parameters or fragment — nothing else, no controls, no page text, no field value, no image, and two empty strings for a tab that is not an ordinary http or https page, so no Chrome internal title crosses. It exists so Félix Desktop stops showing you what it saw on a page you already left. It never triggers a look, it is sent once per actual change, it travels over the same local channel to the program on your own device and never over the network, and the extension keeps no record of it. Turning the switch off, disconnecting Félix Desktop, or panic mode stops it. Optional Login help is off by default and requires separate, revocable consent for each site. It detects only visible login-form structure and can focus a field so your own browser or third-party password manager can offer its normal fill. It does not read, copy, store, log, transmit or inject passwords, passkeys, one-time or recovery codes, tokens, cookies or clipboard contents. It cannot confirm that a password manager is installed or open one directly, and it reports only whether the login form disappeared or stayed visible — never that authentication succeeded. Because you choose which page or screenshot to capture, visible content may contain personally identifiable, health, financial or payment, authentication, personal communication, location, web-history, user-activity, or other website-content data. These nine categories are disclosed even when handled only on-device. The extension can fill ordinary fields, select, scroll, copy selected text or click visible controls under your chosen approval mode. It refuses passwords, payment-card fields, one-time codes, API keys, tokens and government identifiers in every mode, and it never clicks the final purchase control. It makes no hidden background request, contains no advertising or analytics, and never sells browser data. The use of information received from Chrome APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Who helps Félix answer
Only the service providers we need to make Félix work: AI engines that generate Félix's replies (your messages travel there and back over HTTPS; see the AI providers section for what we can and cannot say about how they handle them); payment processors that handle checkout and billing; and infrastructure providers that host the site and store data. We never sell your data, and we never hand it to advertisers.
Our subprocessors, named
Here are the providers our code calls to run the features described here, what each receives, and why. The list is not presented as a complete inventory. Anthropic (its Claude models, called directly) writes Félix's replies and condenses your conversations into memory; OpenRouter can route those same calls, but only when an explicit switch is turned on in the code (it is off unless set). Vercel hosts the site and runs our servers. Upstash stores your conversations, your memory card and your billing state. Stripe and Lemon Squeezy process payments — they see what you buy and your billing details, never your conversations. Resend sends the emails you asked for. Plaid handles banking connections, and only if you connect a bank. Composio is the integration partner for the long tail of apps — the limits on what Félix reads through it are spelled out in the next section. Telegram carries your messages only if you choose to talk to Félix there. AssemblyAI turns your voice messages into text. ElevenLabs runs Félix's live voice calls and turns his replies into speech, and Twilio provides the phone line for the calls Félix places for you. When you share your location, OpenStreetMap (Nominatim) converts it to a place name, Foursquare or Google Places finds places near you, OSRM and Google Maps estimate routes, and Open-Meteo provides weather. Expo delivers push notifications to the mobile app. Sentry receives error reports (our filter removes request bodies, headers, cookies, e-mail addresses, tokens and FOX keys before sending). Jina Reader and, when its key is configured, Firecrawl read a web page you ask Félix to open (the page address can contain a tracking number). UPS, FedEx, Canada Post, USPS and Purolator receive the tracking number when you ask where a parcel is. Yahoo Finance, Coinbase, CoinGecko, Nasdaq and CNBC supply public market prices (the symbol you ask about is sent to them). PostHog (website only, inactive without a project key) measures coarse product events. Vercel AI Gateway (the Jev evaluation model), only when its key is configured, receives a copy of your message text (or, for an invoice, the merchant and key line items) to propose a classification. Nominatim, OSRM, Open-Meteo and the public price sources are public services used without an account: there is no contract between them and us, and we do not claim that a contract limits what they do with a request. The services you connect (Outlook, iCloud, Todoist, Square, QuickBooks, Toast, Wise, business phone systems such as Phone.com and others) are contacted with a credential or token that the account holder provides to connect that service, or through a webhook the account holder configures.
Where each connection goes
Some services connect straight to Félix, while the long tail signs in through Composio, our integration partner. Signing in gives that partner an authorization until you disconnect it, but connected does not mean functional. Before Félix can read anything, the exact connector and toolkit must be classified, the account must belong to the signed-in owner, and the exact provider tool must pass our safe-read checks. Credential-bearing reads, document-body downloads, money movements and mutations are excluded from this read path. Provider errors never become a success, and a catalogue or connection status is never presented as proof that a read worked. Actions through this path are not available today; any future write will require an owner-scoped account plus explicit confirmation before the provider is called. Anything unclassified fails closed. The Connections page separately reports connection, verified reading, available actions, required approval and unsupported states.
AI providers & your messages
Félix thinks using third-party AI engines. As our code stands, your words, and the context and memory needed to answer, are sent over HTTPS to Anthropic (its Claude models, called directly) and the reply comes back. For a request that needs your location, your shared position and its place name are part of that context. Our code can instead route these calls through OpenRouter, but only when an explicit switch is on (off unless set); when it is on, the requests that write replies and memory carry OpenRouter’s option that refuses routes which log or train on inputs, but the image-generation request (which sends your image description) does not. Our calls to Anthropic carry no equivalent per-request setting, and this page does not describe the terms under which Anthropic handles them. What we can't claim — and won't — is that no system ever processes your messages: the server and the AI engines do, by necessity. What we say is that humans at OptimizeMyLife don’t read them as a matter of course, no advertiser touches them, and we don’t use your conversations to train models.
Your location
Félix asks for your location only when a request you send needs it, such as finding a place nearby or directions from where you are. Before anything is read, the app asks: “Use your location for this request?” — Share once, or Without location. Only if you choose Share once does the app ask your phone for permission and read your position, and only while the app is open: there is no background tracking. What is sent is the latitude and longitude of your phone, its accuracy and a timestamp, with that one message. To answer, we turn the coordinates into a place name with OpenStreetMap's Nominatim, include your position and that place name in what the AI engines see (Anthropic, called directly), send coordinates to Foursquare or Google Places to find places near you and to OSRM and Google Maps to estimate routes, and look up weather with Open-Meteo. A position shared once in the mobile app is used for that request only: our code does not write it to your stored conversation, and the next message does not carry it. In Telegram, a position you share is written to our datastore for 15 minutes as soon as you share it, so Félix can keep it if you say yes; if you do not, it expires by itself. On the web chat and in Telegram there is also an optional “keep my position” setting: only if you turn it on, the position is stored under your FOX key, expires by itself after 30 days, and is erased when you turn it off. The mobile app has no such setting, but a position kept through the web or Telegram is also read by the mobile app and sent to the AI engines for later requests; to stop that, turn the option off on the web or in Telegram, or erase your data.
Voice messages
If you record a voice message for Félix, the audio travels to our server and is passed to AssemblyAI, a speech-to-text provider, for one purpose: turning it into text. We don't keep the recording — the audio is transcribed and discarded, never saved on our servers. In the app and on the web, the text comes back to you as an editable draft, and nothing reaches Félix until you choose to send it; once sent, it lives in your conversation under your FOX key like any typed message, with the same erase controls. Voice notes spoken to Félix on Telegram go through the same transcription path — audio transcribed, then discarded — and there Félix answers what you said directly. Live voice calls work differently: when you start a call, your device connects to ElevenLabs, a voice-agent platform, and your live audio streams to it so it can hear you and speak Félix's replies; the words it hears are passed to our server so Félix can answer. When a reply of Félix is spoken aloud, its text is sent to ElevenLabs to be turned into speech. Outbound phone calls are different again. Before Félix calls someone, the account holder must confirm that the person called has agreed and give a reference for that agreement; our code does not itself send the person called any notice, and what the voice agent says when the call is answered is configured on ElevenLabs' side. The number called, the contact's name, your name, the mission you gave Félix and the call audio pass through ElevenLabs and Twilio, the phone-line provider. Afterwards our code writes a summary and an excerpt of the conversation, including what the person called said, into your conversation; keeps a call record and an audit log (contact name, masked number, a fingerprint of the number, status) for 30 days; and, when ElevenLabs sends the full call audio to our server, can hold that audio for up to 15 minutes so it can be matched to your account. A short excerpt (up to 2,000 characters) of what the person called said is also kept for up to 30 minutes for that matching. Those call records sit under a key that does not contain your account identifier, so the erase tool does not reach them; they expire by themselves after 30 days. The microphone is used only when you start a call or a dictation. What AssemblyAI and ElevenLabs keep on their own systems is governed by their terms and any agreement we have with them, which this page does not describe.
Reporting an AI response
The mobile app puts a report control below Félix's AI messages. Nothing is sent until you confirm. If you do, we keep the reported response and its message identifier only so our team can review a safety or policy problem.
How we protect it
Data is encrypted in transit (HTTPS/TLS). Access to stored data is limited to what's needed to operate the service and is guarded by your FOX key. No system is perfectly secure, so we keep the footprint small — we don't store your full payment-card details, and you can erase your data on demand.
The keys stay in your hand
You can export or erase your on-device data from your Account page, and erase your server-side Félix data (conversation, memory, reminders) at any time. The page optimizemylife.ai/companion/mes-donnees lets you download a copy of what is stored under your FOX key and erase it, including a kept position if you turned that option on. It does not reach outbound-call records, which expire on their own after 30 days. The mobile app has no erase button of its own — it does not create accounts, and its Settings → Privacy screen opens the web deletion guide; Sign out only removes the key from that phone and ends its session. Write to us to ask what we hold about you or to close your account. Cancelling stops future billing.
Children
Kids and teens content is parent-mediated by design. We do not create accounts for children, do not collect children's personal data, and no AI assistant or installer feature is available to minors.
What we never do
We don't sell your data. We don't let humans at OptimizeMyLife read your conversations. We don't hand your data to advertisers or use it to train AI models. We don't run hidden tracking of your learning activity.
Questions? Write to us before you open anything wider: support@optimizemylife.ai, read our Terms of Service, or head back home.