Fernet AES-128-CBC + HMAC-SHA256 At RestStrict Multi-Tenant PostgreSQL 16 IsolationStripe PCI-DSS Level 1 · TLS 1.3 Edge

Institutional Security & Financial Ledger Trust

FleetPulse AI processes toll transponders, municipal camera tickets, OBD-II GPS trip logs, and reimbursement packets for car-sharing hosts. Every layer is built around authenticated encryption, narrow read-only OAuth permissions, automatic duplicate protection, and private workspace isolation.

Pillar 01 · Cryptography

Fernet Encryption at Rest & TLS 1.3 in Transit

  • Fernet Symmetric Authenticated Encryption: All Google Gmail OAuth refresh/access tokens, Bouncie OAuth2 tokens, and connected toll-portal credentials are encrypted prior to database write via Fernet (AES-128-CBC + HMAC-SHA256) using environment-isolated keys (ENCRYPTION_FERNET_KEY) with fail-closed startup enforcement in production.
  • Cloudflare Edge TLS & Zero Exposed DB Ports: All public web, API, and webhook traffic terminates over TLS 1.2+ / TLS 1.3 via outbound-only Cloudflare Tunnel with HSTS, X-Frame-Options: DENY, X-Content-Type-Options: nosniff, and strict CSP. PostgreSQL 16 and Redis 7 bind solely to isolated internal container networks with zero public port exposure.

Pillar 02 · Least-Privilege OAuth

Read-Only Scoped Gmail & OBD-II Integrations

  • @turo.com-Filtered gmail.readonly: Adheres strictly to the Google API Services User Data Policy (including Limited Use). Queries only @turo.com reservation/incidental notices, cannot send/modify/delete emails, never indexes personal correspondence, and never trains generalized AI models.
  • Scoped Bouncie OBD-II Telemetry: Ingests read-only trip odometer readings, ignition timestamps, and corridor GPS coordinates with cryptographic webhook verification to prove guest vehicle custody during disputes.

Pillar 03 · Payment Integrity

Stripe PCI-DSS Level 1 & Deterministic Idempotency

  • Zero Raw Card Storage on FleetPulse Servers: Payment cards, Apple Pay, Google Pay, Link, and US Bank ACH mandates are handled exclusively inside Stripe PCI-DSS Level 1 certified frames and webhooks verified via Stripe-Signature HMAC.
  • Exact Cent-Level Totals & Duplicate Protection: Every toll and ticket charge is stored to the exact cent with zero rounding drift, and every imported transaction is automatically fingerprinted so re-uploaded statements never double-count guest charges.

Pillar 04 · Browser Sandboxing

Manifest V3 Chrome Extension Security Model

  • Zero Remote Code Execution: FleetPulse Host Bridge is built on Chrome Manifest V3 with script-src 'self'; object-src 'self'. All scripts are compiled into the extension bundle at build time; backend communication exchanges validated JSON only.
  • Narrow Explicit Host Allowlist (No <all_urls>): Restricted strictly to Turo host workflows, authorized FleetPulse origins, and named U.S. toll portals, paired with revocable fp_ext_* handoff tokens and explicit extension-ID CORS verification.

Built for Accuracy, Privacy & Zero Lock-In

Daily Encrypted Backups · 14d Retention

SUBSCRIPTION FLEXIBILITY

Cancel Anytime

1-click cancellation from Billing Settings with zero contracts. Keep full access through the end of your billing period; subscriptions are non-refundable.

CLAIM ACCURACY GUARD

95%+ Match Confidence

Every toll is cross-checked against trip pickup and return times. Unclear scans pause in Needs Review so you never misbill a guest.

DEDICATED PERFORMANCE

Instant Duplicate Protection

Re-uploading an overlapping E-ZPass CSV or screenshot automatically skips already-processed tolls so guests are never double-counted.

Private Account Data Isolation

Every host fleet runs inside its own isolated workspace. Your vehicles, license plates, guest reservations, connected inbox data, and reimbursement packets are strictly scoped to your account and protected by edge rate limiting and cryptographic signature verification.

Daily Encrypted Backups

Automated background jobs capture daily encrypted snapshots onto isolated backup storage with 14-day retention rotation and automatic integrity verification, keeping your fleet history and claim records safely recoverable.

Responsible Vulnerability Disclosure & Security Contact

Discovered a potential security vulnerability or OAuth scope concern? Report it directly to [email protected] with reproduction steps. Our engineering team acknowledges good-faith reports within 24 hours and commits to safe harbor for researchers acting within our responsible testing scope.