Last updated: 14 November 2026
Your context. Your choices.
This policy covers the me.md website, waitlist, and beta product: personal profiles, private context, agent connections, messages between members, the member directory once it opens, and email features when enabled.
Who is responsible
ONLIN’IN, 236 rue André Philip, 69003 Lyon, France (RCS Lyon 849 167 705), is the controller of your personal data. Contact us at [email protected].
Your account and sign-in
We process your email address, verified sign-in identity, username, session information, and the information you choose to provide to create and operate your account. Email sign-in links are delivered through Emailit. Google sign-in, when available, verifies your identity and email address. Signing in with Google does not authorize access to your Gmail inbox or sending email.
You can also sign in with GitHub, X or Facebook when those buttons are shown. When you do, the service sends us your basic profile: for GitHub your public profile (such as your username, name, bio and location), for X your name and username, for Facebook your name. We keep only your account ID with that service and your email address (for GitHub its verified primary email, for X the email you confirmed with X), plus your name when it creates your account. We use them only to sign you in. We do not keep the access tokens that Google, GitHub, X or Facebook give us at sign-in. We never post, follow, send messages or read your content on these services, and we do not keep your profile picture. A Facebook account signs in only after you connect it from your signed-in me.md account, with the same email address. You can remove me.md’s access at any time in the security or app settings of each service.
Your profile, context, and agents
We store the profile, projects, contact channels, photos, preferences, and context you save. When you claim your name, your page is published with your name; if you fill it from a GitHub username, that public headline, location, projects and link are shown too. The member directory is not open yet (coming soon): your choice to be listed in it is set to yes when you claim your name, and is kept for when it opens. While that choice is on, search engines may index your page. You can unpublish the page or change that choice at any time. Each field has its own visibility, and everything else you add starts private. Publishing a public field makes it accessible on the web, including through the public Markdown and JSON representations of your profile. Public information may be indexed or copied by others.
Private context is shared only through the permissions you grant to connected agents. Agent keys and OAuth connections can be restricted and revoked. If you give an agent permission to edit your page or save your preferences, it can make those changes when you ask it to: page edits, preferences picked from the options we offer, and short private notes. We record which connection made each change and when; you can undo any of them, or turn direct saving off so that each change waits for you. Notes saved by an agent are never shown on your page. Suggestions from agents without that permission do not change your context until you approve them. Importing context requires your review before it is saved. The service does not need your complete assistant chat history; avoid importing sensitive information you do not want to store here.
Your chosen AI or agent provider receives the information you authorize it to access and applies its own policies. Revoking a connection prevents future access; it cannot remove copies already obtained by that provider.
Public lists
A published page also appears on me.md’s public lists: the latest pages (me.md/new, and short notices on the homepage) and the most visited pages (me.md/leaderboard, and its top five on the homepage once enough pages have visitors). The lists show only what your page already shows publicly: your name, username, headline, up to two areas, your photo, when your page appeared and, on the leaderboard, how many visitors were counted for it. They are also available to programs and agents through the me.md API and MCP tools. A page is listed one hour after it has a public name, a public headline and a public way to reach you, and ranked once its account is seven days old.
The switch “Show my page on me.md’s public lists” is on by default; you can turn it off when you claim your name or at any time in Settings, and your page leaves the lists within a minute while staying online. We may also take a page off the lists to prevent abuse. We rely on our legitimate interest in helping members’ pages be found; the switch is how you object to it, and you can also write to us.
Email connections and messages
me.md is currently receive-only: outbound email is not offered, and no sending provider can be connected. The following two paragraphs describe a sending option that is switched off and would apply only if it is introduced later.
Sending is optional and requires a separate provider connection and review. You may connect Gmail, Microsoft, SMTP, Resend, AgentMail, Emailit, Amazon SES, or Cloudflare when that integration is available. We store connection metadata and encrypted credentials or authorization tokens to submit messages you approve. The connected provider processes the message contents, addresses, and delivery information under its own terms.
Connecting Gmail for sending is separate from Google sign-in. It requests sending permission and identity information; it does not import or read your Gmail mailbox. You can disconnect the provider in Email senders and revoke its authorization in your Google or Microsoft account. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Mail received at your me.md address is processed through Cloudflare and stored for seven days with its headers, text, sanitized HTML, and attachments. We automatically extract verification codes, links, and amounts from each message so agents can use them without reading the full text; this extraction runs on our servers and uses no AI model or third party. Connected agents can read mail only if you grant inbox access, and messages from senders you have not trusted are withheld from agents until you release them. External images are blocked in the inbox viewer. Agents can prepare drafts when authorized; sending still requires your approval and the applicable account and provider checks.
Members can also write to each other at their me.md addresses. These messages stay inside me.md: they are never sent as email and pass through no email provider. A first message is a request that only its recipient can accept, by replying, or block; the sender is not told about a block, and no read receipts are shown. Connected agents can read your messages from other members only with inbox access, and can write to members only with a separate grant you give them. Messages from other members are kept for seven days and their contents are left out of backups.
Activity records
To run the beta, fix problems and prevent abuse, we keep a record of the steps taken on each account: for example signing in, finishing a setup step, saving or publishing the page, creating or revoking an agent key, an agent connecting or calling a tool, and receiving or sending a message. Each record holds the step, its time, the account’s name, username and email address, and short details such as which fields changed or how many recipients a message had. It never holds message contents, context text, keys, tokens or passwords. When you join the waitlist or ask for a sign-in link before you have an account, we record that step with your email address in the same way. The operator receives these records in the operator dashboard and as notifications in a private Discord channel.
Page statistics
We count visits to public member pages so each member can see how many people and AI agents read their page, where visitors came from and which of their links were opened, and to show the public ranking of the most visited pages (see Public lists), which members can leave. The ranking counts unique human visitors per day, never agent reads, leaves out visits that come from the ranking itself, and counts a single day for at most three times the page’s usual day plus 50. We set no cookie for this and store no IP address. A visit is counted only when the page is actually shown in a browser: prefetched and prerendered pages, programs, automated browsers and the member’s own visits are left out.
A visitor is identified only by a code computed from the network address and the browser, with a key that changes every day and is deleted as soon as that day is over, and separately for each member page, so nobody can follow a visitor from one page or one day to the next. With each visit we keep that code, the time, the country (from the network, never from a location request), the device type, the browser and system family, the site you came from (its name only, not the page), and the campaign word of the page address (utm_source or ref). A click on a contact link or a project of the page is counted the same way, with the kind of link (for example “email” or the website’s name), never its address or number. Web links on member pages carry ref=me.md, so the sites they lead to can see that you came from me.md. Reads of a page’s Markdown and JSON versions are counted separately, with the name of the program that read them (for example ChatGPT or a crawler), and a member’s own agents reading their profile are counted for that member.
Detailed records are deleted after 90 days and daily totals after 25 months; to limit abuse, keyed hashes of the network, and of the network with the browser, are kept for 48 hours. Members see only totals and lists, never an individual visitor. To opt out, turn on Global Privacy Control or Do Not Track in your browser, or use the button below; nothing is then counted for your visits.
Email lists members collect
A member can add a sign-up form to their page, or a sign-up page at me.md/<name>/collect, so visitors can leave their email address to get updates from that member. If you sign up, the member is the controller of your address: they decide to collect it and write to you from their own email tool. ONLIN’IN keeps the list for them as their processor, on their instructions and under our terms, and never writes to it, sells it or uses it for anything else.
With your address we keep the member it was given to, the form you used, the time, the consent line shown to you and its version, and a keyed hash of your network address, as proof of your consent and to prevent abuse. When confirmation emails are switched on, we send you one email asking you to confirm, from a sender kept for this purpose and separate from sign-in emails; an address not confirmed within 7 days is deleted, and only a keyed code of it is kept for 30 days so it is not sent another confirmation in that time. The member can see, export and remove the addresses on their list, and so can the agents they allow to.
You can leave a list at any time with the private link shown when you signed up, or after you confirmed, by asking the member, or by writing to [email protected]. When you leave or the member removes you, your address is deleted from the list and only a keyed code of it is kept so the forms do not add it again. When one of the member’s agents removes you, the address is set aside for 30 days so the member can undo the removal, then deleted the same way. Addresses on a list are deleted when the member deletes their account. Copies the member exported are theirs to delete.
Why we process this information
We use account and product data to provide the services you request. We rely on our legitimate interest in operating a secure service for abuse prevention, rate limits, access records, directory lookup records once the directory opens, and manual sending reviews, in showing published pages on the public lists as described under Public lists, and in measuring the audience of member pages for their members as described under Page statistics, within the limits the CNIL sets for audience measurement exempt from consent. Waitlist and launch updates are based on your consent, which you may withdraw at any time. We may also retain information needed to meet a legal obligation.
Retention and deletion
Profile and context data remain until you change them or delete your account. Received messages and attachments become inaccessible seven days after receipt and are queued for deletion. Draft and sent message contents expire after seven days; submission and abuse-prevention metadata may remain while your account is active. Messages between members are deleted seven days after they are sent; whether you accepted or blocked a member is kept until either account is deleted. Deleting your account deletes your conversations for both members. This inbox is not a permanent email archive.
Deleting your account deletes the statistics of your page: its daily totals at once and its detailed records within minutes.
Deleting your account revokes access, closes its inbox, removes account records, and queues stored files for deletion. We retain a minimal deletion record to prevent deleted data from being restored, and retired usernames are not reassigned. Backups may retain deleted records for up to 30 days; they are used for recovery, with deletion requests reapplied after restoration.
Activity records are deleted after 180 days. When you delete your account, the email address is removed from its activity records, including the sign-in link requests made before the account existed; the steps themselves remain until they expire, without your email. When you leave the waitlist, your address is removed from its waitlist records at once. Notifications already delivered to Discord are kept by Discord until the operator deletes them.
Waitlist registrations expire after 12 months or are removed earlier when you unsubscribe. Short-lived waitlist security counters are removed after 48 hours. Download your account export or any email attachments you need before deleting your account or before those messages expire.
Providers and international processing
Authorized ONLIN’IN personnel and the providers needed to operate the service may process this information: Mevspace for application and database hosting in Poland; Cloudflare for network security, email routing, and file storage; Emailit for sign-in emails and, when they are switched on, the confirmation emails of members’ lists; Discord, in the United States, for the operator’s activity notifications (name, username, email address and the steps taken); and any email or agent provider you choose to connect. We do not sell your personal data or use your private context for advertising.
Some providers operate internationally and may process data outside the European Economic Area. Relevant contractual safeguards include the providers’ data-processing commitments and, where applicable, standard contractual clauses. See Cloudflare’s data processing addendum. Contact us for information about the safeguards applicable to your data.
Cookies
We use necessary cookies for sign-in, sessions, authorization, and security. If you arrive through a member’s invitation link, one more cookie remembers that member’s username for 30 days so the invitation can be credited when you claim a name. Page statistics use no cookie and nothing stored in your browser; the only exception is the opt-out button above, which keeps your choice in this browser. The homepage’s short notices about new pages remember, in this browser, which pages they showed during your visit (forgotten when the tab closes) and when you last closed one (so they stay quiet for 7 days). We use no advertising trackers and no third-party analytics. Cloudflare may use security mechanisms needed to protect the service.
Your rights and choices
You can edit your profile and context, see your page statistics, change visibility, choose whether to be listed in the directory and on the public lists, revoke agent or email connections, export your account, and delete it in your workspace. You may also request access, correction, erasure, restriction, or portability of your data, and object to processing based on legitimate interest. Waitlist updates include an unsubscribe option.
Email [email protected] with the address concerned so we can verify your request. You may lodge a complaint with the CNIL. Providing profile and context fields is optional; information needed for sign-in is required to operate an account. Manual sending review is performed by an operator.