Privacy policy

1. Who is responsible

The data controller is meemoo, operated from Mexico by its founder. For anything related to privacy, including exercising your rights, write to hola@meemoo.tech.

This policy covers people with an account and also people who leave us data without one: on the waitlist, when booking a meeting through someone's link, or when writing to someone who uses meemoo.

2. What data we process

We process only what meemoo needs to work for you:

• Account: name, email address and password and, if you add them, the names people call you in your tools and your “About me”. The password is stored hashed: nobody at meemoo can see the one you set. Your initial password, and a temporary one if you ask for a reset, is created by meemoo's administration to give to you; change it when you sign in.
• Preferences: language, theme, summary times, whatever you tell us matters to you, the day's focus (the projects or experiences you choose to prioritize today) and your dictation dictionary.
• Your content: concepts, thoughts, projects, tasks, milestones, people (with the details you record for them, including the person you mark as “This person is me”), experiences, notes, tags, pages, links, your CV (and the PDF you import it from), the files you upload (up to 1 GB each, depending on your plan), your conversations with the Assistant and what you attach there. It is the heart of the product and it belongs to you.
• Invoicing, if you use it: your tax profiles (RFC, name or legal name, tax regime, CFDI use, postal code, address, phone and the emails used to receive and to request invoices), photos or details of your receipts, the email sent to request the invoice, a screenshot of how the portal ended up, and the invoices you receive as PDF and XML. Your tax status certificate (Constancia de Situación Fiscal) is read to prefill the profile and is not stored.
• Forms, if you use them: each form's address, its fields, the values you approve, the page's response and a screenshot of how it ended up.
• Job applications, if you use the Jobs agent to apply to openings: the opening (its text and link), the analysis (your strengths and weaknesses for the role), the CV and cover letter used (the letter is written when the opening or its form asks for one), what you answered and the history of the process. They are recorded in your Jobs agent and in a «Postulaciones de trabajo» project created in your account. If your email is connected, emails from a hiring process (acknowledgment, interview, rejection, offer) are matched to your applications to update their status and create the next step.
• Memory brought from other AIs, if you bring it (in the welcome or from Account → Assistant): the text you pasted or uploaded with what another AI (ChatGPT, Gemini or another) remembered about you, with its version per source (bringing it again saves a new version). Your Assistant reads it to propose what to bring into your Brain (Cerebro); you accept what you want. You can view, download or delete it anytime in Account → Assistant, and deleting it really deletes it (what you already accepted into your Brain stays). We also keep the name you gave your Assistant and, if you share it in the welcome, what you say about yourself is added to your “About me”.
• Job hunting, if you use it: the analysis of your CV (where you add value, your level, what to learn and new paths), the roles and industries you look for, the companies it reviews (including the ones you paste, with their link), the openings it finds with their score, what you are missing and what you should learn, and the study projects you create. If you ask who to write to at a company: for each recruiting person (or the company's jobs email) we find in public sources (the company's site, its openings and the web), their name, title, work email if it is published, public link (for example, their LinkedIn profile) and where it came from. Those contacts are kept only in your account, are not shared with other accounts and are deleted when you remove the company or the contact. For the emails you send from there we keep the recipient, subject, text, the account it was sent from and the date.
• Controller (your expenses), if you turn it on: for each subscription and recurring payment we recognize in your email, the service, plan, amount (or that it varies), currency, how often it is charged, the next date, the end of the free trial, which email it arrives at, what the plan includes and its last 12 charges; if you follow it, also its recurring task. For each one-time payment we detect in your email, on Slack or on WhatsApp, or that you save by uploading its receipt or invoice: the merchant, the amount, the date, a description, where it came from and the file you uploaded. For any expense, the project or experience you assign it to and, if you requested its invoice, the Invoicing request. What is detected only becomes an expense if you say yes; if you say «Not mine» («No es mía») or «Not an expense» («No es un gasto»), it is marked so it is never proposed to you again.
• What you connect: if you turn on a connection, we read from that tool what you authorize (see section 4). That includes messages and emails from other people: the ones they send you and, in the channels you follow, what is written there.
• If someone books you: the name, email and, if they leave them, the WhatsApp number and note of whoever requests a meeting through your link (section 9). If you accept the meeting, it also goes to your Google Calendar, with that person as a guest.
• Waitlist: the name and email you leave in the form to request access. To know how you found us we also keep the source of the link you came through (for example, LinkedIn or a campaign), the page language and, if you arrived through someone's personal link from the list, who invited you. When you join you get your own personal link to invite others.
• Technical data: a session cookie to keep you signed in; server logs (date, route, IP address and errors) to operate the service, prevent abuse and debug errors; and a usage record of your account (when you sign in, what kind of things you create and how much AI you use, without their content). After 90 days, the detail of that record remains only as monthly totals. If you install meemoo as an app on a device, we keep when and on what kind of device (system, browser and whether it is a phone, tablet or computer), without your device's identifier.

We do not ask for data we do not need. There are no advertising profiles and no cross-site tracking.

3. What we use it for

• Keeping and organizing your memory: whatever you write, dictate or upload lands in its place and can be found again, by meaning too.
• Proposing things: your Assistant (powered by artificial intelligence) summarizes, suggests tasks, documents and connects information. Everything is a proposal: approve it, adjust it or dismiss it. Nothing applies without your click, except closing what you already set in motion: when the confirmation of a form you sent arrives, we close its task; when an invoice you requested arrives, we save it, and when the schedule of a flight in a trip you created changes, we move its tasks to the new time, and when the cancellation of a subscription you follow arrives, its task stops repeating. It never acts on your tools by itself. Your Assistant has no power to delete: at most, it proposes dismissing.
• Doing what you ask with a click: filling in a web form, requesting an invoice, reading a link, designing smart filters or asking for a thinking pass (sections 5 and 6).
• Reminding you: morning and evening email summaries, alerts about what matters, a weekly review on Fridays and, if you turn it on, your daily (what you did yesterday, what you will do today and what to remember), at the times you choose in your time zone.
• Operating the service: signing in, keeping your session, preventing abuse and fixing errors.
• Improving the public page: on the meemoo.tech home page we measure it ourselves, without cookies and without storing anything in your browser: how many people arrive, from which site or campaign, on what kind of device (phone, tablet or computer) and which parts of the page they use (how far they scroll, which sections they see, which buttons they press, whether they open a question or submit the form), without your name or email. To count visitors we use a fingerprint computed from your IP address and your browser that changes every day: we do not store your IP or the previous day's fingerprint, so we cannot recognize you from one day to the next. It is not used inside the app.

4. Connections to your tools

No connection is active until you turn it on from Connections (you can also turn on mail reading from the Google connection card in your Assistant), and you can turn it off whenever you want. When you disconnect an account, we stop reading it and delete its credentials, along with the copy of what we read from it: messages, emails, GitHub activity, their summaries and the proposals you did not accept. What you already accepted into your memory (tasks, projects, people, documents, invoices) stays until you delete it, and the notes already left in the Assistant chat stay too (section 11). Unfollowing a channel or turning off “Read mail” only stops the reading: what was already read is deleted when you disconnect the account.

• Google Calendar and Meet: when you connect a Google account we ask permission to see your Google name and email, see your calendar, create, change and delete events in your calendar, create Meet calls, read information about your Meet meetings and the files Meet saves to your Drive, read your email and send email. We show your events in the Calendar agent and keep a copy of your meetings (title, description, time and who attends) for your daily, your Brain and your Assistant; for your booking links we only check whether you are free or busy (you can turn this off per link). We write to your calendar only when you do it from meemoo, in the account you choose in Calendar: creating an event (with the guests and the Meet call you add), changing or deleting one you organize, and saving the meetings you accept from your booking link (with whoever requested it as a guest); if you cancel one of those meetings, we delete it. Google sends the guests the invitation, the change or the cancellation, as when you do it in Google Calendar. We never change or delete events you do not organize, and we never write to your calendar on our own. We create a Meet call only when you ask. When a Meet meeting you took part in ends, we read its transcript once (if someone turned it on) or the Gemini notes Meet saved to Drive, plus the list of who joined, to pull out who was invited, attended and spoke, the summary, what was decided, each person's commitments and the key notes, and show them in your Assistant; tasks are created only with your click. We do not keep the meeting text, only the summary, decisions and commitments.
• Gmail: reading starts only when you turn it on for that account (“Read mail” (“Leer correo”) in Connections, or “Connect mail” (“Conectar correo”) in the Google connection card in your Assistant), and you choose whether we read from that moment on or also the last month. From then on we read your inbox and sent mail, without spam or trash, and store sender, recipients, subject, an excerpt of the body and a short summary of each thread, to build summaries, flag what matters and propose tasks; if a flight booking arrives, we highlight it in your Assistant with the proposal to create the trip (an experience with the flight details, the check-in and the preparations as tasks), which is created only with your click; if the receipt, renewal, price change or end of the free trial of a subscription or a recurring payment (phone, power, rent) arrives, we show it to you with the proposal to follow it as a recurring task, which is also created only with your click; with Controller on, if the receipt or confirmation of a one-time purchase arrives, we ask you whether to save it as an expense; to understand a thread we also read its earlier messages, without storing them. If you requested an invoice, we also check the recent emails that talk about invoices in your connected Google accounts, even if “Read mail” is off, and from the email that brings it we keep its PDF, its XML, its subject and its sender. We send email in only two cases, always with your click: the one requesting an invoice, when you press “Send the email” (“Enviar el correo”), from the account you chose in your tax profile (if you did not choose one, one of your connected Google accounts; the card tells you which before sending), and in Job hunting the email to a recruiting person that you review and send with “Send” (“Enviar”), from the account you choose (with your CV as a PDF if you leave it checked), up to 10 a day. We never delete, move or mark your emails.
• Slack: with read-only permissions we read your direct messages and group direct messages (followed when you connect) and the public or private channels you choose to follow; the first read brings the last 3 days, and you can unfollow any of them. With that we summarize what was said, what you were asked and what you promised, and we only propose from what involves you. With Controller on, the messages you wrote in those channels are also checked, only to detect a payment you made («I already paid for dinner, $850»); if one looks like it, we ask you whether to save it as an expense. We never post messages on your behalf: when you close a task that came from there, we leave you the message ready for you to send.
• Discord: a meemoo bot, which is invited to each server, receives the messages of the channels it can see, but we only store those of the channels you choose to follow, among those you can see in Discord, and their threads (the first read brings the last 3 days; private threads only if you are part of them); messages from other people in those channels are stored in your account. If you lose access to a channel or leave the server, we stop reading it for you. It does not read direct messages, and your own account only tells us who you are and which servers you belong to. The bot writes only when someone mentions @meemoo: if it is you, your Assistant replies by direct message and leaves only a notice in the channel (section 9); if it is someone without meemoo, or if they just greet it, it introduces itself without saying who uses it.
• GitHub: we work with the repositories you link to a project: their activity, files, README, issues and pull requests, and for your signals only what involves you (yours, assigned to you, reviews requested from you and mentions). With the type of connection meemoo uses, GitHub does not allow access repository by repository, so the permission covers every repository you have access to, private ones included; meemoo only lists the others so you can choose which one to link. We write only when you explicitly ask: creating a repository, publishing files from your Documents as commits, or deleting a repository, with a warning first.
• Notion: you link one or more task boards from the pages you share with meemoo to a project. We read their tasks and statuses; we create, rename, change the status of or archive tasks only when you do it from meemoo, and when syncing with the Backlog you first see a preview and decide each conflict. Unlinking a board changes nothing in Notion.

Google data and Limited Use: meemoo's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: we use your Google data (calendar, email, profile and your Meet meetings with their transcripts and notes) only to provide the features in this section, which you see and control in the app; we do not sell it or use it for advertising or profiling; we only transfer it to third parties when necessary to provide those features (for example, to the AI provider in section 5 to build your summaries, under a contract that does not allow it to train on that data), to comply with the law or, with prior notice, as part of a merger or acquisition; no person reads it except with your express permission, when necessary for security (investigating abuse) or to comply with the law; and we do not use it to develop, improve or train generalized artificial-intelligence or machine-learning models. You can revoke access at any time from Connections or from your Google account's security settings.

Each connection's access credentials (tokens) are stored encrypted at rest with AES-256-GCM and used only for what this section describes. Each platform has its own terms, which also apply to your use of it.

5. Artificial intelligence

To summarize, propose, classify, read documents and act when you ask, meemoo sends fragments of your content to a language-model provider based in the United States. It happens at two moments:

• Without you doing anything, depending on what you have turned on: classifying new email, recognizing a flight booking, the receipts of your subscriptions and recurring payments and, with Controller on, your one-time purchases and the payments you mention in the messages you wrote on Slack and WhatsApp, building the morning and evening summaries, analyzing the Slack and Discord conversations you follow and the activity of your GitHub repositories when something involves you (the rest of that day's conversation goes along as context), pulling out the summary, decisions and commitments of the Meet meetings you took part in when they end (from their transcript or the Gemini notes), the weekly review and, if you turn it on, the daily (with your tasks, meetings, summaries, what is new in your Brain and what you wrote to the Assistant).
• When you ask: your Assistant's chat (also when you write to it with @meemoo on Discord) and what you attach to it (images are seen as images; PDFs, as their text), thinking passes, or pensadas (the page, the element it belongs to, your “About me”, the titles of your other pages and previous passes), smart filters (name, summary and tags of the items in that section), documenting or proposing tasks, importing a document, your CV (reading it from a PDF or translating it), forms (their fields and the details of the person they are filled in with), invoices (your receipts, your tax certificate and the tax-profile data the process needs), reading a link, importing a diagram from a link into a canvas (a screenshot of the page, its text or the diagram image), the transcripts of an audio, a video or YouTube (the text, to translate it, analyze it and connect it with your concepts), Job hunting (your CV, level and places, for the career analysis and to review openings; the link of a company you paste; the search for who recruits at that company, and the draft of the email to one of those people) and your job applications (the opening and your CV, to analyze it and write the cover letter when the opening or its form asks for one; and emails from a hiring process, to know which application they belong to). To read the opening, the AI provider opens its public link with its web-reading tool and, if the page does not open, searches the web for it by role and company; it does not carry your name or your data. In Job hunting, the AI provider also searches the web for companies, their careers pages and who recruits at them: those searches carry the company's name and the roles, not your name. When you prepare a trip (the questions on a flight's card), if a pet travels, minors travel or the flight is international, the AI provider searches the web for the current official requirements: those searches carry the countries, cities, dates, airline and what you answered (whether minors travel and with whom, the pet, your passport), never your name or your booking code. In Controller, «How do I cancel it?» («¿Cómo la cancelo?») has the AI provider search the web for the official steps to cancel and what the plan includes: that search carries only the service, the plan's name and your country, nothing from your account or your charges; and the receipt or invoice you upload is read to get the merchant, date, total and folio.
• With the Chrome extension (section 6), the first time a task sees a page, the AI provider also receives screenshots of that page, to check that the questions it understood are the ones shown; in Invoicing, also the photos of your receipt. Those screenshots are not stored.

The AI only receives the snippets each task needs, through a commercial API whose terms don't allow training on your data. To place what is new within your memory, the chat and the analysis of your connections also carry the name and a one-line summary of your items, and your open tasks; to plan, the chat also carries how you put together your finished projects and experiences (their milestones, how long they took and some tasks), only yours. The notice of late milestones is calculated without AI. Never your whole database, and never your password, your connection credentials or your Vault.

Search by meaning (embeddings) is computed with an open-source model that runs inside meemoo: that content does not go to any provider.

Training models: to improve meemoo's agents we may train models on events and categories of how they are used (for example, «a form on a type of portal got stuck at a step» or «a proposal was corrected»). Never on the content of your account: your texts, emails, conversations, names, files or what you answer. What comes from Google (your email, your calendar and your Meet meetings with their transcripts and notes) is never used for training, neither as events nor as categories. The examples you keep with «Improve my agents» are only used to test improvements, not for training. Those models are used only inside meemoo: they are never sold or shared with third parties. You can turn it off anytime in Account → Assistant («Use my events to improve meemoo's models»).

What the AI proposes on its own waits for your approval. What you ask for with a button (a thinking pass, reading a link, designing filters, proposing tasks for a milestone) is saved as the result of your request, and you can edit or delete it. It can be wrong: review it before relying on it.

6. When meemoo acts on the web for you

Apart from what you ask it to do in your own tools (section 4), it doesn't send messages for you: it leaves you the draft. Something reaches third parties in five cases, never on its own: the email requesting an invoice, when you press “Send the email” (“Enviar el correo”); the email to a recruiting person in Job hunting, when you press “Send” (“Enviar”); a form or portal (invoicing, jobs or any other) that the Chrome extension fills in in your browser, only when you approve the submission; the invitations for an event you create or change in your calendar, or for a meeting you accept, which Google sends to the guests; and its bot's reply in Discord, by direct message to whoever mentioned @meemoo.

• Forms: you give it a form's address and the meemoo extension for Chrome opens it in your browser; meemoo reads what the extension sends from each page (text, fields and buttons) and proposes what to enter using the details of the person you marked as yourself (or the one you name), your project and your notes. It proposes a value for every field, also reusing what you answered before in other forms and applications; if it is a guess it tells you so, and it does not make up hard facts (identifiers, phone numbers, addresses): those become a question. Voluntary demographic questions get «prefer not to answer» unless you already answered them. You approve what gets filled in on each page and the submission. Newsletter or advertising boxes stay unticked unless you ask, and you decide on terms or consent boxes. We keep what was answered and, if meemoo reads your email, we close the follow-up when the confirmation arrives.
• Invoicing: with the button on the card, meemoo looks up how that merchant issues invoices (with a known guide or a web search that only carries the merchant's name), without opening the portal. If it is a portal, the meemoo extension for Chrome opens it in your browser and goes through it step by step: it fills in only what you approve and submits only with your OK. If it is by email, we send it from your Gmail with the receipt attached when you press “Send the email” (“Enviar el correo”). The agent is instructed to use only your tax profile, your receipt, the values you approved and your instructions, and to accept only the notices the portal requires for the process, never newsletters or promotions; if it is missing a piece of data, it stops and asks you. When the PDF and the XML arrive, we keep them; if the portal offers them for download once the invoice is confirmed, the extension downloads them in that same tab and they go to your invoices account (useful when the invoice is emailed to someone else).
• Invoicing guides: what is learned about how a merchant issues invoices (method, address, each portal screen with its fields and buttons, which receipt details it asks for and how it delivers the invoice), without your tax details, those of your purchase or what you answered, becomes a guide for the whole platform, so the next person does not start from scratch. Internally we record which account originated each guide, and only meemoo's administration sees it.
• Job portal guides: when an application through the extension is submitted successfully, what is learned about how that job portal works (whether it asks for a candidate account, the password rule it accepts, the steps and what is confusing) becomes a guide for the whole platform. The guide describes the portal, not you: it does not store who applied or to which opening, nor your email, your password or the details of your CV.
• Cancellation steps: what «How do I cancel it?» finds (the official steps, the link and what a plan includes) is public information and becomes a guide for the whole platform for 120 days, so it is not searched again for each person. It does not store who asked for it or anything from your account.
• Reading a link: when you ask, our server opens the public page of a link you added to your Documents, without your session or your cookies, and saves its content as a text page. It does not open internal addresses, and if the page asks you to sign in, it tells you and saves nothing. The same applies when importing a diagram from a link into a canvas: the public page is opened, a screenshot and its text are taken, and only the redrawn diagram is saved in your canvas.
• Chrome extension, if you install it: it is your Assistant's eyes and hands in your browser and never acts on its own. When you ask from meemoo (for example, to apply to a job or to request an invoice on a merchant's portal), it opens the page in a new tab marked «meemoo is working in this tab», with a button to stop it, and sends meemoo what that page shows (its text, fields and buttons and, the first time, screenshots) to suggest what to fill in. It only writes on the page what you approve and only clicks «Submit» with your OK. It does not read or touch your other tabs, does not store your passwords, and you solve any captcha yourself. To read the page without clutter, in that tab it closes cookie banners by rejecting non-essential cookies (it never accepts them) and informational notices covering the page; it does not touch a window that asks you to decide something. If the site asks you to create a candidate account, with your OK the extension generates a unique password for that site that meemoo never sees; it stays only in your browser until you decide to save it in your Vault (which you open with your OTP or PIN; it goes straight from the extension to the Vault, without the meemoo page seeing it) or discard it. If you already have an account on that site and your Vault holds its login, meemoo asks before creating another one: if you choose to use it, you hand it over from your open Vault, it goes straight from your Vault to the extension, without passing through the meemoo page or the address and without being stored by meemoo; the extension uses it only on that site to sign in with your OK and forgets it when the task ends, when that tab is closed or after 15 minutes, whichever comes first; otherwise you sign in yourself. Captchas, codes and email confirmation are done by you. If you press «Report this page» («Reportar esta página»), meemoo receives that page's structure (its labels, controls and texts, never what you typed in the fields), what the extension read and the steps of the task, to review what your Assistant understood; it is deleted after 30 days. Improving the agents: each agent is measured by what you do next (whether you sent the task, corrected what it proposed or undid a connection) and we keep those numbers (cost, time and whether it went well). Only if you turn on «Improve my agents» in Account → Assistant do we also keep examples of what it did and what you corrected, for 90 days, to test improvements on real cases; they are not used to train models (section 5). When an invoice is done, if the page offers the PDF and the XML for download, the extension downloads them in that tab and sends them to your meemoo account, without leaving them in your Downloads folder. You can revoke its permission or uninstall it anytime from Chrome.
• WhatsApp, if you connect it: the meemoo extension opens WhatsApp Web in its own tab, on your computer with Chrome and with your own session (you link it yourself with the QR code), and only reads: it never writes, never sends, doesn't react or delete. It reads the chat list (name, last message and how many are unread) so you choose which ones your Assistant reads; it opens each of those to read it, which marks it as read for your contacts, and sends meemoo the new messages (who wrote it, when and the text, and whether it had a photo, voice note or document) and the photos, which stay in your account. With that your Assistant suggests tasks, events and reminders, as with Slack or Discord. Your contacts' messages go through meemoo only for that. It reads while meemoo is open on that computer (every 5 minutes or when you press «Read now» («Leer ahora»)); chats you didn't choose are never opened or read. «Disconnect WhatsApp» («Desconectar WhatsApp») deletes your chat list and the messages read; what you already accepted stays. With Controller on, the messages you wrote in the chats you chose are also checked, only to detect a payment you made; if one looks like it, we ask you whether to save it as an expense.

If a site asks to sign in, solve a captcha or pay, meemoo stops and leaves you the step-by-step. What you send to a site or a merchant is also subject to their own privacy policy.

7. Dictation and transcription: audio never leaves your device

Voice dictation runs in your own browser with local models (Whisper and Vosk, with Silero voice detection). Audio is never sent to our servers or to third parties. Only the transcribed text is saved, and only if you decide to send it; from then on it is treated like any message you type. Your dictation dictionary (the names it must spell exactly) is stored in your account.

Transcribing an audio or a video from your Documents also runs in your browser with local models: the file is not uploaded, only the text. For a YouTube video, the Chrome extension opens the video in a work tab and reads the transcript YouTube offers, without downloading the video or the audio. The transcript is saved in your account as a Document and its text goes to the AI provider to translate and analyze it (section 5).

8. Vault

What you keep in the Vault (keys, credentials, secrets) is encrypted at rest with AES-256-GCM, with a key of your own vault protected by your PIN and by a key that lives on the server, not in the browser. The title you give each item is not encrypted. The vault opens with your PIN; if you turn on an authenticator app, its code opens it for reading and the PIN is required to edit. Every opening and every revealed secret goes into a log you can see. Nobody on the meemoo team reads it, and it is not sent to AI providers.

9. What you choose to make public or share

Everything in meemoo is private by default. Only what you decide leaves your account:

• Public CV: if you enable it, that page is visible to anyone with the link, with the information you choose to include. You can disable it at any time and it stops existing.
• Booking link: its public page, visible to anyone with the link, shows your name, the title and description you write and your free time slots; busy times appear as “Taken”, with no details. Whoever requests a meeting leaves their name and email and, if they want, their WhatsApp number and a note: that reaches only you. If you accept it, we save it in your Google Calendar with that person as a guest and Google sends them the invitation with the Meet call (and the cancellation, if you cancel); apart from that, we do not write to them. You can turn the link off whenever you want.
• Shared projects: if you share a project with another meemoo user, they can see it and, depending on the role you give them, edit it. You can remove their access whenever you want.
• Discord: when you mention the bot with @meemoo, your Assistant replies by direct message, because the reply may use information from your memory; only a notice stays in the channel. If your direct messages are closed, the notice asks you to see it in meemoo.
• API tokens: if you create one in Account → Apps & API, the agent or program using it can do in your account whatever you can, as if it were you, and what it does with that depends on whoever runs it. You can revoke it and it stops working instantly.

10. Who we share data with

We do not sell, rent or hand over your data. Only providers needed to run the service take part, under contract and limited to what this document describes:

• A server provider in Germany (European Union): where the application, the database, your files and the backups live.
• A language-model provider based in the United States: the AI processing in section 5, under a contract that does not allow it to train on your data.
• The platforms you connect (section 4), only to the extent you authorize them.

In addition, when you ask, data goes to the site or merchant you send a form to or request an invoice from (what you approve), to a web search engine, which only receives the merchant's name when looking for its invoicing portal, to the AI provider's web reading and search tool, which receives the link of an opening you analyze (or its role and company, to look it up) and, in «How do I cancel it?», only the service, the plan's name and your country, to the guests of the events and meetings you save in your calendar (section 4), to the people or channels you decide to share with (section 9), and to the recruiting people you decide to write to from Job hunting (the email you reviewed and, if you leave it, your CV).

We may disclose data if a law or a competent authority requires it, and only to the extent strictly necessary. If that happens and the law allows it, we will tell you.

11. Where it is stored, for how long and how we protect it

Your data lives on servers in Germany and is kept for as long as you have an account, with these rules:

• If you disconnect an account, we delete its credentials and what we read from it (section 4).
• If you ask us to delete your account, we erase your account, your content, your files (attachments and invoices included) and your connection credentials within 30 days at most; the database backups, which are encrypted, delete themselves within 15 days at most.
• The Assistant chat history and what you attach there are kept for as long as you have an account. The app does not yet let you delete them one by one: if you want something deleted from there, write to us. What you type in the chat and have not sent yet (the draft) is kept in your account so it is not lost if you close the tab or sign out; it does not go to the AI provider until you send it, and it is deleted when you send it or clear the box.
• Booking requests stay in the account of whoever receives them until that person deletes them from their history, deletes the link or closes their account.
• Waitlist data is kept while you are on the list. When we open your account, that record stays linked to it (to know how you found us) and is deleted when the account is deleted, or earlier if you ask us.

All traffic is encrypted (HTTPS). Passwords are stored with Argon2id, connection credentials encrypted at rest with AES-256-GCM, the Vault with its own encryption and your PIN, and database backups encrypted. Server access is restricted to the minimum necessary and protected with anti-intrusion measures. To operate the service, meemoo's administration sees your account details, your usage (including the titles of the pages where you ask for thinking passes) and an activity list with the names of what you create or delete (projects, people, files and so on).

No system is infallible: if we detect an incident affecting your data, we will tell you without delay and with what we know.

12. Cookies and local storage

• Session cookie: keeps you signed in. It is strictly necessary and expires by itself after 30 days. When you connect a tool, a temporary cookie also protects that step.
• Browser storage: keeps your language, your theme, how you left the interface (sidebar, list or card view, filters and hidden calendars), what you import from a .ics calendar file, the dictation models, whether we already recorded that you installed the app on that device, and whether the meemoo extension was installed in that browser (to warn you if it disappears). To make it installable, the app registers a minimal service worker in your browser that keeps no copy of your information. It stays on your device.
• Public page: if you join the waitlist, your first name, the date and your personal invite link are stored in your browser to greet you when you come back and to build your share card (the card is drawn in your browser). If you arrived through someone's personal link from the list, your browser keeps their code for 30 days and only sends it to us if you join (we remove it from the page address as you arrive, so analytics does not see it). The link's source (for example, LinkedIn or a campaign) is also remembered for 30 days to send it if you join, and the page analytics sees it as part of your visit. What you approve in the demos lives only in that tab.
• Public page analytics: it uses no cookies and stores nothing in your browser (section 3), which is why the page has no cookie notice. It does not run inside the application.
• Videos in «Ideas and notes» («Ideas y notas»): a YouTube video is shown with its thumbnail, which loads from YouTube, and when you press ▶ (or on a Vimeo one) that site's player loads right there (YouTube's in its privacy-enhanced mode), and it is subject to that site's own privacy policy.

13. Your rights

Under Mexico's Federal Law on the Protection of Personal Data Held by Private Parties and, where applicable, other rules such as the GDPR, you can at any time:

• Access your data, correct it, cancel it or object to its processing (ARCO rights).
• Withdraw your consent and disconnect any integration from Connections, without affecting the rest of your memory.
• Request a copy of your content or the complete deletion of your account.
• Limit the use or disclosure of your data.

To exercise them, write to hola@meemoo.tech from your account email saying what you need. If you do not have an account and your data reached meemoo through the waitlist, a meeting you requested, messages to someone who uses meemoo or because someone used Job hunting to look for who to write to at your company, write to us from the email you used. We answer within 20 business days at most. If you believe we did not handle your request, you can turn to Mexico's personal data protection authority, the Ministry of Anti-Corruption and Good Governance (Secretaría Anticorrupción y Buen Gobierno), which took over the functions of the former INAI.

14. Minors

meemoo is meant for people over 18. We do not knowingly collect data from minors; if we detect a minor's account, we will close it and delete its data.

15. Changes to this policy

If we change something relevant (new providers, new uses, new connections) we will update this document, change the date above and notify you inside the application before it applies. Continuing to use meemoo after that notice means you accept the new version.