Privacy Statement, Mideye EAM
How Mideye processes personal data when Microsoft Entra ID uses Mideye for multi-factor authentication
Summary
Who is responsible
Your organisation is the controller of its users' data. Mideye AB is the processor. Mideye is the controller only for administrator accounts and billing records.
What the Service uses
The user's Microsoft Entra identifiers and sign-in name, the mobile phone number or token serial number, and the IP address of the browser.
What Mideye keeps
- Directory lookups: 5 minutes by default, in memory only.
- Users that an administrator adds: until the administrator removes them.
- Records of portal changes: 7 days.
- Authentication records and token checks: 13 months.
- Billing records of text messages: 13 months, then only monthly totals.
- Logs: 30 days in central logging. The sign-in service and the authentication API keep their own logs until the logs rotate.
Where
Microsoft Azure in Sweden, and Mideye Switch at hosting providers in Finland and Sweden. Push notifications pass through Apple and Google in the USA. Text messages pass through SMS providers and mobile networks that depend on the phone number. Yubico checks Yubico OTP passwords.
What Mideye does not do
Mideye does not sell the data. Mideye does not use it for marketing, for profiling or for any purpose that this statement does not list.
Full statement
1. Scope
This statement covers Mideye EAM (the "Service"). Organisations use the Service as an external authentication method in Microsoft Entra ID. The statement covers the users that an organisation signs in with the Service, and the administrators who manage it.
This statement uses these terms:
- Your organisation: the organisation that uses the Service.
- Sign-in service: the part of the Service that Microsoft Entra ID calls. It has a separate sign-in realm for each organisation.
- Mideye Cloud: the Mideye services that send approval requests and text messages, and check one-time passwords.
- Mideye Switch: the Mideye system that routes text messages and token checks. It sends text messages to SMS providers and mobile networks.
- Mideye portal: the website where your organisation's administrators manage the Service.
When they process data for Mideye EAM, all of these are part of the Service.
The Mideye+ app shows the approval requests of the Service. The Mideye+ app privacy policy covers the data that the app itself collects.
2. Controller and processor
Your organisation decides why and how the Service processes its users' data. Your organisation is the controller and decides the legal basis.
Mideye AB is the processor. Mideye processes users' data only on your organisation's documented instructions. These instructions are the data processing terms in the Terms of Service, and the settings that your organisation selects in the Service. A data processing agreement that your organisation signs with Mideye takes precedence.
Mideye is the controller for two kinds of data:
- administrator accounts in the Mideye portal (section 3);
- billing records of text messages (section 5).
Mideye processes this data to provide and invoice the Service under its agreement with your organisation, and to meet accounting law.
Users who have questions about their own data contact their organisation's IT administrator first. Mideye helps your organisation to answer requests.
3. Personal data that the Service processes
From the sign-in request of Microsoft Entra ID
Microsoft Entra ID sends a signed token with each sign-in request. The Service uses these values from the token:
- the user's object ID and the tenant ID;
- the sign-in name (user principal name) and the display name;
- the subject identifier that Microsoft Entra ID issues for the Service.
The Service uses them to identify the user, and to check that the request comes from your organisation's tenant.
From your organisation's directory
Your organisation can turn on the directory lookup. The Service then reads these values through Microsoft Graph:
- the mobile phone number, from the user's mobile phone property or from the phone number that the user registered as an authentication method;
- the token serial number, from a user property that your organisation selects.
The Service reads this data only for the user who signs in, and only if your organisation did not add that user in the Mideye portal.
Users that an administrator adds in the Mideye portal
Instead of the directory lookup, an administrator of your organisation can add users in the Mideye portal. The Service then stores the object ID, the tenant ID and the mobile phone number of each user.
During the sign-in
- The IP address of the user's browser.
- The mobile phone number. Mideye Cloud uses it to send the approval request or the text message.
- The text of the approval request, which the Mideye+ app or the sign-in link page shows. By default, the text shows the sign-in name and the IP address, so that the user can recognise the sign-in. Your organisation can change the text.
- The one-time password from a hardware token. Mideye Cloud checks it.
Administrators
Administrators sign in to the Mideye portal with a Mideye portal account. Mideye processes the administrator's name, email address and organisation, and the changes that the administrator makes in the Mideye portal.
4. Why the Service processes the data
- To authenticate your organisation's users for Microsoft Entra ID.
- To protect the Service and your users against misuse and fraud.
- To operate the Service, and to find and correct faults.
- To give administrators access to the Mideye portal.
- To invoice the Service (billing records only).
Mideye does not sell the data. Mideye does not use it for marketing, for profiling or for any purpose that this statement does not list.
5. How long the data is kept
- Directory lookup results: in the memory of the sign-in service, for 5 minutes by default. Your organisation can set a time from 30 seconds to 1 hour. The sign-in service does not write these results to a database. A restart of the sign-in service deletes them.
- Users added in the Mideye portal: until an administrator removes them, or until the Service ends for your organisation.
- Changes in the Mideye portal: the sign-in service keeps a record of each change for 7 days. The record contains the changed user entry, including the mobile phone number.
- Approval requests: Mideye Cloud keeps an open request, including its text, only until the sign-in ends or times out.
- Authentication records: the sign-in service keeps no sign-in history. Mideye Cloud keeps a record of each authentication for 13 months: the time, the method, the result and your organisation's account. The record shows only part of the phone number.
- Token checks: Mideye Cloud keeps a record of each token check, with the token serial number, the time and the result, for 13 months.
- Billing records: Mideye keeps a record of each text message, with the phone number, the time and the result, to invoice the Service. The invoice counts the different phone numbers in these records each month. Mideye keeps these records for 13 months. After that, Mideye deletes the phone numbers and keeps only the monthly totals for your organisation.
- Logs: the sign-in service and the Mideye Cloud authentication API keep their logs on the servers that run them. A log rotation or a restart of the service deletes them. The logs of Mideye Switch and of the other Mideye Cloud services stay for 30 days in Microsoft Azure in Sweden. Logs can contain Microsoft Entra identifiers, token serial numbers and IP addresses. The sign-in service and the authentication API mask phone numbers in their logs.
- Administrator accounts: as long as the administrator has access to the Mideye portal. Mideye removes an account when your organisation asks.
- When the Service ends: Mideye deletes your organisation's sign-in realm and the other personal data that Mideye processes for your organisation within 30 days, unless the law requires Mideye to keep it.
6. Where the data is processed
Mideye runs the sign-in service, Mideye Cloud and the Mideye portal in Microsoft Azure in Sweden.
Mideye Switch runs on servers that hosting providers operate for Mideye in Finland and Sweden.
Some data leaves the EU/EEA:
- Push notifications pass through Apple and Google in the USA (section 7).
- A text message to a phone number on a network outside the EU/EEA goes to that network.
- Yubico checks Yubico OTP one-time passwords. Yubico has not published in which country it checks them, so the check can take place outside the EU/EEA.
7. Who else receives data
Mideye uses these sub-processors for the Service:
- Microsoft hosts the sign-in service, Mideye Cloud and the Mideye portal in Microsoft Azure, in Sweden.
- UpCloud hosts Mideye Switch, in Finland.
- Bahnhof hosts the standby of Mideye Switch, in Sweden.
- SMS providers send text messages from Mideye Switch to the mobile networks. The provider depends on the country of the phone number. TO CONFIRM: the list of providers.
- Apple and Google deliver push notifications to the Mideye+ app, from the USA. By default, the notification contains the title of the request ("Microsoft sign-in"), a device token and a Mideye identifier. Your organisation can add the sign-in name or the IP address to the title. The notification then contains them. The notification never contains the phone number. The app collects the text of the request directly from Mideye Cloud. Transfers to Apple and Google rely on the EU-US Data Privacy Framework.
- Yubico checks the one-time password if a user signs in with a YubiKey that uses Yubico OTP. Mideye sends Yubico only the one-time password. It identifies the YubiKey, but not the user.
Mideye tells your organisation about a new sub-processor before it starts, as the Terms of Service describe.
These parties also receive data:
- Mobile network operators receive the phone number and the text message with the sign-in link. By default, the text message contains no sign-in name and no IP address. If your organisation adds them to the text, the operators receive them.
- Microsoft Entra ID and Microsoft Graph are your organisation's own services. The Service exchanges data with them for your organisation.
- Authorities receive data only if the law requires it. Mideye tells your organisation first, unless the law forbids it.
8. Security
- Each organisation has its own sign-in realm. The realm accepts sign-in requests only from your organisation's Microsoft Entra tenant.
- Connections to the Service use HTTPS.
- The database and the key vault of the sign-in service accept connections only from Mideye's private network. The database is encrypted at rest.
- Mideye stores no password or client secret for your organisation's tenant. The Service reads Microsoft Graph with a federated credential.
- If Mideye becomes aware of a personal data breach that affects your organisation's data, Mideye tells your organisation without undue delay.
9. Your organisation's choices
- Turn off the directory lookup, and add users in the Mideye portal instead.
- Remove users from the Mideye portal at any time.
- Stop using the Service. First remove Mideye as an external authentication method in Microsoft Entra ID. Then delete the Mideye EAM enterprise application. This stops new sign-ins and directory lookups. It does not delete the data that Mideye keeps.
- Ask Mideye to delete the sign-in realm and its data, or to send your organisation a copy of the data first.
10. Rights of users and administrators
Under the GDPR, users and administrators have the right to access, correct and erase their personal data, to restrict or object to its processing, and to data portability.
- Users send requests to their organisation, as the controller. Mideye helps the organisation to answer them.
- Administrators send requests about their Mideye portal account to Mideye.
Anyone can also complain to the data protection authority in the country where they live or work. In Sweden, this is the Swedish Authority for Privacy Protection (IMY), www.imy.se.
11. Changes to this statement
Mideye updates this statement when the processing changes. The date of the latest update is at the end of this page.
Contact
Mideye ABDrottninggatan 96
SE-111 60 Stockholm, Sweden
Email: support@mideye.com
Phone: +46 8 54514700
Related documents
Latest update: 3 November 2026