Legal

Terms of Service, Mideye EAM

Mideye multi-factor authentication as an external authentication method in Microsoft Entra ID

Summary

Who these Terms are for

Organisations that use Mideye EAM in their Microsoft Entra ID tenant, under an agreement with Mideye or with a Mideye partner.

What the Service does

Microsoft Entra ID sends the user to Mideye for the second factor. Mideye checks the user and returns the result. Microsoft Entra ID decides on access.

Beta

The Service is a beta. During the beta, Mideye gives no service level unless a signed agreement sets one.

Personal data

The organisation is the controller. Mideye is the processor. Section 10 is the data processing agreement. The Mideye EAM privacy statement describes the data.

Terms

1. About these Terms

These Terms of Service ("Terms") govern the use of Mideye EAM (the "Service"). Mideye AB ("Mideye") operates the Service.

The "Customer" is the organisation whose Microsoft Entra ID tenant uses the Service. The Service is for organisations only, not for consumers.

Mideye provides the Service only to Customers that have an agreement for it, directly with Mideye or through a Mideye partner. These Terms apply to every Customer.

An agreement that the Customer and Mideye sign takes precedence over these Terms. An agreement between the Customer and a Mideye partner does not bind Mideye and does not change these Terms.

The administrator who grants consent to the Mideye EAM application in Microsoft Entra ID also accepts these Terms for the Customer. The administrator confirms that they have the authority to do so.

Microsoft's terms apply to Microsoft Entra ID. These Terms do not change them.

2. Beta

Until Mideye announces general availability, the Service is a beta. During the beta:

  • Mideye gives no service level, unless an agreement that the Customer and Mideye sign sets one;
  • Mideye can change or remove functions of the Service;
  • Mideye can end the Service, with at least 30 days' notice to the Customer.

3. What the Service does

The Service connects Microsoft Entra ID to Mideye multi-factor authentication. The Customer adds Mideye as an external authentication method in Microsoft Entra ID.

When Microsoft Entra ID asks a user for a second factor, it sends the user to the Service. The Service checks the user with one of these methods, as the Customer configures:

  • an approval request in the Mideye+ app;
  • a sign-in link in a text message (SMS);
  • a one-time password from a hardware token.

The Service then returns the result to Microsoft Entra ID. Microsoft Entra ID makes the access decision, under the Customer's Conditional Access policies.

Mideye hosts a separate sign-in realm for each Customer.

4. Permissions that the Customer grants

The consent screen in Microsoft Entra ID lists the Microsoft Graph permissions of the Mideye EAM application:

  • openid and profile (delegated): Microsoft requires these for every external authentication method.
  • User.Read.All (application): the Service reads the mobile phone number and the token serial number of the user who signs in.
  • UserAuthenticationMethod.Read.All (application): the Service reads the mobile phone number that the user registered as an authentication method, if the Customer selects this source.

The Service uses the two application permissions only when the Customer turns on the directory lookup. It reads data only for the user who is signing in.

The Customer can withdraw these permissions at any time. Section 14 describes how.

5. The Customer's responsibilities

The Customer agrees to:

  • configure its Conditional Access policies, and decide which users and applications use the Service;
  • keep the mobile phone numbers and token serial numbers of its users correct, in Microsoft Entra ID or in the Mideye portal;
  • keep emergency access accounts that do not depend on the Service, so that an interruption of the Service does not lock out its administrators;
  • make sure that it has a legal basis to process its users' personal data with the Service, and inform its users;
  • use the Service only for its own users;
  • make sure that its users follow section 6;
  • keep its administrator accounts secure, and tell Mideye about suspected misuse.

6. Users

The Customer makes sure that its users:

  • approve only sign-ins that they started themselves;
  • keep one-time passwords and sign-in links confidential;
  • reject an unexpected sign-in request and tell their organisation's IT administrator.

7. Availability

The Service depends on Microsoft Entra ID, Microsoft Azure, mobile networks and the push notification services of the mobile platforms. Mideye does not control these services.

Mideye does not guarantee that the Service is always available, unless an agreement that the Customer and Mideye sign sets a service level.

8. Security

Mideye can limit attempts, block requests and change security controls to protect users and the Service.

Multi-factor authentication reduces the risk of unauthorised access. It does not remove it. Mideye is not responsible for unauthorised access that the Service did not cause. Examples:

  • a user shares a one-time password or a sign-in link, or approves a request that they did not start;
  • a phishing site passes the user's sign-in on to Microsoft Entra ID;
  • malware on a user's device;
  • the loss or theft of a user's device, a SIM swap, or a transfer of the user's phone number;
  • incorrect phone numbers or token serial numbers in the Customer's directory or in the Mideye portal;
  • the Customer's configuration of Microsoft Entra ID, including its Conditional Access policies;
  • a fault in Microsoft Entra ID, a mobile network or a push notification service.

9. Acceptable use

The Customer and its users must not:

  • try to bypass, overload, probe, scan or test the security of the Service without Mideye's written permission;
  • send sign-in requests for accounts that they do not own or manage;
  • interfere with the Service or its infrastructure.

Mideye can suspend access if it has reasonable grounds to suspect misuse or fraud. Where it can, Mideye limits a suspension to the affected users or requests. Mideye tells the Customer about a suspension without undue delay.

10. Data processing

This section is the data processing agreement under Article 28 of the GDPR. The Customer is the controller and Mideye is the processor. A data processing agreement that the Customer and Mideye sign takes precedence over this section.

  • Subject and duration: the processing that the Service needs. It lasts while the Customer uses the Service, and until Mideye deletes the data after the Service ends.
  • Nature and purpose: authentication of the Customer's users for Microsoft Entra ID, and the security and operation of the Service.
  • Data and data subjects: the personal data of the Customer's users that the privacy statement describes.
  • Instructions: Mideye processes the data only on the Customer's documented instructions. These Terms and the settings that the Customer selects in the Service are these instructions. If the law requires Mideye to process the data in a different way, Mideye tells the Customer first, unless the law forbids it. Mideye tells the Customer if it thinks that an instruction breaks data protection law.
  • Confidentiality: the people at Mideye who process the data are bound to confidentiality.
  • Security: Mideye uses appropriate technical and organisational measures to protect the data, as Article 32 of the GDPR requires. The privacy statement describes the main measures.
  • Sub-processors: the Customer gives general authorisation for Mideye to use sub-processors. The privacy statement lists them. Mideye tells the Customer about a new sub-processor at least 30 days before it starts. The Customer can object in this period. If Mideye cannot solve the objection, the Customer can stop the Service. Mideye gives each sub-processor the same data protection obligations, and stays responsible to the Customer for them.
  • Transfers: Mideye transfers data outside the EU/EEA only with the safeguards that Chapter V of the GDPR requires.
  • Help: Mideye helps the Customer to answer requests from its users. Mideye also helps the Customer to meet its obligations for security, breach notification, impact assessments and prior consultation.
  • Breaches: Mideye tells the Customer without undue delay after it becomes aware of a personal data breach that affects the Customer's data.
  • End of the Service: at the Customer's choice, Mideye deletes the data or returns it to the Customer. Mideye deletes it within 30 days after the Service ends, unless the law requires Mideye to keep it.
  • Audits: Mideye gives the Customer the information that it needs to show compliance with this section. Mideye allows an audit by the Customer, or by an auditor that the Customer selects. The Customer gives 30 days' notice and pays the cost. Audits happen at most once a year, unless a breach gives cause.

Mideye is the controller of the administrator accounts in the Mideye portal and of the billing records that the privacy statement describes. This section does not apply to them.

Mideye does not sell personal data and does not use it for marketing.

11. Fees

The Customer's agreement sets the fees for the Service.

12. Confidentiality

Each party keeps confidential the non-public information that it receives from the other party about the Service or the other party's business. This does not apply to information that is public, that the party already had, or that the law requires the party to disclose.

13. Intellectual property

Mideye or its licensors own the Service and all related software, branding and content. The Customer receives a non-exclusive, non-transferable right to use the Service for its own users while its agreement is in force. The Customer cannot sublicense this right.

14. Suspension and termination

The Customer can stop using the Service at any time. 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.

Mideye can suspend or end the Service for a Customer if:

  • Mideye has reasonable grounds to suspect misuse or fraud (section 9);
  • the law requires it;
  • the Customer's agreement for the Service ends;
  • Mideye discontinues the Service, with at least 30 days' notice to the Customer.

The Service ends for a Customer when the Customer's agreement ends, or when the Customer tells Mideye in writing to end it. Mideye then deletes or returns the personal data as section 10 describes.

15. Changes

Mideye can change the Service or these Terms to improve security, compliance or functionality.

Mideye tells the Customer about a material change to these Terms at least 30 days before it takes effect. A change that the law or an urgent security need requires can take effect earlier. If the Customer continues to use the Service after the change takes effect, the Customer accepts the updated Terms.

16. Disclaimers

Unless an agreement that the Customer and Mideye sign states otherwise, Mideye provides the Service "as is" and "as available". Mideye does not guarantee:

  • that messages and approval requests always arrive immediately;
  • that every device and mobile network supports every method;
  • error-free operation;
  • that the Service prevents all unauthorised access;
  • that the Service meets the Customer's legal or regulatory requirements.

17. Limitation of liability

To the maximum extent that the law permits:

  • Mideye is not liable for indirect loss. Indirect loss includes loss of profit, revenue, business or goodwill, loss or corruption of data, business interruption, and claims from third parties.
  • Mideye's total liability under these Terms, including section 10, is limited to the fees that the Customer paid to Mideye for the Service in the 12 months before the event that caused the claim. If the Customer paid no fees to Mideye in that period, Mideye is not liable to the Customer.
  • These limits do not apply to loss that Mideye caused intentionally or by gross negligence, or to a liability that the law does not allow to be limited.

18. Events outside a party's control

Neither party is liable for a delay or a failure that a cause outside its reasonable control causes. Examples are a fault in Microsoft Entra ID, Microsoft Azure, a mobile network or a push notification service, a power failure, and a decision of an authority.

19. Subcontractors and transfer

Mideye can use subcontractors to provide the Service. Section 10 sets the rules for sub-processors. Mideye stays responsible for its subcontractors.

Neither party can transfer these Terms without the written consent of the other party. Mideye can transfer them to a company that takes over the Service.

20. General

  • Notices: Mideye sends notices under these Terms by email to the Customer's contact in its agreement. The Customer sends notices to support@mideye.com.
  • Invalid terms: if a court finds a part of these Terms invalid, the other parts stay in force.
  • After the end: sections 10, 12, 17 and 21 continue to apply after the Service ends, for as long as their purpose requires.

21. Governing law

The laws of Sweden govern these Terms, without their conflict-of-law rules. The Stockholm District Court (Stockholms tingsrätt) is the court of first instance for disputes, unless mandatory law states otherwise.

Contact

For questions about these Terms or the Service, contact:

Mideye AB
Drottninggatan 96
SE-111 60 Stockholm, Sweden

Email: support@mideye.com
Phone: +46 8 54514700

Related documents

Latest update: 3 November 2026