Security
Last updated August 15, 2026
PestOPS is used by pest control businesses to run their operations and by their customers to manage service, so keeping every business's data separate and protected is core to how the product is built, not an add-on. Here's what that means in practice.
Every business's data is isolated at the database level
Every table in our database enforces row-level security (RLS) scoped to your business account. This isn't just an application-layer check that a bug could bypass — it's enforced by the database itself on every single query, for every table, with no exceptions. A staff member, technician, or customer can only ever read or write rows that belong to their own account.
Your customers' payments go directly to you
Each business connects its own Stripe account. Payments from your customers are deposited straight into your bank account through your own Stripe account — they are never pooled through a shared PestOPS account. Card numbers are collected directly by Stripe's own tokenized payment fields; they never touch our servers.
Encryption
- All data in transit is encrypted with TLS (HTTPS) — the app, our APIs, and our database connections.
- All data at rest is encrypted by our infrastructure providers (Supabase/Postgres, Vercel).
Access control
The Service supports role-based permissions — admin, office, technician, and customer roles each see only what they need to. Role and permission checks are enforced both in the application and, independently, at the database level, so a bug in one layer doesn't expose data the other layer would have blocked. Passwords are never stored in plain text; authentication is handled by Supabase Auth using industry-standard hashing and session management.
Ongoing review
We regularly review the codebase for security issues — including access control, tenant data isolation, and payment-handling correctness — and fix what we find. Security is an ongoing process, not a one-time audit.
Sub-processors
We rely on a small set of established infrastructure providers — Supabase, Vercel, Stripe, Resend, and Sent — each of which maintains its own security program. See our Data Processing Agreement for the full list.
Reporting a security issue
If you believe you've found a security vulnerability in PestOPS, please email [security@yourdomain.com] with details. We ask that you give us a reasonable opportunity to investigate and address the issue before public disclosure, and that you avoid accessing or modifying data that isn't your own while testing.