Updated: 2026-11-19 · Third-party components embedded in this app
Listen Step embeds the following third-party components:
Firebase Cloud Functions, Firestore and Cloud Storage also process opted-in live execution snapshots, random device/session identifiers, platform and latest online time, execution epochs/revisions, leases, request IDs and the attachment files you select, including names, sizes and checksums. These are private to your Firebase account and are not group shares or public download links. Cloud Sync and attachment access require authentication and eligible cloud access.
sherpa-onnx (open-source offline speech recognition) — Function: on-device speech-to-text. Personal data processed: microphone audio. Data flow: processed entirely on-device; no network access, no uploads.
@capacitor-community/text-to-speech — Function: reads step text aloud via the device system TTS engine. Personal data processed: none (only the text to speak is passed). Data flow: handled on-device by the system TTS engine.
@capacitor-community/speech-recognition — Function: fallback that invokes the device's built-in speech recognition service when the offline component is unavailable. Personal data processed: microphone audio. Data flow: handled by the device's system recognition provider (only in the fallback case).
@capacitor/filesystem — Function: writes Word files you export to the device "Documents" folder. Personal data processed: the protocol content you choose to export. Data flow: written to local storage only.
@capacitor/share — Function: opens the system share sheet so you can send an exported report (Word file, experiment or Sample photos, voice-note audio) through an app you choose, such as Gmail. Personal data processed: the report files and saved Sample snapshots you choose to share. Data flow: passed directly to the app you pick; nothing is sent to us.
Google ML Kit Text Recognition — Function: on-device text recognition for the "Scan printed protocol" feature on the Create page. Personal data processed: the single photo you take for scanning. Data flow: processed entirely on-device; the photo is deleted immediately after recognition; no network access, no uploads.
Firebase Authentication (Google) — Function: "Sign in with Google" and email/password sign-in. Personal data processed: your display name, profile photo URL when provided, email address and UID; passwords are processed by Firebase and never reach us. Data flow: sent to Google's Firebase servers for authentication; profile images are requested from the returned HTTPS image host after consent. See Google's privacy policy.
Firebase JavaScript SDK (App and Authentication) - Function: Google/email sign-in and session/token management for the PC web workspace. Data: the account credentials you enter, Firebase UID, display name/email and authentication tokens. Processing: Firebase handles authentication; the browser keeps a tab-session login after privacy consent. No Firebase Analytics component is initialized.
Firebase Cloud Functions, Firestore and Cloud Storage — Function: verify sign-in tokens, manage trial state, optional signed-in Cloud Sync and group sharing. Personal data processed: UID and trial state; with Cloud Sync on, protocols, Samples and their photos, runs including Sample snapshots, in-app calendar entries, preferences, experiment photos and voice-note audio; when using groups, memberships, display names, invitations, selected protocols, grants, working copies and gifts. Samples and Sample photos are not group content. Data flow: stored on Google's Firebase servers; group content is accessible according to the sharing permissions you choose.
MiniMax AI service — Function: identify experimental steps and split PDF methods after you explicitly choose PDF quick split. Data processed: extracted document text, including method text. Data flow: sent from our private extraction service to MiniMax for AI processing; MiniMax's own retention and processing terms apply.
Google Play Billing - Function: Pro/Pro Max subscription purchase, restore and management, plus consumable PDF credit purchases. Personal data: purchase token, product ID and order ID; card details stay with Google Play. RevenueCat verifies purchase records.
Paddle (website checkout only) - Function: payment processing, receipts, taxes and subscription management for enabled website purchases. Paddle receives the billing/contact and payment information entered at checkout. RevenueCat associates the purchase with your Firebase UID and reports verified purchase status to our backend. No Paddle payment SDK is bundled in the Android app. See Paddle privacy policy.
RevenueCat (Purchases and RevenueCatUI) - Function: native subscription options, Pro/Pro Max and PDF credit purchase verification, entitlement sync and restore. Personal data: purchase token, product ID, order ID, purchase/subscription status, app user ID and paywall presentation/purchase/restore events. Android payments remain with Google Play; enabled website payments are handled by Paddle. Listen Step never receives full card details. Authenticated PDF purchase/refund events are sent to our Firebase backend. See RevenueCat's privacy policy.
This app contains no advertising, analytics, or push-notification SDKs.