Governing Language: This document is provided in multiple languages for your convenience. In the event of any conflict or discrepancy between translated versions and the English version, the English version shall prevail and govern.
CrewRadr ("the App," "we," "us," or "our") is a zero-knowledge, safety-focused location-sharing, driving telematics, and emergency-preparedness platform for trusted groups ("crews") — families, field teams, commercial fleets, and close-knit communities. This Privacy Policy explains what data we collect, how we use it, how our Zero-Knowledge End-to-End Encryption (E2EE) and trip-sealing architecture protect it, and your global privacy rights regarding your data.
This policy applies to all CrewRadr platforms:
crewradr.app)By using CrewRadr, you acknowledge this Privacy Policy. If you do not agree, discontinue use immediately.
GPS coordinates (latitude, longitude, speed, altitude, bearing, accuracy, and vertical accuracy) collected while background or foreground location sharing is enabled. Real-time coordinates are end-to-end encrypted on your device and shared only with crew members you explicitly choose to connect with (or via ephemeral Live Share links you generate). When a trip ends, raw breadcrumb coordinates are cryptographically sealed into an E2EE blob and scrubbed from plaintext server columns.
Email address (for authentication, account recovery, and deletion verification), optional phone number (for emergency SMS alerts or 2FA), ECDH P-256 public key (for end-to-end encryption key agreement), display name, avatar, and optional WebAuthn / Passkey credentials.
Operating system version, device model, battery level and charging state, network connectivity status (Wi-Fi / cellular / offline), and Firebase Cloud Messaging (FCM) / APNs push notification token.
Which crews you belong to, your role within each crew (Captain, Co-Captain, Member), and which users you share location with. Crew membership metadata is visible to other members of the same crew.
walking, driving, cycling, stationary). During active driving, CrewRadr maintains a motion-gated 50Hz Inertial Measurement Unit (IMU) rolling ring buffer and monitors barometer cabin-pressure spikes (indicative of airbag deployment or structural impact) to detect severe vehicular collisions and capture a pre-/post-impact Crash Blackbox.Application crash logs and stack traces, error reports, performance metrics, installation ID for diagnostic correlation, and anonymized feature health telemetry.
Battery percentage and charging status, shared with your crew members for safety awareness. The app automatically alerts your crew when your battery falls below critical thresholds (e.g., 5%).
Geofenced locations you register as trusted destinations (e.g., home, office, school, job site). Used to trigger arrival/departure notifications, suppress overdue check-in alerts upon safe arrival, and trigger optional Smart Home automations.
Structured safety incident logs and collision reports you create in-app, including optional photos, descriptions, witness notes, and encrypted Crash Blackbox telemetry attachments. Visibility is scoped strictly to your crew.
Audio recordings attached to location check-ins, SOS events, or incident reports. Requires microphone permission. Encrypted on-device prior to upload.
Aggregated safety engagement and driving scores (smooth braking, cornering, speed compliance, check-in consistency, Ghost Watch usage). Visible to crew members per your crew's leaderboard visibility settings.
Configuration controlled by your Crew Captain: location sharing lock, sign-out lock, leave-crew lock, work-hour schedules, encryption key rotation state, crew name, and member role assignments.
Membership tier (Deckhand / First Mate / Captain / Admiral), subscription status, billing interval, and transaction identifiers. Payment processing is handled directly by Apple App Store, Google Play Store, RevenueCat, and Stripe — CrewRadr never stores full credit card numbers or bank account credentials.
Encrypted backup of your crew encryption keys, protected by your Security PIN using PBKDF2-HMAC-SHA256 (600,000 iterations) or your 12-word BIP-39 recovery phrase. Stored server-side as an opaque ciphertext blob; decryptable only on your device with your PIN or recovery phrase.
Browser-based access logs, session tokens, and dashboard preferences when accessing the CrewRadr Web Portal (crewradr.app). Includes fleet analytics and administrative audit logs for Captain and Admiral tiers.
CrewRadr uses Bluetooth Low Energy (BLE) and system audio-route metadata for four strictly safety-related purposes:
1. Offline BLE Mesh SOS Relay: When a user triggers an SOS or Crash Alert without cellular or Wi-Fi connectivity, CrewRadr broadcasts an encrypted, signed emergency packet over BLE so nearby CrewRadr devices can opportunistically relay the SOS to the cloud when they regain connectivity. Relaying devices cannot decrypt the identity or message of the sender unless they belong to the same crew.
2. OBD-II Vehicle Adapter Pairing: Optional connection to user-owned Bluetooth OBD-II adapters for vehicle diagnostics.
3. Vehicle Bluetooth Audio Route Detection: Detecting connection/disconnection to your car's hands-free Bluetooth audio system to improve automatic trip start/stop accuracy.
4. Smart Home Matter Proximity: Optional BLE advertising and scanning for local Smart Home Matter arrival handshakes.
origin_airport, destination_airport, flight_number, departure/arrival times) so your crew can track flight status and Safe Landing arrival.When a Crew Captain enables Workplace Compliance Mode for an enterprise or commercial fleet crew, CrewRadr processes optional administrative records submitted by drivers and managers, including pre-/post-trip Driver Vehicle Inspection Reports (DVIR), defect sign-offs, driver license/medical certificate expiration dates, Hours-of-Service (HOS) / shift summaries, OSHA Form 301 incident logs, IRS mileage classifications, and immutable enterprise audit logs.
| Data Type | Purpose |
|-----------|---------|
| Location & sealed trips | Real-time E2EE crew map, sealed trip history, Safe Landing arrival/departure detection, SOS & Ghost Watch alerts, driving safety reports |
| Account identifiers | Authentication, account recovery, deletion verification, ECDH P-256 E2E encryption handshake |
| Device information | Crew status display (battery, connectivity), push notification delivery, platform-specific power optimization |
| Crew associations | Enforcing crew-scoped Row-Level Security (RLS) access, managing roles and permissions |
| Motion, barometer & OBD-II | Crash detection (30s countdown to SOS), 50Hz Crash Blackbox buffer, airbag pressure spike detection, journey auto-start/stop, vehicle health & DTC alerts |
| Diagnostic data | Bug fixing, crash stability monitoring, service reliability improvement |
| Battery telemetry | Low-battery crew alerts (<5%), battery drain rate estimation, status display |
| Safe Landing zones | Arrival/departure detection, overdue check-in alert suppression, Smart Home trigger |
| Incident reports & voice notes | E2EE crew safety documentation, collision reconstruction exports, and audio context |
| Safety streaks & scores | Gamified safety engagement, Eco-Driving coaching, crew leaderboard |
| Crew policy & workplace logs | Enforcing captain-defined rules, DVIR/OSHA/HOS recordkeeping, mileage & carbon ROI reporting |
| Subscription data | Tier provisioning, feature gating, billing, renewal management |
| PIN vault | Zero-knowledge encrypted key backup and multi-device key recovery |
| Bluetooth & BLE Mesh | Offline BLE Mesh SOS packet relay, OBD-II pairing, car audio trip detection, Smart Home proximity |
| Calendar & flight data | Optional flight status tracking and suppression of ground-driving penalties during flights |
We do NOT sell, rent, or share your personal data or location history with third parties for marketing, cross-context behavioral advertising, or data-broker purposes. Your data belongs to you.
When you provide your mobile phone number, you may voluntarily opt in to receive transactional, safety alert, and emergency notification text messages (SMS) from CrewRadr (including automated crash detection notifications, Ghost Watch dead-man switch alerts, SOS emergency check-in alerts, fleet consultation responses, and account security OTP verification codes).
Carrier Non-Sharing Clause:
> *No mobile information will be shared with third parties/affiliates for marketing/promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.*
Voluntary Consent & Service Independence:
Opting in to receive text messages is completely voluntary. Consent to receive text messages is not a condition or requirement of purchase, registration, or receiving services from CrewRadr. You may use all core location-sharing and navigation features of the app without providing SMS consent.
Opt-Out & Support:
You can opt out of receiving SMS text messages at any time by replying STOP to any text message sent from CrewRadr, or by modifying your notification preferences in the app settings. For help, reply HELP or email us at support@crewradr.app. Message frequency varies based on safety triggers and user activity. Message and data rates may apply.
encrypted_details) and invokes our trip-sealing pipeline, which permanently overwrites (NULLs) plaintext latitude/longitude breadcrumb rows in the database. Start and end locations are converted into non-reversible keyed HMAC-SHA256 place tokens so recurring trips can be grouped without exposing geographic coordinates to the server.~1.1 km Grid): To compute fleet safety scores and detect hard braking/speeding anomalies without exposing precise home or workplace addresses to the server, driving event coordinates are truncated to 2 decimal places (~1.1 km neighborhood-level grid) before server storage, while exact coordinates remain strictly inside the E2EE payload.#key=...). Per HTTP standards, URL fragments are processed exclusively in the recipient's browser and are never transmitted to CrewRadr servers. Anyone in possession of the link can view your live progress until it expires or is revoked; you remain solely responsible for your choice of link recipients.| Data Category | Retention Period |
|---------------|-----------------|
| Location & Sealed Trip Logs | Deckhand: 7 days · First Mate: 30 days · Captain: 90 days · Admiral: 365 days. Automatically purged by scheduled retention jobs after window expires. |
| Ephemeral Live Share Sessions | Automatically expire upon the user-selected timer (15 minutes to 24 hours) or trip completion. |
| Check-In Requests | Expire after the configured grace period (~2–15 minutes). |
| Scheduled Reminders | Automatically deleted 24 hours after scheduled time. |
| Incident Reports & Safety Scores | Persist until deleted by the creator, crew dissolution, or member departure. |
| Workplace Compliance Logs (DVIR / HOS / OSHA) | Retained for the Admiral crew's configured regulatory retention window (up to 365 days or until exported/deleted by the Crew Captain). |
| Account & PIN Vault Data | Retained until you delete your account. |
Account deletion is immediate and irreversible. When you delete your account (Settings → Account → Delete Account), all server-side data — location history, sealed trips, crew memberships, bonds, messages, safety scores, schedules, reminders, check-in data, PIN recovery vault, crew key backups, and all other personal information — is permanently purged from active production databases. Device-local keys, secure storage, and SQLite caches are simultaneously wiped. Encrypted disaster recovery backups are retained in secure cold storage for up to 30 days solely for business continuity, after which they are automatically overwritten. Deleting your account does not cancel Apple App Store or Google Play subscriptions; you must cancel active subscriptions directly through your app store account settings.
To ensure complete transparency across different account and organization types, data deletion operates as follows under specific scenarios:
Settings → Crews → Leave Crew) removes your profile and immediately stops location and trip broadcasting to that specific crew. Your underlying CrewRadr account, private trip archives, and memberships in other crews remain intact. In contrast, Account Deletion (Settings → Account → Delete Account) permanently destroys your user profile, authentication identity, and data across all crews.crew_messages). Collective safety incident reports involving vehicular collisions or physical hazards that were filed for the benefit of the entire crew remain in the crew vault for remaining members, but all direct profile links and identifiers attributing them to the deleted user are permanently anonymized.Data export (GDPR Art. 20 / CCPA Portability): Any registered user may export their personal account data and decrypted trip history in machine-readable JSON/CSV format at any time, free of charge, from Settings → Data Export.
CrewRadr relies on carefully vetted infrastructure sub-processors and public hazard feeds to operate. We never share plaintext crew keys with any sub-processor:
| Service | Purpose | Data Shared & Safeguards | Privacy Policy |
|---------|---------|--------------------------|---------------|
| Supabase | Database hosting (PostgreSQL), authentication, real-time WebSockets, Edge Functions | Encrypted payloads, account identifiers, RLS-protected metadata (US/EU regions) | supabase.com/privacy |
| Firebase Cloud Messaging (Google) | Push notification dispatch for check-ins, Ghost Watch, and SOS alerts | Device push token and opaque notification wake payload | firebase.google.com/support/privacy |
| Google Maps Platform / OpenStreetMap / CARTO | Map tile rendering, route polylines, and reverse-geocoding | Viewport map tile requests and anonymized coordinate lookups | policies.google.com/privacy |
| RevenueCat & Stripe | Mobile in-app subscription validation and Web Portal billing | Pseudonymous app user ID, subscription tier, and payment token | revenuecat.com/privacy · stripe.com/privacy |
| Cloudflare | Web Portal hosting, Pages Functions, CDN, and DDoS protection | Standard HTTP connection metadata and TLS termination | cloudflare.com/privacypolicy |
| Twilio / Resend | Optional transactional SMS emergency alerts, OTP codes, and support emails | Recipient phone number or email address only when explicitly triggered by user | twilio.com/legal/privacy · resend.com/legal/privacy-policy |
| OpenWeatherMap / NOAA NWS / NASA FIRMS | Severe weather radar overlays and active wildfire perimeter hazard feeds | Anonymized regional bounding-box queries only (no user identifiers transmitted) | openweathermap.org/privacy-policy · nasa.gov/privacy |
| Right | How to Exercise |
|-------|----------------|
| Access & Know | View all personal data in-app: Journey page (trip history), Settings (profile), Dashboard (crew memberships). |
| Export & Portability | Settings → Data Export (machine-readable JSON/CSV, GDPR Art. 20 & CCPA compliant). Free to all users. |
| Delete (Right to Erasure) | Settings → Account → Delete Account. Immediate, permanent, and irreversible server + device wipe. |
| Rectify / Correct | Update your display name, email, phone number, Safe Landings, and preferences at any time in-app. |
| Withdraw Consent & Opt-Out | Disable background location, Crash Detection, OBD-II, calendar, or microphone access in Settings, or enable Stealth Mode to pause location broadcasting immediately. |
Under GDPR and UK GDPR, CrewRadr acts as a Data Controller for your account data and as a Data Processor on behalf of Commercial Customers for enterprise fleet compliance logs. Our legal bases under GDPR Article 6 are:
Under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA/CPRA):
CrewRadr SOS, Crash Detection, Ghost Watch, and Offline BLE Mesh Relay features are supplementary peer-to-peer notification tools and do NOT contact 911/112 or guarantee emergency responder dispatch. Users must dial local emergency services (e.g., 911, 112, 999) directly during life-threatening situations. These features may not function in areas without network coverage or nearby BLE peers, on devices with depleted batteries, or when required permissions are not granted. CrewRadr is not a replacement for 911 or certified emergency services.
CrewRadr is not directed to children under 13 years of age (or under 16 in the EEA/UK where applicable without parental consent). We do not knowingly collect personal information from children under 13 without verifiable parental consent. If a parent or guardian discovers that a child under 13 has created an account without consent, please contact privacy@crewradr.app immediately and we will promptly purge the account and all associated data.
CrewRadr data is hosted in Supabase cloud data centers (United States and European Union regions). Because your location history, messages, and trip details are end-to-end encrypted on your device prior to transmission, plaintext location data is not exposed during cross-border transit. Where personal metadata is transferred internationally outside the EEA, UK, or Switzerland, transfers are safeguarded by European Commission Standard Contractual Clauses (SCCs) and the UK International Data Transfer Addendum.
iOS Settings → CrewRadr → Location. The app respects iOS stationary power-saving states.crewradr.app): Browser sessions use secure authentication tokens via Supabase Auth and local IndexedDB / WebCrypto storage for E2EE keys. We do not use third-party advertising trackers or cross-site tracking cookies.We will notify users of material changes to this Privacy Policy via in-app notice and/or email prior to the change taking effect. Continued use of CrewRadr after the effective date constitutes acknowledgment of the updated Privacy Policy.
For privacy questions, GDPR/CCPA data subject requests, or to report suspected misuse:
privacy@crewradr.appsupport@crewradr.appSettings → Support & FeedbackEffective Date: 2026-10-16