Skip to content
RTI

Security and trust

Records that hold up when someone disputes them.

RTI protects inspection records in three ways: each submission, review decision and sign-off is written to a SHA-256 chained activity log, each workspace’s rows stay its own, and the record exports as files whenever you ask. A closeout package is only worth what it can prove months later.

Start freeTry the live demo
  • SHA-256 chained activity log
  • Row-level security on every table
  • Export as CSV and PDF
The audit trail

Each entry carries the one before it

  1. REC-003914:18

    prev
    d02c…41ab
    hash
    3b19…77e0

  2. REC-004014:26

    prev
    3b19…77e0
    hash
    9f5c…10d4

  3. REC-004114:32

    prev
    9f5c…10d4
    hash
    a4f7…9c21

Edit an entry and its hash stops matching; remove one and the next link breaks. Each check a manager runs is saved with its date.

Illustrative values. Every workspace has its own chain.
The challenge

What goes wrong when a record can change quietly

  • Edited after the fact

    A spreadsheet row or a shared document can be changed months later, and nothing shows that it was.

  • Nothing to check it against

    When a record is disputed, nobody can show it is the one that was signed.

  • Locked in someone’s app

    Records that only open inside one vendor’s app leave nothing to hand over when you change tools.

With RTI

  1. A change breaks the chain
  2. Checkable in your own browser
  3. Your records export as files

Each activity entry carries the hash of the one before it, so changing or removing one shows up the next time the chain is checked.

How the record is protected

Four things we hold ourselves to

  1. Tamper evident

    Each activity entry is hashed with SHA-256 together with the hash of the entry before it, so each workspace’s log forms one continuous chain. App users cannot edit or delete its entries.

  2. Isolated

    Row-level security is on for every table, and the web and phone apps read through it, so a query returns only your company’s rows. Server tasks that need wider access check your workspace first.

  3. Yours

    Inspections, checklist answers, photo lists, signatures and client sign-offs export as CSV, and inspection reports and turnover packages as PDF with the photos and signatures inside.

  4. Available offline

    In the RTI phone app and on the web inspection page, a finished inspection and its photos are saved on the device without signal and upload when it returns.

What we don’t claim

  • No third-party security certification. RTI holds no SOC 2 or ISO 27001 report, and we won’t imply one.
  • Tamper evident, not tamper-proof. The chain makes a change detectable; it does not make one impossible.
  • Photos are attached and listed, not hashed. The seal covers each inspection’s answers, status and review decision.
  • RTI documents the inspection. The AHJ or the licensed professional on the job accepts the work.
In plain language

What we keep, where it lives, and who can see it

What is stored

Your workspace and projects, the tags you print, your checklists, each inspection with its answers, photos, observations and signatures, and an activity log entry for each submission, review decision, markup, NCR change and client sign-off.

Where it lives

In a managed Postgres database with file storage alongside it, run by our infrastructure provider, Supabase, in the US. Photo, signature and logo storage is private. The app shows those files through links that expire within an hour, and a full-workspace export is emailed as a download link that lasts 7 days.

Who can see it

The people you invite, and anyone who joins with your workspace code, which expires after 7 days and starts them on the most limited role. Clients see only the approved inspections on projects you grant them. If RTI support signs in as one of your users, it must give a reason, and the session is written to your activity log.

Use cases

Three moments it answers

  • Use case 1

    An approval questioned later

    When an owner’s rep questions an approval months later, the activity log shows who approved it and when, and a chain check shows whether anything changed since.

  • Use case 2

    A client on one project

    When a client is granted one project in the portal, they see that project’s approved inspections and nothing else in the workspace.

  • Use case 3

    Leaving RTI

    When a company cancels, the workspace turns read-only, and its records can still be opened and exported for at least 30 days.

Security questions we get asked

6 answers

Can other companies see our work?
No. Every table has row-level security, and the web and phone apps read through it, so a query returns only your company’s rows. Server tasks that need wider access check your workspace before they read anything.
Who can see our data, and where is it stored?
The people you invite, anyone who joins with your workspace code (it expires after 7 days), and clients on the projects you grant them. Data sits with our infrastructure provider, Supabase, in the US, encrypted in transit and at rest, and the app shows photos through links that expire within an hour. RTI support can sign in as one of your users only with a stated reason, for 30 minutes, and the session is written to your activity log.
What happens to our records if we cancel?
The workspace turns read-only: no new inspections, but every record can still be opened and exported as PDF and CSV, and nothing is deleted while the account stays open. If you close the account, our Terms give you 30 days to export before deletion.
Can a record be changed without anyone knowing?
Not the parts RTI seals: each activity entry, and each inspection’s answers, status and review decision. Each entry carries the hash of the one before it, so an edited entry no longer matches its hash and a removed one breaks the next link. A manager can run the check at any time, and each run is saved with its date.
Does RTI have SOC 2 or ISO 27001?
No. RTI holds no third-party security certification and won’t imply one. This page says how the product is built instead, and the subprocessors page lists the services that hold your data.
How can someone check a record themselves?
A manager downloads the verification package from Activity. Anyone handed it can check it on the verify page, where the browser recomputes the chain itself and nothing is uploaded.

Put it on a real project.

Run a walk, then open the activity log and check the chain yourself.

Start freeTry the live demo

30-day trial · No card required