Security Overview

Each Organization's data is isolated at the database layer using row-level security policies scoped to the Organization identifier on every tenant-owned table. Cross-tenant access is denied by default and tested by an automated cross-tenant test suite.

• Sign-in with email and password or Google, provided through a managed authentication service.
• Optional multi-factor authentication.
• Role-based authorization (owner, admin, manager, employee) enforced in server-side code.
• Suspended and removed users lose access.
• Support-mode actions by internal staff are audit-logged.

Traffic to and from Pinstripe Fleet is encrypted in transit using TLS, terminated by our hosting and edge providers.

Uploaded job media is stored in a private object-storage bucket. Access is only through short-lived, server-issued signed URLs. The bucket is not publicly listable.

Portal tokens are hashed at rest and are subject to expiration, rate limiting (five failed attempts per token per fifteen minutes), and revocation. ZIP-code or last-four-digit checks are not strong identity verification; they are a defense-in-depth measure.

Inbound webhooks from Stripe (platform billing and Stripe Connect) are signature-verified before any privileged action. Unknown signatures are rejected without a database write.

Application secrets are stored in a managed secret store and are not present in source code or client bundles. The service-role key for the database is used only inside server-side handlers after role verification.

Sensitive actions are recorded in an internal audit log with the action, entity, metadata, and a hashed IP (not the raw IP). Support-session actions are attributed to the internal user who performed them.

Our database and object storage providers maintain their own backup regimes designed for disaster recovery. We do not offer per-user file restoration.

If you believe you have found a security issue, please email [email protected] and give us a reasonable opportunity to investigate before publishing details. We do not currently operate a formal bug-bounty program.

• Use a strong, unique password and enable multi-factor authentication when available.
• Keep your invitations and portal links private.
• Promptly remove access for departing employees.
• Report suspected security issues to us right away.

We do not claim SOC 2, ISO 27001, PCI DSS, HIPAA, or GDPR certification. We do not offer a HIPAA Business Associate Agreement. We do not claim uninterrupted availability, complete protection from data breaches, or end-to-end encryption.