Updated: 2026-11-19 · Personal information collected by this app (including embedded components)
Report sharing: at your request, Word and Markdown reports, experiment/Sample photos, recordings and private attachments are packaged locally in a ZIP. Authenticated cloud downloads retrieve selected files as needed. Android writes a temporary app-cache file and shares it through your selected app; supported browsers share the ZIP or download it for manual email attachment. Listen Step does not send an email or choose recipients automatically.
Listen Step collects the following personal information:
Online presence: opted-in Cloud Sync foreground sessions send platform (Android or web), random device and session IDs and latest online time to private account storage. One latest entry per platform is retained to detect simultaneous web and phone use; entries older than 45 seconds do not enable real-time execution updates. No hardware identifier or location is collected. Single-platform execution stays local until a result is saved, except for attachment uploads you initiate. Turning off Cloud Sync stops presence updates; account deletion removes them.
Active execution and private attachments: with eligible Cloud Sync enabled after sign-in and privacy consent, Firebase receives the running protocol snapshot, step/timer, checklist, calculations, saved notes and photos, Sample snapshot, result record, persistent random device ID, per-tab or per-process session ID, execution epoch/revision, lease and request IDs. These identifiers coordinate explicit takeover and stale-write protection, not hardware identification. Only files you choose are uploaded (any type, up to 50 MB each, within the shared account quota (200 MB basic, 2 GB Pro, 20 GB Pro Max)), together with filename, size, step, checksum and private references. Other authorized sessions of the same account can follow the run read-only and download selected attachments. Devices do not turn on each other's microphones or cameras. Complete local snapshots, offline pending writes, completion intents and recovery copies stay in local account/device storage until synchronized or local data is cleared. Incomplete private chunks can remain and count toward quota until cleanup or account deletion; canceling an upload prevents publication but does not promise immediate byte erasure. Account deletion removes execution documents and private chunks.
Android account avatar: Firebase Authentication may return a profile photo URL with your signed-in account. After privacy consent, the app uses it in memory for the header and requests the image over HTTPS without a referrer. It is not saved in shared preferences or shared with groups; sign-out and account switching hide the previous account photo. No camera or photo-library permission is requested.
Optional web profile photo: the single image you select or capture is cropped and compressed locally into a JPEG without original metadata. It is saved in account-scoped browser preferences and included in private Firebase Firestore preferences only when you enable eligible Cloud Sync. It is not published or shared with groups, and does not modify your Google photo. Reset removes the custom image locally and the next successful sync applies the change remotely. Clear site data removes local copies; account deletion removes cloud preferences.
Recipes and Samples — Purpose: organizing reusable recipe tables and plate-based experiment samples. Data: Recipe names, tags and multiple tables; Sample names, tags, plate type, well-use states and recipe snapshots in wells. Handling: stored on this device or in account-scoped browser storage. Selecting a Sample for a Protocol run saves its snapshot, including image references, in run history for reports and explicit share attachments. Sample content uploads when you enable Cloud Sync after sign-in and privacy consent, or when you explicitly authorize an eligible agent to import a Sample package to your cloud account. Samples are not publicly uploaded or added to Groups. Deleting a Sample leaves saved run snapshots unchanged.
Microphone audio — Purpose: recognizing voice commands ("next", "check", "back", "repeat"). Scenario: when you enable "Hands-free" on the execution page. Handling: processed offline on-device when available; if offline recognition is unavailable, the device's system recognition provider may process the audio. Command audio is not stored by Listen Step.
Voice-note recordings — Purpose: voice notes attached to a run and report. Scenario: during a run between your spoken start and end words. Handling: stored on this device; also uploaded to Firebase Cloud Storage if you turn on Cloud Sync. Local audio may remain after the run entry is removed; uploaded media may remain until account deletion.
Camera photos — Purpose: (a) scanning printed protocols offline, with the scan image deleted immediately afterward; (b) attaching experiment photos to a run; (c) attaching photos to a Sample. Experiment and Android Sample photos stay in private app storage. Web Sample photos are compressed into JPEG data URLs in account-scoped local browser data. Sample and experiment photos upload to Firebase Cloud Storage only when you enable Cloud Sync after sign-in and privacy consent; they also leave the device when you explicitly share a report containing them. Sample photos are not publicly uploaded or added to Groups.
Calendar schedules (experiment name, start/end time, reminder minutes) — Purpose: phone-calendar reminders for your experiments and in-app history. Scenario: when you schedule or delete future, unfinished experiments, including repeat dates. Handling: written to your phone calendar; only matching events created by Listen Step are deleted when you remove a schedule.
Existing phone-calendar event titles and times — Purpose: an optional read-only calendar view. Scenario: only after you turn on "Phone events". Handling: read for the visible date range and held in app memory; not saved to Listen Step storage or uploaded to its cloud.
Account and trial info (name, email, UID, trial start time and extension flag) — Purpose: sign-in, session keeping, named attribution and trial timing. Scenario: when you sign in, save your User name, create a protocol/module, run a protocol or share with a group. Handling: your name is stored in Firebase Authentication and used across devices. New content and execution records save a name snapshot; group members see current account names. UID and trial state are stored in Firestore. Profile changes do not upload protocol content. Account profile records are removed when you delete your account; copies already shared with others may retain their historical attribution.
PC browser workspace cache and session - Purpose: account-isolated editing and access to the same cloud protocols, Samples and run records. Handling: Firebase browser authentication maintains a tab-session login; account-scoped browser storage keeps protocols, drafts, modules, Recipes, Samples, Sample JPEG data URLs, history and pending PDF tasks. Sign-out hides but does not erase the local cache. Clear site data to remove it. Cloud media preview bytes remain in memory. Cloud Sync and PDF uploads occur only when you choose them; a content-free authenticated probe verifies cloud access.
Purchase & entitlement records (purchase token, product ID, order ID, purchase/subscription status, app user ID) - Purpose: Pro/Pro Max access, PDF credit purchase verification, cross-device sync and fraud prevention. Scenario: purchasing or restoring a subscription or credit, signing in, or purchase/subscription status changes. Handling: Android payment through Google Play, enabled website payment through Paddle, and verification through RevenueCat; cached on your device. Confirmed PDF transactions also update Firebase accounting.
Protocols and step content you create — Purpose: creating, editing, combining, running and sharing protocols. Data: content, custom creator name and origin/source metadata. Handling: stored on your device; saved protocols are uploaded to Firebase Firestore when you enable Cloud Sync, explicitly authorize an eligible agent import, or explicitly share with a group, or sent to your chosen share app when you share. Unfinished New protocol drafts are automatically kept on this device only until saved or discarded.
PDF quick split documents and results — Purpose: extract and split a PDF you choose into complete routes or modules. Scenario: after you sign in, select a PDF, agree to processing and tap Upload and split. Handling: the PDF and sign-in token go to our extraction service; extracted text goes to MiniMax AI. The service limits access to your account; the app requests deletion after import and a scheduled cleanup removes remaining files after 7 days. Selected protocol packages return to this device. MiniMax's own retention follows its service terms.
PDF credit accounting (UID, welcome grant, monthly allowance windows, balances, hashed purchase identifiers, purchase/refund status, task IDs, result checksums and timestamps) - Purpose: welcome credit, Pro Max monthly allowance, purchased extraction credits and successful-extraction-only accounting. Handling: RevenueCat verifies subscription and purchase/refund status; Firebase stores the ledger separately from document content until account deletion. Minimal hashed transaction markers remain to prevent duplicate crediting. Payment-card details and raw purchase tokens are not stored in this ledger.
Group memberships, invitations, grants, working copies and gifts — Purpose: group access and permission-controlled protocol sharing. Handling: Firebase stores group names, member UIDs and display names, invitation hashes and expiry, selected protocol content, grants and independently edited working copies. Members see group details and content shared with them; gifts become independent recipient copies. Samples and Sample photos are not group content. Account deletion removes your groups, memberships and private group data, but cannot recall gifts or historical experiment records held by others.
Run history, in-app calendar entries and preferences — Purpose: history, reports, schedules and settings. Handling: stored on your device; uploaded to Firebase Firestore if you turn on Cloud Sync. Run history retains selected Sample snapshots, including image references, after the source Sample is deleted. Phone-calendar events themselves are not synced by Listen Step.
Not collected: contacts, messages, call logs, location, photo library, device identifiers (IMEI, MAC address, Android ID). Existing calendar events are viewed locally only when you enable the optional view.
Generated Word reports, including saved Sample snapshots, leave the device only when you explicitly share them. Photos and audio also upload when you turn on Cloud Sync after sign-in and privacy consent. Turning it off does not erase existing cloud copies; account deletion does.