RidePerk legal
Privacy Policy
We built RidePerk to protect people, not to harvest their data. This policy explains exactly what we collect, what we don't, and how we protect the audio from your trips.
1. What We Collect
Audio
Processed in real time on our servers. Not stored unless a high-risk event is detected. When stored, audio is encrypted with AES-256-GCM and auto-deleted after 7 days. If the session is escalated to authorities, the retention window extends to 30 days.
Trip metadata
Start time, session duration, and number of alerts. The current version does not collect or store GPS coordinates.
Contact information
Your email address, if you submit it through the waitlist form. Nothing else.
2. What We Do NOT Collect
- We do not record or store audio from low or medium risk sessions.
- We do not sell data to third parties. Ever.
- We do not share data with rideshare platforms without your explicit consent.
- We do not build advertising profiles.
3. How Audio Is Protected
- All audio streams travel over TLS 1.3 (wss:// encrypted WebSocket connection). Your voice never travels over an unencrypted connection.
- Flagged audio segments are encrypted with AES-256-GCM before storage. Encryption keys are never stored alongside the data they protect.
- Data is stored in Supabase (EU region) with row-level security enabled.
- Audio from sessions with no high-risk events is never written to disk.
4. Your Control
- You opt in explicitly before every session — we show a consent screen before your microphone activates.
- You can end the session at any time. Analysis stops immediately when you tap End Trip.
- You can request deletion of any data we hold by emailing privacy@rideperk.ai.
5. Contact
Privacy questions and deletion requests: privacy@rideperk.ai