Ship secure contractor software.
TLS 1.3 in transit, AES-256 at rest, and row-level isolation per company, protecting your customer data, quote history, payment records, and crew timesheets. And a privacy stance you can show a homeowner without hedging.
What's default here is optional somewhere else.
Four controls most field-service tools leave to chance.
of traffic on TLS 1.3
AES at rest
breaches to date
breach notification SLA
Secure by default. Compliant from day one.
Every control here is enforced on every account. Nothing is a premium add-on, and nothing is configuration you have to remember to turn on.
SOC 2 Type II
In progressType II audit preparation underway, with controls mapped to the Trust Services Criteria.
TLS 1.3
No fallbackAll traffic encrypted in transit on the latest protocol, with no fallback to older versions.
AES-256 at rest
Every rowEvery row, attachment, and backup is encrypted at rest in a US-hosted region.
Row-level security
Database layerEnforced at the database. A rep physically cannot read another company's data.
Scoped access
4 rolesOwner, Manager, Rep, and Tech roles, each limited to the minimum surface they need.
Hosted in the US
AWS us-eastVercel edge plus Supabase on AWS us-east. No data transferred abroad without your direction.
How your data actually flows.
The same request path handles a quote lookup, a payment, and a crew clock-in. No secret back-channels, no customer tier that unlocks weaker defaults.
TLS 1.3, HSTS preload, no TLS 1.2 fallback.
Row-level security and service-role isolation on every table.
AES-256 on every row and attachment, with cross-region backups.
Three pillars. Built in, not bolted on.
Encryption, end to end
Every byte is encrypted in flight and at rest. Backups are stored in a geographically isolated region and verified with automated restoration tests.
- TLS 1.3 with HSTS preload
- AES-256 at rest on every row
- Cross-region backups, restore-tested weekly
Access, always scoped
Row-level security on every table. Service-role keys are never exposed to the client. Every privileged operation happens server-side and is logged.
- Supabase RLS, not app-layer checks
- Service-role keys held server-side only
- Four canonical roles, nothing ad-hoc
Detection, on a loud schedule
Error monitoring with PII scrubbed before send. Rate-limiting on every public endpoint. Dependencies reviewed weekly, with an on-call runbook already written.
- Sentry with PII scrubbing
- Rate-limited public endpoints
- Weekly dependency review cycle
Secure SDLC. Boring on purpose.
Security is not a quarterly review deck. It is enforced in the commit, the pull request, and the deploy pipeline, so the engineers who built the product cannot ship something unsafe by accident.
Every change to auth, billing, or access control needs a second set of eyes before merge.
Automated audit plus a human sweep every week. Critical CVEs patched within 72 hours.
Typecheck, lint, and tests all green before a deploy is allowed.
Material incidents disclosed to affected customers within a calendar day, in plain English.
Security is also what we don't collect.
No continuous GPS, no fleet telemetry, no just-in-case data. On Pro and Scale we capture location server-side at exactly three crew events to prove presence. Outside of those, we don't know where your crew is, and we are not asking.
- Clock-in. One location fix, verified against the job address.
- Clock-out. One fix, when the crew finishes or leaves.
- Job-site photo. One fix, attached to the photo record itself.
- Live-location map. Not streamed, not stored, not rendered.
- Driving telemetry. We are not a fleet tool. No braking events.
- Background location. The phone is not reporting when off the job.
Your data, across its whole life.
No hidden copies. No secret retention.
Capture
Clock-ins, photos, quotes, and payments arrive over TLS 1.3. The server signs and timestamps every event before anything is stored.
Encrypt
Data is written through row-level security into an AES-256 at-rest volume. Attachments are encrypted before storage hands the upload back.
Replicate
Point-in-time snapshots and daily backups are copied to a second region. A backup that cannot restore is not a backup, so we test them.
Export
Export your customer, job, and payment data as CSV or JSON at any time. No support ticket, no retention bait.
Delete
Account closure triggers a 30-day hold, then a permanent purge across primary, replica, and backups. We publish the clock, we don't hide it.
What we don't ship yet, and where it's headed.
We would rather tell you the gaps up front than have you find them during a vendor review.
SSO / SAML
Roadmap, Q3 2026No tenant-side SSO or SAML today. Enterprise SSO through Okta or Google Workspace is targeted for Q3 2026. If you need it sooner, talk to sales.
SOC 2 Type II
In progress, not yet auditedControls are designed against SOC 2, but we have not yet completed a Type II audit. Email security@revcorepro.com for our internal controls letter.
Custom-domain portal
RoadmapThe Scale plan supports a white-label portal with your logo and brand color today. A fully custom domain on the homeowner portal is on the roadmap.
24/7 incident hotline
Email-first, business hourssecurity@revcorepro.com is monitored during weekday business hours, with an after-hours pager rotation for confirmed priority-one incidents.
Published, not promised.
Report a vulnerability
security@revcorepro.com
Subprocessors
Third-party data processors
Status page
Live uptime and incidents
DPA
Data Processing Agreement
We acknowledge reports within one business day, with a 90-day coordinated disclosure window. Material incidents are disclosed to affected customers within 24 hours.
Common questions, plainly answered.
Still wondering if RevCore fits your crew? Talk to our team →
Is RevCore Pro SOC 2 certified?
A SOC 2 Type II audit is in progress, with our controls mapped to the Trust Services Criteria. Email security@revcorepro.com for our current controls letter while the audit completes.
Where is customer data stored?
In the United States. Vercel edge plus Supabase on AWS us-east, with cross-region backups. No data is transferred abroad without your direction.
Has RevCore Pro had a security breach?
No breaches to date. If a material incident ever occurs, affected customers are notified within 24 hours in plain English.
How does RevCore Pro handle crew GPS and location?
We capture location at exactly three crew events, clock-in, clock-out, and job-site photos, to prove presence. There is no live-location map, no driving telemetry, and no background tracking.
Who at RevCore Pro can access my data?
Access is row-level and role-scoped. Service-role keys are held server-side only, and every privileged operation is logged. Internal access is least-privilege and reviewed.
Can I export my data? Can I delete it?
Yes to both. Export customers, jobs, and payments as CSV or JSON anytime. Account closure triggers a 30-day hold, then a permanent purge across primary, replica, and backups.
