Terms of use for Inxo · Inxo fra CIRON

1 The agreement

1.1

These terms apply between CIRON AS ("we") and the organisation that creates an account in Inxo ("you"). They also apply to each individual user the organisation gives access.

1.2

Alongside these terms, the privacy notice and the data processing agreement apply. In the event of conflict, the data processing agreement prevails for the processing of personal data.

A self-service account is created as a trial account with a click-accepted trial agreement. The full data processing agreement applies from signature. Which agreement applies to you is always shown in the app under Organisation.

2 What Inxo is — and is not

2.1

Inxo is a tool for keeping preparedness in order: plans, exercises, incident response, notification deadlines and logging.

This is what it does:

Keeps plans versioned and available, including offline
Starts the notification deadlines from the moment you became aware
Tells you on the device when a deadline approaches, if you turn that on
Records who did what, when and why

This is what it does not do:

Monitors nothing and detects no incidents
Sends no notifications to authorities or anyone else on your behalf
Makes no decisions, and replaces no role
Sends no email — there is no code that could

2.2 The responsibility to detect, notify and respond is yours.

It cannot be transferred to a tool, and we do not pretend it can. The clocks in Inxo are a reminder, not the discharge of a notification duty.

2.3

The service is not approved for information classified under the Norwegian Security Act, and shall not be used for it.

2.4 We prepare. We never notify.

Inxo is built to prepare, and it can also carry the response for an organisation that has no system of its own for that. If you already have a crisis management system — the one you log the incident in and send notifications from — we do not replace it. That is still where the incident is handled and the notifications go out. Inxo covers what most such systems do not: making practice part of daily operations, so that the shift into heightened operations and preparedness is something the organisation already knows how to do — and being able to document that it does.

2.5 We are not a notification organisation, and never will be.

We do not build mass notification — no SMS, no voice, no call chain working down a list. If you need to reach many people quickly, you should use a tool built for that. We recommend others where they are better than us, and we say so unprompted.

2.6 The assistant on the device.

Where it is turned on, a language model runs in the browser on your own device. The model is downloaded from our service once, at your choice, and all processing happens locally — nothing you write and nothing from the log is sent to us or to anyone else. The assistant writes drafts that a person reads and saves. It never changes the log, never decides deadlines, and never sends anything out.

3 Account and access

3.1

Sign-in uses a passkey. There are no passwords. You are responsible for who may register a passkey with you, and for withdrawing access when someone leaves.

3.2

Activation codes are issued by your own administrator over a channel you already have. The service does not send them.

3.3

Each organisation sits at its own address under inxo.app, with its own data store and its own encryption key. A passkey works only at the address where it was created.

3.4

You choose who is owner and administrator, and decide the roles of everyone else.

3.5 Make sure more than one person can grant access.

We hold no standing access to your organisation. If you lose everyone who can assign roles, we cannot open the door either. The tool says so when the organisation is down to a single way in, and suggests what you can do.

4 Your responsibility for the content

4.1

You own the content you enter. We use it for nothing other than providing the Service, and never to train models, for marketing, or for analysis across customers.

4.2

You are the controller for personal data you record about employees, contacts and third parties, and for there being a lawful basis for recording them.

4.3

Attachments are off by default. Turning them on happens per organisation and after a data protection impact assessment.

4.4

The log is append-only. An entry can be corrected by a new entry, not removed. That is a property, not a limitation: a log that can be changed afterwards is not documentation.

5 Availability, and the fact that this is being built

5.1 Inxo is under construction.

We release functionality once it has been in real use in our own preparedness. What is finished is stated on the front page and in the app.

5.2

We promise no particular uptime unless separately agreed. We aim for continuous operation and give notice of planned downtime.

5.3

We may change and develop the Service. If we remove something you depend on, we say so in good time and explain why.

5.4 The plans must work without us.

Approved plans can be made available on devices and read and run offline — including when our service is down. That is the most important property of a preparedness tool, and we treat it accordingly.

5.5 Universal design.

We measure accessibility against WCAG 2.2 level AA, with text contrast against level AAA, in every theme. What is in order and what is not is set out in the accessibility statement. If you find something that does not work, write to contact@ciron.no.

6 Use that is not permitted

6.1

You shall not attempt to reach other organisations' data, circumvent access control, or load the Service in a way that affects others.

6.2

You shall not use the Service for anything unlawful, or enter content you have no right to process.

6.3 Security testing is welcome

— against your own organisation, and by arrangement with us. Report findings to contact@ciron.no. We reply, and we credit the person who reports. We do not pursue anyone who reports in good faith, and we ask for reasonable time to fix before disclosure.

7 Termination, export and deletion

7.1

You may terminate at any time.

7.2

Content can be exported from the app while the account is active. Export what you need before you terminate.

7.2.1

The trial account lasts 14 days. When the trial is over, the account is locked against entering new data. You can still sign in, read everything already there and export it — for up to 90 days.

7.2.2

After 90 days the content is permanently deleted and cannot be recovered. Deletion happens automatically, by the procedure in 7.3. It cannot be undone, and we cannot retrieve the content for you. The same applies when you terminate an agreement yourself: ninety days from termination, and the content is gone.

7.2.3

If you move to a paid subscription before the deadline, the account reopens with the content intact.

7.2.4 For customers with a signed data processing agreement, Annex VII of that agreement applies.

It sets out the transitional period, the retrieval window, the exportable data and the erasure guarantee in exhaustive form. We charge nothing for switching or retrieval.

7.3

On deletion, the organisation's encryption key is deleted first. After that the content is unreadable, including in backups. Then the rows and the whole data store are deleted.

7.4

The audit trail is preserved. It contains only internal identifiers, and documents the deletion itself.

7.5

We may close an account for material breach, or for use that puts other customers at risk. We say so first, unless it is not justifiable to wait.

8 Liability

8.1

The Service is provided as it is. We give no warranty that it is error-free or always available.

8.2

We are not liable for indirect loss, lost profit, or loss arising from your failure to meet a notification duty. The deadlines in the Service are a reminder; the duty is yours.

8.3

Our total liability is limited to what you have paid for the Service over the last twelve months. For trial accounts liability is limited to zero, since no fee has been paid.

8.4

The limitations do not apply in cases of intent or gross negligence, or where they cannot be agreed under mandatory law.

9 Changes, governing law and disputes

9.1

We may change these terms. Material changes are notified in the app at least 30 days before they take effect, and the version date above changes. If you disagree, you may terminate before the change takes effect.

9.2

The notice is for those of you who have already accepted an earlier version. The version you have accepted remains valid throughout the notice period — nothing is blocked, and you can use the service as before while you consider the change. The date the new version takes effect is stated in the notice.

9.3

When the period ends, each user must read and confirm the updated terms at next sign-in. Until that is done, you can still sign in, read everything already there and export it — but not save new changes. Signing out, the documents themselves and the confirmation are always available.