Omnel · for organisations · terms, processing and service · v1 · 16/10/2026

What we owe you, and what we ask of you.

Three documents in one place: the terms for organisations, the data processing agreement, and the service commitment. They are written to be read in one sitting. A lawyer reviews them before our first contract; what changes is dated here, and an organisation already seated is told thirty days before a material change applies.

Request access

1 · Terms for organisations

  1. Who we are, and what Omnel is. Omnel is operated by Selione, a company in formation in the United Arab Emirates; its registered name and address are added to this page the day the registration is complete. Omnel sells evidence about systems that speak for people or decide about them: an evaluation registered before it runs, a human decision the person can verify, an expert's knowledge kept and measured. Omnel measures; it never certifies. It is not a conformity assessment body, it confers no presumption of conformity with any law or standard, and what it publishes supports your own assessment without replacing it.
  2. Your organisation and your people. The person who opens your organisation becomes its owner and seats its members. You answer for who you seat, for the keys you make, and for what your people do with them. Your judges, your reviewers and your experts are yours: you choose them, you pay them, and Omnel pays no judge of yours.
  3. What you buy. Credits for the offers on the offers page, each described in one sentence there. Prices in US dollars. The price that binds is the one on your checkout or your invoice, fixed before anything runs. Taxes are added where the law requires them. A card pays at once; a transfer is paid against an invoice within thirty days of its date. A credit is valid for twelve months from purchase. What has not started can be refunded on request; what has run cannot. A monthly item ends at the end of the month in which you cancel it.
  4. The Register. You commit a protocol before any result exists; the registry draws the sample, your judges judge, and the close produces a signed report. What is published carries fingerprints, counts, bounds and dates, never the words of an item. The public log is append-only: a line written cannot be removed, by you or by us, and a mark withdraws itself the day its measurement stops holding. You may publish your report anywhere, with its signatures intact, and you may not present a withheld or withdrawn result as a measurement.
  5. Reviewed. You decide; we decide nothing. You are the controller of the decisions your reviewers take, and you keep your own legal basis for them. You commit a review policy before the first case, you choose reviewers who have the authority to depart from a recommendation, and you inform them, and where the law asks their representatives, that their openings, their time and the golden cases are recorded. The person's receipt is always free, and we never withhold it.
  6. Tacit. An expert takes part of their own will. What an expert says belongs to the expert until they publish it; a published card is your work product. Nothing unpublished leaves the expert's room, nothing of an expert trains a model, and an expert who erases their account takes everything of theirs with them.
  7. What you promise us. To use Omnel lawfully and for your own systems, people and decisions; to declare truthfully what you register; never to try to identify a person from the public log, nor to open what is sealed for someone else; and never to use a measurement to present a system as something its report does not say.
  8. What stays whose. Your items, your files, your cards and your reports are yours. Our software is ours; the specification of the Register is open, and anyone may implement a registry that behaves like ours. We may say that your organisation uses Omnel only with your written consent.
  9. Confidentiality. What you give us that is not published is confidential, and so is what we tell you about how Omnel is run. Each side protects the other's confidential information as it protects its own, for the duration of the contract and five years after.
  10. Availability, changes and suspension. The service commitment below says what we promise and what we do when we fall short. We may change the console and the offers; a material change is told thirty days ahead. We may suspend an organisation that breaks these terms, attacks the service or endangers a person, warning it first where we can, and we always let it export what is its own.
  11. Liability. Each side's liability for a year of contract is capped at what you paid us in the twelve months before the event. Neither side is liable for indirect or consequential losses. A report is a measurement of a system, not advice, and you remain responsible for every decision you take about a person. Nothing here limits a liability that cannot be limited by law, including for fraud and for breach of the processing agreement.
  12. Ending. You may close your organisation at any time; a one-off item runs to its close, a monthly item to the end of its month. Within thirty days of closing you may export everything that is yours in a documented format, and within thirty days after that we delete it, except the lines of the public log, which are fingerprints and cannot be removed, and what the law obliges us to keep.
  13. Law and disputes. These terms are governed by the laws of the United Arab Emirates. Before any proceeding, the two sides talk, in good faith, for thirty days. An organisation established in the European Union or the United Kingdom keeps every protection its own law grants it and that cannot be waived, and the place of any court is agreed in the signed order.
  14. Order of precedence. A signed order prevails over these terms; the processing agreement prevails on anything about personal data; the service commitment prevails on anything about service levels.

2 · The data processing agreement

Article 28 of the GDPR, and its equivalents in the United Kingdom and wherever your organisation is. This agreement binds us from the moment your organisation is seated, without a signature; a signed copy is given to any organisation that asks.

  1. Roles. For the Register (your items and your judges), for Reviewed (the files of the decisions your reviewers take, the statements of the people heard) and for Tacit (your experts' answers and cards), you are the controller and Selione is your processor. For the accounts of your members, their invitations and their keys, Selione is a controller in its own right, and the privacy page says what it keeps.
  2. What is processed. Register: the items of your pool, sealed; the private links of your judges and their verdicts. Reviewed: the recommendation, the inputs, the notice, the name and address of the person decided about, their statement, the reviewer's reasons, the reviewer's role, reference and public key. Tacit: an expert's answers, their cards, the questions colleagues ask. Door and console: addresses, roles, invitations. Data subjects: the people your decisions and your items are about, your judges, your reviewers, your experts, your members. Duration: the contract, then the export and deletion windows above.
  3. Our instructions are yours. We process only on your documented instructions, which are the console's actions, the API's calls and the protocols and policies you commit. If an instruction seems to us to break the law, we tell you before acting. We take no decision about a person, we read no sealed content for our own ends, and we use nothing of yours to train a model.
  4. Security. The content of a Reviewed file and of a Register pool is sealed under envelope keys the console never prints; reviewers sign with a key bound to their own device; every published artefact can be verified without us; our machines accept keys only, and every secret lives in a vault; encrypted backups are kept outside the main host and a restoration is rehearsed. The people who can reach your data are bound to confidentiality. A description of these measures, as they stand, is given on request.
  5. Sub-processors. The table below names them, with the country they work from. We tell seated organisations thirty days before adding or replacing one; an organisation that objects on reasonable grounds may end the affected service and is refunded what has not run.
  6. Transfers. Our database, our server functions, our witness and our encrypted backups run in Germany; we work from the United Arab Emirates, which holds no adequacy decision of the European Commission. For an organisation established in the European Union we sign the standard contractual clauses of Decision 2021/914 (module two, and module three for our sub-processors); for the United Kingdom, the Addendum of the Information Commissioner; and we give a transfer impact assessment on request. An organisation that needs its Reviewed files held in the European Union, or in the United Arab Emirates, says so before its first case: we answer in writing whether we can, and from what date, before it commits anything.
  7. Representative. Our representatives in the European Union and in the United Kingdom under Article 27 are named on the privacy page from the day of the public launch.
  8. Helping you answer people. The person decided about receives their receipt from us, free, and can verify it without us. When a person exercises a right with you — access, rectification, erasure, objection, human intervention — we give you, within ten days, what we hold about them in a form you can pass on, and we carry out the erasure you instruct. The words go; the fingerprints, signatures and log lines stay, because they cannot be removed and name nobody.
  9. Breaches. If personal data you entrusted to us is breached, we tell you without undue delay and in any case within forty-eight hours of becoming aware of it: what happened, which data, which people, what we did, what we advise. We help you notify your authority and the people concerned.
  10. Audit. Once a year we give you a written account of how we honoured this agreement. Once a year, on thirty days' notice, under confidentiality and at your cost, you or an auditor you appoint may verify it, on documents first and on site if documents do not suffice. A supervisory authority's request is answered without delay.
  11. End. When the contract ends, or when you ask, we return what is yours in a documented format and delete it within thirty days, and we confirm the deletion in writing. What stays is said in the terms above.
  12. Financial entities. For an organisation subject to the European rules on digital operational resilience, we provide the information its register of information requires and accept the contractual provisions those rules ask of a service that does not support a critical or important function. A service you classify as critical or important is contracted on its own terms, before the first case.
Sub-processorWhat forWhere
SupabaseDatabase, authentication, encrypted file storageGermany (Frankfurt)
VercelHosting of the console, the API and the public pagesGermany (Frankfurt), with a global edge
DigitalOceanThe witness of the public log, the scheduled jobs, the encrypted backupsGermany
ResendThe letters the console sendsUnited States
The model provider named on the privacy pageReviewed: up to three clarifying questions on a person's draft statement. Tacit: drawing cards from an expert's own answers, the echo's answers from published cardsUnited States
StripeCard payments, once switched on: the buyer's address, the product, the amountUnited States, Ireland
OpenTimestamps calendarsAnchoring the day's root of the log: they receive a fingerprint, never dataPublic servers

3 · The service commitment

  1. Availability. We aim for the console, the API, the public register and the public log to be available 99.5 % of each month, outside maintenance announced forty-eight hours ahead and kept under four hours a month. When a month falls under 99.5 %, you receive, on request within thirty days, a credit of a tenth of that month's recurring fees; under 99 %, a quarter. A published report stays verifiable without us whatever happens to the service.
  2. Incidents. An incident that stops the service or puts data at risk is acknowledged within four hours, worked on until resolved, and followed within five working days by a written account of what happened and what changed. Any other incident is acknowledged within one working day.
  3. Support. By email, and a person answers within two working days. There is no telephone line. A vulnerability reported to us is acknowledged within one working day and never held against the one who reported it in good faith.
  4. Durability. Encrypted backups are kept outside the main host, their restoration is rehearsed, and the public log is mirrored by a witness on a separate machine. A reading, a decision or a card lost by us is a breach of this commitment and is told to you as such.
  5. Exit. At any time, you export everything that is yours in a documented format. Signed reports and receipts verify forever with the public key published on the verification page; the specification is open, so another registry can carry your protocols on.
  6. What this does not cover. The availability of your own judges, reviewers and experts; outages of a sub-processor beyond our control; a feature marked as experimental in the console.
  7. During the closed beta. Until the public launch, the service is given with the same care and without the credits above, and this is said plainly to every organisation we seat. The credits apply from the first paid month after the public launch.

Write to contact@selione.ai: a person reads it. The privacy page says what Selione keeps about people, and the terms for travelers govern Selione itself.