Privacy Policy

Information Briefly processes

Briefly processes message content only when you deliberately submit it for a rewrite or summary. Depending on what you choose to submit, that content may include email text, SMS or MMS text, or messages copied or shared from another application.

Briefly does not require a user account and does not collect your name, email address, phone number, contacts, precise location, photos, videos, payment-card information, advertising identifier, or device identifier through the app.

How message content is used

Submitted message content is encrypted in transit and sent through Briefly's secure server to OpenAI, our AI processing service provider. It is used only to produce the rewrite or summary you requested. Briefly does not sell message content, use it for advertising, or allow OpenAI to use it for independent marketing purposes.

Briefly requests stateless API processing with OpenAI response storage disabled. Briefly does not save the content of messages you rewrite or summarize. OpenAI's standard abuse-monitoring systems may retain API input and output data for up to 30 days, unless a different retention arrangement applies.

Voice input and audio

Briefly's keyboard voice input uses Android's on-device speech-recognition service when it is available. Raw microphone audio is not sent to Briefly's server or to OpenAI by Briefly. Android and the speech-recognition service installed on your device may process voice input under their own terms and privacy policies.

Microphone access is optional. You can deny or revoke microphone permission in Android settings and continue using Briefly's non-voice features.

Information stored on your device

Briefly stores content-free usage information on your device, such as the number of successful rewrites and summaries, estimated token usage, and estimated usage cost. This information does not contain the text of your messages. It may be removed by clearing the app's data or uninstalling the app.

Briefly may temporarily keep the original and rewritten text in application memory when needed to support the immediate result and Undo function. This temporary content is not written to Briefly's files or databases and is cleared when it is no longer needed or the relevant app component ends.

Sharing and service providers

Briefly does not sell or share personal information for targeted advertising. Message content is disclosed only to service providers needed to perform the requested feature, including Briefly's hosting infrastructure and OpenAI. These providers process data on Briefly's behalf to deliver the service.

We may disclose information if required by law or when reasonably necessary to protect the rights, safety, and security of users, Briefly, or others.

Your choices

Using Briefly's AI rewriting and summarizing features is optional. Message content is processed only when you choose to submit it. You can avoid this processing by not submitting a message. You can also revoke microphone permission, clear Briefly's local app data, or uninstall the app through Android.

Because Briefly does not create user accounts or retain message content in its own storage, Briefly generally has no stored message history to access, export, correct, or delete on your behalf.

Security

Briefly is designed to protect message content throughout the limited period in which it must be processed. We use encrypted HTTPS connections when information travels between the app, Briefly's server, and OpenAI. This helps protect submitted text from being read or altered while it is moving across the network.

The OpenAI API credential used to generate results is kept on Briefly's server and is not embedded in the Android app. Requests to Briefly's processing service require authentication, and authentication values are checked using a comparison method designed to reduce timing-based attacks. Briefly also limits accepted request sizes and rejects malformed, unauthorized, or unexpectedly large requests.

Briefly follows a data-minimization approach. The app sends the message text and instructions needed to create the rewrite or summary you requested, rather than sending unrelated information from your device. Briefly does not automatically read your conversations, contacts, photos, files, or other apps. Processing begins only when you deliberately submit content through a Briefly feature.

Message drafts are not written to Briefly's server logs, and Briefly does not maintain a database of the messages you rewrite or summarize. OpenAI response storage is disabled for Briefly's API requests. As explained above, OpenAI's abuse-monitoring systems may still retain API input and output for up to 30 days unless a different retention arrangement applies.

Content-free usage information stored by Briefly on your Android device is kept in the app's private storage area. This includes counts and estimates, not the words from your messages. Android's application sandbox helps prevent other ordinary apps from directly accessing this private storage. Clearing Briefly's app data or uninstalling the app removes this locally stored information.

Microphone access is protected by Android's permission system and remains optional. Briefly cannot use its microphone feature unless you grant permission, and you can revoke that permission at any time. When on-device speech recognition is available, Briefly relies on Android's speech service rather than sending raw microphone audio to Briefly's server.

Access to Briefly's processing systems and operational secrets is restricted to what is required to operate and maintain the service. We use technical controls such as authenticated requests, input validation, processing limits, and disabled message logging to reduce opportunities for unauthorized access, misuse, or accidental disclosure.

If Briefly becomes aware of a security incident involving personal information, we will assess it and take appropriate steps consistent with applicable law. Those steps may include containing the issue, correcting the vulnerability, notifying affected people or authorities when required, and improving safeguards to reduce the likelihood of recurrence.

You also play an important role in protecting your information. Keep your phone and Android security updates current, use a secure device lock, install Briefly only from an authorized source, review text before submitting it, and avoid submitting information that is not necessary for the result you want.

No application, server, network transmission, or storage system can be guaranteed completely secure. Briefly's safeguards are intended to reduce risk, but we cannot promise that unauthorized access, technical failure, or other security incidents will never occur. We will continue reviewing and improving security as Briefly develops.

Children's privacy

Briefly is a general-audience communication utility and is not designed specifically for children. Briefly does not create user profiles, sell personal information, or knowingly collect children's personal information for advertising. If a parent or guardian believes a child has submitted personal information through Briefly in a way that requires attention, they may contact us using the information below.

Changes to this policy

We may update this Privacy Policy as Briefly changes or as legal and operational requirements evolve. The current version will be posted at this public Privacy Policy URL, with an updated effective date when appropriate.