Mr. Latte StoryPedalTalk Privacy Policy
This English page is a machine translation of the Korean original, so some wording may read a little off.
Last updated 2026-10-18
PedalTalk lets people who ride bicycles together talk by voice. This page explains what the app receives, what it is used for, and how long it is kept.
1. Voice
Your voice goes directly to the phones of the other riders in your room and is never stored on a server. The internet path is encrypted with WebRTC (DTLS) and the Bluetooth path uses a Google Nearby Connections link. If a relay (TURN) server helps the connection, it only forwards encrypted packets and does not record their content.
2. Data briefly kept on the server
- An anonymous account identifier (Firebase Anonymous Authentication uid). We do not collect names, email addresses or phone numbers.
- Room data: the 6-digit room code, the display name each rider enters, a random device number, and a random value used to verify the nearby link
- Connection setup data: network candidate addresses (including IP addresses) and session descriptions that let the two phones find each other
Room data expires 24 hours after the room is created and connection setup data expires after 1 hour. Expired data is deleted automatically, usually within a day of expiry. Connection setup data is also deleted as soon as the other phone reads it. This data is stored in Google Firebase (Cloud Firestore, Seoul region).
3. Data kept only on your phone
Your display name, app settings, and the names and dates of recent partners stay on this phone and are excluded from backup and device transfer. They are removed when you uninstall the app.
4. Error reports and usage statistics
When the app crashes or a connection error occurs, the device model, OS version, error details and connection state log are sent to Firebase Crashlytics to find the cause. Voice and conversation content are never included. The "Export logs" button on the diagnostics screen shares logs only when you choose to.
Usage statistics are sent only if you turn on "Send usage statistics" on the setup screen at first launch or in Settings. They include which screens you open, how long you use the app, the device model, OS and app versions, your approximate country and a per-install identifier, and go to Google Analytics for Firebase. Voice, room codes and display names are not included. No advertising identifier is collected, and Google keeps the statistics for up to 14 months.
5. Permissions
- Microphone: to send your voice to the other riders during a talk.
- Nearby devices (Bluetooth, Wi-Fi): to connect directly to nearby riders when the internet drops. On Android 12 and earlier the same feature requires the location permission, but no location is recorded.
- Notifications: to show the talk status and mute and end buttons while the screen is off.
- QR scanning is handled by the Google Play services code scanner, and the app does not hold the camera permission.
6. Third parties
We do not sell or share data for advertising. The service runs on Google Firebase (authentication, database, remote config, crash reporting, usage statistics) and Google Play services (nearby connections, code scanner).
Update checks use Google Play in-app updates. When the app asks the Play Store app on your phone whether a new version is available, the Play Store sends the app version and device information to Google to check. This is governed by the Google Play Terms of Service.
7. Deletion requests and contact
Server-side data is deleted automatically after the periods above. To have it removed sooner, or for any question, email hello@mrlatte.net with your room code. Requests are handled within 30 days.