Beta eligibility
The BRIJI closed beta is currently available to participants in the United States who are 18 years of age or older. This operational beta restriction is separate from eventual app-store content ratings.
Information you provide
This includes your name, email and account details; contacts you create or explicitly choose to import; typed Capture text; optional microphone audio you choose to record for transcription; transcripts returned to the editable Capture field; relationship notes and context; corrections; and settings or preferences.
Information BRIJI creates
BRIJI may create summaries, relationship memories and context, learned relationship information, signals, connections, Strengthen Opportunities, Connect Opportunities, and related ranking, evidence, and lifecycle information.
Local storage and cloud sync
Account-specific storage on your device supports local and offline use. Supported account data synchronizes to Briji cloud infrastructure so an authenticated account can restore supported synchronized data. We use safeguards designed for this personal information, but no system can promise perfect security.
AI processing
BRIJI uses OpenAI as a third-party AI service for Capture interpretation and optional speech-to-text transcription. Briji sends data to OpenAI only through the authenticated BRIJI backend; the OpenAI credential is not included in the mobile app.
Typed Capture
When you submit a typed Capture, the app sends the Capture text, capture timestamp, and timezone context through Briji's authenticated backend to the OpenAI Responses API for semantic interpretation. Normal Capture does not send your entire contact database or historical relationship database to OpenAI with each request.
Briji configures these OpenAI Responses API requests with store: false. This prevents the response from being retained as Responses API application state under OpenAI's documented default controls, subject to endpoint-specific exceptions described by OpenAI. OpenAI may separately process prompts, responses, and related metadata in abuse-monitoring logs. OpenAI currently documents default abuse-monitoring retention of up to 30 days, unless longer retention is required by law or is reasonably necessary to protect its services or third parties from harm.
Optional voice transcription
If you choose voice input, BRIJI requests microphone permission and records audio only after you start recording. The app sends the temporary audio file through Briji's authenticated backend to OpenAI's audio transcription endpoint. OpenAI returns text, which BRIJI places in the ordinary editable Capture field. Voice input does not automatically save or semantically analyze the transcript; you can edit or discard it before submitting the Capture.
BRIJI does not intentionally add the audio recording itself to relationship records or cloud synchronization. The app is designed to delete its temporary local audio file after successful transcription, cancellation, abandonment, interruption, backgrounding, or an invalidated session. That cleanup is best effort when the operating system interrupts or terminates native recording activity.
OpenAI's current API data-control documentation lists the audio transcription endpoint as having no application-state retention and no abuse-monitoring retention. Provider controls, exceptions, and documentation may change, so Briji does not promise that a provider will retain no operational or legally required records in every circumstance.
Model training and provider controls
OpenAI states that data sent to its API is not used to train or improve OpenAI models by default unless the API customer explicitly opts in to share data. Briji does not intentionally opt Capture text, audio, or transcripts into model training. Model-training controls, Responses application-state storage, abuse-monitoring logs, and BRIJI's temporary local audio files are separate forms of data handling and may have different retention rules.
AI interpretations and transcripts can be incomplete or wrong. Voice transcription returns editable text without automatically submitting a semantic Capture. Normal Capture may save AI-interpreted relationship information after analysis without a separate mandatory review screen. Inspect saved information, correct errors where supported, and verify important information before acting on it.
Consent and withdrawal
Updated BRIJI mobile clients require acknowledgment of Privacy Policy version October 13, 2026 and Beta Terms version September 27, 2026 before sending new typed Capture content or optional audio to OpenAI. Material changes to AI processing require renewed acknowledgment. Server-wide enforcement of this consent version is planned for a coordinated activation and is not active before that activation; older installed clients may not apply the updated mobile checks. After server enforcement is activated, server requests without authoritative current consent are denied.
If you decline consent, updated clients block new typed AI Capture and voice-transcription uploads. Withdrawing consent immediately blocks new AI processing on the device where you withdraw and queues the authoritative cloud withdrawal. If that device is offline, cloud withdrawal remains pending and retries when connectivity returns. Other devices may not reflect the withdrawal immediately. Once authoritative cloud withdrawal is confirmed and server enforcement is active, new server requests for that account are denied until you explicitly consent again. Withdrawal does not cancel provider requests that already started, reverse processing that already finished, or by itself delete information you previously chose to save.
You may separately edit or delete supported information through BRIJI, stop using Capture, or delete your account. A later consent does not recreate audio files or other information previously deleted by BRIJI.
How BRIJI uses information
We use information to operate Capture, maintain and synchronize relationship information, generate relationship context and intelligence, surface Opportunities, protect service integrity, and troubleshoot the service. BRIJI does not currently use relationship information for behavioral advertising.
Service providers
- Supabase provides authentication and synchronized storage.
- Render hosts the authenticated BRIJI backend.
- OpenAI provides typed Capture interpretation and optional speech-to-text transcription.
- Expo, Apple, and Google provide application build, distribution, and platform services as applicable.
- Cloudflare hosts this public company, support, privacy, and policy website.
- Purelymail supports company and deletion email.
Operational diagnostics
BRIJI uses limited operational metadata such as request status, timing, counts, token usage, AI cost/accounting information, model, and service status. Reviewed BRIJI application diagnostics are designed not to log raw Capture relationship content, names, audio, transcripts, credentials, or arbitrary relationship records. Independent providers may maintain their own infrastructure logs under their policies.
Device permissions
Contact permission is requested only when you choose contact import. You control which contacts are imported. Microphone permission is requested only when you choose to record audio for transcription. Typed Capture remains available without microphone permission. The current beta does not request camera, background location, or notification permission for normal Capture.
Retention
Account-owned BRIJI data generally remains while your account exists unless you change or delete applicable information through normal product behavior or delete the account. Synchronization, integrity, conflict-prevention, replay-protection, and trustworthy-history records may remain while needed to protect the account and service. We do not promise automatic deletion after a period of inactivity. Temporary local audio and OpenAI API data handling follow the more specific descriptions above. Service-provider operational or legally required records follow provider policies where applicable.
Account deletion
You can delete your account in BRIJI or follow the external account-deletion instructions. Account deletion permanently removes the account and associated BRIJI cloud data as described there. It also removes that account's local app database after remote deletion is confirmed. Account deletion cannot undo AI processing completed before deletion and does not override records a service provider must retain for legal or security reasons under its applicable terms.
Your choices
You choose whether to import contacts, use typed or voice Capture, submit a Capture for AI processing, correct editable information, save relationship information, and act on Opportunities. You may withdraw AI-processing consent, delete supported information, or delete your account. For privacy, access, correction, deletion, withdrawal, or safety questions, contact us. We may reasonably verify control of the associated account or email.
Material policy changes
Material changes to this policy or the Beta Terms may require renewed acknowledgment in BRIJI. Spelling, formatting, or other non-material corrections do not.
Contact
Briji Enterprises LLC
[email protected]