Updated: 2026-11-19 · Effective: 2026-11-19 · Applies to: v2.55.0 and later and the Listen Step web workspace
Listen Step is a voice-guided step assistant that helps you follow protocols hands-free — in the kitchen, in the lab, and beyond. We take your privacy seriously. This policy explains exactly what we do with your personal information.
1. Personal information we process (item by item)
Agent cloud import — If you choose to authorize an agent, Listen Step processes the JSON package you submit and a temporary, limited import authorization to add new items to your account's cloud workspace. Requests pass through Cloudflare and our Firebase service; a security rate limiter processes the request IP address. Authorization codes and access grants expire; import receipts expire after 30 days to prevent duplicate imports, and automatic deletion may take longer. Security rate-limit records are temporary. The grant cannot read or modify existing items. You can import JSON files manually without this feature. Account deletion revokes agent grants and removes associated import receipts; a hashed account deletion safeguard is retained temporarily to prevent further imports while deletion completes.
Unfinished protocol drafts — The New protocol form automatically stores its name, creator, tags, steps, materials and tables on this device to recover unfinished work after an app restart. Drafts are not uploaded by Cloud Sync and require no account or subscription. A draft is removed when you successfully save the protocol or confirm Discard draft; clearing app data or uninstalling also removes it. Saved protocols follow the sharing and Cloud Sync choices below.
Recipes and Samples — Recipes contain a name, tags, tables and Materials. Samples contain a name, tags, plate type, well-use states, per-well sample names and amounts, recipe colors and recipe snapshots in wells. They are stored on this device or in account-scoped browser storage. You can attach independent Sample or Recipe snapshots after a protocol step; changes to that copy do not update the library original. Step attachments are included in saved protocol drafts, private Cloud Sync, run snapshots and reports or protocol packages you explicitly export or share. Attached Sample photos use the same opted-in private media transfer as other Sample photos. When you select a Sample for a Protocol run, its snapshot is also saved in run history. Deleting a library item does not change existing step or run snapshots. Protocols containing these step snapshots cannot currently be published publicly or added to Groups.
Microphone audio — Purpose: (a) recognizing your spoken commands ("next", "check", "back", "repeat") to control step execution; (b) voice notes you deliberately record during a run using your own start/end words. Method: command listening happens only when you turn on "Hands-free" on the execution page; a voice note is recorded only between your spoken start word and end word. Processing: speech recognition uses the offline component on your device (sherpa-onnx) when available; Listen Step does not save command audio. Voice-note recordings are stored on your device, attached to the run record, included in exported reports, and uploaded if you turn on Cloud Sync. Deleting a run removes the in-app record after its 7-day Trash period, but local or cloud audio files may remain as described below. If your device lacks the offline component, the app falls back to the device's built-in speech recognition service; in that case audio is handled by that service provider under its own privacy policy, and you can manage it in system settings.
Camera photos — Three scenarios, each only when you tap the button yourself: (a) Scan printed protocol on the Create page: the photo is recognized offline on your device (built-in Google ML Kit component) and is deleted immediately after recognition — never stored, never uploaded; (b) Experiment photos during a run: photos you take or pick are stored in private app storage, shown in the report, attached when you export or share it, and uploaded if you turn on Cloud Sync; (c) Sample photos in the Sample editor: on Android, photos you take or choose are stored in private app storage. On the web, the selected image is compressed into a JPEG data URL in account-scoped local browser data. Sample photos are referenced by saved run snapshots, included in reports and explicit share attachments, and uploaded only if you turn on Cloud Sync after sign-in and privacy consent. They are not publicly uploaded or added to Groups. Local or cloud photo files may remain after a run is deleted as described below.
Calendar schedules you create — Purpose: adding experiment schedules with reminders to your phone calendar, showing completed runs in Listen Step, and deleting future schedules you choose to remove. Method: when you schedule a protocol on the Calendar page, the app reads the calendar account list to find a writable calendar, then writes one phone-calendar event for each scheduled date, including repeat dates. When you delete a future, unfinished schedule, the app deletes the matching phone-calendar event that Listen Step created; completed run records cannot be deleted from the Calendar page. Data written: experiment name, start/end time and reminder minutes. Your calendar account provider may sync these phone events under its own policy.
Existing phone-calendar events (optional read-only view) — If you turn on "Phone events" on the Calendar page, the app reads event titles and times for the visible date range from your phone's calendar and displays them in Listen Step. These other events are held only in memory, not saved in Listen Step's local database or sent to its Cloud Sync. Listen Step cannot edit or delete other apps' events. Turning off "Phone events" clears them from the view.
Account and trial info — Purpose: signing you in, keeping your session, and calculating your free-trial entitlement. Method: Google or email sign-in through Firebase Authentication; the app then checks the trial through Firebase Cloud Functions. Data: your display name, email address, user ID (UID), server-recorded trial start time and whether you extended the trial by creating a protocol. You can save a custom User name in your Firebase account profile. It appears in new protocol/module attribution, execution records and shared group member lists; group members can see your current name, while historical records and gifts retain their saved attribution. Your name is not a unique identifier and does not change account ownership. Your password is handled by Firebase and is never visible to us or stored by the app. Processing: account data is stored in Firebase Authentication; the UID, trial start and extension flag are stored in Firebase Firestore. Trial status is held in app memory during the session, not used from local storage to unlock features. Protocol content is not sent to the trial service.
Purchase & entitlement records - Purpose: activating/restoring Pro and Pro Max, verifying PDF credit purchases, cross-device entitlement sync and fraud prevention. Android payments are processed by Google Play Billing. Where enabled on the website, Paddle processes web payments as merchant of record; hosted checkout uses RevenueCat. We never receive your full card details. RevenueCat handles purchase verification and entitlement sync. Data: purchase token, product ID, order ID, purchase/subscription status and app user ID. Processing: stored on RevenueCat's servers and cached on your device; authenticated purchase/refund events update the separate Firebase PDF credit ledger.
Cloud sync (optional for every signed-in account) — If you turn on Cloud Sync while signed in, we upload your own protocols and steps, edits to built-in protocols, Samples and their photos, run history including protocol and Sample snapshots and notes, experiment photos, voice-note audio, in-app calendar entries, and app preferences to your account in Firebase Firestore and Cloud Storage. Basic accounts have 200 MB, Pro has 2 GB and Pro Max has 20 GB of shared content space per account (binary units: MB = 1024 squared bytes, GB = 1024 cubed bytes). RevenueCat verifies expanded subscription capacity on the server. If a subscription expires or capacity drops, existing data is retained for reading and cleanup; new uploads exceeding the limit pause. Local execution and saving remain available. Once enabled, syncing runs at app launch, sign-in, at least daily while the app stays open, and after local changes when online; you can also tap Sync now. The side menu shows cloud storage and the last successful sync time on this device. On first use when both the device and cloud contain data, you choose which copy to keep. Later conflicts on one item use the last modification time. System-calendar events are not copied to another device's calendar; only the in-app schedule entry syncs.
PDF quick split (optional) — When you sign in, select a PDF and tap Upload and split, the app sends the PDF and your Firebase sign-in token to our extraction service. The service verifies your user ID, parses the PDF with MinerU, and sends extracted text to MiniMax AI to produce steps and split routes. It stores the PDF, intermediate extraction and results privately under your user ID. After selected protocols are imported, the app requests deletion of the service copy; remaining files are cleaned up after 7 days. The app downloads the selected results to your local protocol library. Those results are included in optional Cloud Sync only if you enable it. MiniMax processes extracted text under its own service terms; do not upload a document you are not authorized to process.
PDF extraction credits - Firebase stores your UID, one-time welcome-credit grant, available/reserved/used counts, subscription-month windows, hashed purchase identifiers, purchase/refund status, task IDs, result checksums and timestamps. New and existing accounts can receive one welcome credit per Firebase account. When paid PDF billing is enabled, RevenueCat verifies the Pro Max subscription for 20 extractions per subscription month without rollover; new single-credit purchases are no longer offered. Previously purchased credits and verified historical purchase/refund events remain supported. Processing reserves a credit; valid final results consume it once. Failed, empty or invalid results release the original reservation; expired monthly allowance does not roll into a later month, and refunded purchased credits are not restored. Google Play handles Android payments and Paddle handles enabled website payments; RevenueCat confirms purchase/refund events to our server. Accounting records remain after PDF cleanup until account deletion, except minimal hashed transaction markers retained to prevent a previously credited purchase from being credited again. The ledger does not store PDF text, payment-card details or raw purchase tokens. Availability depends on server billing being configured.
On-device usage data — Protocols, Recipes, Samples, run history, photos, voice-note audio and in-app calendar entries remain on your device and can be used without Cloud Sync. Generated Word reports are not part of Cloud Sync.
Sharing you initiate — When you tap "Share" on a report, the app prepares a ZIP containing Word and Markdown reports, experiment and Sample photos, voice recordings and private attachments. Selected cloud files are downloaded through your authenticated account; packaging happens on your device. Android keeps a temporary package in app cache and hands it to your chosen email or sharing app. Supported browsers use the system share sheet; other browsers download the ZIP for you to attach yourself. Files are sent only through the app and recipients you choose. Missing files prevent a complete share; AI Package export can separately produce an incomplete archive after confirmation. "Send via email" after a Word export and protocol sharing remain available. A report can contain Sample snapshots and their photos. A custom creator name is included in protocol email and JSON. This sharing action is separate from optional Cloud Sync.
We do not collect your contacts, messages, call logs, location, photo library, or device identifiers (IMEI, MAC address, Android ID). Existing phone-calendar events are read only for the optional on-device view and are not uploaded to Listen Step.
Optional web profile photos: only when you choose Upload photo or Take photo, the browser crops and compresses that selected image into a small JPEG, removing original image metadata. The saved image is kept in your account-scoped browser preferences and uploaded to your private Firebase Firestore preferences only if you enable Cloud Sync after sign-in and privacy consent. It is not a public image URL, is not sent to other group members, and does not change your Google account photo. Reset photo removes the custom image from current browser preferences; that removal reaches cloud preferences on the next successful sync. Signing out hides but does not erase the local image. Clear site data to remove the local copy. Account deletion removes cloud preferences, subject to the retention rules below.
Android account avatar: after privacy consent and sign-in, the header can display the profile photo URL returned by Firebase Authentication. Loading the photo makes an HTTPS request to that image host without a referrer. The app holds the URL in the current authenticated session, does not save it in shared device preferences or publish it to groups, and hides it when signed out or switching accounts. If no photo is available, initials or a guest icon are shown. This does not access your camera or photo library.
2. Device permissions
Live execution sync and attachments: after you sign in, accept privacy consent and enable eligible Cloud Sync, foreground sessions send their platform (Android or web), random device/session identifiers and latest online time to your private Firebase account, including while no experiment is open. Only the latest presence per platform is retained; presence older than 45 seconds no longer enables real-time execution sync. With both platforms online, the protocol snapshot, current step, timer, checklist, calculations, saved notes/photos and selected Sample snapshot synchronize privately. Otherwise execution stays local and completed or paused results upload in the background. Web followers use Take control to edit; phone controls save locally without waiting for takeover or network requests. These random identifiers, execution epoch/revision and short leases prevent stale writes; they are not hardware identifiers. Microphones and cameras do not start on another device automatically. Complete local execution snapshots, offline writes, completion intents and conflict recovery copies remain in this account/device's local storage until synchronized or local app/site data is cleared. You can select any file type for a private run attachment, up to 50 MB each, within the shared account cloud quota (200 MB basic, 2 GB Pro, 20 GB Pro Max). File bytes, original filename, size, step, checksum and private references are uploaded only after you select the file; no folder or photo-library scan occurs. Attachments are downloaded only on request, not executed or published. Pending uploads may delay cloud finalization but do not prevent saving and leaving an experiment on this device. Interrupted chunks may remain in private cloud storage and count toward quota until cleanup or account deletion; canceling stops attachment publication, not guaranteed immediate chunk erasure. Do not attach files you are not authorized to upload, including other people's sensitive personal data. Turning Cloud Sync off stops automatic transfers without erasing existing cloud copies; account deletion removes presence, execution documents, run records and file chunks.
PC web workspace: the website uses Firebase browser authentication for Google or email sign-in to the same Listen Step account. Authentication is initialized only after privacy consent, and the sign-in session is kept for the browser tab session rather than a permanent remembered login. Protocols, drafts, modules, Recipes, Samples, Sample JPEG data URLs, run records and pending PDF-task references are cached in this browser under separate Firebase-account namespaces. Signing out hides that account's workspace but does not erase its local cache; clearing this site's browser data removes it. The account is verified before its cache is opened. Cloud Sync remains optional for every signed-in account, with the same account capacity as Android. A server-authorized empty-page probe checks cloud access without downloading protocol content before you opt in. When you open cloud experiment or Sample photos or voice-note audio, authenticated media chunks are verified and previewed in memory, not stored as permanent browser media files. Google Play checkout is not available on this website. No Firebase Analytics SDK is initialized by the workspace.
Groups (optional): when you create or join a group, Firebase stores its name, your UID, chosen display name and membership. Other members can see these group details. Invitation codes expire after 7 days and can be replaced by the owner. Anyone with a valid code can join. Sharing uploads only the selected protocol's title, steps, category, creator, materials and tables, even when personal Cloud Sync is off. Samples, Sample photos, other photos, audio, experiment records and schedules are not shared with the group. Current members receive the permission you select; future members require a new share. Each member needs an active trial or Pro to join, share, open, edit or start a granted protocol.
Execution-only grants and independently editable working copies are stored in Firestore. The From cloud sharing section of My Protocols retrieves group/share titles, permissions, author display names and gift-inbox contents while you are signed in. This directory is held in memory and refreshes when you open the page, return to the app while viewing it, or tap Refresh. Opening, editing, saving and starting a grant still requires an online authorization check. Granted content stays in memory on the device and is excluded from personal protocol storage, combination, export and Cloud Sync. Revocation, membership removal or group deletion prevents new authorized access; already-started experiments can finish. Experiment records preserve their protocol snapshots and may be exported or personally synced. Copies already seen or exported in records cannot be remotely erased. Gifts are permanent independent copies delivered to the current members' private gift inboxes. They appear in From cloud sharing and are saved in local protocol storage when you save, edit or start a gift; these saved copies may be personally synced, edited, exported and shared, and cannot be revoked. Signing out clears the in-memory cloud directory but retains already-saved gifts with other local protocols. Removing a gift from its cloud inbox does not remove already-saved copies or experiment records.
Group limits: 20 groups per account, 50 members and 100 shares per group, 200 KB per protocol/working copy and 100 gifts per inbox. These limits are separate from the personal Cloud Sync allowance (200 MB basic, 2 GB Pro, 20 GB Pro Max). Expiry pauses new authorized use without automatically deleting data. You can still revoke, leave, delete a group you own or remove gifts after expiry. Removed memberships delete that member's working copies and revoke their grants; other revoked working copies remain inaccessible until the group is deleted. Account deletion removes owned groups, memberships, your working copies and gift inbox; gifts already delivered to other accounts and their experiment records remain.
Microphone — used only for the voice commands and voice notes described above, requested only when you actively use a voice feature.
Camera — used only when you tap the scan button on the Create page (photo deleted right after recognition), the photo button during a run or in the Sample editor (photo stored on your device), or Take photo in the web profile photo editor. The web profile editor requests video only, not microphone audio, and stops camera tracks when closed or when the page goes into the background. Captured photos are kept only when you save them.
Calendar — read access is requested when you turn on "Phone events" to show existing events on this device. Read and write access is requested when you schedule an experiment or delete an unfinished future schedule you created in Listen Step. Other apps' events are never changed.
Vibration — used for timer alerts, drag-and-drop feedback when combining protocols, and other interaction feedback.
Network — used for sign-in, trial checks, subscription verification, optional signed-in Cloud Sync through Firebase, protocol downloads you choose from listenstep.app, and PDF quick split you choose to upload. System speech recognition may process command audio if offline recognition is unavailable. Sample content and photos, run photos and voice-note audio upload only when Cloud Sync is on after sign-in and privacy consent; reports and their Sample snapshots and attachments also leave the device when you explicitly share them through another app.
3. Where and how long your data is stored
Location: local protocols, Recipes, Samples, run records, photos, voice-note audio and settings stay in private app storage. On the web, Recipes, Samples and Sample JPEG data URLs use account-scoped browser storage. Optional trial or Pro Cloud Sync also stores selected content in Firebase Firestore and Cloud Storage under your UID; these servers may be outside your country. PDF quick split sends your chosen PDF to our extraction service and extracted text to MiniMax AI; processing locations depend on those services. Phone-calendar events remain with your calendar provider. Account and trial records are processed by Firebase, and purchase records by Google Play, Paddle (website purchases) and RevenueCat.
Retention: on-device data remains until you delete it or uninstall the app; there is no app-imposed per-protocol limit on saved runs or on protocols you create. Deleting a Sample does not delete or alter Sample snapshots already saved in run history. After a successful PDF quick split import, the app requests deletion of the service files; a scheduled cleanup removes any remaining service files after 7 days. MiniMax's own retention follows its service terms. Deleted run entries remain in Trash for 7 days; local photo and audio files may remain until app data is cleared, including Sample photos. Cloud records follow synced edits and deletions; uploaded media, including Sample photos, may remain in Cloud Storage after a run or Sample is deleted until the account is deleted. When the trial ends or Pro expires, Cloud Sync pauses; your device data and existing cloud data are not automatically deleted after a fixed number of days. Turning Cloud Sync off stops future transfers but does not delete existing cloud data. Deleting your account removes the Firebase account, trial state, cloud records and cloud media; it does not delete local protocols, Recipes, Samples or run records on this device. Google Play, Paddle and RevenueCat retain purchase records under their own policies.
4. Your rights and how to exercise them
Access & correct — view and edit your protocols, Recipes and Samples in their editors.
Delete — delete protocols, Recipes and Samples you created and run records (Trash keeps them restorable for 7 days); deleting a Sample leaves saved run snapshots unchanged. Manage exported Word files yourself.
Withdraw consent — open the side menu (tap the logo) → "Privacy Consent Settings" to change your choice at any time; voice features and Cloud Sync stop, while basic on-device features keep working.
Cancel subscription — open the side menu → "Manage subscription" (opens Google Play's subscription page) to cancel at any time; access continues until the paid period ends.
Delete account — open the side menu → "Delete account"; the app requests deletion of your Firebase sign-in account, trial record and any Cloud Sync content and media. Local protocols, Recipes, Samples and run history stay on this device. Manage your subscription separately in Google Play.
Contact & complaints — use the developer contact email on the Google Play store listing.
5. Children
This app is not directed at children under 14 and does not knowingly collect their personal information. If you are a minor, please use the app with a guardian's consent and supervision.
6. Third-party SDKs
See the "Third-Party SDK List" in the side menu. This app contains no advertising, analytics, or push-notification SDKs.
7. Changes to this policy
If this policy changes, we will notify you in the app. The latest version is always available in the side menu.