1. Who is responsible
E2E Design AB, organisation number 559416-2843, Rehnsgatan 19, 113 57 Stockholm, Sweden, provides Midland and is the controller of the personal data described in this policy.
Contact for anything about privacy: support@midland.md. We have not appointed a data protection officer, because we are not required to.
2. Two kinds of data, two roles
Account and usage data. The data we need to give you an account, sign you in, keep the service secure and understand how it is used. We decide how this is handled, so we are the controller. This policy is about this data.
Workspace content. The items, files, metrics and other material that a workspace's people, agents and couriers store in Midland. The customer who runs the workspace decides what goes in and why, so the customer is the controller and we only process it on their behalf, under our Data Processing Agreement. If your personal data appears in a workspace's content, contact the people who run that workspace. If you contact us, we pass your request to them.
3. What we collect, why, and for how long
| Data | Why we use it | Legal basis | How long we keep it |
|---|---|---|---|
| Email address and sign-in times | To create your account, send sign-in links and let you in | Contract | Until your account is deleted |
| Profile: display name, team, description, tags and picture, if you add them | To show the people in a workspace who you are | Contract | Until you change them or your account is deleted |
| Invitations: the invited email address, who invited them, and when | To let people join a workspace | Legitimate interest in letting customers bring in their team | Until the workspace is deleted |
| Sign-in session: a cookie that keeps you signed in | To keep you signed in securely | Contract | Up to 400 days, or until you sign out |
| Agent connections: the name an agent gave when it connected, where it sends you back to, when it was last used, and scrambled copies of its access tokens | To let your agent act for you and to let you see and end that access | Contract | Access expires after 8 hours and renewals after 30 days. Records are kept until the workspace is deleted |
| Courier records: who added or removed a courier and when | Security and accountability | Legitimate interest in a traceable record of who granted automated access | Until the workspace is deleted |
| Access log: which person, agent or courier called which tool, on which item, when, and with what result. Search words, item names and metric values are recorded. The content of files is never recorded | To show a workspace what has happened to its content, and to investigate misuse | Legitimate interest in security and in giving customers an audit trail | Until the workspace is deleted |
| Write and deletion records: who wrote or deleted what and when. A deleted item's name, and a deleted file's name and opening lines, remain in these records | The same | The same | Until the workspace is deleted |
| IP address, when you ask for a sign-in link or create a workspace | To limit abuse, such as mass sign-ups | Legitimate interest in protecting the service | 30 days |
| Technical logs: IP address, browser type, the address requested and status | To run and troubleshoot the service | Legitimate interest in a working, secure service | 1 day |
| Usage events: an account identifier, the pages you open in the console, sign-up steps, and for agent calls the tool name, duration and result. No email address and no content | To understand how the product is used and improve it | Legitimate interest in improving the product | 12 months |
| Emails we send you: sign-in links and invitations | To deliver them | Contract | Delivery records up to 30 days |
| Messages you send us | To answer you | Legitimate interest in handling requests | 24 months after the last message |
Where we rely on legitimate interest, you may object (section 8).
You do not have to give us any data, but without an email address we cannot create an account or sign you in.
We do not make decisions about you by automated means, and we do not build profiles of you.
4. If someone invited you
If a person in a workspace invited you, we received your email address from them. We create a sign-in account for that address so the invitation can work. We use the address only to send the invitation and to let you accept it. If you do not want it, ignore the email, or write to us and we will delete the account.
5. Deleting your data
- People in a workspace can delete items and files themselves at any time. This removes the content and all its versions.
- To delete your account, or a whole workspace, email support@midland.md. We do it within 30 days.
- If you are removed from a workspace, your sign-in account remains until you ask us to delete it.
- When an account is deleted, content that person wrote stays in the workspace, because it belongs to the workspace, but their name is removed from it.
- Deleted data can remain in backups for up to 7 days before it is overwritten.
6. Who we share it with
We do not sell personal data. We share it only with the suppliers that help us run Midland, each under a data processing agreement:
| Supplier | What for | Where |
|---|---|---|
| Supabase | Database, sign-in and picture storage | Stockholm, Sweden |
| Vercel | Hosting and technical logs | Application runs in Stockholm; network and support in the EU and the United States |
| Resend | Sending sign-in and invitation emails | United States |
| PostHog | Usage analytics | Frankfurt, Germany |
The current list is on our Sub-processors page.
We may also disclose data where the law requires it, or to a company that takes over the service, under the same commitments as this policy.
Agents are not on this list. If you connect an agent to Midland, the company that provides it receives whatever your agent reads. That company is your supplier, chosen by you, and it handles the data under its own terms.
Profile pictures. A picture you upload is stored at a web address that is not listed anywhere but can be opened by anyone who has it. Do not upload a picture you would not want others to see.
7. Cookies and similar storage
We use only what is needed to make the console work, so we do not ask for cookie consent.
| Name | What it does | How long |
|---|---|---|
sb-…-auth-token (cookie) | Keeps you signed in | Up to 400 days |
midland_oauth_request (cookie) | Carries an agent's connection request while you sign in | 10 minutes |
midland_oauth_unfinished (cookie) | Remembers that you left an agent approval unfinished, so we can tell you | 1 hour |
midland.theme (local storage) | Remembers light or dark mode | Until you clear it |
Our usage analytics stores nothing in your browser.
8. Transfers outside the EU and EEA
Your data is stored in Stockholm. Some of our suppliers are US companies, and their staff or systems outside the EU and EEA may handle personal data, for example when delivering email or routing a request through a global network. Where that happens, the transfer is covered by the European Commission's standard contractual clauses or by the supplier's certification under the EU–US Data Privacy Framework. Email us for a copy of the safeguards.
9. Your rights
You can ask us to:
- give you a copy of the personal data we hold about you;
- correct it;
- delete it;
- restrict how we use it;
- give it to you in a portable format;
- stop using it where we rely on legitimate interest.
Email support@midland.md. We answer within one month. There is no charge.
You can also complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY), imy.se, or to the data protection authority where you live.
10. Children
Midland is for business use by adults. We do not knowingly collect data from anyone under 18.
11. Changes to this policy
When we change this policy we update the date above. For a significant change we email the people in each workspace before it takes effect.