Privacy Policy
Effective: 3 November 2026.
Replaces the version effective 18 October 2026. What changed: section 5 now says what removing a line Melelem remembers about you does, and what it leaves in place; and section 11, which is new, covers the Melelem companion: what it reads, what it sends and what we keep. The 18 October version replaced the version effective 17 October 2026. It named Microsoft among the processors in section 4, and said in section 5 how to delete your account the way the terms do. The 17 October version replaced the version that went live on 24 September 2026. It changed section 1 to name every way to sign in, not Google alone.
This explains what Melelem collects, why, and what control you have. The data controller is Melelem, Inc., a company incubated by Fountech.ai Limited (“we”, “us”). Contact: legal@melelem.ai.
1. What we collect
Your account (app.melelem.ai): you sign in with Google, with Microsoft, or with a link we email to you. We receive your email address, and your name when you sign in with Google or Microsoft, and we store the email and the sessions tied to it. Nothing else, no tracking pixels, no ad tech.
Your content: conversations, material you add as context, writing you provide to train your personal model, and the model’s outputs for you.
Handoffs: when you send or receive work, the shared package (the items you confirmed) and the messages added to it.
Connectors: if you connect services like Notion or Linear, we store the access tokens encrypted and request the narrowest scopes that make the feature work. We access connected data to do what you asked and not otherwise.
Model calls: every call to a model provider runs on Melelem’s own keys. You do not add provider keys, so there are none of yours for us to hold.
Technical basics: logs needed to run and secure the Service (timestamps, IPs, errors). No advertising analytics on the site.
2. Why we process it
To provide the Service you asked for (contract): running your conversations, training your personal model on your writing, executing handoffs you confirm, operating connectors you enabled. To keep the Service secure and debug it (legitimate interest). To contact you about the Service at your account email (legitimate interest, and consent where required; every non-essential email has an opt-out).
3. What we do not do
We don’t sell your data. We don’t show ads. We don’t use your content to train any model but yours: training is per-account, and what your model learns from you serves only you. The router keeps shared scores of how well each model does, which hold none of your content and name nobody. Handoff content goes only to the people you explicitly confirmed.
4. Who processes data for us
We use a small set of processors to run the Service: Vercel (website and app hosting), Fly.io (application gateway), Tigris (backups of the gateway’s data), Amazon Web Services (the server your personal model runs on, and its storage), OpenRouter (model routing, and the route every outside model call made for your requests takes), Google (sign-in, and Google connectors you enable), Microsoft (sign-in), Stripe (payments), and Resend (transactional email). Where these processors handle data outside the EEA, transfers rely on recognised safeguards such as the EU-US Data Privacy Framework or standard contractual clauses. The model makers OpenRouter reaches for us may be in any country, under their own terms. Other connectors you enable are reached at that service, under your own account with it.
When your request consults an outside model, the content needed to answer it goes through OpenRouter, which reaches that model on our behalf. The catalogue it reaches runs to several hundred models across many makers, so the maker is whichever one the routing chose for that part of your request. Every request for a written answer asks OpenRouter to use only providers whose published terms say they do not train on what they are sent, and none is sent any other way. That is a rule about training, not about storage: a provider may keep a request for a time under its own terms, for example to check it for abuse. A request for a picture goes to the picture provider OpenRouter chooses, under that provider’s own terms.
5. How long we keep it
Account data and content: for the life of your account. You can delete your account yourself in the app’s settings. If you cannot sign in, write to legal@melelem.ai and we will delete it for you. A deletion request is honoured within 30 days.
What you ask Melelem to remember: the lines it keeps about you are listed in the app’s Steering panel, under What I remember about you, and you can remove any of them there. Removing a line takes it off that list, so it is no longer carried into your conversations. It does not take the words out of the conversations that hold them, or out of what your personal model has already been trained on, and it does not reach a copy outside your account, such as work you handed to someone else or a request a model provider has already received.
Backups: the Service’s backups keep 14 days of history. What you delete, including your conversations and any pictures you generated, can stay in them for up to 14 days after it leaves the Service.
What a deletion does not remove, and why:
- your invoices and any chargebacks on them, because accounting records are kept by law;
- a record that you asked to be deleted, holding your address, the dates, how the request reached us, which connected services were disconnected, a count of what was removed and the error from any step that failed, because it is how we show the request was honoured;
- a line holding your address that stops your old sign-ins working again;
- your unsubscribe from our emails, if you gave one, so you are not put back on a mailing list;
- work you handed to someone else, which lives in their account like a delivered email. It is no longer linked to your account, though anything you wrote in it stays as written;
- the shared scores of how well each model does, drawn from everybody’s use, which hold none of your content and name nobody.
Some copies are out of our reach: Stripe keeps its own record of your payments, and emails we have already sent stay in your inbox and in our email provider’s sending record.
Logs: short rotation, weeks not years. Operational logs can carry your address until they rotate out.
6. Your rights
Under the GDPR you can ask for access, correction, deletion, restriction, portability, and you can object to processing based on legitimate interest. Write to legal@melelem.ai. You can also complain to your local data protection authority.
7. Cookies
melelem.ai sets no advertising or analytics cookies. app.melelem.ai uses strictly necessary cookies only: a session cookie that keeps you signed in. That’s the list, which is why there’s no cookie banner.
8. Security
Content in transit is encrypted (TLS). Connector tokens are encrypted at rest. What your browser sends to a computer running the Melelem companion, and what that computer sends back, is sealed end to end, so our servers pass it on without being able to open it (section 11). Access to production systems is restricted. No system is perfectly secure; if a breach affects your data we will notify you as the law requires.
9. Children
The Service is not directed at children and requires users to be 16 or older.
10. Changes
We’ll post any changes here with a new effective date, and flag material changes in the app.
11. The Melelem companion
The companion is a program you can download from app.melelem.ai and run on a Windows computer, so Melelem can work with files in folders you choose there. It is an early version: it is not yet code-signed, and it has not been independently audited.
What it can reach: only the folders you share with it on that computer, unless you change its setting there to reach your whole user folder or the whole computer, which we advise against. It never reaches its own key files, and it cannot run programs, scripts or commands. A file it saves can still be opened or run later by Windows or another program, for example one saved in a folder that starts programs when you sign in, so do not share such a folder.
What it does without asking: it lists, reads and searches files in a shared folder without asking you each time. Treat anything in a shared folder as something Melelem can see. Before it saves, moves or deletes a file it asks you on that computer, and it does nothing unless you say yes within 20 seconds.
What it sends, and where: today the app asks it for two things: to save an answer as a file where you said, and to list a folder you named. The request is read from your own message, which is kept with your conversation like any other message. When you ask Melelem to save an answer, your message, including the path you named, goes to the model providers in section 4 like any other turn, and the text saved is that answer, which we keep with the conversation. What your computer sends back, such as a folder listing, is sealed so only your browser can open it: we do not store it and it is not sent to a model. If you then put anything from your computer into a conversation, it is handled like the rest of your content. The companion connects to app.melelem.ai and melelem-beta-gateway.fly.dev, and pairing and staying connected leave the same technical logs as using the app (section 1).
What we keep: for each paired computer, any name you gave it, an identifier and public key for it, a one-way hash of the token it connects with, the account it belongs to, when it was paired, last connected and cut off, and the details of each pairing. For every turn you take in Melelem, whether or not you use the companion, a record of whether its instruction came only from you or also from a document, connector or shared work, and how many times it was used to reach your computer; and for every conversation, whether it has ever carried such outside words. The companion checks this before it acts. A turn’s record that marks nothing is deleted once it is more than 7 days old, when our servers next restart; the rest stay until you delete the conversation or your account. We never hold the files your computer reads, or the listings it sends back. Deleting your account deletes all of these records.
What stays on your computer: in the folder .melelem\companion in your user folder, the companion keeps its keys, sealed with Windows’ own protection, the list of folders you shared, and a journal of what it did: each action and the paths it touched, the account it is paired to, the conversation and turn each request came from, what it refused, the folders you shared and took back, changes to how much it may reach, and when its connection dropped. The journal never holds what was in a file. Melelem does not ask for it. The browser you paired from also keeps a key for that computer, until you press Cut off in that browser.
Stopping it: press Ctrl+C in its window, or close the window, to stop it. Pressing Cut off in the app stops that computer connecting to your account. Running the companion’s revoke command on that computer does that too, and also erases the keys it was paired with and forgets the folders you shared; if it cannot reach us at that moment, the app may still list the computer until you press Cut off there. To remove it, delete the program and the .melelem folder. Deleting your account does not reach that computer, so do this too.
Contact: legal@melelem.ai