Your data

The terms on this page are summarised from the licensing agreement. The signed agreement governs, and a redline is the place to change any of it. Everything here is published because a buyer usually has to ask for it, and asking late is expensive.

Getting your data back

On termination, mode40 returns all customer data in a mutually agreed format, or deletes it, on written request.

The format is agreed at the point of exit rather than fixed in advance, so if you need a particular structure on the way out, write it into the agreement while you are still negotiating it. The clause also runs on a written request, so send one. A verbal wind-down does not start the clock.

Backups and archival copies

Backup and archival copies are securely deleted within 90 days.

That covers the copies that live outside the working system, which are the copies most people forget to ask about. It is also the only figure attached to backups anywhere in the agreement. There is no separate backup schedule published, and no retention figure for copies while the agreement is live.

Ending the agreement

• For convenience: 90 days’ notice. Either side can end the agreement without alleging a fault, on three months’ notice.
• For cause: 30 days, with a cure period. A for-cause termination is not immediate. The other side gets the chance to fix the breach inside the window.

Plan the exit work against the 90-day figure. Agreeing an export format, running the export, confirming it is complete, and then issuing the deletion request all sit inside that period.

Liability and warranty

• Liability is capped at 12 months of fees.
• The service is provided on an AS IS basis, with other warranties disclaimed.

They are on this page because quoting only the friendly half of an agreement is a way of hiding it. If your procurement standard needs a higher cap or an express warranty, that is a conversation to have before signature.

Retention and purge policy

Retention and purge policy is defined by the customer during implementation. mode40 does not impose a default schedule, and there is no platform setting that decides it for you.

The work happens in the data backbone phase, alongside your own role definitions, escalation workflows, firewall and VLAN posture, and MQTT topic access rules. How implementation works covers where that sits in the sequence. Bring your existing records policy to that session. It is faster than writing one from scratch at the table.

What is not defined

• There is no documented disaster-recovery plan.
• There is no published recovery point objective.
• There is no published recovery time objective.

The 90-day deletion clause is the only backup commitment written down anywhere. If a continuity requirement in your own policy depends on a recovery figure, ask for one in writing during scoping. There is no published number to cite, and treating the availability term as a substitute for a recovery target is a mistake.