Privacy Policy

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)

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.

3. Where and how long your data is stored

4. Your rights and how to exercise them

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.