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. Passwords are held by Amazon Cognito, Amazon's sign-in service, and must be at least twelve characters with an upper case letter, a lower case letter and a digit. A new password is checked against known breached passwords, and your last five passwords cannot be reused. Sign-in is limited to ten attempts per account per caller in fifteen minutes. Sign-in tokens expire after fifteen minutes and are renewed in the background, 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. Restomo does not offer two-factor sign-in.
• Notifications. Browser notifications use the Web Push standard (RFC 8291), which encrypts each message to the receiving device, so the push services in between cannot read them. Notifications to the iPhone app go through Amazon SNS and Apple's push service, are not encrypted end to end, and carry only a short title and line of text.
• 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 email address 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. Only a small number of Restomo administrators can open a company's account, and they do so only to support your company when you ask, to keep Restomo secure and working, or when the law requires it.

05Your data is yours

Your company owns every record it enters. You can export your boards, contacts, reports, hours and documents yourself at any time, and the Owner can ask for a full copy of everything, which we send within 30 days at no charge. If you leave, we delete your data when the Owner asks and confirm in writing when it is done.

06Reporting a security problem

If you find a vulnerability, email security@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

Restomo does not run a public status page. If something seems wrong, write to support@restomo.com and we will tell you plainly whether anything is wrong and what we are doing about it.