MCP Data Practices
Last updated: 14 September 2026
This page describes what happens to data when an AI assistant is connected to Bimedis over
the Model Context Protocol at mcp.bimedis.com. The integration is provided and
operated by Bimedis, the company behind the marketplace at
bimedis.com, and the data controller is the
same legal entity as for the marketplace itself.
It supplements, and does not replace, the Bimedis Privacy Policy, which describes how Bimedis processes personal data in general. The rules for using the connection itself are in the MCP Usage Terms.
1What leaves the server
Without a connection the assistant sees public catalog data only: listing titles, descriptions, prices, condition, location, images and links to the site — the same information any visitor sees.
With a connection the assistant additionally reaches the data covered by the permissions you approved: your profile name and e-mail, your adverts and your conversations.
2Contact details are stripped out
Public catalog responses are passed through a filter that removes phone numbers, e-mail addresses, messenger handles and external links — including ones sellers typed into a free-text description. Contact data is exchanged where it belongs: in the marketplace conversation between buyer and seller, not in a machine-readable catalog response.
Your AI provider sees what the assistant sees. Every response we return travels into the assistant you connected — ChatGPT, Claude, Cursor or another client — and is processed under that provider's terms and privacy policy, which we neither control nor can enforce. This matters most for your own data: conversations and buyer messages leave our perimeter the moment a tool returns them. If that is not acceptable for a given account, do not approve the corresponding permissions.
3The access token
After you sign in and approve the permissions, the server issues an access token to the client that asked for it. The token:
- identifies your account and carries exactly the approved permissions, nothing wider;
- is stored by the AI client, on its own infrastructure — we do not receive a copy of the client's storage and cannot read it;
- does not expire on its own, and stays valid until you revoke it;
- is revoked in My office → API keys, per connection: revoking one leaves your other connections and keys untouched.
Your password is never handed to the assistant. Sign-in happens on a Bimedis page, and the client only ever receives the token.
4What we log
Each tool call is recorded so we can keep the service working, enforce limits and see which searches come back empty. A record holds:
- the tool name, the time, how long it took, the number of results, and the error code if it failed;
- the client name and version as reported by the assistant, and the protocol version;
- a one-way hash of the caller's IP address — the address itself is not stored;
- call arguments: for public catalog tools, the search parameters after the same contact-stripping filter; for account tools, only a short list of identifiers — never message text, advert descriptions, e-mail addresses or the token.
These records are not linked to your account id, and are used for operating and improving the service — not for profiling or advertising. Retention, access rights and how to raise a request about your personal data follow the Bimedis Privacy Policy.
5What we do not do
- We do not sell MCP usage data, and we do not share it with advertisers.
- We do not use the content of your conversations to train models.
- We do not place cookies on
mcp.bimedis.comfor tracking; the sign-in page keeps no session of its own.
6Contact
Questions about data in MCP connections, or a request concerning your personal data: bimedis.com/contacts or [email protected].