Trust & Data
Your security data stays yours — separated, access-controlled and factual.
Incident reports contain sensitive information about guests and staff. This page describes exactly how Security Report AI handles it today. We do not claim certifications we do not hold.
One private workspace per property
Each hotel is its own workspace. Database rules check workspace membership on every read and write, so one property can never see another property's incidents, logs or documents.
Role-based access
Owner, manager and officer roles have different permissions, enforced on the server — not only hidden in the interface. Owners invite and remove team members.
AI uses only the facts supplied
The officer's account is kept verbatim. Report fields are filled only from what was said, and anything not stated is listed as missing information — never guessed or invented. Procedure answers cite your own uploaded SOPs and say when something is not covered.
Private documents and exports
Uploaded SOPs and PDF exports are stored privately and opened through short-lived signed links. Connections to the service are encrypted in transit.
Export controls
Any saved report can be exported as a PDF. Workspace owners can download a data export of their workspace from Settings.
Deletion
SOP documents can be deleted from the knowledge base at any time. Deletion of a whole account or workspace is handled on written request.
Measurement on the public site
The public pages record anonymous, first-party usage steps (for example “demo opened”) with a random browser key, the campaign that brought the visit, a country code and a device type. No name or email is attached to these steps. The demo stores nothing you type.
Policies
Company details
To be completed: the operating company, registered address and VAT number will be published here once registration is finalised. Until then, written privacy, security and data-processing terms are provided before any hotel data is entered.