Security and data protection

Your data, your jurisdiction, your record of who touched it.

You are being asked to put trading figures, leases, covenants and valuations into someone else's system. That is a reasonable thing to be careful about, so here is what holds today and what is still being certified.

What holds today.

Isolated per organisation

Separation is enforced at database level rather than by a filter in the application. Another customer's query cannot reach your rows even if the application is wrong.

Encrypted in transit and at rest

TLS 1.2 or better on every connection, and encryption at rest on every store and backup. Keys are managed by the hosting platform and rotated.

Access by role, not by trust

A home manager sees their home. A financial controller sees the portfolio. A lender sees the covenant pack and nothing else. Single sign-on and multi-factor authentication where you use them.

Nothing is deleted

A mistaken record is marked void with the reason and the person, and stays searchable. Every change is held permanently against the figure, which is what makes an internal number usable as evidence.

Hosted where your law requires

United Kingdom, European Union or United States, chosen per organisation. Your data stays in the region you choose and is not copied to another one. Sensitive staff records sit in a separate store.

Backed up and recoverable

Point-in-time recovery with tested restores. A backup nobody has restored is an assumption rather than a backup.

The data processing agreement, the sub-processor list, the hosting regions and the penetration testing position are all written down, and we will answer any of it in writing before you commit to anything.

Certification: where we are, and when.

We would rather tell you what we hold today than imply more. Two standards matter to a client in this market, and we are working to both. Neither is held yet, and this page will say so until it is.

SOC 2 Type II

In progress

An independent auditor's opinion on whether our security controls were designed properly and operated continuously over a monitoring window, not a snapshot. It is the one most institutional clients and US counterparties ask for first. There is no exact European equivalent: the closest is an ISAE 3000 Type II assurance report, which is the same idea issued under a European standard.

  1. Controls written and mapped to the Trust Services Criteria
  2. Access control, change management, logging and backup in operation
  3. Readiness assessment with an independent firm
  4. Type I report: controls judged suitably designed at a point in time
  5. Observation window of at least three months, running continuously
  6. Type II report issued, then renewed annually

Budget is allocated and the assessment is the next step. We expect a Type I report first and a Type II report after the observation window closes. We are not publishing a date we cannot hold to: ask and we will tell you where it stands that week.

ISO/IEC 27001

In progress

A certified information security management system, a standing way of identifying risk, deciding what to do about it and proving the decision was taken. Where SOC 2 reports on controls, 27001 certifies the management around them. European and UK clients tend to ask for this one.

  1. Scope defined: the platform, its hosting and the people with access
  2. Risk assessment and statement of applicability drafted
  3. Policies in force and being operated, with evidence retained
  4. Internal audit and management review
  5. Stage 1 and Stage 2 audit by an accredited certification body
  6. Certificate issued, with surveillance audits each year

The two overlap by roughly two thirds, which is why they are being run together rather than one after the other. ISO 27701 for privacy follows 27001 if customers ask for it.

Until both are issued, this page says in progress. If you need certification in place before you can contract, tell us at the first conversation and we will be straight with you about timing rather than let it surface at procurement.

Where the AI stops.

Your data is messy. So is everybody's. Weekly returns arrive in different layouts, rows get renamed, figures go missing and PDFs are scanned. That is the problem Runko exists to absorb, and it is also the thing people are right to question.

AI reads. It does not calculate.

The model's only job is to work out that the cell marked Occ % wk38 is occupancy for week 38. Every number after that, EBITDARM, the valuation, the covenant test, is fixed arithmetic in code, which can be inspected and cannot drift.

Nothing counts until a person says so

What the model read is shown beside what arrived, and someone on your team approves it with a click. Confidence is not a substitute for a decision.

Missing stays missing

A figure that is not in the document is shown as absent. It is never estimated, interpolated or carried forward, so you can see which homes send complete returns and which do not.

Your documents are not training data

Nothing you send trains a model, for us or for anyone else. Documents are processed to extract your figures and are then held as your record.

If a screen cannot produce a number honestly, it shows the gap instead. A portfolio total prints its coverage, £84.6m across 12 of 14 homes with the two exclusions named, rather than quietly averaging over what it could not value.

Five sites or more?

Start with one module, or one part of the platform, set up around your own reporting cycle rather than a demonstration. Yours, not ours.