Security
Your maintenance records, kept in Frankfurt and in the right hands
The database and the app run in Frankfurt. Every request to the database is checked against the person’s workspace and role, and every change leaves a trace.
- Hosted in Frankfurt
- Access checked by the database
- Two-factor sign-in
The question
“Before our records go into a new system, IT wants to know where they live and who can read them.”
Fair questions. Here are the answers, covering only what Ophelm does today.
Data sheet
Where your data lives, and who sees it
The five things your IT department will ask about first.
- Hosting
- Frankfurt, Germany
- The database, the files and the app run in Frankfurt, inside the EU.
- Access
- Checked by the database
- Rules in the database itself decide which records each person may read or change: only in the workspaces they belong to, and only what their role allows. Not just on the app’s screens.
- Sign-in
- Two-factor, with an authenticator app
- Anyone can add a 6-digit code from an authenticator app to their password, with 10 recovery codes in case the phone is lost. Until the code is entered, the account reaches nothing.
- Changes
- Logged, never edited
- Every record keeps its activity history. Changes to permissions, roles, statuses, types and fields go into a change log with who and when; nobody can edit or delete an entry.
- Backups
- Every day
- The production database is backed up daily.
In the product
Control you set yourself
Seven roles, three answers per permission
For each permission a role gets All, Own or None, for the whole organisation or changed for one workspace. The organisation can lock those changes.
Who did what, on every record
Each work order and asset shows its activity: who changed what and when, signatures included.
Closed work stays closed
A work order completes only with its required fields, steps and signature, and closed work orders can be locked. Reopening one removes the signature.
Data protection
GDPR, in plain terms
What we can tell you today, and what follows with the legal pages.
Data processing agreement
Ophelm processes the data in your workspaces on your behalf, and a data processing agreement under Article 28 GDPR sets that down. It is being prepared together with our privacy policy and will be published here.
Who handles the data
Ophelm runs on a few providers. The full list, with each one’s role and region, comes with the data processing agreement.
- Supabase
- Database, sign-in and files · Frankfurt
- Vercel
- Runs the app · Frankfurt
- Resend
- Sends email
- Sentry
- Error reports · EU
People who report through the portal
The portal asks for a name, email or phone only once your workspace links its privacy policy. The details are removed 3 to 24 months after the report is closed, as you choose, or at once for anyone who asks.
Questions from your IT department?
Write to us, or start the free trial and look at the roles and the change log yourself.