This page summarizes the technical and organizational measures HRGrove uses to protect Customer Data. It's a companion to our Privacy Policy and Data Processing Addendum, not a replacement for them. Those documents control if anything here is unclear or out of date.
Tenant isolation
Every customer's data is isolated at the database level using Postgres row-level security policies, enforced by the database itself on every query, not just an application-layer check. One company can never see or query another company's records, regardless of what a bug in our application code might otherwise allow.
Encryption
Data in transit is encrypted with TLS 1.2 or higher, everywhere, between your browser and our servers, and between our servers and our infrastructure providers. Data at rest is encrypted at the database and storage-volume level. Social Security Numbers and similar tax identifiers get an additional layer of field-level encryption (AES-256-GCM) on top of that, so they're protected even in the unlikely event other database-level protections were somehow bypassed.
Authentication & access control
Passwords are hashed, never stored in plain text, and never visible to HRGrove staff. Optional two-factor authentication (TOTP authenticator apps) is available for every account. Access inside a workspace is role-based: admins, managers, and employees see only what their role permits, enforced by the same row-level security that keeps companies isolated from each other.
Audit logging
Sensitive actions, such as role changes, document signatures, employee record edits, and data exports, are logged with who did it, what changed, and when. Admins can review this trail any time from the dashboard, without filing a support request.
AI features
Only the minimum context a feature needs is sent to our AI provider, Anthropic, to generate a response. See our Privacy Policy, Section 4, for exactly what that is for each feature. We never send Social Security Numbers or payment information to our AI provider, and that data isn't used to train Anthropic's models under our agreement with them.
Payments
Card and bank details are collected and stored directly by our payment processor, Stripe, on infrastructure built for that purpose. HRGrove never receives or stores your full card number.
Infrastructure
HRGrove runs on Supabase (database, authentication, file storage) and Vercel (application hosting), both mainstream providers used broadly across the industry, hosted in the United States.
Data portability & deletion
You can export your workspace's data at any time from Settings, and request full deletion whenever you want. There's no lock-in and no waiting on a support ticket to get your own data back. See our Privacy Policy, Section 9, for the specific retention timeline after cancellation.
Certifications
HRGrove is a young platform and hasn't pursued its own formal security audit or certification (such as SOC 2) yet. To be clear about what that means: the certifications below are held by the vendors we run on, not by HRGrove itself.
- Supabase(database, authentication, file storage) — SOC 2 Type 2 compliant, ISO 27001 certified, and HIPAA compliant.
- Vercel(application hosting, CDN) — SOC 2 Type 2 compliant.
- Stripe(payment processing) — certified to PCI Service Provider Level 1, the most stringent level in the payments industry. HRGrove never stores or sees your card details.
Running on certified infrastructure is not the same as being certified, and we don't claim otherwise. What we do control — per-tenant data isolation, encryption of sensitive fields, and a full audit trail — we built in from day one rather than adding it later. We'll update this page if we complete an audit of our own.
Reporting a security issue
If you believe you've found a security vulnerability in HRGrove, please report it to info@hrgrove.combefore disclosing it publicly. We'll acknowledge reports promptly and keep you updated as we investigate.