Last updated: October 17, 2026
BriefFox (“BriefFox,” “we,” “us”) is a local-first business preparation app developed by FoxForge Studio. It helps you prepare for a business conversation using a public company website, information you provide, optional AI-assisted preparation, meeting notes, and follow-up drafting.
This Privacy Policy explains what information BriefFox processes, where it is stored, when information may be sent to third parties, and what choices are available to you.
You may enter a public company or business website.
BriefFox accepts ordinary public HTTP or HTTPS website addresses.
The current implementation rejects certain addresses that are not appropriate for this feature, including:
You may also prepare a brief using context that you paste yourself when a website cannot be used.
You may optionally enter a company or person name.
This information can be used to label and tailor your preparation.
When you request an AI-generated brief, this information may be included in the Gemini request.
You choose a preparation purpose such as:
The selected purpose is stored as part of the local preparation draft and saved brief.
When AI generation is used, the purpose is included in the AI request.
You may optionally describe what would make the conversation useful.
Your goal is saved locally as part of your preparation draft and saved brief.
When AI generation is used, the goal may be included in the Gemini request.
You may optionally enter information such as:
Context notes are saved locally.
When you build an AI-assisted brief, relevant context notes are sent to Gemini.
BriefFox’s interface tells you to add only information that you want to send for AI processing.
Do not enter passwords, authentication credentials, full payment-card numbers, regulated information, or confidential information that you do not want transmitted to the AI provider.
BriefFox saves the preparation form locally as you type.
The local preparation draft can contain:
The draft is stored in BriefFox’s local Documents/application storage as a JSON file.
On iOS, BriefFox applies Apple’s file-protection mechanism to this local draft file.
You can use Clear current draft in Settings to clear the current preparation form.
Clearing the draft does not delete your already saved briefs or meeting notes.
In the current release, BriefFox does not ask Gemini to browse the URL using Gemini URL Context.
Instead, BriefFox itself requests the public website address you entered.
The request uses an ephemeral network session.
The current implementation:
BriefFox normally extracts limited information such as:
Scripts, style blocks, and similar markup are excluded from the extracted context.
When BriefFox requests a public website, the website or its hosting/network providers may receive ordinary network-request information.
This can include information such as:
The current website request identifies itself using a BriefFox user-agent.
The website may retain its own server or security logs according to its own privacy and retention practices.
FoxForge Studio does not control those independent website logs.
If BriefFox cannot retrieve the website but you supplied sufficient context yourself, the AI-assisted brief may be generated using your supplied context instead.
BriefFox records the website source as unavailable rather than pretending that the website was successfully retrieved.
If no usable website or context is available, BriefFox does not fabricate website research.
When you deliberately choose Build my brief, BriefFox may send Google Gemini through Firebase AI Logic:
BriefFox does not send the entire raw website response to Gemini.
The website extract passed to Gemini is bounded by the application’s retrieval limits.
Gemini may return structured preparation such as:
AI output may be incomplete, inaccurate, or misleading.
BriefFox is designed to distinguish retrieved website evidence, user-provided information, and AI inference where applicable.
You should verify important details before relying on them in a real conversation.
When BriefFox successfully retrieves a webpage, the locally saved brief may include:
If the website could not be retrieved, BriefFox may save a local source record stating that it was unavailable.
If you supplied context yourself, BriefFox may store that context as a user-provided source.
When available in the app, you may deliberately choose a basic template instead of successfully completing an AI-assisted preparation.
The basic template:
The resulting template is saved locally like another brief.
BriefFox saves briefs locally in its private application storage.
A saved brief may contain information such as:
BriefFox does not upload this saved brief archive to a FoxForge Studio database.
Saved briefs and locally saved notes remain available without an active network connection.
BriefFox does not sync the local saved-brief archive between your devices.
Search and filtering of saved briefs are performed locally using your saved BriefFox information.
Local search may inspect information such as:
Using Saved search does not itself create a new Gemini request.
You can record text notes while using BriefFox’s meeting workflow.
Meeting notes are stored locally as part of the applicable saved brief.
BriefFox also stores information about which suggested questions you marked as asked and whether you marked the meeting flow complete.
Entering or editing meeting notes does not itself send them to Gemini.
Meeting notes may be sent to Gemini later if you deliberately request an AI-generated follow-up or AI rewrite.
You may enter what happened during the conversation and any actual next steps or outcomes.
This information is stored locally.
It is not automatically emailed or sent to the other party.
When you deliberately request an AI-generated follow-up, BriefFox may send Gemini:
The current implementation can send up to approximately:
Gemini generates an editable follow-up draft.
BriefFox does not automatically send that draft as email or a message.
The resulting draft is stored locally after it is accepted and saved by the app.
BriefFox can request AI-assisted wording changes such as:
When you request one of these changes, BriefFox may send Gemini:
The current draft is limited before being sent for a rewrite.
The AI is instructed to change wording rather than invent new facts or commitments.
The revised draft remains editable and is not sent automatically to another person.
BriefFox provides an Apple system paste control for the company-website field.
Clipboard content is read for this purpose when you deliberately use the paste action.
BriefFox does not need to continuously monitor the clipboard.
When you deliberately tap a Copy control, BriefFox places the selected text on the iOS clipboard.
Other apps or system services may be able to access clipboard content according to iOS behavior and permissions.
BriefFox provides Apple system sharing for certain generated or saved content, including brief text and follow-up drafts.
Sharing occurs only when you deliberately invoke the Share action and choose a destination.
Once content is passed to another app, person, file location, or service, that destination controls its copy according to its own privacy practices.
BriefFox cannot automatically delete a copy that you exported or shared elsewhere.
BriefFox stores its active saved-brief archive as a local JSON file.
Writes are performed atomically to reduce the risk of an interrupted write damaging the active archive.
On iOS, BriefFox applies Apple’s file-protection mechanism to the saved archive.
When BriefFox upgrades certain older local save formats, it may create a local backup copy of the previous archive before migrating it.
The current release may also create an exact local backup of an older archive before removing an unchanged retired bundled sample.
These backups exist to protect user information during migration or cleanup.
A backup may contain information that existed in the saved archive at the time the backup was created.
These backup files remain local to the app’s storage.
Deleting an individual brief from the current active archive does not necessarily modify an older migration/recovery backup that was already created.
Deleting the BriefFox app removes files from the app’s active local container subject to normal iOS backup and restore behavior.
The current release does not provide the prior fictional sample-brief creation flow on the preparation screen.
During upgrade, an unchanged legacy bundled sample may be removed after BriefFox first creates an exact local backup of the prior archive.
If the legacy sample contains user edits or activity, BriefFox is designed to preserve the record rather than automatically deleting the edited content.
Settings provides a Clear current draft action.
This clears the current preparation form.
It does not delete your saved briefs, meeting notes, or follow-up work.
You can delete an individual saved brief from Saved.
Deleting it removes the brief from BriefFox’s active saved-brief archive.
That deletion includes the active brief’s saved preparation, meeting notes, follow-up information, and other state contained in that brief.
Deleting an individual brief does not:
Deleting the app removes information in BriefFox’s active application container from the device, subject to normal iOS backup and restore behavior.
Deleting the app does not:
The current release does not require a BriefFox account or login.
During normal app use, BriefFox does not request access to:
The current release does not use CloudKit to sync your saved briefs.
The current release does not use StoreKit for an active BriefFox purchase or subscription flow.
BriefFox does not display third-party advertising.
The current privacy manifest declares tracking as disabled.
BriefFox does not use your preparation or meeting information for cross-app or cross-website advertising tracking.
The current release does not include Firebase Analytics or Firebase Crashlytics in the BriefFox app target.
BriefFox does not send your raw brief archive to a FoxForge Studio analytics database.
Google, Firebase, Apple, or public websites may independently process technical service information necessary to provide their respective services.
BriefFox uses Firebase AI Logic to access the Gemini Developer API for optional AI-assisted functionality.
The current app uses Gemini for:
Firebase states that Firebase AI Logic itself does not store customer input and output data sent to and received from the selected generative-AI provider.
The selected Gemini provider’s own processing, security, data-use, and retention terms still apply.
Firebase privacy information:
https://firebase.google.com/support/privacy
BriefFox uses Gemini Generate Content requests through Firebase AI Logic.
Google’s data-use and retention rules can depend on factors such as:
Google’s current documentation distinguishes provider processing from optional project logging and monitoring.
Generate Content project logging is configurable. If logging or Firebase AI monitoring is enabled, prompts, generated output, request metadata, or sampled request information may be retained according to the applicable Google/Firebase configuration and retention settings.
BriefFox therefore does not promise one fixed provider-side retention period for every AI request.
FoxForge Studio cannot recall an individual request after it has already been transmitted to Google.
BriefFox does not itself use your preparation, meeting notes, or follow-up text to train a separate FoxForge Studio AI model.
Google information:
https://ai.google.dev/gemini-api/docs/logs-policy
https://ai.google.dev/gemini-api/docs/zdr
https://policies.google.com/privacy
BriefFox uses Firebase App Check to help protect Firebase-connected AI requests from unauthorized clients.
Production builds use:
App Check may process:
Firebase states that App Check itself does not retain attestation material.
Attestation material sent to Apple is subject to Apple’s applicable terms and policies.
App Check tokens are handled according to Firebase’s applicable TTL, security, and retention practices.
BriefFox does not use these integrity signals to build a profile of the content of your briefs.
Firebase App Check information:
https://firebase.google.com/docs/app-check
Public websites that BriefFox retrieves are independent third parties.
Their operators may process ordinary request information according to their own privacy and security practices.
If you deliberately open a source link from BriefFox, Apple or your selected browser may separately contact that website.
BriefFox does not control the destination website’s privacy practices.
Support communications are optional and separate from normal BriefFox use.
BriefFox does not automatically attach your briefs, meeting notes, website extracts, or follow-up drafts to a support email.
If you contact FoxForge Studio at Simon.Yam227@gmail.com, we receive only the information you voluntarily provide.
This may include:
Support communications are used to respond to your request, troubleshoot reported issues, investigate bugs, prevent abuse, maintain reasonable support history, and meet applicable legal obligations.
The Simon.Yam227@gmail.com mailbox is provided through Gmail, operated by Google LLC.
Google processes the email information necessary to route, deliver, store, secure, and filter those messages according to its applicable policies.
Google Privacy Policy:
https://policies.google.com/privacy
Support emails may be retained while a support request is open and for a reasonable period afterward when needed for:
FoxForge Studio does not promise one fixed automatic deletion period for support messages.
Support messages may remain in Gmail according to Google’s applicable retention, backup, security, and service practices.
You may request deletion of a support conversation that you previously sent by emailing:
Simon.Yam227@gmail.com
Please provide enough information to identify the applicable conversation.
Where reasonably possible, we will delete the identified communication from active support records, subject to legal, security, fraud-prevention, backup, and provider-related retention requirements.
This Privacy Policy is hosted using GitHub Pages, operated by GitHub, Inc.
Visiting this privacy-policy webpage is separate from using BriefFox.
GitHub states that GitHub Pages logs visitors’ IP addresses for security purposes.
BriefFox does not send your local saved briefs, preparation drafts, meeting notes, or follow-up drafts to GitHub Pages.
GitHub Privacy Statement:
https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement
Google/Firebase process information for the optional AI and app-integrity functionality described above.
Apple may process information for App Attest, DeviceCheck, iOS clipboard/paste controls, sharing interfaces, and ordinary operating-system services.
Public websites you deliberately submit receive the limited website requests described above.
Gmail processes information you voluntarily send to FoxForge Studio support.
Any third party that processes user data for BriefFox or BriefFox support will provide the same or equal protection of user data as stated in this Privacy Policy and as required by Apple’s App Review Guidelines.
You can:
Avoid entering information that you do not want processed as described in this policy.
BriefFox is not directed to children under 13.
BriefFox does not operate a FoxForge Studio user-account system through which children provide profile information.
We may update this Privacy Policy if BriefFox’s features, providers, or data practices change.
The Last updated date above reflects the latest version.
For privacy questions or requests regarding BriefFox, contact:
FoxForge Studio
Email: Simon.Yam227@gmail.com