This is a starting draft, not reviewed by a lawyer. It describes what this application does with personal data, as far as the code goes. The parts in square brackets are placeholders: fill them in, check every statement against what you really do, and have the result reviewed for your jurisdiction before you rely on it.
Who is responsible
[Placeholder: the name, address and registration number of the organisation or person responsible for mcp deploy migrate.] Questions about your data, and requests to use your rights below, go to [Placeholder: contact address, for example hello@example.com].
What we keep, and why
Your account. When you sign in we keep your email address, your name, how you signed in (an emailed code, a one-time link, or Google, Microsoft or LinkedIn), when you agreed to the Terms of Service and this Privacy Policy, and your account status. We use it to recognise you and to let you use your own data. We do not receive a password from those providers. If you did not give a name, one is made from your email address; you can change it in the account menu.
Where you are signed in. For each browser, and each connected tool (MCP), we keep a short label (for example “Chrome on Windows”), when it signed in, when it was last used and how. Not your IP address, and not your full browser identification. You can see and end these in the account menu.
Sign-ins that did not work. To find out what goes wrong at sign-in, we keep a short technical log of failed or unfinished sign-ins: the time, the way you tried, the reason, a short browser label, and scrambled (keyed-hash) codes for your email address and your network address, from which neither can be read back. The address, the code you typed and your name are not in it. These lines are deleted after 30 days, or when you ask to be forgotten.
What you add. [Placeholder: describe the data your application keeps for a person (what they enter, upload or save), who can see it, and for how long. This kit itself keeps only the account and session details above, plus whatever your application stores under the person’s record.]
[Placeholder: for each of the above, the legal basis, for example performance of the agreement to provide the service, legitimate interest, or consent.]
Who else receives data
Other services. [Placeholder: any other service your application sends data to (maps, analytics, payment, an address lookup), what it receives, and a link to its privacy policy. Delete this paragraph if there is none.]
Sign-in providers. If you sign in with Google, Microsoft or LinkedIn, that provider tells us your email address (we ask for nothing else) and knows that you signed in here.
Email. The emailed sign-in code is sent through [Placeholder: your mail provider].
Connected tools receive your data. When you allow a connected tool (MCP client) you choose what it may do: read the data you keep here, and optionally change it. What it reads is sent to that tool and to any service it relies on, such as an AI model, and is handled under that tool’s own terms and privacy policy. We cannot recall it. You can end a tool’s access at any time with End session.
We do not sell personal data, and we do not use it for advertising.
How long we keep it
Your account details are deleted after 30 days without activity. A session ends by itself after 7 days without use. An account that an administrator has suspended or closed is kept, with its status, until the administrator changes it. [Placeholder: say how long the data your application keeps is stored, and how it is removed.]
Your rights
You have the right to ask for a copy of your data, to have it corrected or deleted, to limit or object to how it is used, and to receive it in a usable form, and to complain to your data protection authority [Placeholder: name it, for example the Swedish Authority for Privacy Protection, IMY].
GDPR: forget me (in the account menu, the round icon with your initials at the top right) deletes your account data, ends every session, and replaces your email address and name on record with “anonymous”. One minimal pseudonymous record is kept, by default without a time limit: a one-way, keyed hash of your email address and the date you asked to be forgotten, so that your request can be honoured and we do not collect data about you again. [Placeholder: state your legal basis for keeping it.] [Placeholder: say whether anything your application published about the person is removed by this.]
Emails we send
Invitation and announcement emails contain a small image and a personal link so that we can count how many people opened the email, clicked the link and signed in. Every such email has an opt-out link; if you opt out we keep only a scrambled form of your address so that we do not write to you again.
Cookies
We set one cookie that identifies your session, and we remember in your browser (until you close the tab) whether you accepted the cookie notice. We do not use advertising or tracking cookies. Any other service named above may set its own.