Draft outline. This lists what the privacy policy must cover; the final text has to be written with a lawyer before MCO launches.
Privacy policy
How MCO handles personal data under the GDPR.
1. Controller and contact
- MCO legal entity and a contact email for privacy questions.
2. What we collect and why
- Account: name, work email, company, role, password (stored by Microsoft Entra, never by MCO).
- Security: sign-in history (time, browser and device, approximate location), two-step status, audit log of admin actions.
- Orders, configurations, projects and library files; billing details via Stripe.
- Legal basis for each: contract, legal obligation (accounting), legitimate interest (security).
3. Who we share it with
- Processors: Microsoft Azure and Entra (hosting, sign-in), Stripe (payments), the email provider.
- Publishers see the company name and order details for their own products.
- Where data is stored (EU regions) and transfers outside the EU, if any.
4. How long we keep it
- Account data while the account exists; audit log 2 years; invoices and order records as accounting law requires.
- Rejected sign-ups deleted after 30 days.
5. Your rights
- Access and download your data (My profile › Download my data).
- Correct your details (My profile) and delete your account (My profile › Delete my account).
- Object, restrict, complain to the data protection authority.
6. Cookies and browser storage
- MCO only stores what is needed to run the app: the sign-in session and your own settings (for example menu width). No analytics or advertising cookies, so no consent banner is needed.
- If analytics or marketing tools are added later, a consent banner must be added first.