Scope

This policy explains how VoiceBrief handles data when you create an account, share audio, purchase a subscription, or contact support.

Data We Process

• Account data: email address, account identifier, sign-in provider, and a name or profile image when supplied by that provider.
• Audio content: the file you choose to share, import, or record for processing.
• Generated results: transcript, summary, key points, tasks, dates, and suggested replies.
• Subscription and usage: product, entitlement status, subscription period, purchase history, expiration status, and processing minutes used.
• Support and diagnostics: information submitted through support or deletion forms, redacted operational error codes, and hashed identifiers used to prevent abuse.

Google Sign-In SDK Disclosure

Build 18 includes the Google Sign-In SDK. Under the SDK disclosure supplied for Google Play, when Google sign-in is made available or used, the SDK may collect Name, Email, Phone Number, Coarse Location, User ID, Device ID, Other Usage Data, and Other Data Types for app functionality and analytics. These SDK data categories are treated as linked to the user and are not used for tracking.

This disclosure describes potential processing by the embedded Google SDK; VoiceBrief does not directly ask you for a phone number or coarse or precise location, and the app does not request location permission for this purpose. Actual processing by Google depends on account, device, and service configuration and Google’s policies.

How Audio and Results Are Processed

Uploading starts only after you select or record audio. The audio is uploaded to private temporary storage in Supabase, then sent to OpenAI for transcription and result generation. The normal processing path attempts to delete the temporary copy when processing succeeds or fails. If an interruption prevents immediate deletion, the copy may remain in private storage until operational cleanup or account deletion removes it; VoiceBrief does not present it as permanent audio history.

In the ordinary in-app flow, a result is written to local history only when you choose Save. A Share Extension result is automatically saved locally on your device after import so the completion notification can open it. You can delete local results in the app.

The Supabase processing_jobs.result record may contain the complete generated result—including transcript, summary, tasks, dates, and replies—for up to 24 hours to support safe retries and prevent duplicate charging.

OpenAI Processing

VoiceBrief sends OpenAI requests with store: false, so Responses output is not retained as stored application data through that API feature. OpenAI may nevertheless retain API inputs and outputs in abuse-monitoring logs for up to 30 days unless the VoiceBrief account has been approved and configured for Zero Data Retention or Modified Abuse Monitoring. We do not currently claim that Zero Data Retention is enabled.

Service Providers

• Supabase: authentication, database, temporary storage, and server processing.
• OpenAI: audio transcription and generation of summaries, tasks, dates, and suggested replies.
• RevenueCat, Apple, and Google: subscription status and Purchase History. VoiceBrief maps the Supabase account ID to the RevenueCat App User ID, so RevenueCat Purchase History and subscription or entitlement status are linked to the VoiceBrief user. These providers may process product, entitlement, purchase date, expiration, and transaction history under their policies.
• Apple or Google: sign-in when you choose that option, including profile data shared by the provider.

Calendar events open in your device’s system editor for review before saving. VoiceBrief does not store your calendar on its servers.

What We Do Not Do

We do not sell your data, use an advertising network, or include advertising-tracking tools. VoiceBrief cannot access audio you did not choose to share or record.

Retention and Deletion

Account and usage data needed to provide the service remains until account deletion or until it is no longer operationally required. You can delete a VoiceBrief account in Settings or submit a request on the Delete Account page. Canceling an App Store or Google Play subscription is a separate action and is not performed by deleting the VoiceBrief account. Transaction records may remain with the store or RevenueCat for legal or operational reasons. A Sign in with Apple user may also need to revoke VoiceBrief access manually in Apple Account settings after deletion.

We do not currently promise a fixed retention period for support and deletion requests. They are kept as needed to respond, verify account ownership, investigate abuse, protect the service, and satisfy legal obligations.

Your Choices and Data Security

You can choose not to upload audio, delete local results, sign out, revoke system permissions, and delete your account. We use encrypted transport and restricted access, but no online service is completely risk-free.

Changes and Contact

This policy may change when the service or requirements change. The date at the top will be updated for material changes. For privacy questions or data requests, use the Support page. To delete an account, use the Delete Account page.