Last updated: October 13, 2026
MononcleAI ("we", "us", "our") operates the website mononcleai.ca. This policy explains how we collect, use, and protect information when you use our service.
Account information. When you sign in with Google, we receive your name, email address, profile picture and Google account ID. We use this to manage your account and subscription, and to email you as described in section 2.
Usage data. We track session counts, session duration, and feedback you voluntarily submit (ratings, comments, optional email). This helps us improve the service. If you leave an email address with your feedback, we may also use it to email you as described in section 2.
Usage totals and session costs. If you are signed in, or your device is recognized as a subscriber's, we keep a running total for your account for each calendar month: the number of sessions, the seconds practiced on each day, when your last session ended, and token counts. Token counts measure how much AI processing a session used. Your browser reports them to us at the end of a session, with the name of the AI model. Your profile menu shows this month's sessions and minutes from this total. For each session that reports token counts, whether or not you are signed in, we also keep a cost record: the session ID, when the session ended, how long it lasted, how it ended, whether it was a free trial or a subscriber session, whether you were signed in, and the token counts. A cost record does not hold your email address or your device identifier. The same session ID does appear in your usage events and, for subscribers, in the session summary described below.
Device identifiers. We generate a random identifier stored in your browser's local storage to manage session limits. This is not linked to your real identity unless you sign in, or give us your email address when you send feedback.
Network address. To limit free trial sessions per network and to slow down abuse, our server uses the IP address that some of your requests come from. It stores a hashed form of the address, not the address as written. For an IPv6 address, only the first half is used. Each free trial session you start leaves one record under that hash, with its start time, for 24 hours. If a network reaches its daily limit of free sessions, a marker saying so is also kept for 24 hours. Counters that limit how often one network can call some parts of our server last from about a minute to about an hour. These records are not stored with your account or your device identifier. They do carry a time, though, and records that hold your hashed device identifier or your account are written at almost the same moment. The two could be matched by time for as long as a network address record exists. Sessions started by subscribers do not create the 24-hour records.
Payment information. Payments are processed by Stripe. We do not store your credit card number. Stripe notifies our server about your checkout and your subscription. From those notices we keep your Stripe customer ID, your subscription ID and your subscription status. When you start a checkout, we send Stripe your email address, the plan you chose and, if we have one, the first-visit record described in section 4. We attach these to your checkout and your subscription in Stripe.
Cancelling a subscription. You manage or cancel your subscription on a billing page hosted by Stripe, opened from the profile menu in the app. When a cancellation is scheduled, Stripe notifies our server. We record the date your plan ends and, if Stripe passes them on, the reason you picked, your comment and Stripe's own code for why the plan is ending. We keep this with your email address and your Stripe customer and subscription IDs, and the same details are emailed to our team. If you undo the cancellation before the plan ends, we record that too.
Voice audio. Voice conversations are processed in real time by OpenAI's API. Audio is streamed directly between your browser and OpenAI via WebRTC. We do not record or store the audio of your conversations.
Conversation text. During a session, OpenAI also turns what you and Michel say into text, and your browser uses that text to show live subtitles. After a session, your browser sends the text of the conversation to our server so that an OpenAI language model can write your session review. Our server passes the text on, returns the review to your browser, and does not keep the transcript.
Conversation memory (signed-in subscribers). So that Michel can pick up where you left off, we keep two kinds of short text notes for signed-in subscribers. Both are written by an OpenAI language model from the text of your sessions, so they can contain mistakes.
How it works: when a session ends and you are signed in, your browser sends the text of the conversation (never the audio) to our server. If you are a subscriber, the server sends that text and your existing profile to OpenAI, which returns the updated profile and the summary. We store those two notes under your account email in our database, which is hosted by Cloudflare. We do not store the transcript itself. At the start of your next session the profile is sent to your browser and added to the instructions given to OpenAI's voice model, so that Michel can use it. If you are signed in but not a subscriber, the text is discarded and no notes are created.
These notes have no automatic expiry. We keep them until you ask us to delete them, and they are not deleted automatically when a subscription ends. To have them deleted, email hello@bluebooktech.ca from the address on your account. Deleting them does not switch memory off: if you keep practicing as a subscriber, new notes start with your next session.
We use the following third-party services, which may process your data:
Several of these providers are based in the United States, so your information may be processed and stored outside Québec and outside Canada.
We use your browser's local storage to keep the app working. It holds your device identifier, your sign-in (a sign-in token and a copy of your account record), your caption preference, your daily session state, a note that you have seen the welcome screen, and the address of our server. On the purchase confirmation page it also holds your checkout reference, so that a purchase is counted once and the optional question is asked once. Our code does not remove that reference afterwards. Our own code sets no cookies.
The site loads these measurement tools:
Google Sign-In, which loads in the app, may also set cookies. After a purchase, the confirmation page asks an optional question, "How did you hear about us?". If you type an answer and press Send or Start practicing, we receive your answer together with your checkout reference. We use the reference to find your account and save the answer with it.
You may request access to, correction of, or deletion of your personal data by emailing hello@bluebooktech.ca. If you are in Canada, you have rights under PIPEDA. If you are in the EU, you have rights under GDPR including the right to data portability, erasure, and to lodge a complaint with a supervisory authority.
We use industry-standard security measures including HTTPS, hashed identifiers, and secure third-party providers. However, no method of transmission over the Internet is 100% secure.
MononcleAI is not intended for children under 13. We do not knowingly collect information from children.
We may update this policy from time to time. We will notify you of significant changes by posting the new policy on this page with an updated date.
Questions about this policy? Email us at hello@bluebooktech.ca.