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

Data processing agreement

The agreement required by Article 28 of the General Data Protection Regulation. 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.

This agreement sets out what ISIRO may and must do with information about the customer's end users. The customer is the controller, and Rishah ApS is the processor. The agreement is entered into when the customer ticks the box at sign-up and applies for as long as the customer relationship runs.

The agreement covers the end users only. For information about the customer's own company and the customer's own portal users, ISIRO is itself the controller, and that is what the privacy policy is about.

Precedence

The provisions of this agreement take precedence over corresponding or conflicting provisions in any other agreement between the parties, including the terms of business. That also applies to any cap or time limit that would otherwise restrict the obligations set out here.

1. The parties

The processor

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 contracting party is Rishah ApS. ISIRO is a secondary name and not a separate company.

The controller is the customer: the company that has created an account with ISIRO.

The division of roles. The customer decides why and how the end users' information is processed and is therefore the controller. ISIRO processes it solely on the customer's instructions and is therefore the processor.

The customer's own obligations. As controller, the customer must:

The customer bears responsibility for their own instructions. ISIRO is not responsible for the customer having a lawful basis for creating an end user.

Contact persons. Each party appoints a contact person for this agreement and informs the other party if the contact person changes. At ISIRO it is the company's owner; written enquiries are sent to support@isiro.dk, which is always read. At the customer it is the portal user registered as the owner of the account, and the email address on the account. The customer must keep that address up to date — a notification of a breach is sent to precisely that address.

2. Subject matter, duration, nature and purpose

The subject matter is the verification of one-time codes. The customer's own IT system calls ISIRO's API with an API key, and ISIRO answers whether a one-time code is correct.

The nature is automated processing. No human being sits and looks at the information. ISIRO creates an end user, stores an encrypted secret, calculates a code according to the RFC 6238 standard, compares and answers yes or no. ISIRO sends no SMS and supplies no app. The end user uses any authenticator app they choose and never signs in with ISIRO.

The purpose is to give the customer's end users two-factor authentication, so that the customer's own system can require more than a password.

The duration follows the customer relationship. The processing begins when the customer creates the first end user and ends under section 11, once the customer relationship has terminated.

3. What information, and about whom

The data subjects are the customer's end users: the people the customer gives two-factor authentication. They may be the customer's employees, but they may equally be the customer's own customers. ISIRO sees no difference and has no need to.

The information:

ISIRO never receives an end user's name, email address, telephone number or personal identification number. There is no field for it, and the API does not accept it. If the customer nonetheless sends a name or an email address as the id, that is the customer's own choice and the customer's own responsibility, and under the terms of business the customer is obliged to use a pseudonymous id instead.

The pseudonymous id is personal data all the same. ISIRO cannot itself connect the id to a human being, but the customer can, and pseudonymisation does not remove the protection. ISIRO therefore treats the id as personal data throughout.

No special categories of data under Article 9 and no data on criminal convictions under Article 10 are processed.

4. Instructions

ISIRO processes the information solely on the customer's documented instructions. The instructions consist of this agreement, the developer documentation, which describes what each call does, and the calls the customer's own system actually makes.

ISIRO does not process the information for its own purposes. ISIRO does not sell it, does not use it for statistics, does not use it to develop the product, and does not let it enter into any form of model training.

If ISIRO considers that an instruction infringes the data protection rules, ISIRO informs the customer and may refuse to follow it.

If the customer wishes to give instructions beyond what the API offers, they must be given in writing to support@isiro.dk, and ISIRO may charge for the work.

5. Confidentiality

Only the company's owner has access to ISIRO's server and database. There are at present no employees, freelancers or suppliers with access.

If anyone is given access, it is on these conditions, and they cannot be departed from:

6. Security

ISIRO takes the technical and organisational measures set out in Annex 1 at the bottom of this page. The measures have been chosen on the basis of what the information is and what can go wrong: a TOTP secret that gets out gives whoever holds it access to the customer's system in the same way as the end user themselves.

ISIRO may change a measure if the new one is at least as good. If security is reduced, the customer is given 30 days' notice and may object.

7. Sub-processors

The customer gives general written prior authorisation for ISIRO to use sub-processors.

The complete and only valid list is set out in ISIRO's document on sub-processors. The list is not repeated here, so that it cannot end up stated differently in two places. The customer can always obtain it by writing to support@isiro.dk.

Changes and additions are made on at least 30 days' notice by email. The customer may object, and if ISIRO makes the change anyway, the customer may terminate the agreement without notice and without paying for the remaining period.

ISIRO imposes on each sub-processor the same obligations as in this agreement and remains liable to the customer for the sub-processor's work.

8. Assistance with data subjects' rights

If an end user contacts ISIRO directly, ISIRO does not answer the enquiry. ISIRO refers the end user to the customer, because it is the customer who is the controller, and ISIRO does not know who the end user is.

ISIRO assists the customer in meeting the end user's rights under Articles 15 to 22 as follows:

The assistance is given free of charge as long as these are individual cases. If an enquiry requires substantial work, the price is agreed first.

9. Assistance with security, breaches and impact assessments

ISIRO makes available the information the customer needs in order to meet their own obligations under Articles 32 to 36. That covers the description of the security measures in Annex 1, the list of sub-processors and processing locations, the retention periods, answers to the questions the customer has to address in their own impact assessment, and the event log for the customer's own processing.

10. Personal data breaches

ISIRO notifies the customer no later than 24 hours after ISIRO has become aware of the breach. The period runs from ISIRO's awareness, not from the time the breach occurred.

The law requires "without undue delay" and gives the controller 72 hours to notify the supervisory authority. The 24 hours are ISIRO's own undertaking and are shorter than the law requires, precisely so that the customer has time left of their own 72.

The notification is given to the email address on the customer's account and contains as much as ISIRO knows at that point:

If ISIRO cannot provide everything within the 24 hours, ISIRO notifies within the deadline anyway with what is known and sends the rest as it emerges.

ISIRO does not notify the Danish Data Protection Agency of a breach affecting the customer's end users, and does not notify the end users either. That is the customer's task as controller, and ISIRO does not know the end users. ISIRO assists the customer in doing so.

11. Termination: erasure or return

The choice is the customer's. The law places it with the controller, and ISIRO does not choose on the customer's behalf. On termination of the customer relationship, the customer may require ISIRO either to erase all end user information or to return it and then erase it.

What return means in practice. The customer receives their own pseudonymous ids in a machine-readable file. The encrypted TOTP secrets are handed over in the form they are held in. The encryption key is not handed over — handing it over would be a security breach with no benefit to the customer, because the key also unlocks other customers' secrets. The recovery codes cannot be handed over, as they exist only as hashed fingerprints. The customer can export the event log themselves in the portal while access is still open, and ISIRO hands it over on request afterwards.

If the customer asks for nothing within 30 days of the account being closed, ISIRO erases. All end user information is erased no later than 30 days after the closure.

The customer's remaining information — the company's master data and the portal users — is information for which ISIRO is itself the controller, and it does not fall under this agreement. The period for it is set out in the privacy policy, and only there.

What remains:

12. Audit and inspection

The customer's right to inspect ISIRO cannot be contracted away. It is framed as follows:

13. Where processing takes place, and transfers to third countries

At launch, all processing takes place in the EU. The server and the database are held at ISIRO's hosting provider in Denmark, in a data centre in Denmark. The backups are held on the server's own storage in the same data centre. No information is transferred to countries outside the EU and the EEA.

ISIRO uses no American services to run ISIRO — not for mail, not for statistics, not for captcha and not for anything else. No JavaScript runs on the public pages, so there is no third party that can read along in the visitor's browser.

If ISIRO one day decides to process information outside the EU and the EEA, it will be done only on one of the bases in Articles 44 to 49 of the Regulation, and the customer will be given 30 days' notice as for a change of sub-processor.

14. Liability

Liability between the parties follows the terms of business, sections 9 and 10. Those provisions are not repeated here.

Two things stand firm regardless of what the terms of business say:

The cap in the terms of business also applies to a claim under Article 82 of the Regulation — but the exception for intent and gross negligence also covers breaches of this agreement. A cap therefore cannot be used to escape what ISIRO itself has promised about data security.

A data subject end user's own claim against the customer or against ISIRO under Article 82 cannot be limited by this agreement. An agreement between two parties cannot deprive a third party of a right the law gives them.

15. Duration, changes, version and acceptance

Duration. The agreement takes effect when the customer ticks the box at sign-up and applies for as long as ISIRO processes information on the customer's behalf. Section 11 also applies after termination.

Changes. ISIRO may change the agreement on at least 30 days' written notice by email. 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.

Version. Each version has a number and a date, shown at the top and bottom of this page and in ISIRO's own document. The two are always the same.

The customer's own data processing agreement. ISIRO uses its own agreement and no other. One set of obligations for all customers is the precondition for the list of sub-processors, the periods in the deletion policy and the breach procedure being able to fit everyone at once. The agreement is written to the Danish Data Protection Agency's own template and can be read here before the customer signs up.

Acceptance. The customer accepts the agreement with a separate tick box at sign-up. No field is ticked in advance, and the box for the data processing agreement is a different box from the one for the terms of business. On acceptance, we store the time, the version number, an unalterable copy of the exact text the customer agreed to, and a checksum of it. The copy is written once and is never overwritten.

Governing law and venue. Danish law. Disputes are settled by the Copenhagen City Court at first instance. The same applies in the terms of business, so that the two agreements cannot end up before different courts.

Language. The agreement exists 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.

Annex 1 — Security measures

The annex describes what has been built today. Anything not yet set up is marked, and it must not be read as a promise of a feature that exists.

1. Encryption

2. What is never stored in readable form

The event log must never contain a one-time code, a recovery code, an API key, a TOTP secret or a password. This is not merely a rule on paper: the logging function actively refuses to write a field with any of those names and throws an error instead. Only the outcome is recorded.

3. Access control

4. Limits on the number of attempts

5. What a refusal may reveal

An answer must never reveal whether something exists. An unknown id answers exactly as a wrong code does. An unknown email address in the portal answers exactly as a wrong password does. An invalid set-up link answers the same whether the token is wrong, expired or used.

An answer may disclose something the person asking is already entitled to know about themselves. The customer's own system calls with the customer's own key, and therefore the customer is told that an end user is blocked, that a key is suspended, and when it is free again.

6. Separation of customers

All of a customer's rows carry the customer's id, and every lookup in both the API and the portal is bound to it. There is no page and no call that shows data across customers. An API key can only reach the customer it was created under.

7. Logging and traceability

Every significant action is written to the event log with its time, type, outcome and a pseudonymised IP fingerprint: creation and deletion of end users, accepted and rejected codes, reused codes, used recovery codes, blocks, portal sign-ins, creation and revocation of API keys. The customer can see and export their own log in the portal.

Somebody has to notice an attack. An email is sent immediately if any of the following happens within an hour: more than 50 rejected calls from the same key, more than 20 failed portal sign-ins in total, or more than three keys suspended. In addition, a short weekly summary is sent every Monday.

8. What cannot be attacked

9. Backups

10. If a key is suspected of having got out

All TOTP secrets are re-encrypted under a new key. Until that has been done, the affected customers are suspended.

11. Keys and secrets in the code repository

The configuration folder has been outside the code repository from the very first commit. No encryption key, no secret fingerprint key and no password has ever been placed in the repository, not even temporarily. The repository history has been reviewed.

12. The server

13. Testing of the security

ISIRO tests its own security. Every change is tested before it is put into use, and the test must show both that what is permitted works and that what is not permitted is refused. The test and its result are kept, so that it can afterwards be shown what was measured.

Annex 2 — Processing locations

The processing locations follow the list of sub-processors. The list is not repeated here, so that it cannot end up stated differently in two places.

At launch: Denmark. The server and the database are held at ISIRO's hosting provider in a data centre in Denmark, and the backups are held on the server's own storage in the same place.

Version 1.0 – 15 November 2026