Privacy Policy — OptimizeMyLife
AI-prepared draft — to be reviewed by legal counsel.
Effective September 26, 2026
OptimizeMyLife is operated by 9569-7173 Québec inc., doing business as OptimizeMyLife ("OptimizeMyLife", "we", "us", "our"). This Privacy Policy explains, in plain language, what personal information we collect through Félix — our AI companion and personal assistant — why we collect it, how we collect it, who processes it on our behalf, how long we keep it, how we protect it, and the rights you have over it.
We have written this to be honest and readable, but it is a binding legal document. OptimizeMyLife is an early preview: the service is still evolving, and this Policy describes what the product actually does today. We do not promise capabilities we have not built, and we do not claim that "no one can see" your data — the server and our service providers necessarily process it to make Félix work, and we say so plainly below.
This Policy applies to every way you reach Félix: the web chat, the mobile app, any desktop app or desktop beta we provide, the Félix Browser Bridge Chrome extension, and the Telegram bot and Mini App, as well as our marketing site. It works alongside our Terms of Service.
At the time of this version, the Windows desktop build is a controlled beta distributed privately to selected testers. When this Policy refers to a desktop app, that includes such beta builds; it does not mean there is a generally available signed public installer today.
By creating an account, activating a FOX key, connecting an account, or otherwise using the service, you acknowledge this Policy. Where the law requires your consent for a specific use, we ask for it separately and you may withdraw it as described in Section 10.
1. Who is responsible for your information (data controller)
The organization responsible for the personal information described here — the enterprise responsible for protecting personal information under Québec's Act respecting the protection of personal information in the private sector (Law 25), the "data controller" under the GDPR, and the "business" under California law — is:
9569-7173 Québec inc. (d/b/a OptimizeMyLife) 780 chemin du lac Brompton, Orford, Québec, J1X 6L7, Canada Email: support@optimizemylife.ai
2. Privacy Officer / Responsable de la protection des renseignements personnels (Law 25)
Under Law 25, we have designated a person in charge of the protection of personal information (our "Privacy Officer" / Responsable de la protection des renseignements personnels), who oversees our privacy practices and handles your requests and complaints. You can reach the Privacy Officer directly:
- Privacy Officer / Responsable de la protection des renseignements personnels — Maxime Jodoin, founder / fondateur
- Email: support@optimizemylife.ai
- General support: support@optimizemylife.ai (please write "Attention: Privacy Officer" in the subject line)
- Mail: Privacy Officer, OptimizeMyLife (9569-7173 Québec inc.), 780 chemin du lac Brompton, Orford, Québec, J1X 6L7, Canada
The founder, Maxime Jodoin, is the person with the highest authority in the enterprise and is the person in charge of personal information protection. The same contact handles privacy questions and complaints.
3. Scope of this Policy
This Policy applies to personal information we process through OptimizeMyLife and Félix across all surfaces (web chat, mobile app, desktop app or desktop beta, Chrome browser extension, and Telegram bot and Mini App) and through our marketing site. It does not apply to third-party services you choose to connect (such as Gmail, Google Calendar, Notion, GitHub, Slack, or your bank), which are governed by their own privacy policies, nor to any third-party website Félix may reference, nor to Telegram itself when you reach Félix through Telegram (see Section 7).
4. Your FOX key (your identity and access)
Your access and identity are tied to a FOX key rather than a traditional username and password. The FOX key is your identity and your key to the account. Anyone who holds your FOX key can reach your account, your conversations with Félix, and any accounts you have connected. Treat it like a password: keep it private and do not share it with anyone you do not trust. You are responsible for activity under your key, except to the extent applicable consumer-protection law limits that responsibility (for example, activity after you have notified us of a loss or unauthorized use). Notify us immediately at support@optimizemylife.ai if you believe your key has been lost or exposed, and we will act with reasonable diligence to help secure your account. Because the FOX key functions as a credential, we treat it as sensitive information, store it in protected form, and use it to associate your data with you and to gate access to it.
5. The information we collect, and how we collect it
We collect only the information we need to operate, secure, and improve the service. We collect it directly from you (what you type or send to Félix, what you enter at signup or checkout, and the settings you choose), automatically when you use the service (basic technical and log data), and from the accounts you choose to connect (read-only, and only those you enable — see Section 6).
Depending on how you use the service, the categories are:
- Identity and contact data — the email address you provide (waitlist or account) and any name or handle you choose. If you reach Félix through Telegram, your Telegram user ID and handle (see Section 7).
- FOX key and account data — your FOX key (stored in protected form), your plan and entitlements, and your account status.
- Conversations with Félix — the messages, prompts, files, and other content you send to Félix, Félix's replies, and the text produced when a voice message is transcribed. Voice audio is processed only to create that text and is discarded after transcription; it is not stored on our servers. The audio is sent to a speech-to-text provider, AssemblyAI, for that purpose (Section 5.4).
- Memory — the notes and context Félix keeps so he can remember what helps you across sessions and devices (his "memory card"), including reminders you set.
- Connected-account data — read-only data drawn from the accounts you choose to connect (Section 6): Gmail, Google Calendar, Notion, GitHub, Slack, optional long-tail connectors through Composio, and banking data via Plaid.
- Product and progress data — course progress, exam results, certificates, setup and installer preferences (including controlled-beta desktop setup choices), and similar in-product state (some of which is stored on your device).
- Payment and transaction data — your billing status, plan, purchase history, applied discounts (for example the founders' discount), and limited card metadata (for example, card brand, last four digits, expiry, and a processor token). We do not collect or store full payment-card numbers — these are handled by our payment processors (Section 8, Section 13).
- Technical and log data — device and browser information, IP address, timestamps, error and diagnostic logs, aggregate, non-identifying analytics about page and feature use, and a mobile push-notification token when you choose notifications.
- Communications with us — support requests, correspondence, and an AI response plus its message identifier when you deliberately tap “Report this response.” A profile photo selected in the mobile app stays on that device and is not uploaded to us.
- Voice recognition data (who's speaking on a call) — a voiceprint computed from your speech during a phone call with Félix, used to automatically recognize who is speaking. See Section 5.2.
- Precise location (only when you choose to share it) — the latitude and longitude of your device, with its accuracy and a timestamp, sent to us when you tap Share once in the mobile app for a request that needs it (or turn on the location option on the web or in Telegram). See Section 5.3.
We do not intentionally collect special categories of sensitive information beyond what you voluntarily share with Félix or expose through a connector you choose to enable; where such information is unavoidably processed (for example, financial data via Plaid), we handle it with heightened protection.
5.1 Félix Browser Bridge for Chrome
The Chrome extension requires access to ordinary http:// and https:// pages because it is a general browser assistant that must work on the sites you choose. On those pages it can read the URL and title, selected and visible text, non-sensitive field labels and control metadata, and scroll position. While an ordinary web page is open, the extension keeps capped in-page ring buffers of recent visible console messages and request metadata (URL, method, status and timing — never request or response bodies). This buffering begins while the page is open; the extension displays the buffered diagnostics only after you explicitly choose Console & network, and it never sends them in the background. The Compare tabs control reads the same context from open web tabs only after you press it. Chrome internal pages remain inaccessible.
A visible-tab screenshot is captured only after you press Screenshot or give that voice command. It is displayed temporarily and is not stored or transmitted by a background service. The optional session navigation path is off by default, stays in chrome.storage.session, is capped, and clears when the browser session ends. Captured page context, saved tasks and task values, per-site consent, playbook domains, the local activity and safety log, panic state, and prepared-purchase amounts and budget stay in chrome.storage.local. Extension settings use chrome.storage.sync, which means Chrome may sync those settings through the browser account 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 that audio under its own privacy terms.
You can ask about a page by choosing Ask Félix through the context menu (right-click) or the floating button. When you choose Ask Félix, the extension opens https://optimizemylife.ai/companion and includes the current page URL, page title, selected approval mode and, when enabled, a short domain-only breadcrumb in that navigation request. For this ordinary Ask Félix flow, the full captured page text stays in extension-local storage; it is not sent to the web companion.
Since extension version 0.4.3, the separate Guide feature can send a bounded, filtered DOM observation, your stated goal, and session metadata to our first-party https://optimizemylife.ai/api/felix/guide/step endpoint to generate one suggested step. Guide requires a separate, revocable page-read consent for that site and an explicit start by you; it does not observe pages in the background. Sensitive controls and detected personal identifiers are masked or omitted before the request. Guide only highlights a visible control; it does not click or fill it, and you can stop it or revoke consent at any time. The extension makes no other hidden background network request and contains no advertising, third-party analytics or remote executable code.
The optional Félix Desktop bridge, added in extension version 0.4.0, is a link between this extension and 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 (their label, their kind, and whether they are enabled). 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 extension 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. This travels over Chrome native messaging from the extension 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 (POST to our /api/felix/convo route) to answer your question — only on that same click of the camera; neither the look nor the screenshot is stored, only used to answer that one question. Panic mode refuses it like every 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.
Extension version 0.4.1 adds the one message this extension sends over that bridge without being asked. While Félix Desktop is connected and the same Settings 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 — and nothing else: no controls, no page text, no field value, no image. For a tab that is not an ordinary http or https page (a chrome:// page, the new-tab page), it announces two empty strings, so no Chrome internal title crosses. It exists so that Félix Desktop stops showing you what it saw on a page you have already left. It never triggers a look, it is sent once per actual change rather than once per browser event, it travels over the same local native-messaging channel to the program on your own device — never over the network, never to a server of ours, never to a third party — and the extension keeps no record of it. Turning the Settings switch off, disconnecting Félix Desktop, or using panic mode stops it.
The optional Login help feature 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. The extension 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 a third-party manager directly. Its bounded, device-local status check can report only that the login form disappeared or remained visible; it does not claim that authentication succeeded.
Because you choose which page or screenshot to capture, that 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 they are handled only on-device. Under the approval mode you select, the extension can fill ordinary fields, choose options, scroll, copy selected text and click visible controls. Independent of that mode, it refuses passwords, payment-card fields, one-time codes, API keys, tokens, government identifiers and other detected secret fields. It never clicks the final purchase control. These browser safety boundaries cannot be disabled by choosing a more autonomous mode.
The use of information received from Chrome APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
5.2 Voice recognition on calls — context, not security
When you or someone else talks to Félix over the phone, we use voice-recognition (speaker-identification) technology to automatically recognize who is speaking, so Félix can respond with the right context for that person instead of treating everyone who calls the same way. This is a personalization feature, not a security or authentication feature. It is entirely separate from your FOX key (Section 4) and from any device-level Face ID / Touch ID confirmation the app may ask for before a sensitive action — voice recognition never unlocks your account, approves a payment, or grants access to anything, and no one can use it to authenticate as you.
What we compute and keep. During a call, we compute a voiceprint — a mathematical representation of voice characteristics (a numeric embedding) — from the audio. We do not keep the underlying call audio for this purpose once the voiceprint has been computed; only the voiceprint and the name associated with it are kept.
How a voice gets a name. The first time we hear a voice we do not already recognize on your account, we listen for a name spoken in that same conversation (for example, when Félix or the other party says who they are) and use it to label the new voice profile automatically. You can also correct or rename a voice profile, or remove one entirely, from your Account settings.
Scoped to your account, never shared. Voice profiles are stored within your own OptimizeMyLife account only. A voiceprint is never compared against, matched with, or shared with any other customer's account — Félix does not build a cross-account or global voice database, and recognizing a voice on your account tells us nothing about whether that same person has called anyone else's Félix.
Legal basis and your rights. A voiceprint is biometric information. In Québec, this means it is subject to Law 25's specific rules for biometric characteristics and measurements used to identify a person, including our obligation to disclose the use and keep a register of it. We rely on your consent, given when the feature is enabled on your account, and you may withdraw it at any time by disabling voice recognition or erasing your Félix data (Section 14), which deletes the associated voice profiles. The rights described in Section 16 — including access, rectification, and erasure — apply to your voice profiles the same as to any other personal information.
5.3 Precise location
When it is collected. The mobile app asks for your location only when a request you send needs it (for example, finding a place nearby or getting directions from where you are). Before anything is read, the app shows a prompt — "Use your location for this request?" — with the choices Share once and Without location. Only if you choose Share once does the app ask your phone's operating system for permission and then read your position. Your phone's permission on its own is not what sends it. The app asks for location while it is in use only: it does not track you in the background, and the app is configured without background location. You can also decline and type a city or neighborhood instead.
What is sent. The latitude and longitude read from your phone's location service (at the "balanced" accuracy level), the accuracy of that reading, and its timestamp, sent to our server together with that one message. A reading older than 60 seconds is not used.
What we do with it. We use it to answer that request: (a) we convert the coordinates to a place name using OpenStreetMap's Nominatim service; (b) we include your position and that place name in the context sent to the AI engines that write Félix's reply (Section 12); (c) we send coordinates to a places-search provider (Foursquare and/or Google Places, depending on which is enabled) to look for places near you, and to routing providers (OSRM and Google Maps) to estimate routes; and (d) we look up weather for the place name with Open-Meteo. The providers are listed in Section 13.
How long we keep it. A position shared with Share once in the mobile app is used for that request only. Our code does not write it to your stored conversation or to any other stored record for the mobile app, and the next message does not carry it. The reply Félix writes may itself mention a place name.
In Telegram, a shared position is kept for 15 minutes. As soon as you share a position in Telegram, our code writes its coordinates to our datastore, before you answer anything, so that Félix can keep it if you then say yes; if you do not, it expires by itself after 15 minutes.
Optional "keep my position". On the web chat and in Telegram, there is a setting that lets you ask Félix to keep your position so he stops asking. Only if you turn it on, that position is stored under your FOX key; it expires on its own 30 days after it was last stored, Félix treats it as out of date after 3 hours, and you can turn it off at any time, which erases it. The mobile app has no setting to turn it on or off. However, a position kept through the web or Telegram is also read by the mobile app's conversation route and sent to the AI engines for later requests, and the app can still end a reply by asking whether Félix may keep your position, which the app cannot answer with a setting; to stop it, turn the option off on the web or in Telegram, or erase your data (Section 16).
Erasing and exporting. A kept position is part of the data covered by the export and erase tools described in Sections 14 and 16.
5.4 Voice features and the providers behind them
Félix can work with your voice in three ways. In each, a third-party provider processes the audio or the text as described below.
- Voice message or dictation (mobile app, web, Telegram). The audio is sent to our server and passed to AssemblyAI, a speech-to-text provider, to produce text with automatic language detection. Our server does not store the audio. The text comes back to you and, once you send it, is part of your conversation like any typed message. What AssemblyAI does with the audio on its side is governed by its own terms and by our contract with it.
- Live voice call with Félix (mobile app and web). When you start a call, your device connects to ElevenLabs, a voice-agent platform, and your live audio streams to it so that it can hear you and speak Félix's replies. Our server issues the short-lived token that lets your device start that session. The words ElevenLabs hears are passed to our server so that Félix can compose the reply.
- Spoken replies. When Félix's reply is spoken aloud (for example a voice reply on Telegram), the text of that reply is sent to ElevenLabs to be turned into speech.
- Outbound phone calls. When you ask Félix to place a phone call, the account holder must first confirm that the person to be called has agreed and give a reference for that agreement; our code does not itself send the person being called any notice, and the call request it sends to ElevenLabs contains no opening statement; what the voice agent says when the call is answered is configured on ElevenLabs' side, which this Policy does not describe. The call is made through ElevenLabs' voice agent and a telephone line provided by Twilio, so the number being called, the contact's name, your name, the mission you gave Félix, and the call audio pass through those providers. Our code then writes the following on our side: (a) a summary and an excerpt of the conversation — including what the person called said — as a message in your conversation, kept and erasable like any message; (b) a call record (contact name, masked number, a fingerprint of the number, status) and an audit-log entry for each event, kept for 30 days; (c) the call request itself, with the full number, name and mission, until the call is placed and at most 10 minutes; and (d) when ElevenLabs sends the call's full audio to our server, that audio is held in our datastore for up to 15 minutes if it arrives before the call's transcript, so that it can be matched to your account for the voice recognition described in Section 5.2; and (e) a short excerpt (up to 2,000 characters) of what the person called said, kept for up to 30 minutes to match the call to your account.
The microphone is used only when you start a call or dictation. The providers above are listed in Section 13.
5.5 Music search handoff
If you choose to open a music search in Spotify, YouTube, YouTube Music, or Apple Music, Félix sends only your minimized music search terms in a search link to the service you selected. Your conversation with Félix is not included. The selected service may open its app on your device and may ask you to take an action there. The search terms you choose are sent to that service and are handled under its own privacy terms. Félix does not control playback or read your music library in this handoff.
If you ask Félix to analyze a public YouTube video, our server requests the video's public page and thumbnail from YouTube (i.ytimg.com) using its video ID. It does not send your conversation or account credentials in those requests.
6. Connected accounts (read-only connectors)
Félix can connect to certain third-party services only when you choose to connect them, and this access is read-only. You control which connectors, if any, you enable, and you can disconnect them at any time. Enabling a connector is your consent to the read-only access it describes. Connectors include:
- Gmail (Google APIs) — read-only access to the email content and metadata you authorize, to help Félix understand and act on your inbox context;
- Google Calendar (Google APIs) — read-only access to the events and scheduling data you authorize, for example to reason about your day or estimate travel time;
- Notion — read-only access to the pages and content you authorize;
- GitHub — read-only access to the repositories and activity you authorize;
- Slack — read-only access to the workspaces, channels, and messages you authorize;
- Optional long-tail connectors through Composio — read-only access to the specific third-party service you authorize, for day-to-day, non-sensitive tools (for example Figma, Zoom, Trello, Asana). Composio is not used for Gmail, Google Calendar, bank data, or the other sensitive core connectors that OptimizeMyLife operates directly — those always connect straight to the provider, never through Composio. One named, bounded exception: read-only lookups on HubSpot, Pipedrive, Salesforce, Attio, PayPal, and Clover may also run through Composio, filtered in our code to zero-argument, read-only queries — never a tool that moves money, exports a full customer list, or takes any action;
- Banking data via Plaid — read-only access to balances and transactions (see Section 6.2);
- Weather via Open-Meteo — general weather data based on a location you provide; no account or key is required; and
- Google Maps — travel-time estimates based on locations relevant to your request.
Actions that commit your money or your time require your explicit approval each time. Félix does not send email, post messages, move money, make payments, transfers, purchases, or bookings, or change your connected accounts without an explicit "OK" from you. Our connectors are read-only.
6.1 Google user data — Limited Use
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically:
- We access your Gmail and Google Calendar data only to provide and improve the user-facing features you have asked for and enabled in OptimizeMyLife;
- We do not transfer or sell this data for advertising, and we do not use it for advertising purposes;
- We do not use this data to train, fine-tune, or develop generalized AI/ML models;
- Humans do not read this data, except with your explicit consent (for example, to troubleshoot an issue you report), where necessary for security or to comply with applicable law, or in aggregated/anonymized form for internal operations consistent with Google's policy; and
- Access is read-only and limited to the scopes you approve during Google sign-in.
You can review and revoke OptimizeMyLife's access to your Google account at any time in your Google Account permissions (myaccount.google.com/permissions).
6.2 Banking data via Plaid
If you connect a bank, Plaid handles your bank sign-in; OptimizeMyLife never receives or stores your bank credentials. Félix obtains read-only access to balances and transactions — never the ability to make 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. Our use of Plaid and of your financial data is subject to Plaid's end-user privacy practices and terms, in addition to this Policy. During the early preview, banking connections may move from Plaid's sandbox to production; we process real financial data only through the production environment and with your consent.
7. Using Félix through Telegram
If you reach Félix through the Telegram bot or Mini App, your messages travel through Telegram's platform before reaching us, and Telegram processes them under its own privacy policy and terms, which we do not control. Through this surface we receive the information Telegram makes available to a bot you interact with — typically your Telegram user ID, username/handle, and the content of the messages you send to Félix — which we then handle as described in this Policy (including linking it to your FOX key and account). Do not send anything through Telegram that you are not comfortable also passing through Telegram's systems.
7.1 Optional WhatsApp channel — inactive pending activation and legal review
The WhatsApp connection card is visible by default. The channel remains unconnected until a Félix business number is actually configured and the applicable platform and privacy requirements have been reviewed. A visible card does not mean a number exists or that messages are being delivered.
If activated, WhatsApp is solely a channel for messages you send directly to Félix and Félix's replies. Félix does not read your WhatsApp conversations with other people. Linking requires your explicit agreement from the app and a single-use code sent to Félix's business number. We receive your sending phone number, message identifier, timestamp, and the text addressed to Félix. These messages use the same conversation and memory path, permissions, retention, and account-deletion process as messages in the app. STOP or ARRET stops replies; a new explicit account link is required to resume. Removing the link stops future access through that number; it does not by itself erase conversation history already held in your Félix account. A minimal pseudonymous opt-out marker remains after unlinking so we can continue to respect STOP; it contains neither your message text nor your phone number in readable form. A content-free account revocation marker is retained for up to 90 days to prevent delayed requests from recreating a removed link. Account deletion removes the associated link, outstanding codes and encrypted session, as well as opt-out markers that can be associated with that account.
Messages on this channel necessarily transit through WhatsApp/Meta, subject to its own terms and privacy policy. If Kapso is selected as the intermediary, those same messages and delivery metadata also transit through Kapso. Kapso is not currently active for this channel. Its privacy policy, data-processing addendum, and subprocessor list must be reviewed before activation, including storage outside Québec, retention and backup deletion, and the free plan's data-use provisions. We do not represent that these providers store the channel data only in Canada or erase their copies immediately when you delete your Félix account. Before any activation using Kapso, the responsible person must complete the applicable privacy assessment and contractual review and verify that the selected data-use controls meet our commitments.
8. Payment information
Subscriptions (recurring plans) and one-time purchases (powers and lifetime packs) are processed by our payment processors, Stripe (primary) and LemonSqueezy (redundancy). They collect and process your card or payment details directly, under their own privacy policies and PCI-DSS obligations. We do not receive or store your full payment-card number — only limited metadata (such as card brand, last four digits, expiry, and a processor token) and records such as your plan, subscription and billing status, purchase history, and applied discounts, so we can manage billing, renewals, refunds, fraud prevention, receipts, and support. Amounts are billed in the currency shown at checkout (USD unless otherwise stated). Consistent with Québec's Consumer Protection Act, we do not impose a "credit-card fee" or payment surcharge on consumers. Billing, renewal, cancellation, and refund terms are set out in our Terms of Service and our Refund & Billing Policy.
9. Why we process your information, and our legal bases
We process personal information for the purposes below. Where a legal basis is required (for example, under the GDPR), the applicable basis is your consent, the performance of our contract with you, our legitimate interests, or compliance with a legal obligation.
| Purpose | Examples | Legal basis (where required) |
|---|---|---|
| Provide the service | Let Félix understand you, remember useful context, generate replies, run connectors you enable | Performance of a contract; your consent for optional features and connectors |
| Accounts and access | Activate and secure your FOX key, manage plans and entitlements | Performance of a contract |
| Payments | Process subscriptions, one-time purchases, founder discounts, refunds | Performance of a contract; compliance with legal (tax/accounting) obligations |
| Communications you request | Waitlist updates, service notices, support replies | Your consent; performance of a contract; legitimate interests |
| Marketing (with consent) | Our own product news and offers, sent per CASL/CAN-SPAM (Section 10.1) | Your consent (express or, where the law allows, implied) |
| Security and integrity | Detect and prevent abuse, fraud, and outages; protect users and systems | Legitimate interests; compliance with legal obligations |
| Improve the service | Fix bugs, measure aggregate usage, prioritize features | Legitimate interests (using aggregated/de-identified data where feasible) |
| Legal compliance | Respond to lawful requests, enforce our Terms, exercise or defend legal claims | Compliance with legal obligations; legitimate interests |
We rely on legitimate interests only where those interests are not overridden by your rights and freedoms, and we never use legitimate interests as a basis to sell your data or to train AI models on your private content.
10. Consent and how to withdraw it
For core functions (running the service, securing your account, and processing payments), processing is necessary to provide what you asked for. For optional functions — connecting an account, receiving certain communications, or any use that requires consent under applicable law — we ask for your consent, which must be clear and given for specific purposes.
You may withdraw consent at any time, without affecting the lawfulness of processing carried out before withdrawal, by:
- disconnecting a connector in your account settings;
- unsubscribing from communications;
- erasing your Félix data (Section 14); or
- writing to our Privacy Officer.
Some information must be kept to run your account, meet legal obligations, or complete a transaction you started. Withdrawing consent for a feature may mean that feature can no longer function; if so, we will tell you.
10.1 Consent records
When you activate a FOX key or connect a third-party account, we ask for an explicit acceptance of the current Privacy Policy and Terms. To prove that consent if there is a dispute, security incident, or Law 25 compliance review, we keep consent records that include your FOX key identifier, the timestamp in UTC, IP address, user agent (browser/device string), coarse country/city from the IP when available, and the Privacy Policy and Terms versions accepted. We do not collect a civic/street address for this purpose. These consent records are kept for 7 years for legal-proof and compliance purposes, then deleted or anonymized unless a legal obligation requires a different period.
10.2 Marketing communications (CASL / CAN-SPAM)
When we send you our own promotional or marketing emails (for example, product news or special offers), we comply with Canada's Anti-Spam Legislation (CASL) and comparable laws such as the U.S. CAN-SPAM Act:
- we send marketing messages only where we have your consent — express consent, or implied consent where the law allows it (for example, an existing business relationship such as a recent purchase or an active account) — given separately from your acceptance of this Policy;
- every marketing message identifies us (our name and a valid contact address) and includes a working unsubscribe mechanism; and
- we honour unsubscribe requests promptly, within the time the law requires.
Unsubscribing from marketing does not stop essential service or transactional messages (for example, security notices, billing receipts, or important changes to the service), which we may still need to send you to operate your account.
11. What we never do
- We do not sell your personal information, and we do not rent, trade, or share it with data brokers.
- We do not use your conversations, memory, or connected-account data to train, fine-tune, or develop AI/ML models. What the AI engines that generate Félix's replies do with the requests they receive is described in Section 12, and we do not claim more than that section says. Where a connector runs through our integration partner Composio instead of connecting directly, our processor contract requires Composio to process every connector service it routes for OptimizeMyLife only to provide that connector service to us, and not to sell that data, use it for advertising, or use it to develop, train, or improve AI/ML models. For Google user data specifically, Composio's published privacy terms also confirm the same no-sale / no-AI-training limits as an independent confirmation (Section 6).
- We do not let humans at OptimizeMyLife read your conversations as a matter of course. Narrow exceptions apply only with your consent (for example, to troubleshoot a problem you report), where strictly necessary for security, or to comply with the law — and in aggregated/de-identified form for internal operations.
- We do not hand your data to advertisers or use it to serve you ads.
- We do not take actions that commit your money or time without your explicit approval, and our connectors are read-only.
- We do not claim your data is invisible or "end-to-end encrypted" — the server and our service providers process it by necessity, and we describe that honestly here.
12. AI engines and your messages
Félix generates replies using third-party AI engines. Your messages, the photos you attach, and the context and memory needed to answer you are sent over HTTPS to an AI engine, and the reply comes back. In our current configuration, most of these requests go through OpenRouter, a routing service, to an OpenAI model; some requests, including some photos, go to Anthropic's Claude models, through OpenRouter or by calling Anthropic directly at api.anthropic.com. OpenRouter is used only while an explicit routing switch is turned on in our configuration (in the code that switch is off unless it is set, and the mere presence of an OpenRouter key does not turn it on); when it is off, these requests go to Anthropic directly. This is the same list the mobile app shows before your first conversation. For a request that needs your location, the position you shared and the place name derived from it are part of that context (Section 5.3). The same engines are also used to condense your conversation into Félix's memory. The requests that go through OpenRouter to write Félix's replies and memory carry OpenRouter's option that refuses routes which log or train on inputs; the image-generation request (the Picture It power, which sends your image description to OpenRouter) does not carry it. Our direct calls to Anthropic do not carry an equivalent per-request setting, and this Policy does not describe the terms under which OpenAI or Anthropic handle those requests. What we cannot claim — and will not — is that no system ever processes your messages: the server and the AI engines do, by necessity. Humans at OptimizeMyLife do not read them as a matter of course, and no advertiser touches them.
Félix can be wrong. Responses are generated by AI and may be inaccurate, incomplete, or out of date. Nothing Félix produces is professional medical, legal, financial, tax, accounting, or therapeutic advice. You are responsible for how you act on anything Félix tells you; for decisions that matter, consult a qualified professional.
The mobile app places a Report this response control below AI messages. When you confirm a report, we store the reported response and its message identifier so our team can review safety or policy problems. We do not receive an unsent report.
13. Service providers and third parties who process your data
We share personal information with the service providers we need to run the service. The terms differ from one provider to the next: some are commercial services we use through an account with them, and some (for example OpenStreetMap's Nominatim, the public OSRM router, Open-Meteo, and the public market-price sources) are public services used without an account and without any contract between us and them. Where a service is public, we do not say that a contract limits what it does with a request. The table names the providers our code calls to run the features described in this Policy; it is not presented as a complete inventory. Our principal processors ("subcontractors" under Law 25) include:
| Provider | What they do | What they handle |
|---|---|---|
| Anthropic (Claude models, through OpenRouter or called directly) | Generate some of Félix's replies and read some photos; generate all replies and condense conversations into memory when the routing switch is off | The messages, context, memory, and — for a request that needs it — your shared position and its place name, sent over HTTPS (Section 12) |
| OpenRouter (while the routing switch is on, which is our current configuration) | Route Félix's reply and memory requests to the AI model that answers them | The same content as above, including photos you attach; the text-reply and memory requests carry OpenRouter's option that refuses routes which log or train on inputs; the image-generation request does not (Section 12) |
| OpenAI (models reached through OpenRouter) | Write most of Félix's replies in our current configuration | The same content OpenRouter receives, as passed on by OpenRouter (Section 12) |
| Vercel AI Gateway (Jev evaluation model) | A classification service, used only when its gateway key is configured | A copy of your chat message text (to propose a label for the message) or, for an invoice, the merchant name and key line items (to propose an expense category) |
| Stripe | Primary payment processing | Your payment and billing details |
| LemonSqueezy | Redundant payment processing | Your payment and billing details |
| Plaid | Bank connection (when you connect a bank) | Your bank sign-in and read-only balances/transactions (we never receive your banking credentials) |
| Google APIs | Gmail and Calendar access you enable, Google Maps travel-time and route estimates, and Google Places nearby-place searches | Read-only Gmail and Calendar data (subject to Google Limited Use — Section 6.1); location inputs for travel time, routes and place searches (Section 5.3) |
| Notion, GitHub, Slack | Connectors you enable | Read-only content you authorize |
| Spotify | Read music data to build your music taste profile, only if you connect Spotify and consent to the requested reads with the required permissions | Your OAuth access token in authenticated GET requests for your top artists, recently played tracks and playlists (up to 50 items per request; top artists use the medium-term range) |
| Composio | Connector gateway for day-to-day, non-sensitive tools (e.g. Figma, Zoom, Trello), plus one named, bounded exception for read-only CRM/payment lookups (HubSpot, Pipedrive, Salesforce, Attio, PayPal, Clover) | Read-only connector tokens and data for the specific service you authorize; not used for Gmail, Google Calendar, bank data, or the other sensitive core connectors we operate directly — those always connect straight to the provider. Our processor contract with Composio covers every connector service Composio routes for OptimizeMyLife and limits that processing to providing the connector service to us: no sale, no advertising use, and no use to develop, train, or improve AI/ML models. For Google user data specifically, Composio's own published privacy terms also confirm the same no-sale / no-AI-training limits independently. Each connector goes live only after its own Privacy/Consent sub-processor review; not every listed connector is active for every account (Section 6). |
| Open-Meteo | Weather data | A location you provide (no account, no key) |
| AssemblyAI | Speech-to-text for voice messages and dictation | The audio of the voice message you record (Section 5.4) |
| ElevenLabs | Voice agent for live calls, text-to-speech for spoken replies, and the voice agent behind outbound phone calls | Your live audio during a call; the text of Félix's spoken replies; for an outbound call, the number called, the contact's name, your name and the mission you gave Félix (Section 5.4) |
| Twilio | Telephone line for the outbound phone calls Félix places when you ask | The number called and the call audio (Section 5.4) |
| OpenStreetMap (Nominatim) | Converts coordinates to a place name, and place names to coordinates | Your shared coordinates, or a place name in your request (Section 5.3) |
| OSRM (Project OSRM public router) | Route and travel-time estimates | Start and destination coordinates (Section 5.3) |
| Foursquare and/or Google Places | Search for places near you or along a route (whichever is enabled) | Your shared coordinates or a place name, and the kind of place you asked for (Section 5.3) |
| Telegram | Delivery of the Telegram bot / Mini App surface | Your Telegram messages, user ID, and handle (Section 7) |
| Vercel | Hosting and application delivery | Technical operation and logs |
| Vercel Web Analytics | Aggregate page-view and visit measurement for our website only (not the mobile app), cookie-free: it sets no cookie and does not follow you across sites | The page visited, referrer, country, browser and device type, and an anonymized, daily-rotating visit identifier; never your account or your messages (Section 22) |
| Expo push service (and your phone platform's own notification service) | Deliver push notifications to the mobile app | Your push token, and the title and text of each notification (Section 5, item 8) |
| Sentry | Error monitoring for the website and servers, active only when its address is configured | Error reports; our code removes request bodies, headers, cookies, e-mail addresses, tokens and FOX keys before sending |
| Resend | Send the emails you asked for or that your account triggers | Your email address and the content of those emails |
| Jina Reader and, when its key is configured, Firecrawl | Read a web page that you ask Félix to open (for example a package-tracking page) | The page address, which can include a tracking number; the page is then fetched from its own site by that service |
| Package carriers (UPS, FedEx, Canada Post, USPS, Purolator) | Package tracking, when you ask Félix where a parcel is | The tracking number, placed in the address of the carrier's public tracking page |
| Yahoo Finance, Coinbase, CoinGecko, Nasdaq, CNBC | Public market prices | The ticker symbol or coin you asked about |
| PostHog (website analytics require a project key; native app analytics additionally require your explicit consent) | Coarse product analytics | A few coarse event names and a random identifier kept in browser storage on the website or secure device storage in the native app; no message content, account, email or FOX key |
| Services you connect — for example Microsoft Outlook (Microsoft Graph), Apple iCloud calendar and contacts, IMAP mailbox providers, Google Drive and Sheets, Google Business Profile, Todoist, Square, Lightspeed, QuickBooks, Toast, Clover, PayPal, Wise, Agendrix, Nethris, Vercel, and phone systems such as Telzio, 3CX, Aircall and Phone.com | The connectors and business-system integrations you set up | In the code, these services are contacted with a credential or token that the account holder provides to connect that service, or through a webhook the account holder configures. If you paste your own OpenAI, Anthropic or xAI key, it is sent once to that provider to check it and then stored encrypted |
| Upstash (key-value datastore and associated storage) | Store your account data, conversations, Félix's memory, and encrypted connection tokens | The data described in Section 5, keyed to your FOX key |
We may also disclose personal information (a) to comply with applicable law, legal process, or a lawful request from a public authority; (b) to enforce our Terms or protect the rights, property, or safety of OptimizeMyLife, our users, or others; or (c) in connection with a merger, acquisition, reorganization, financing, or sale of all or part of our assets, in which case the successor or acquirer must be bound by confidentiality and privacy commitments at least as protective as those in this Policy, we will notify you where required by law, and data from accounts you have connected (for example, your Google data) will be transferred only in accordance with your consent and with the applicable provider policies (including the Google API Services User Data Policy — Section 6.1). This mirrors the assignment terms in our Terms of Service and our Connected Accounts & Data Consent notice.
Before entrusting personal information to a service provider outside Québec, we assess the privacy protection it will receive, as required by Law 25 (see Section 13.1).
13.1 Where your data is stored and international transfers
Some product data (such as course progress, exam results, certificates, and setup preferences) is stored in your browser or on your device. Your Félix conversations, memory, and encrypted connection tokens are stored on our servers under your FOX key so Félix can remember you across devices.
OptimizeMyLife is based in Québec, Canada, and our users may be located anywhere in the world. Our service providers (Section 13) may store or process personal information outside Québec and outside Canada, including in the United States and other countries, whose data-protection laws may differ from those of Québec, Canada, or your own country. Before communicating personal information outside Québec, we conduct the privacy assessment required by Law 25, and we rely on contractual and technical safeguards (including the terms imposed on our processors, and, for transfers subject to the GDPR, appropriate transfer mechanisms such as the European Commission's Standard Contractual Clauses) to provide an adequate level of protection. By using the service, you understand that your information may be transferred to and processed in these locations.
14. How long we keep your data, and your right to erase it
We keep personal information only as long as needed for the purposes described in this Policy, or as required by law, after which we destroy or anonymize it. The retention periods below are our current targets and are to be confirmed as our operations mature:
- Conversations and memory — kept while your account is active so Félix can help you. You can erase all of it — conversation, memory card, and reminders — at any time from the product, and it is deleted from active systems shortly after. When you close your account, we delete your conversations and memory from active systems within 30–90 days (exact period to be confirmed), except for the minimum we must keep by law.
- Precise location — a position you share once in the mobile app is used for that request only and is not written to your stored conversation. A position shared in Telegram is held for 15 minutes (Section 5.3). If you turn on the optional "keep my position" setting on the web chat or in Telegram, the stored position expires on its own after 30 days and is erased when you turn the setting off.
- Voice audio — for voice messages and dictation, not stored by our server (the audio is processed in memory and passed to AssemblyAI). For outbound phone calls, the call's audio can be held for up to 15 minutes as described in Section 5.4. Text produced from voice is kept in your conversation like any message you send. The retention practices of AssemblyAI and ElevenLabs on their own systems are governed by their terms and any agreement we have with them, which this Policy does not describe.
- Outbound-call records — the call request is kept until the call is placed and at most 10 minutes; the call record and audit log for 30 days; the summary and excerpt in your conversation until you erase them (Section 5.4). The call records are stored under a key that does not contain your account identifier, so the erase tool of Section 16 does not reach them; they expire on their own after 30 days.
- Push-notification registrations — kept up to 180 days, refreshed each time the app confirms its registration.
- Connected-account tokens and connected-account data — kept only while the connection is active and deleted when you disconnect (or when you revoke access at the provider); a Plaid bank token also expires after 180 days of non-use.
- On-device data — remains on your device until you clear it or use the in-product export/erase controls on your Account page.
- Account and billing records — kept for as long as your account exists and afterward for the period required by tax, accounting, and legal-defence obligations (generally up to 6–7 years for financial records; to be confirmed).
- Technical and log data — kept for approximately 12 months (to be confirmed) for security and troubleshooting, then deleted or de-identified.
- AI response reports — kept only as long as needed to investigate safety and policy issues, targeted at no more than 12 months, then deleted or de-identified unless law requires longer retention.
When you delete your account or erase your data, we remove it from active systems within a reasonable period and instruct our processors to do the same. Residual copies may persist in secure backups for a limited time before being overwritten, and we may retain the minimum information necessary to comply with law, resolve disputes, prevent fraud, or enforce our agreements.
15. How we protect your data
We use technical and organizational measures appropriate to the sensitivity of the information, including:
- encryption in transit (HTTPS/TLS);
- storage of your FOX key and connection tokens in protected/encrypted form (sensitive tokens, such as bank connection tokens, are encrypted at rest);
- access controls limiting stored data to what is needed to operate the service and gated by your FOX key;
- minimizing what we hold (for example, we do not store full payment-card numbers); and
- monitoring and logging for security purposes.
No method of transmission or storage is perfectly secure, and we cannot and do not guarantee absolute security — this is especially true during an early preview. You play an essential role in protecting your data by keeping your FOX key private. If something goes wrong, we respond as described in Section 17.
16. Your rights
Subject to applicable law and reasonable verification of your identity, you have the following rights. Québec's Law 25 and Canada's PIPEDA apply to all users; residents of the EEA/UK (GDPR) and California (CCPA/CPRA) have the additional rights described in Section 21.
- Access — obtain confirmation that we hold personal information about you and a copy of it.
- Rectification — have inaccurate or incomplete information corrected.
- Portability — where applicable under Law 25 and the GDPR, receive the computerized personal information you provided in a structured, commonly used technological format, or have it transferred to another organization where technically feasible.
- Withdrawal of consent — withdraw consent for optional processing (Section 10).
- Erasure / deletion — erase your Félix data at any time, and request deletion of your personal information subject to legal-retention limits (Section 14).
- De-indexation / cessation of dissemination — under Law 25, request that we stop disseminating your personal information or de-index a hyperlink giving access to it where the conditions of the law are met.
- Object / restrict — object to or request restriction of certain processing where the law provides.
- Automated decisions — be informed of, and request review of, decisions based exclusively on automated processing (Section 18).
- Non-discrimination — we will not discriminate against you for exercising your privacy rights.
- Complain — lodge a complaint with a regulator (Section 19).
Do it yourself, without writing to us. The page optimizemylife.ai/companion/mes-donnees lets you download a copy of the data stored under your FOX key and erase it (you type your FOX key, then confirm the erase). That erase covers Félix's conversations, memory, reminders, preferences, and saved access to linked services, including a kept position if you turned that option on. It does not cancel your subscription, and it does not erase billing records kept for legal and tax reasons, the operational records listed on that page, or the outbound-call records described in Section 14 (they expire on their own after 30 days). The mobile app has no erase or account-deletion button of its own: it does not create accounts (your FOX key is issued outside the app), and its Settings → Privacy screen opens the web deletion guide at optimizemylife.ai/privacy/delete. In the app, Sign out removes the key from that phone, ends its session on our server and removes the push-notification registrations stored for your key; it does not erase your conversation or memory.
How to exercise your rights. Write to our Privacy Officer at support@optimizemylife.ai (or support@optimizemylife.ai, subject: "Attention: Privacy Officer") or by mail at the address in Section 2. We may need to verify your identity before acting. We will respond within the timeframe required by law (generally 30 days under Law 25 and PIPEDA, and within the timeframes set by the GDPR and CCPA/CPRA where they apply). Access to your own personal information is provided free of charge; where a request is manifestly unfounded, excessive, or repetitive, we may charge a reasonable fee (which we will tell you about first) or decline, and we will explain why.
17. Privacy incidents (Law 25)
We maintain procedures to detect and respond to a confidentiality incident (as defined by Law 25 — for example, unauthorized access to, use of, disclosure of, or loss of personal information). If an incident occurs, we will:
- Take reasonable steps to reduce the risk of harm and to prevent recurrence.
- Assess whether the incident presents a risk of serious injury to affected individuals, considering the sensitivity of the information and the likely consequences of its use.
- Where such a risk exists, notify the Commission d'accès à l'information du Québec (CAI) and the affected individuals with reasonable diligence, and notify any other regulator where the law requires (for example, under PIPEDA's breach-of-security-safeguards obligations or the GDPR's breach-notification rules).
- Keep a register of confidentiality incidents as required by Law 25.
We will not promise that a breach can never happen — no service can. We commit to responding honestly and quickly, and to telling you when you need to know.
18. Automated decision-making and profiling
Félix uses AI to generate responses and helpful context, but during the early preview we do not make decisions that produce legal or similarly significant effects about you based solely on automated processing without a way to involve a human, and we do not use profiling or identification/location technologies to track you for advertising. Any such functions, if introduced, would be off by default. If this changes, we will inform you as required by Law 25 and the GDPR, tell you about the personal information used and the principal factors and parameters involved, give you the means to activate or deactivate the function, and give you the ability to submit observations and request a review by a person.
19. Complaints and regulators
If you are not satisfied with how we handle your personal information, please contact our Privacy Officer first so we can try to resolve it. You may also contact a regulator:
- Québec — Commission d'accès à l'information du Québec (CAI).
- Canada (federal) — Office of the Privacy Commissioner of Canada (OPC), under PIPEDA.
- EEA/UK — your local Data Protection Authority.
- California — the California Privacy Protection Agency or the California Attorney General.
20. Children and minors
The AI agent and OptimizeMyLife's account features are for adults, and the AI agent is for users 18 and over. We do not create accounts for children, and we do not knowingly collect personal information from children. Content intended for kids and teens is parent-mediated by design — set up and supervised by a responsible adult — and Félix's assistant and installer powers are not available to minors. If you set up the service in connection with a minor, you do so as the responsible adult and are accountable for that use. If you believe a minor has provided us personal information without appropriate adult involvement, contact our Privacy Officer and we will delete it.
United States (COPPA). OptimizeMyLife is not directed to children under 13, and we do not knowingly collect personal information from children under 13 in the United States, consistent with the U.S. Children's Online Privacy Protection Act (COPPA). If we learn that we have collected personal information from a child under 13 without verifiable parental consent, we will delete it.
Québec (Law 25). Under Law 25, the personal information of a minor under 14 may be collected only with the consent of the person having parental authority (or the tutor), unless collecting it is clearly for the minor's benefit. Because our account features and the AI agent are for adults 18 and over, we do not knowingly provide them to minors; where any content is used in connection with a minor, it must be set up and supervised by the responsible adult, who provides any consent the law requires.
21. Region-specific rights
21.1 European Economic Area and United Kingdom (GDPR)
If you are in the EEA or UK, the data controller is 9569-7173 Québec inc. (Section 1) and our legal bases are described in Section 9. In addition to the rights in Section 16, you have the right to object to processing based on legitimate interests, the right to restrict processing, and the right to lodge a complaint with your supervisory authority. Where we transfer your data outside the EEA/UK, we rely on appropriate safeguards such as the Standard Contractual Clauses (Section 13.1). Where processing is based on consent, you may withdraw it at any time.
21.2 California (CCPA/CPRA)
If you are a California resident, you have the right to know the categories and specific pieces of personal information we collect, use, and disclose (Sections 5–13); the right to delete and to correct your personal information; and the right to opt out of the "sale" or "sharing" of personal information and to limit the use of sensitive personal information. We do not sell or share your personal information as those terms are defined under the CPRA, and we do not use sensitive personal information for purposes that would trigger the right to limit. We will not discriminate against you for exercising your rights. To exercise CCPA/CPRA rights, contact our Privacy Officer; you may use an authorized agent, and we will verify your request as permitted by law.
21.3 Other jurisdictions
Where local data-protection law grants you rights beyond those described here, those rights apply, and this Policy is read together with any mandatory local requirements.
22. Cookies and similar technologies (témoins)
Our marketing site and service use a small number of cookies and similar technologies that are necessary to operate the service, keep you signed in, remember your preferences, and measure aggregate, non-identifying usage. On our website, aggregate visit measurement is provided by Vercel Web Analytics, which is cookie-free (it sets no cookie and keeps no identifier across sites). The optional usage statistics in the mobile app are described in the section "Félix mobile usage statistics" below and are off unless you turn them on. We do not use advertising or cross-site tracking cookies, and we do not sell information gathered through cookies. Where required by law, we ask for your consent for non-essential cookies and choose privacy-preserving defaults. You can control cookies through your browser settings; disabling some cookies may affect how the service works. If we publish a separate Cookie Notice, it is incorporated into this Policy by reference.
23. Third-party services and links
The service may reference or link to third-party websites, tools, or content, and it depends on the third-party providers listed in Section 13. Their handling of your information is governed by their privacy policies and terms, not this Policy. We are not responsible for the privacy practices, security, or content of third parties, and we encourage you to review their policies before you connect an account or follow a link.
24. Disclaimers regarding data and privacy
To the fullest extent permitted by applicable law, the service — including all data storage, processing, connectors, and security features — is provided "as is" and "as available", without warranties of any kind, express or implied, including any implied warranties of merchantability, fitness for a particular purpose, non-infringement, or that the service will be uninterrupted, secure, error-free, or that data will never be lost, accessed, or altered without authorization. We do not warrant the accuracy, completeness, or reliability of any output generated by Félix or the AI engines. Nothing in this Section limits or excludes any warranty or right that cannot be limited or excluded under Québec's Consumer Protection Act, Law 25, or other applicable mandatory law, including the legal warranty of quality; those protections apply in full and prevail over any conflicting term here.
25. Limitation of liability
To the fullest extent permitted by applicable law, and consistent with our Terms of Service, OptimizeMyLife and 9569-7173 Québec inc., together with their directors, officers, employees, and service providers, are not liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of data, profits, revenue, goodwill, or business, arising out of or relating to the collection, use, storage, disclosure, loss, or unauthorized access to your information, or your use of or inability to use the service, whether based in contract, tort (including negligence), or any other theory, even if we have been advised of the possibility of such damages.
To the fullest extent permitted by law, our total aggregate liability for all claims arising out of or relating to your information or the service is limited to the total amount you paid to OptimizeMyLife in the three (3) months before the event giving rise to the claim, or US$100, whichever is greater — subject to anything that cannot be limited under applicable law and to the mandatory rights of consumers. This limitation is stated identically across our Terms of Service, this Policy, and our other legal documents.
Nothing in this Section limits or excludes liability that cannot be limited or excluded under applicable law, including liability under Québec's Consumer Protection Act and the mandatory rights of Québec consumers, liability for bodily or moral injury, or liability for intentional or gross fault. Where such law applies, the limitations above apply only to the extent permitted, and your mandatory statutory rights are unaffected.
26. Indemnification
To the fullest extent permitted by applicable law, and except to the extent restricted for consumers under Québec's Consumer Protection Act or other mandatory law, you agree to indemnify and hold harmless OptimizeMyLife and 9569-7173 Québec inc., and their directors, officers, and employees, from and against any claims, damages, losses, liabilities, and reasonable costs (including reasonable legal fees) arising from (a) your misuse of the service; (b) your violation of this Policy or our Terms; (c) your infringement of the rights of any third party, including through data you connect, upload, or share; or (d) content or instructions you provide to Félix. This obligation does not apply to the extent a claim results from our own fault or from liability that cannot be shifted under applicable law.
27. Governing law, forum, and dispute resolution
Governing law and forum. This Policy is governed by the laws of the Province of Québec and the applicable laws of Canada. Subject to the mandatory consumer-protection rules of the place where you reside, any dispute relating to this Policy or your personal information that is brought before a court will be heard by the courts of the Province of Québec, judicial district of Saint-François.
Time to bring a claim. To the fullest extent permitted by law, any claim relating to this Policy or your personal information must be brought within one (1) year after the event giving rise to it, except where mandatory law (including consumer-protection law) provides for a longer period, in which case that longer period applies.
Arbitration (where permitted). Where and to the extent permitted by applicable law, disputes arising out of or relating to this Policy or your personal information will be resolved by binding arbitration on an individual basis, seated in Québec and governed by the laws of the Province of Québec and the applicable laws of Canada, and you and OptimizeMyLife waive participation in any class or representative proceeding to the extent permitted.
Consumer protections prevail. This Section does not apply where it is prohibited or unenforceable. In particular, under Québec's Consumer Protection Act, a consumer cannot be compelled to arbitrate or be deprived of the right to bring or join a class action; Québec consumers retain the right to bring their dispute before the competent courts of Québec, including the Small Claims Division, and to participate in class actions. Consumers and other users in jurisdictions where such clauses are restricted keep all rights their local law guarantees, including the right to complain to a regulator (Section 19) and to seek relief in their local courts to the extent the law provides.
28. Language / Langue
This Policy is published in English, which is the governing version, and a French version is provided. La présente politique est publiée en anglais, qui en est la version qui fait foi, et une version française est fournie.
For consumers in Québec: in accordance with the Charter of the French Language (Bill 96), the French version is made available to you and, if there is any divergence between the English and French versions that concerns a mandatory consumer right, the interpretation most favourable to the consumer prevails. Pour les consommateurs du Québec : conformément à la Charte de la langue française (Loi 96), la version française vous est fournie et, en cas de divergence portant sur un droit impératif du consommateur, l'interprétation la plus favorable au consommateur prévaut.
29. Survival
Any provision of this Policy that by its nature should continue to apply after your account is closed or your data is erased — including what we never do (Section 11), service providers and international transfers (Sections 13 and 13.1), retention and residual copies (Section 14), security (Section 15), privacy incidents (Section 17), disclaimers (Section 24), limitation of liability (Section 25), indemnification (Section 26), governing law, forum, and dispute resolution (Section 27), language (Section 28), and this Survival section — survives the termination of your account or of this Policy, to the extent permitted by law and subject to the mandatory rights of consumers.
30. Changes to this Policy
As the product grows, we may update this Policy. If we make a material change, we will update the effective date above and, where appropriate or required by law, notify you and seek consent. Continuing to use the service after an update means you acknowledge the revised Policy, subject to any consent the law requires.
31. How to contact us
Questions, requests, or complaints about your personal information:
- Privacy Officer / Responsable de la protection des renseignements personnels: Maxime Jodoin
- Email: support@optimizemylife.ai (or support@optimizemylife.ai, subject: "Attention: Privacy Officer")
- Mail: Privacy Officer, 9569-7173 Québec inc. (d/b/a OptimizeMyLife), 780 chemin du lac Brompton, Orford, Québec, J1X 6L7, Canada
You can also read our Terms of Service.
Draft — pending review by legal counsel.
Statistiques d’utilisation de Félix mobile (FR)
Félix mobile utilise un pipeline de statistiques interne, sans fournisseur tiers d’analytique ni suivi publicitaire. Ces mesures sont facultatives et désactivées par défaut : rien n’est capté ni envoyé tant que tu n’as pas répondu Oui à la demande affichée dans Réglages › Statistiques d’utilisation (ou activé l’interrupteur). Tu peux retirer ton accord en tout temps au même endroit : l’envoi s’arrête immédiatement, la file locale est vidée et les mesures déjà reçues pour ton compte sont effacées de nos serveurs. Un envoi reçu à l’instant même du retrait peut avoir été traité avant qu’il prenne effet. Le retrait est communiqué au serveur; en cas de panne, l’app affiche que la synchronisation reste à confirmer, mais les nouveaux envois restent arrêtés. Refuser ou retirer ton accord ne change rien aux fonctions de Félix.
Nous enregistrons des noms de fonctions et d’écrans issus d’une liste fermée, les actions et leurs résultats (réussite, échec ou annulation), la date et l’heure, et des identifiants aléatoires d’événement et de session. Le catalogue prévoit aussi des catégories de durée, des réglages booléens et des états sans montant; seules les actions effectivement instrumentées produisent ces mesures. Aucun texte de conversation, titre de calendrier ou de facture, contenu de fichier, courriel, clé FOX, jeton de connecteur ni montant n’est accepté. Les chemins contenant des paramètres ne sont jamais envoyés.
Une file de 100 événements au maximum reste dans le stockage privé de l’appareil pour réessayer hors ligne pendant au plus 7 jours. Les envois groupés ont lieu toutes les 30 secondes et lors du passage en arrière-plan. Sur nos serveurs, le client est représenté par un pseudonyme HMAC calculé à partir de son identifiant avec la barrière propriétaire HMAC du système de session existant. Ce pseudonyme reste une donnée liée au compte, pas une donnée anonyme. Les compteurs et les 200 derniers événements par jour de réception et par client sont conservés au maximum 13 mois. Ils servent à comprendre l’adoption des fonctions, les étapes d’utilisation et les cohortes de retour afin d’améliorer Félix. L’accès au bilan et à la chronologie est réservé à l’administrateur autorisé. L’effacement des données du compte supprime aussi ces événements, les dédoublonnages et leurs contributions aux compteurs; un indicateur sans contenu empêche leur recréation.
Félix mobile usage statistics (EN)
Félix mobile uses an internal analytics pipeline with no third-party analytics provider or advertising tracking. These measurements are optional and off by default: nothing is captured or sent until you answer Yes to the request shown in Settings › Feature statistics (or turn the switch on). You can withdraw at any time in the same place: sending stops immediately, the local queue is emptied and the measurements already received for your account are erased from our servers. An upload received at the very moment of withdrawal may have been processed before it took effect. The app also sends the choice to the server; if that fails, it displays a sync error while new uploads remain stopped locally. Declining or withdrawing does not change any Félix feature.
We record closed-list screen and feature names, actions and outcomes (success, failure or cancellation), timestamps, and random event and session identifiers. The catalogue also supports duration buckets, boolean settings and states without amounts; only instrumented actions produce measurements. Chat text, calendar and invoice titles, file contents, emails, FOX keys, connector tokens and amounts are never accepted. Route parameters are never uploaded.
At most 100 events remain in private device storage for offline retries for up to seven days. Batches are uploaded every 30 seconds and on backgrounding. On our servers, a domain-separated HMAC of the account identifier uses the existing owner-session HMAC fence. This pseudonym is account-related data, not anonymous data. Counters and the latest 200 events per client and receipt day are retained for up to 13 months. They help us improve feature adoption, usage journeys and return cohorts. Only the authorized administrator can access reports and client timelines. Account data erasure removes these events, deduplication records and counter contributions; a content-free flag prevents their recreation.