Security and data handling
Your PSM records stay yours, and stay separated.
CompAI holds mechanical integrity records, PHAs, audit findings and training history. Here is how that data is hosted, who can reach it, and how our AI features handle it.
Hosted on Google Cloud
CompAI runs on Google Cloud and Firebase infrastructure. Traffic is served over HTTPS, and Google Cloud encrypts stored data at rest and data in transit by default.
Role-based access
People sign in with Firebase Authentication and are assigned a role: Super Admin, Admin, User, Guest, Auditor or Demo. What each role can read or change is enforced by database rules on the server, not only in the screen you see.
Facility-scoped data
Each user is assigned to one or more facilities. Database and file-storage rules check that assignment on every request, so a user cannot open another facility's records.
Third-party auditor access
Outside inspectors use a dedicated Auditor role. Auditor accounts reach the audits they are assigned and cannot edit facility profiles, user accounts or facility records.
Isolated demo accounts
Demo access creates a separate, time-limited sandbox with sample records. Demo accounts cannot read your production facility data or change user accounts.
AI keys stay on the server
AI features call the Gemini API from server-side functions. The API key is held as a secret in Google Cloud, never in your browser, and those functions require App Check verification from the CompAI app.
Abuse protection on public forms
The demo request form and the app use Firebase App Check with reCAPTCHA Enterprise to block automated traffic.
Questions from your IT or safety team?
We will answer a security questionnaire, walk your IT team through how access works, or talk through how CompAI fits your data policies. Email sales@psmcomp.ai or request a demo and ask during the walkthrough.