Your data stays yours

Privacy Policy

Effective date: August 22, 2026

Blabb is developed and published by Joseph Samara (“Blabb,” “we,” “us”). A private contact channel for privacy requests will be published before the private beta opens.

Privacy summary

Blabb is an offline speech-to-text utility. It has no user accounts, advertising, analytics, tracking SDKs, or cloud speech recognition. Dictated audio, transcripts, and active text-field content are processed on the Android device and are not sent to Blabb or to a transcription service.

Website waitlist

Joining the Blabb waitlist is optional and separate from using the app. The waitlist collects the email address a visitor submits and whether the visitor selected Android or iPhone. We use that information only to confirm the subscription and send meaningful beta, availability, development, and launch updates for the selected platform. Consent is confirmed through double opt-in, and each message includes an unsubscribe option.

The signup request passes through Cloudflare, which protects and delivers this website. A small Cloudflare Worker validates and rate-limits the request, then sends the email address and platform tags to EmailOctopus. Blabb does not keep a separate waitlist database or log submitted email addresses. EmailOctopus stores the contact, consent status, tags, and delivery records as our email service provider. Blabb does not currently send campaigns or automated welcome emails. If optional open or click tracking is enabled for future messages, this policy will be updated before it is used. See the Cloudflare Privacy Policy and EmailOctopus Privacy Policy.

Waitlist information is kept until the subscriber unsubscribes or asks for deletion. EmailOctopus may retain the minimum suppression record needed to ensure an unsubscribed address is not added again without permission. A subscriber can make a privacy request by replying to a Blabb waitlist message.

Data Blabb accesses on the device

Microphone and voice audio. Blabb accesses the microphone only after the user starts a dictation and stops capture when the user stops or cancels it, or when the two-minute safety limit is reached. Audio is written to app-private temporary storage and transcribed locally. It is normally deleted as soon as processing completes or is canceled. If processing is interrupted, one recovery recording and encrypted recovery metadata can remain for up to 10 minutes and are processed again only at the user’s request. An orphaned temporary audio file is deleted on the next app startup once it is older than one hour. Clearing Blabb’s storage or uninstalling Blabb deletes app-private audio.

Active text fields and app context. With the user’s separate consent and Android Accessibility permission, Blabb accesses the identity and type of the active app and editable field, the field’s current text, selection, cursor position, and Android editor events. This access is used only to determine whether the bubble should appear, insert dictated text at the correct position, confirm insertion, and safely undo the most recent Blabb insertion. Blabb does not operate in password or PIN fields. It does not retain raw field text, a list of apps used, or screen-content history.

Dictated text. Transcripts are created locally. Blabb does not maintain a dictation history. To prevent loss after an insertion problem or interruption, at most one pending transcript can be stored with Android Keystore-backed AES-GCM encryption for up to 10 minutes. It is deleted when insertion succeeds, the user discards it, or it expires. When the user asks Blabb to insert text into another app, that app receives the text and handles it under its own privacy policy.

Clipboard. When direct insertion is unavailable and the user has enabled one-tap paste, or when the user chooses Copy, Blabb can place a transcript on Android’s clipboard. Blabb labels the clip as sensitive. Android or the user can clear it, and another copied item replaces it. Other apps’ ability to read clipboard data is controlled by Android.

Local compatibility records. Blabb stores bounded success and failure counts so it can choose a reliable insertion method for a text-field type. App and editor identities are transformed with a per-install Android Keystore HMAC key before storage. Raw package names, field text, and transcripts are not stored in these records. Records expire after 180 days, are limited to 512 entries, and can be erased with Reset compatibility learning in Diagnostics.

Device and app settings. Blabb reads device model, Android version, processor architecture, memory, and free storage locally to select a compatible speech model. User preferences, permission state, bubble position, setup state, and installed-model state remain in app-private storage until the user resets app data or uninstalls Blabb.

Diagnostics. Blabb does not transmit crash reports or diagnostics automatically. A user can explicitly create and share a text diagnostic report. The report contains app and Android versions, device manufacturer/model, processor architecture, permission/service states, model state, and content-free compatibility counters and pseudonyms. It excludes dictated audio, transcripts, field text, raw app names, and app-use history. The user chooses the receiving app, whose privacy practices then apply.

Network use and third parties

Blabb uses the internet only to download speech-model files selected during setup or by the user. Current model files are downloaded over HTTPS from GitHub releases operated by GitHub, Inc. Blabb sends no audio, transcript, active-field content, contact information, advertising ID, or Blabb-generated device identifier with a model request. Like any internet request, GitHub and network providers necessarily receive standard connection information such as the source IP address and HTTP request metadata. An IP address can reveal approximate location. GitHub can retain and use this connection information to operate and secure its service. The Blabb developer does not receive that information from these downloads. GitHub handles it under the GitHub Privacy Statement.

Blabb does not sell personal data. It does not share data for advertising, profiling, or cross-app tracking. User-directed insertion, clipboard use, and diagnostic sharing are transfers initiated by the user to the app the user selected.

Security

Blabb uses app-private storage, disables Android cloud backup and device-to-device transfer for its data, encrypts pending transcript recovery records with Android Keystore-backed AES-GCM, marks clipboard fallback as sensitive, uses HTTPS for model downloads, restricts downloads to approved hosts, and verifies model sizes and SHA-256 hashes before installation. No security measure can guarantee absolute protection.

Retention and deletion

The app retention periods above are enforced locally. Users can delete pending recovery content from the recovery screen, reset compatibility learning in Diagnostics, reduce installed-model storage in Settings, clear all local data through Android Settings, or uninstall Blabb. Blabb has no app account or server-side app profile to delete. Waitlist subscribers can unsubscribe through any waitlist message or reply to request deletion.

Children

Blabb is a general productivity tool and is not directed to children under 13. It does not knowingly collect personal information from children.

Changes

Material changes to Blabb’s data access or use will be reflected in this policy, the Google Play Data safety declaration, and any required in-app disclosure and consent flow. The effective date will be updated.

Contact

A dedicated, non-personal privacy contact channel will be published here before the private beta opens.