Where your data lives
- App and website are hosted on Vercel.
- Database and logins run on Supabase (PostgreSQL), which runs on Amazon Web Services.
- RO photos sent through Snap RO are read by Anthropic’s AI. ROFlo does not save the photo.
- Email from the service is sent through Resend.
- HTTPS everywhere. Every connection to the app and website is encrypted in transit.
- Encrypted at rest. The database is encrypted at rest by our host.
- Secrets stay on the server. Service keys and credentials live only on the server and are never sent to the browser.
Who can see what
Every dealership’s data is kept separate. Database row-level security, backed by server-side checks, limits each user to their own dealership. The public key used by the browser cannot read repair-order data; we have verified this directly. Within a dealership, access depends on role:
| Role | What they can do |
|---|---|
| Admin | Full access to the dealership’s ROFlo setup and data. |
| GM | Read-only management views across the operation. Saturday dispatch only if an Admin turns it on for them. |
| Advisor | Their own follow-ups and promise work. Saturday dispatch only if an Admin turns it on for them. |
| Technician | Their own work. |
| BDC agent | Only the recall follow-ups assigned to them. |
Admins can “preview as user” to see exactly what a teammate sees. Preview mode is read-only, so nothing can be changed while previewing.
Protecting customer information
- Customer details in ROFlo (such as names, phone numbers and vehicles on follow-up lists) come from reports the dealer imports, and are visible only to that dealer’s users with the right role.
- The dealer controls its customers’ data; ROFlo processes it only to provide the service. See our Privacy Policy.
- ROFlo does not sell data and does not use it for advertising.
- ROFlo works alongside your DMS and does not write back to it, so it cannot change your DMS records.
What we never store
- Payment card numbers
- Bank account information
- Social Security numbers
- Driver’s license numbers
- Passwords: handled by Supabase Auth and stored hashed. ROFlo never sees them.
Reliability & backups
- All-or-nothing Day Close. Day Close runs as a single database transaction: it either completes fully or changes nothing, so you never get a half-closed day.
- Backups before major changes. We take a full database backup before major changes, in addition to our host’s own backups.
- Watched scheduled jobs. The automatic 2 AM Day Close and the Monday recall scan email Admins if they fail, so problems are seen right away.
Accountability & audit trail
ROFlo keeps audit records of the events that matter, so you can see what changed and who changed it:
- Repair-order events
- Dispatch edits
- Recon labor corrections
- Line completions, with who marked the work finished and when
Questions
Need more detail, or have a security questionnaire for us to complete? Email support@getroflo.com and we will respond.