Updated: 2026-10-06 · Personal information collected by this app (including embedded components)
Listen Step collects the following personal information:
Microphone audio — Purpose: recognizing voice commands ("next", "check", "back", "repeat"). Scenario: when you enable "Hands-free" on the execution page. Handling: recognized offline on-device; command audio is never stored, never uploaded.
Voice-note recordings — Purpose: voice notes attached to a run, replayable in its report and included when you export or share it. Scenario: during a run, between your spoken start word and end word. Handling: stored only on your device; permanently deleted when you permanently delete the record.
Camera photos — Purpose: (a) recognizing text on a printed protocol/SOP to pre-fill the Steps box; (b) experiment photos attached to a run. Scenario: (a) when you tap the scan button on the Create page — the photo is recognized offline on-device and deleted immediately after recognition; (b) when you tap the photo buttons during a run — the photo is renamed by you and stored only on your device, and is permanently deleted when you permanently delete the record. Never uploaded.
Calendar schedules (experiment name, start/end time, reminder minutes) — Purpose: phone-calendar events with reminders for your scheduled experiments, and showing completed runs on the calendar. Scenario: when you schedule a protocol on the Calendar page. Handling: written directly to your phone calendar; the app reads only the calendar account list to find a writable calendar and never reads, modifies or deletes your existing events.
Account info (name, email, UID) — Purpose: sign-in, session keeping. Scenario: when you sign in with Google or with email and password (passwords are processed by Firebase and never reach us). Handling: stored on Firebase servers; cached on your device; deleted when you delete your account.
Purchase & entitlement records (purchase token, product ID, order ID, subscription status, app user ID) — Purpose: activating/restoring Pro, cross-device sync and fraud prevention. Scenario: when you subscribe, restore purchases, or the subscription state changes. Handling: processed and stored by RevenueCat; cached on your device.
Protocols and step content you create — Purpose: create, edit, run and Word-export features. Scenario: when you create or edit a protocol. Handling: stored only on your device.
Run history & voice notes — Purpose: showing your experiment history and generating run reports. Scenario: when you finish or exit a run, or record a voice note. Handling: stored only on your device.
Not collected: contacts, messages, call logs, location, photo library, existing calendar events, device identifiers (IMEI, MAC address, Android ID).
Report files (Word, photos, audio) leave the device only when you explicitly share them (e.g., "Send via email"); they go directly to the app you choose and never to us.