Security & Data Protection

1. Infrastructure

Flow's application and database tiers run entirely on SOC 2–certified cloud infrastructure: Vercel (application hosting) and Supabase on AWS (managed Postgres). One single-purpose sync host (DigitalOcean) retrieves fuel-network pricing files over SFTP from networks that only publish that way, and forwards them immediately into the same encrypted cloud pipeline — it is a retrieval relay, not a data store. API-based integrations (ELD, TMS, fuel-card platforms such as Relay) connect cloud-to-cloud and never touch it.

2. Encryption

All data moves over TLS in transit and is encrypted at rest in the database tier. Payment card data never touches our systems — billing runs entirely through Stripe (PCI DSS Level 1).

3. Tenant isolation

Flow is multi-tenant with two enforcement layers: every query is scoped to your carrier account at the application layer, and Postgres row-level security is enabled across all application tables as defense in depth. Your dispatch data, fuel transactions, and negotiated pricing are never visible to another carrier. Your negotiated fuel pricing is treated as confidential to you — it is never resold and never feeds any shared or cross-carrier dataset.

4. API credentials

ELD and fuel-platform credentials are stored server-side, encrypted at rest, and are never present in our codebase, in browser-delivered code, or in logs. Wherever the vendor supports it, Flow connects with read-only scopes: we read dispatches, positions, and transactions; write access (for example, in-cab messaging) exists only where a feature explicitly requires it and is separately gated (see Section 5). You can revoke Flow's access at any time from your vendor's side, and we delete stored credentials on request or on termination.

5. You control anything driver-facing

Carrier accounts start in Shadow Mode: Flow generates fuel plans your team can review in the portal, but no SMS, email, or in-cab message goes to a driver until your administrators switch outbound delivery on in your own settings. Connecting your APIs cannot, by itself, cause a message to reach a truck.

6. Access control & audit

Role-based access control for your team, signed JWT sessions, two-factor step-up authentication on our internal admin console, and audit logging of sensitive operations — including plan generation and every suppressed or delivered driver-facing message.

7. AI data flow

Flow uses large language models for two features, and we are precise about what they see. Driver SMS parsing sends only the text of the driver's message to Anthropic's API — no names, phone numbers, or account identifiers accompany it. The in-portal support assistant sends the question your team typed plus our own product documentation. No fuel pricing contracts, credentials, or financial data are included in any AI prompt. Anthropic does not train models on API data.

8. Subprocessors

Vercel (hosting), Supabase/AWS (database), DigitalOcean (pricing-file sync host), Stripe (payments), Twilio (SMS), Resend (email), Anthropic and OpenAI (AI features), HERE (routing). We will notify customers under a DPA before adding subprocessors that process their data.

9. Commitments

We commit to breach notification without undue delay, data deletion on termination, and no resale of customer data — ever. These terms are standard in our data processing agreement, available on request, alongside completed security questionnaires and mutual NDAs.

10. Certifications & roadmap

Flow itself does not yet hold a SOC 2 attestation — our infrastructure providers do, and a formal audit is on our roadmap as we scale. In the meantime we answer security questionnaires directly and will walk your IT team through the architecture on a call. Credential envelope-encryption with independent key management is in active development.

11. Contact

Security questions or reports: info@valveride.com. If you believe you have found a vulnerability, we ask for coordinated disclosure and will respond promptly.