Privacy policy
Last updated: November 13, 2026
In plain words: what MeiMei keeps, where it lives, how long, and how to make it go away.
Who is responsible
The controller of your data is LED TECHNO FUSION S.R.L., CUI 40378030, J2019000036229, Str. Petre Andrei nr. 4C, parter, Iași, Romania. You can reach us at support@meimeimonitor.com.
What MeiMei is
MeiMei turns a spare phone into a monitor unit and your own phone into the viewer unit. The monitor unit listens and watches, and the viewer unit shows you what is happening and alerts you. MeiMei reports what it observes, such as sounds and movement. It does not tell you what they mean.
MeiMei is not a medical device and is not made for watching over someone who is unwell or needs medical care: such a person needs an adult with them at all times. If the person you watch over is struggling to breathe, turns blue or goes limp, call your emergency number.
What is kept, and where
| Data | Where it lives | How long | Does it leave your home? |
|---|---|---|---|
| Live video and sound | Streamed from the monitor unit to the viewer unit, only while you ask | Not stored | On your home network: no. When you are away: through a relay, still encrypted from phone to phone |
| Recorded clips | Only on the monitor unit, in the app's private storage (in a browser, the browser's own storage), and never uploaded | Without MeiMei Home or MeiMei Away nothing is saved. With Home or Away, up to 30 nights or 2 GB, whichever comes first | Only a clip you choose to save to your photos |
| Events, nights and sleep reports | On the phones. Without MeiMei Home or MeiMei Away they are only shown while a session runs, then dropped | With Home or Away, up to 30 nights | Never |
| Pairing secret | The secure storage of both phones (Keychain on iPhone, Keystore on Android) | Until you pair again | Never |
| Browser sign-in (only if you sign in in a browser): one refresh token, and for alerts a key derived from the household key | This browser's own storage (local storage and IndexedDB), on that device only, never a cookie | Until you sign out (signing out revokes the token) or turn alerts off | Never. The key cannot be extracted and neither is sent to us |
| Account email | Amazon Cognito | Until you delete your account | Yes, it is the account. Needed for alerts to a locked phone and for remote viewing |
| Device registry: device id, hashed household id, role, phone type, device name, language and push address (for a browser with alerts on, its Web Push address), and whether the unit is a companion screen | Amazon DynamoDB | While the device is registered. A Web Push address goes sooner, as listed under "Alerts to a browser (Web Push)" | Yes, for alerts and remote viewing |
| Purchases: your plan (Home or Away, both subscriptions, with 7 days free once per account, plus any extra devices), the Stripe subscription and customer ids, the dates it started and renews, which account pays for it and, for the free week, which part of the app it was started from | Amazon DynamoDB, with the household's id | Until you delete your account | Yes, only if you buy a plan and are signed in. Stripe and our servers can see it. Payment itself is handled by Stripe, and we never see card details |
| Connection records: connection id, room, device id and the network address the connection came from | Amazon DynamoDB, with an automatic expiry | Expire after 2 hours (signed-in connections) or 10 minutes after the last message (no-account browser connections), and are deleted automatically soon after | Yes, only while you use remote viewing, alerts or the no-account mode in the browser |
| Rate-limit counters (how often a household or network address connected, and how often a device asked to tell others that a message is waiting) | Amazon DynamoDB, with an automatic expiry | Minutes to three days, then deleted automatically | Yes, only when the cloud is used |
| Messages between your phones and alert pushes | Pass through Amazon API Gateway and AWS Lambda | Not stored. Encrypted with your pairing secret, so the cloud sees only ciphertext. Our servers do see the household and device ids, the time and how urgent an alert is, which they need to deliver it. A notice that a message is waiting names the device that wrote it, the devices to tell and the time, and has no words in it. | Yes, only when the cloud is used |
| Server logs | Amazon CloudWatch | 14 days | Yes. Request ids and timings only, never message content, tokens or video |
| Birth month (optional) | On both phones, as birth month and year | Until you change or delete it | Never |
| Telegram alerts (only if you connect your family's own bot) | The bot token and the chat ids stay on your devices: in full on the monitor unit, and on the viewer phone only the bot's name and the chat names. Never in our tables | Until you disconnect Telegram, remove the monitor unit or delete everything | Yes, to Telegram: the monitor unit sends the alert text straight to Telegram's servers. Text only, never pictures or sound, and bot chats are not end-to-end encrypted. For a companion screen the text can describe what the screen noticed about a person |
| Phone number for call alerts (only if you enter one) | Amazon DynamoDB, on the record of the viewer phone it belongs to, exactly as you typed it. Nothing checks it: the number must be your own, and ringing a number that is not yours closes the account | Until you tap “Remove number”, remove the device or delete everything | Yes: our servers ring it through Amazon Chime when an urgent alert goes unanswered, and for the test call. Nothing is said on the call |
| Call log (the number rung, the device, the account that set it, the time, the reason, the outcome) | Amazon DynamoDB, one record per call our servers place | 90 days, then deleted automatically; deleted with your account | No. It is kept so a number rung that is not the user's own can be traced and the account closed |
| Consent log (what the screen asked, who proposed it, who answered, as the person or as a representative, the answer and the time) | On the companion screen. Viewer devices the person agreed to tell keep read-only copies of the latest entries. Never in our tables | Until the home is deleted from the screen | Only as those read-only copies, to the viewer devices that were told |
| Events about a person at home (what the screen noticed and when, and the answers to its “Are you all right?” check), which may reveal something about their health | On the companion screen only | 14 days or 500 events, whichever is smaller, on every plan | Only as the alert for an event the family should hear about, to the viewers who were told and to Telegram if connected: ciphertext for push, and nothing stored on our side |
| Video-call picture and sound (a call the person answers or has allowed) | Directly between the companion screen and the viewer device, encrypted. When they cannot connect directly, through a relay that carries only encrypted data | Not recorded and not stored | Between the two devices only |
| Optional viewer photo, and the person's name, language and usual getting-up time | On the companion screen only. The photo is sent there from the viewer device that took it, and that device keeps its own copy | Until the person or the helper removes it, or the home is deleted | Only to the viewer devices that were told, for the name and the “up today” line |
| Messages between family devices, and to and from a companion screen, with the person's answers | On the viewer devices that sent or received them, and on the companion screen for a message sent to it or by the person. A message that cannot go yet waits on the device that wrote it, never on a server. They travel only over the encrypted connection between your devices, through a monitor unit that keeps nothing | Waiting: up to 20 per person, for up to 7 days, then given up. On a viewer device up to 200 per conversation for 30 days; on a companion screen the last 20 for 14 days, and the person's own messages for 14 days after they finish; or until you delete everything | Only between your own devices, encrypted, sometimes through a relay that carries only encrypted data. Never stored on our side. A waiting message can make our server send the other phone one notice with no words in it (see “Alerts to a browser (Web Push)”) |
Alerts to a locked phone
When your phone is locked, alerts arrive as push notifications through Apple or Google. The notification text is encrypted with your pairing secret before it leaves the monitor unit. Apple, Google and Amazon carry only ciphertext and a generic "MeiMei alert" title. Your phone decrypts it and shows the real message.
No account, in the browser
You can use MeiMei on two devices in a browser, with no install and no account. Browsers cannot find each other on a network, so the two devices meet through a small relay: either our cloud relay, or a program you run on a computer at home so that nothing leaves the house. The cloud relay sees a room code (a scrambled household id), device ids, timing, the network address of each connection and encrypted messages. It does not see video or sound: those travel directly between the two devices. The browser session lasts as long as the devices stay connected, and the room is removed shortly after the last device leaves. In this mode nothing is saved. It needs the browser tab open and the screen on, and it cannot alert a locked phone.
Signing in, in a browser
A browser can sign in to the same account as your phones: with an e-mail one-time code, with a password where you set one, or with a passkey where passkeys are switched on. Once signed in, the browser can be a monitor unit or a viewer device in your household, mixed with phones, through MeiMei's cloud relay. It is the same end-to-end encrypted relay the phones use: video and sound still go directly between the devices, never through MeiMei's servers, and clips never leave the monitor unit.
To keep you signed in, the browser keeps one refresh token in its own storage, not in a cookie, until you sign out. Signing out revokes it. The no-account mode above is unchanged: nothing is sent to an account and nothing is saved.
On the website you can also choose "Continue with Google". Google then confirms your e-mail address to us. We ask Google for nothing else (no name, no picture) and keep the address and the id of your Google account, which links it to your MeiMei account, in Amazon Cognito until you delete the account. Google learns that you signed in to MeiMei, under its own privacy policy. If your address already has a MeiMei account, signing in with Google opens that account. The phone apps do not offer this.
Alerts to a browser (Web Push)
You can switch on alerts for a browser that is signed in, only by tapping a button and accepting the browser's permission question. The browser then creates a push subscription with its own push service: Google (Chrome, Edge, Brave and other Chromium browsers use Google's service), Mozilla (Firefox), Apple (Safari, and the Home Screen app on iPhone and iPad) or Microsoft (Edge on Windows may use Microsoft's service). Your browser chooses the service, and no data goes to anyone else.
A push subscription is an address (a web address at that service plus two public keys) that lets our server send that one browser a message. We store it with the device record, in the same table as phone push tokens, as the push address of that device, in AWS (us-east-1, Lambda and DynamoDB, as for the phones).
The push services only ever carry ciphertext. The alert is encrypted on the monitor unit with the household key, which neither MeiMei's servers nor the push services have, and the push is encrypted again for that browser, as the Web Push standard requires. A service worker in the browser decrypts it with a key derived from the household key, kept in that browser's own storage (IndexedDB), on that device only, as a non-extractable key. If anything fails to decrypt, the notification carries only the generic "MeiMei alert" title. As with Apple and Google for phones, a push service sees the subscription address, the time, the size and our server's address, not the content. The service worker only handles push messages and notification clicks: it caches nothing and intercepts no requests.
A notice that a message is waiting. When a family member's phone, or a companion screen, has a message for you that has not gone through yet, and your browser has alerts switched on, our server sends your browser one push that says only that a message is waiting, and from which device. Unlike an alert, this push is written by our server, because it carries nothing of the message: no word of the message, no kind of message, no message id and no count. All it names is the sending device, by its random id, and whether the message belongs to the Family conversation or to a companion screen's. It is encrypted for your browser, as the Web Push standard requires. The message itself stays on the device that wrote it and travels, encrypted, when both devices have MeiMei open. A message to a companion screen never causes a push.
What our server learns is that one device (named by its random device id), in one home (named by a scrambled id), asked at a given time to tell other devices of the same home that a message is waiting. It learns nothing else: not what the message says, whether it is a typed message or a ready-made one, nor whether or when it is delivered or read. It keeps no record of the request except a counter for the sending device: its random device id, a ten-minute period and how many requests it made in it (at most 30). The counter expires 10 to 20 minutes after the request and is deleted automatically soon after. The server's logs hold, for 14 days, the request id, the route name, the result, the duration, a scrambled home id and how many devices were named and reached; no device id, account, e-mail address, network address, word or request body.
The push service of your browser carries the push for up to half a day if your phone is off. It sees your browser's push address, the time, the size and a label made of “msg-” and the sending device's random id, which lets it replace one sender's waiting pushes with a single one. It cannot read the rest. The notification is written on your phone, in your language, with the same words for every message and the sender's name if your phone knows it from the family names it already keeps for MeiMei.
On iPhone and iPad this works only with iOS 16.4 or newer, and only for MeiMei added to the Home Screen. Alerts are always free; a free account is enough.
A push subscription is deleted when:
- you turn alerts off in the app,
- you sign out,
- you remove the device,
- you delete everything, or your account,
- or the push service reports it expired or invalid, and we then remove it.
Wi-Fi network names (optional)
If you turn on “Show Wi-Fi names” in Settings (phone apps only), the system asks for location access, because it requires it to read the name of the Wi-Fi network. MeiMei uses that access only for the network name: it does not read, store or send your location. The monitor unit sends its network name to your paired devices over the encrypted link, never to our servers, and nothing is stored. The switch is off until you turn it on, it is never asked for at launch, and everything works without it. Browsers cannot read the network name.
Cookies and analytics
The website and the app use no cookies and no analytics. The app keeps its settings, and in a browser the pairing secret of that browser, in the browser's local storage. If you sign in in a browser, it also keeps the sign-in token there, and for browser alerts a key in IndexedDB. That storage is strictly necessary for MeiMei to work, it is never sent to us, and it is not used to track you.
A companion screen for someone at home
A companion screen is a tablet or phone left with an adult at home, so that their family can call them and be told when the screen notices something that needs attention. The adult decides what it does.
- How the screen starts. How the screen starts depends on how it is set up. If the helper sets it up step by step, nothing is switched on until the person says yes to it on the screen. If the helper chooses the recommended settings, the screen starts listening when it is handed over, before the person has been asked: for a smoke alarm, calls for help and long coughing, and for being touched, moved or dropped (on an iPhone browser, not movement until the person says yes). The screen tells the family devices that were paired when it was handed over: they get the alerts for those items, marked as not confirmed. The screen says so aloud and shows it until the person has answered. It then asks the person about each of these, between one hour and a day after the hand-over, and every morning after that until the person has answered. A no switches that item off at once. If nobody has answered three days after the hand-over, the screen switches off the listening that is still on without an answer, at once, and sends the family devices it tells a notice that says so. A family device that was told only since setup stays told until that notice has been sent, and for one minute after that; then it is told nothing again until the person says yes. If the screen is closed or has no connection at that moment, the notice is sent when the screen is open and connected again; if its quiet hours are running, when they end. In a home without an account, where nothing is sent to a closed app, such a device stays told until it has received the notice while connected to the screen. The listening that was switched off stays off in the meantime, and the screen says that the family has been told only once the notice has been sent. What the person said yes to stays on. Nothing is recorded as agreed until the person has said yes, and nobody can connect to the screen without the person answering until the person has agreed to that.
- The person is asked, aloud and in writing. Each thing needs an explicit yes on the screen itself, from the person or from someone who may decide for them.
- Who answered is recorded, not checked. The person answers, or someone who may decide for them. The screen records which, by role and not by name. It cannot verify who is holding it.
- Later changes wait for a yes. A new family member who wants to be told, a Telegram chat and the link to an account all wait for the person's yes on the screen. The only exception is the set of family devices paired when the screen was handed over, when the recommended settings were used, as described above. A device paired after the hand-over is told nothing and cannot call the screen until the person says yes. A family device that was paired when the screen was handed over can send messages to the screen before the person has said yes: the screen shows them and reads them out. Until the person's yes such a device cannot send photos or a status.
- Sound stays on the screen. Sound is analysed on the screen and discarded. Nothing is recorded, and no sound is sent anywhere. Only words leave, such as the text of an alert. A phone-call alert rings and says nothing.
- Picture and sound only in a call the person answers or has allowed. The person can agree beforehand that a family member the person chose may connect without an answer, after an alert the person did not answer or at any time. Both stay off until the person says yes on the screen. Before any picture or sound, the screen sounds a chime, speaks and counts down five seconds, with a large Stop button. The call goes directly between the screen and the viewer device, encrypted, and is not recorded. When the two cannot reach each other directly, a relay carries it, and the relay sees only encrypted data.
- Family learn only that the day began. Viewers see “up today” or “not up yet today”, never the time.
- Pausing is as easy as agreeing. The person can pause at any time with one yes on the screen, and can withdraw consent as easily as they gave it. A pause stops all listening and motion detection, including the smoke alarm.
- A closed screen. If the screen is closed, it sends one short notice to the family who were told, with nothing from the home in it. It never rings a phone.
- Messages from the family. A family member can send the screen a short message. The screen shows it, reads it aloud and keeps the last 20 for 14 days; the person answers with one of four fixed replies, which go back to the family. Messages travel only between the devices, encrypted, and are never stored on our side. A message or an answer never changes what the screen is allowed to do.
- Messages from the screen. The person can send the family one of six ready-made messages, such as “Thinking of you” or “Please call me”, to one family member or to everyone: one touch to choose and a second to send. Nothing is typed. “I need help with something” is a message only: it calls no one and starts no check. The screen keeps what it sent, and whether it was delivered and seen, for 14 days after the message finishes (200 at most).
- A message waits where it was written. If the other device is not connected, a message waits on the device that wrote it, for up to 7 days, and goes when the two connect. It never waits on our servers. A family phone with MeiMei closed can get one notice that says only that a message is waiting (see “Alerts to a browser (Web Push)”). Between two family phones, a message goes when both have MeiMei open at the same time.
- Who is here. A family member the person agreed to tell can let the screen show whether they are available, busy until a time (at most 7 days ahead) or away, and whether their phone will ring. The screen shows only a word such as “here now”, “phone will ring” or “busy until 5:00 PM”. It keeps no “last seen” time, other family members do not see it, and it goes only over the encrypted connection to the screen, never to our servers. A family member can switch it off on their own phone, and then the screen shows only whether a call can reach them.
- Photos from the family. A family member the person agreed to tell can send the screen a photo, made smaller on their phone first (about 200 KB). The screen keeps the newest 30 for up to 30 days, with the sender's name and a short caption, and shows them one at a time on the clock screen by day, unless the person or the helper switches that off. They are pictures the family chose to send, not pictures of the person, and they never leave the screen. The person can remove one on the screen, and the sender can take back their own. A family member's photos go when the person says no to them, when their device is removed or when the home is deleted. After “Set this device up again” they are held out of sight for up to 30 days, and come back if the person says yes to that family member again.
- Planned calls. A family member can plan a call for a later time. The screen keeps the plan until half an hour after that time and says “Ana will call at 6:00 PM” or “Ana will call soon”. It is a reminder: it starts no call. Plans follow the same rules as photos when the person says no to a family member.
- A copy of what the screen keeps. The helper, behind the helper PIN where one is set, can save one file with what the screen keeps: the answers the person gave, the family's names, what the family was told, calls, messages, planned calls, photos and settings. It goes only to the device's share sheet or downloads; MeiMei sends it nowhere and keeps no copy. It holds no PIN, key, token or network address. Once saved it is the helper's file: MeiMei cannot take it back, and “Delete everything” does not reach it.
What the screen notices, such as a call for help, a loud thud or a long stretch of coughing, can reveal something about a person's health. It is kept on the screen only: see the last rows of the table above. A companion screen is not an emergency alarm. It can miss things, and a message can arrive late or not at all. In an emergency, call your emergency number.
The data of the person you watch over
Video and sound of a person at home are sensitive personal data, even when they never leave the phones. MeiMei keeps them on your devices, protects the pairing secret in the phone's secure storage, and streams live pictures only while you ask for them.
A pet unit, in particular
A pet unit is a room unit that is set up to watch a pet. It works as a room unit does: sound is analysed on the unit, nothing it hears is sent anywhere to be analysed, and clips, where a plan includes them, stay on the unit. It listens for more kinds of sound, such as barking, howling, whining and meowing. Its microphone also hears the people at home, such as visitors, a sitter or neighbours through a wall, and its clips can hold their voices and picture. While it watches, the unit's screen is dark, so nothing on it shows that it is on. Tell the people who are in your home, and anyone who comes in, that the unit can see and hear and, with a plan that includes clips, save clips.
A camera unit, in particular
A camera unit is a room unit that you watch and control from your phone. Other people may be in its picture and in its clips, and its microphone hears them. The unit's screen says that the camera is on and shows when someone is watching, listening or talking, so the people there can tell; tell them too. Live picture and sound go between the unit and your phone only while you ask for them. Our servers never see the picture or the sound and do not store them, and a clip stays on the unit, encrypted. Do not point a camera unit at a place where people do not expect to be seen or heard.
Who else is involved
- Amazon Web Services hosts the account, the device registry, the relay and this website.
- Apple and Google deliver push notifications to phones, as ciphertext. For a browser with alerts switched on, the push service of that browser does: Google, Mozilla, Apple or Microsoft, as ciphertext.
- Google, only if you choose "Continue with Google" on the website: it confirms your e-mail address to us and learns that you signed in to MeiMei, under its own privacy policy.
- Stripe processes payments, and Link, Stripe's checkout, is the seller: it collects VAT, sends receipts and invoices and answers questions about a payment. When you buy a plan, we give Stripe your account's e-mail address and random ids that link the purchase to your home and your account; Stripe also gets what you enter on its page (name, address, payment details) and what you bought, under its own privacy policy. Our servers keep the plan, the Stripe ids, the dates and which account pays. Deleting your MeiMei account cancels the subscriptions it pays for.
- Nobody else. MeiMei has no analytics, advertising or crash-reporting services, and it does not sell data.
The MeiMei team can look up an account's e-mail address, devices, plan and phone-call log in a private admin console, to answer support requests and handle misuse. Phone numbers stay hidden there unless we open them for a specific case, and every change and every look at a number is logged.
Where the servers are
MeiMei's cloud runs on Amazon Web Services in the United States (us-east-1, N. Virginia). Personal data sent there (account email, device registry, purchases, connection records) is transferred outside the EU under the EU-US Data Privacy Framework, in which Amazon Web Services participates, and the Standard Contractual Clauses in AWS's data processing terms. Video, sound and clips never go there.
Why we may use your data
To provide the service you asked for (your account, alerts to a locked phone, remote viewing and your plan), because we need it to keep our contract with you. To keep the service safe and working (rate limits and short server logs), because we have a legitimate interest in doing so.
Your rights
You can ask for access to your data, correction, deletion, restriction, a portable copy, and you can object to how it is used. Write to support@meimeimonitor.com; we answer within one month. You may also complain to the Romanian data protection authority, ANSPDCP (Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal, www.dataprotection.ro), or to the authority where you live.
Your choices
- Delete everything. In Settings, "Delete everything" wipes both phones and deletes your account, your registered devices, your connection records, your plan and order records and your household's video channel from our servers.
- Use it without an account. Watching and alerts on your home Wi-Fi, or between two browsers, need no account. The account is for alerts to a locked phone or a browser, and for remote viewing.
- Turn browser alerts off, or sign out. Either one deletes that browser's push address from our servers; signing out also revokes its sign-in.
- Ask us. To see or remove anything we hold about you, write to the address on the support page.
Who the app is for
MeiMei is for adults watching over their loved ones. It is not meant to be used by minors.
Changes
If this policy changes, this page changes, and the date below with it. Translations (machine drafts that still need legal review) are linked below; if they differ from this page, the English text applies.