What protects your job data in Restomo, stated plainly.

01What is true today

Restomo holds your whole job history, so you should be able to read exactly how it is protected without booking a call. This is the current list. Nothing on it is aspirational.

• Row-level security on every table. Every row in the database carries your company's identifier, and the database itself enforces that a session from your company can only read and write your company's rows. The application cannot forget to check, because the check is not in the application.
• Encryption at rest. The database and the file storage that holds your photos, scans and documents are encrypted at rest.
• Encryption in transit. Every connection between a browser or phone and Restomo uses TLS. There is no plain HTTP anywhere.
• Point-in-time recovery. The database keeps a continuous backup, so it can be restored to a moment in time, not just to last night.
• Sign-in protection, without a second factor yet. Passwords are hashed with bcrypt by the authentication server and must be at least twelve characters with letters and digits, checked against known breached passwords. Sign-in is limited to ten attempts per account per caller in fifteen minutes. Access tokens expire after an hour and refresh tokens rotate; a session ends after thirty days idle or ninety days in total, and deactivating a person or lowering their access level ends their sessions at once. The authentication server has TOTP enrolment switched on, but the app does not yet offer a place to enrol, so no account has a second factor today. It is on the list and it is not built.
• Encrypted push notifications. Notifications to phones use the Web Push standard (RFC 8291), which encrypts each message to the receiving device. The push services in between cannot read them.
• Hosted in the United States.

02SOC 2, in progress

We are working through a SOC 2 program now: policies, access reviews, logging, vendor reviews and the evidence trail an auditor needs. We do not hold a SOC 2 report today, and we will not say we do until the report exists. When it does, it will be linked from this page.

03What we do not claim

You will not find a badge on this site for a certification we do not hold. We do not claim HIPAA compliance, ISO 27001 or a completed SOC 2 audit. If a claim you need is not on this page, ask us and we will tell you plainly where it stands.

04Access inside your company

Every person signs in with their own username or email and their own password. Access levels decide what a technician, an office lead or an owner can see and change, and an owner can deactivate any account at any time. Restomo staff do not read your job data in the normal course of business; when support needs to look at something, it is at your request.

05Your data is yours

Your company owns every record it enters. Ask for an export and you receive all of it in an open format. If you leave, we delete your data on request and confirm in writing when it is done.

06Reporting a security problem

If you find a vulnerability, email support@restomo.com with the details and we will reply within one business day. We ask that you give us a reasonable window to fix it before publishing, and we will credit you if you want that.

07Status

There is no public status page yet. status.restomo.com is not live and nothing on this site links to it; this page will link it the day it answers. Until then, ask support@restomo.com and we will tell you plainly whether anything is wrong.