The Bench COO ← Back to site

Security & Vulnerability Disclosure

Last updated: May 28, 2026

We take the security of The Bench COO seriously. This page covers how to report a security issue, what to expect when you do, the third-party services we rely on to deliver the product, and how we handle customer data on connected platforms.

1. Reporting a vulnerability

If you believe you have found a security issue in our app, website, or any connected integration, please email security@thebenchcoo.com with a description of the issue and steps to reproduce. The address forwards directly to the founder.

A machine-readable version of this contact lives at https://app.thebenchcoo.com/.well-known/security.txt per RFC 9116.

2. What to expect from us

We do not currently run a paid bug-bounty program, but we are happy to acknowledge researchers who report issues in good faith.

3. Scope

The following are in scope for vulnerability disclosure:

Issues on the platforms we integrate with (QuickBooks, HubSpot, Square, etc.) should be reported to those vendors directly. We will help coordinate where appropriate.

4. Out of scope

The following are explicitly out of scope and we ask that you do not test them:

5. Safe harbor

If you make a good-faith effort to comply with this policy — you stay in scope, you do not exfiltrate data, you do not disrupt service, and you give us a reasonable window to respond before public disclosure — we will not pursue legal action, regulatory complaints, or DMCA claims against you for your research.

We cannot grant safe harbor on behalf of third parties (the platforms our app integrates with). If your research touches their systems, please follow their published disclosure programs.

6. Subprocessors

We use the following third-party services to operate the product. Each is named here in the spirit of transparency and to support customer due-diligence requests.

ServicePurpose
NetlifyApplication hosting, CDN, edge functions, forms
SupabaseManaged Postgres database, authentication, file storage
AnthropicClaude language model for the COO agent
StripeSubscription billing and payment processing
ResendTransactional email (invitations, notifications)
SentryApplication error monitoring (with sensitive headers and OAuth-shaped query parameters scrubbed before transmission)
PlausiblePrivacy-respecting product analytics (no individual user tracking)
Google WorkspaceOperational email (contact@, daniel@, security@)
Intuit (QuickBooks)Customer-authorized accounting data access via OAuth
HubSpotCustomer-authorized CRM data access via OAuth
SquareCustomer-authorized sales data access via OAuth
JobberCustomer-authorized field-service jobs data access via OAuth
GustoCustomer-authorized payroll data access via OAuth

Customer-authorized integrations are accessed only with the explicit consent of the customer, who can revoke access at any time from within the app or from the connected platform's own settings.

7. Data handling for connected platforms

When you connect a platform like QuickBooks, HubSpot, or Square to the app:

8. Data retention & deletion

Customer chat history, business profile, and team membership data are retained for the duration of the customer's account. Customers may request account deletion at any time by emailing contact@thebenchcoo.com; we honor deletion requests within 30 days.

Connection-related data tied to a third-party integration (OAuth tokens, cached API responses, platform-derived report blocks in chat) is removed within 30 days of disconnection — in practice, synchronously at disconnect time, well before the 30-day limit.

9. Encryption in transit

All traffic between customers, our application, and our subprocessors uses TLS 1.2 or higher. The app and marketing site enforce HTTPS via HTTP Strict Transport Security with a two-year max-age, includeSubDomains, and preload directives.

10. Encryption at rest

The managed Postgres database operated by Supabase is encrypted at rest using their platform-default disk encryption. On top of that, OAuth access and refresh tokens are encrypted application-side using AES-256-GCM before being persisted; the encryption key is held only in environment configuration on Netlify and is never written to the database.

11. Access controls

Database, hosting, and OAuth-provider administration accounts require multi-factor authentication. Access to production data is limited to the founder (daniel@thebenchcoo.com) and is used only for support, incident response, and platform maintenance.

12. Updates to this policy

We may update this page from time to time. Material changes will be reflected in the “Last updated” date above.

13. Questions

Security reports: security@thebenchcoo.com
General contact: contact@thebenchcoo.com
Phone: 916-775-7717

The Bench COO
Daniel Zimmer
5960 South Land Park Dr #608
Sacramento, CA 95822