ISIRO
May we measure whether our ads work?

ISIRO uses Google Ads and would like to know whether an ad turns into a customer. That needs a cookie which is not necessary for the site to work — so we ask before we do it.

If you say no, nothing happens. We remember your no in your browser so you are not asked again, and that is the only thing we store. You can change your mind at any time at the bottom of the page.

Read more in the cookie policy

Terms of business for ISIRO

The terms that apply when your company buys and uses ISIRO. Version 1.0, 15 November 2026.

Note:

This is a translation provided so that you can understand the document. Only the Danish version applies. If the two ever say different things, the Danish one is correct.

These terms are about the agreement, the price, liability and termination. What ISIRO may do with information about your end users is set out in the data processing agreement and is not repeated here.

ISIRO is sold to businesses only and not to consumers. The rules on the right of withdrawal, consumer complaints and easy termination therefore do not apply.

1. The parties

The ISIRO service is supplied by:

Rishah ApS, trading as ISIRO under the secondary name Isiro ApS
Danish company reg. no. 36455071
C/O Suite 408, Østerbrogade 226, 1. tv
2100 København Ø
Danmark
support@isiro.dk

The customer is the company that creates an account. Whoever creates the account warrants that they are entitled to enter into the agreement on the company's behalf.

2. What ISIRO delivers

ISIRO verifies one-time codes according to the RFC 6238 standard through an API. The customer's own IT system calls ISIRO with an API key, and ISIRO answers whether the code is correct. The customer's end users use any authenticator app they choose.

ISIRO sends no SMS and supplies no app. ISIRO is an extra layer of security on top of the customer's own sign-in — not the customer's sign-in, and not the customer's only way into their own system.

What each call does, and what it answers, is set out in the documentation. The documentation is part of the agreement.

3. Who can become a customer

If the EU VAT service does not answer, the customer is admitted with the status unverified, and the check is repeated automatically. An unverified customer cannot be invoiced, and if the check does not succeed within a set period, the account is suspended. The reverse charge may only be used once the VAT number has been verified as valid.

This applies to customers within the EU only. A customer outside the EU has no number to have verified with the EU service and therefore receives neither a deadline nor a suspension on that account.

4. Formation of the agreement

The agreement is entered into when the customer has completed the sign-up and has actively ticked two boxes: one for these terms of business and one for the data processing agreement. No field is ticked in advance, and the two boxes cannot be combined into one.

On acceptance, we store for each of the two documents the time, the version number, an unalterable copy of the exact text the customer agreed to, and a checksum of that text. A version number alone is not evidence, because it does not say what the document said on the day. The copy is written once and is never overwritten.

5. Price

The prices are on the pricing page. They are only there. These terms do not repeat them, so that two different prices cannot end up being stated on the day the price changes.

What is fixed in these terms is:

The price is the same across the whole EU. It does not depend on which country the customer's end users are in, and there is no surcharge for other countries. An end user in Germany, Sweden or Denmark costs the same. This is a term and not an offer: ISIRO cannot send a customer a higher bill because the customer's users have moved, or because the customer has gained users in more countries.

What an active end user is. An end user is active in a month if the end user has confirmed their set-up with a correct code at least once, and the end user still exists with ISIRO at the end of the month. The confirmation is counted once and does not fall away again if the end user later has to set up a new phone.

The count is per person with two-factor authentication, not per company at the customer. If the customer has 30 companies with 10 employees each, and all 300 use two-factor authentication, that is 300 active end users. If only the 30 owners use it, it is 30. ISIRO does not see the customer's own division into companies or departments — only the end users the customer creates with ISIRO.

The customer can always see the figure. On the 1st of each month, ISIRO counts the previous month and writes the figure down for good. The statement is shown in the portal with its date, so the customer can see what the bill is based on. The figure is not recalculated afterwards: an invoice must rest on a figure that was settled at the time.

6. Changes to prices

If ISIRO changes the price list, notice is given at least 30 days in advance in writing to the email address on the customer's account. The customer may terminate without notice before the change takes effect.

7. Payment

If payment is not made on time, ISIRO does not charge interest. Instead, ISIRO does the following:

No more than three fees of DKK 100 are charged per invoice. ISIRO charges neither default interest nor the fixed compensation amount for commercial debts.

Suspension. ISIRO may suspend the customer's access at the earliest 24 days after the due date and only after written notice. That is the closure on day 24, and the notice is the reminder on day 21. A suspended account cannot create new end users, and the API answers no to calls made with the customer's keys. The customer's end users therefore cannot get in through ISIRO, and that is one of the reasons why the customer must have their own emergency access under section 10.

Non-payment never triggers deletion of data. Deletion only happens according to the periods in the data processing agreement.

8. Operation and maintenance

ISIRO does not guarantee any particular uptime. ISIRO corrects faults without undue delay and gives notice of planned maintenance by email where that is possible.

The reason no uptime is promised: a guaranteed uptime has to be measured, documented and compensated, and a service costing a few hundred kroner a month cannot carry that.

9. Liability and limitation of liability

The six provisions belong together and must be read together.

  1. Which losses are not covered. ISIRO is not liable for indirect losses. That includes operating losses, lost profit, lost revenue, loss or destruction of data, loss of goodwill and claims brought against the customer by a third party.
  2. The cap. ISIRO's liability is limited to the amount the customer has paid for ISIRO over the past 12 months, and in any event to at least DKK 2,000.
  3. Remedy first. Where there is a fault, the customer is in the first instance entitled to have ISIRO correct it without undue delay. Compensation only comes into play if the fault cannot be corrected within a reasonable time.
  4. Uptime. ISIRO does not guarantee any particular uptime, but corrects faults without undue delay and gives notice of planned maintenance by email where that is possible.
  5. Time limit for bringing a claim. A claim must be brought in writing no later than three months after the customer discovered or ought to have discovered the matter, and in any event no later than twelve months after the matter arose. After that the claim has lapsed.
  6. The exception. Paragraphs 1 to 5 do not apply where ISIRO has acted intentionally or with gross negligence.

The time limit in paragraph 5 applies to contractual claims, but not to claims arising from the data protection rules. Those follow the statutory time limits.

The cap in paragraph 2 also applies to a claim under Article 82 of the General Data Protection Regulation, but the exception for intent and gross negligence also covers breaches of the data processing agreement.

10. The customer's own responsibilities

  1. The API key. The customer keeps their API keys securely and does not share them. The customer immediately revokes a key in the portal on any suspicion that it has got out. ISIRO is not liable for the use of a key that has escaped at the customer's end. Every call made with a valid key counts as the customer's own.
  2. The customer must have their own emergency access. ISIRO is an extra layer of security on top of the customer's own sign-in, not the customer's only way into their system. The customer must have a documented emergency access so that the customer's own staff can get in if ISIRO is unavailable.
  3. The customer's own system. The customer is responsible for their own system, for their integration with ISIRO and for whom the customer gives access. ISIRO only answers whether a code is correct.
  4. A pseudonymous id. The customer uses a pseudonymous id for their end users — an internal number and not an email address or a name. ISIRO has no need to know who the end user is, and is not to know.
  5. Indemnity. Where a third party brings a claim against ISIRO arising from the customer's own instructions, the customer's use of the service or the customer's breach of the agreement, the customer indemnifies ISIRO.
  6. Unlawful instructions. ISIRO processes information only on the customer's documented instructions. If ISIRO considers that an instruction infringes the data protection rules, ISIRO informs the customer and may refuse to follow it.

11. Force majeure

Neither party is liable for anything caused by an event outside that party's control: a power cut, an outage at the hosting provider, an internet outage, war, a natural disaster or an order from a public authority.

If the situation lasts more than 30 days, either party may terminate the agreement without notice.

Force majeure does not relieve the customer of paying for what has been delivered.

12. Termination

13. Changes to these terms

ISIRO may change these terms on at least 30 days' written notice to the email address on the customer's account. The customer may terminate without notice before the change takes effect.

Where a change in the law or an order from a public authority requires a faster change, it is made as quickly as necessary, and the customer is informed immediately.

Each version has a number and a date, shown at the top and bottom of this page.

14. Assignment

ISIRO may assign the agreement to another company in connection with a sale or restructuring of the business. The customer is informed before it happens and may terminate without notice if the customer does not wish to continue with the acquirer. The customer may not assign the agreement without ISIRO's written consent.

15. Confidentiality

Each party treats what it learns about the other party's affairs as confidential. That also applies after the agreement has ended. ISIRO may name the customer as a customer in marketing if the customer has agreed to it in writing — otherwise not.

16. Governing law and venue

The agreement is governed by Danish law. Disputes are settled by the Copenhagen City Court at first instance. The same applies in the data processing agreement, so that the two agreements cannot end up before different courts.

17. Language

These terms exist in Danish and in English. Only the Danish version applies. The English one is a translation provided for understanding, and where the two disagree, the Danish one prevails. The same applies to the data processing agreement.

Version 1.0 – 15 November 2026