Privacy notice

We handle account and business contact details, sign-in and membership information, and records you or your authorized team add to a workspace. These can include leads, customer details, messages, appointments, quotes, documents, uploads and business activity. Connection settings, delivery history, audit records and technical information help operate and protect the service. Sign-in and browser storage help maintain your session and workspace choices.

When you inquire about Brienta, we save the details you submit so our authorized team can review and respond. Campaign labels may identify how you found us, and technical information helps prevent abuse. An inquiry alone does not subscribe you to marketing messages.

We use information to provide workspaces, manage access, organize customer work, schedule appointments, deliver communications you request, produce reports, troubleshoot problems and protect the service. Company and agency access depends on current membership, assigned scope and permissions. An agency connection does not provide access to unrelated companies.

Cloudflare hosts the application, Supabase provides account and database services, and Cloudflare Email Sending delivers configured email. Optional connections share the information needed for the features a company enables, such as CRM delivery or scheduling. When authorized users request AI features, OpenAI receives the relevant aggregate reporting facts or advertising creative and business context. Google Calendar information is excluded from those AI and advertising flows.

Advertising measurement uses separate settings and consent controls. Brienta's own inquiry measurement is off unless configured and expressly chosen. When offered, its optional disclosure explains the hashed email and advertising event sent to Meta. Global Privacy Control overrides that choice. Calendar permission does not provide advertising or marketing-message consent.

If you choose Continue with Google, Google shares your account identifier, verified email address and basic profile information, such as your name and profile photo, with Brienta through Supabase. We use this information to create or sign in to your Brienta account. Your workspace access still depends on your verified memberships and invitations. Brienta does not receive your Google password.

Google sign-in requests only basic identity information. It does not grant access to your Gmail messages, contacts, files or calendar. Connecting Google Calendar is a separate choice described below. You can review or remove Brienta's authorization in your Google Account connections.

When you choose to purchase or manage a Brienta company or agency subscription, Stripe hosts checkout and the billing portal and processes payments. Payment-card details and billing or contact information you enter on those pages go directly to Stripe. Stripe also receives transaction and technical information to process payments, authenticate transactions, prevent fraud and meet its obligations.

We send Stripe the selected plan, price, monthly or annual billing interval and identifiers linking the purchase to your company or agency workspace. Brienta stores accepted plan and price information, trial and subscription status, billing changes, customer and payment references, invoice amounts, coverage periods, refunds and payment review records. We use these to manage access, recurring billing, price protection, support and payment reconciliation. Brienta does not store full payment-card numbers or card security codes.

If an owner enables supported additional paid usage, we record that choice and the spending limit, service, measured units, applicable rate, billing period and relevant workspace references. We send the billing amounts, service descriptions and associated billing references to Stripe for usage invoicing. Availability and charges depend on the services and additional usage the owner enables.

Stripe describes its own use and retention of information in its Privacy Policy.

Following a Brienta referral link can place a referral cookie in your browser. It stores a click identifier so we can associate a later eligible signup with the referring affiliate during the attribution window shown in the affiliate program. We record the referral code association, a random visitor identifier, timing and signup attribution. Technical request information also helps prevent referral abuse.

When you join the affiliate program, we keep your account association, referral code, program status, commission records and payout references. Eligible subscription payments, refunds and adjustments help calculate commissions. Affiliates can see referral status, selected plan and attributed subscription revenue using numbered referral labels, along with their commission and payout totals. These referral views do not include the referred workspace's customer records or payment-card details.

In-app calls share audio and, when you enable your camera, video with the people in that conversation. Cloudflare provides the call connection. Joining a regular call does not authorize recording.

When recorded calls are available and selected, Brienta asks each participant to agree before joining the recorded conversation. A participant may continue without recording; Brienta then stops recording before admitting that participant. A visible indicator shows when recording is active. The recording feature saves audio, not camera video, and does not automatically create transcripts or AI summaries.

Cloudflare processes the recording, and Brienta stores completed audio privately using Supabase. Call participation, recording choices and recording status are saved with the conversation. People with current access to that conversation may play its recordings. Recordings are retained with the conversation until an authorized deletion request is processed; storage limits may prevent new recordings. Contact us using the details below for access, export or deletion requests.

Connecting Google Calendar is optional. If you connect, you authorize Google access and then choose the calendar to share. Brienta reads your calendar list and connected-account information to identify the account and offer a selection. Event access, availability checks and appointment synchronization for a newly connected account wait for that selection.

For the selected calendar, Brienta can read event titles, descriptions, locations, times, organizer and attendee details, and event or meeting links. Authorized company and agency users with Calendar access can see those details. Brienta uses busy times to check availability and can create, update or cancel appointment events when Google Calendar is chosen for scheduling. Appointment details and attendee information are sent to Google for those actions; Google may notify invited attendees. Connect a calendar you are authorized to share with that workspace.

Brienta stores the account label, selected calendar, company/user association and encrypted connection credentials. Event lists are requested for the calendar view or availability check. Brienta also keeps its own appointment records and identifiers or meeting links that connect those appointments to Google events.

Brienta's use of information received through Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We use Google Calendar information for the calendar and scheduling features described here. We do not sell it, use it for advertising, send it to advertising providers, or use it to train AI models. We do not send Google Calendar contents or credentials to OpenAI. Sharing is limited to the authorized calendar feature and the service providers needed to operate it, subject to Google's data-use requirements.

When an authorized company or agency manager connects Meta, Meta shares the account identity, permissions and selected business assets needed for the features you choose. These may include business portfolios, ad accounts, Pages, lead forms and datasets, together with advertising performance, campaign details and creative information. Brienta uses these records for asset mapping, spend and performance reporting, and the reporting or AI analysis features you request. Brienta does not receive your Facebook password.

Enabling lead access lets Brienta receive submissions from mapped Meta lead forms, including the contact details, answers and advertising attribution supplied with each submission. Your company controls its Lead Flow qualification, routing and follow-up settings. Connecting an ad account alone does not authorize sending marketing messages.

Conversion reporting is a separate choice. When configured and permitted by the applicable consent and measurement settings, Brienta sends selected lead or sales events to your mapped Meta dataset. Events can include timing, value, advertising identifiers and contact identifiers normalized and hashed for matching. Hashing does not make those identifiers anonymous. Meta processes information it receives under its own terms and privacy policy.

Pause stops Brienta from using the saved Meta connection. Disconnect removes its saved authorization credentials and stops new access through that connection while preserving existing company reports, leads and delivery history. You can also remove Brienta in Meta's Business Integrations settings. Revoking an authorization in Meta can affect other workspaces using the same authorization; they may need to reconnect. To request deletion of Meta-related information held by Brienta, follow the instructions under Retention, security and requests below.

Use Disconnect in the company's Google Calendar settings to remove your saved connection from Brienta. Local removal stops Brienta from using that saved credential. It does not automatically revoke your Google authorization, delete existing Google events or erase Brienta appointment history.

To revoke Google access, remove Brienta in your Google Account connections. Google's revocation applies to the authorizations your account granted to the same Google Cloud project. It can affect other Brienta connections using that project, beyond the selected calendar. Affected connections need fresh authorization to resume.

Company owners manage their teams and agency relationship. When a company leaves its agency, company records and ownership remain with the company and the departing agency's access ends. Billing read-only status does not delete company records.

Workspace records remain available for the company's continuing work and recordkeeping. Disconnecting an integration removes its saved credential as described above; it does not automatically erase appointment history, delivery evidence or audit records. Billing, payment reconciliation, referral, security, support and operational records are retained as needed for their purposes. Canceling a subscription does not automatically erase those records.

Brienta uses access controls, secure connections and encrypted storage for integration credentials. No online service can guarantee absolute security.

Contact support@brienta.com to request access, correction, export or deletion of information, or help disconnecting an account. We may need to verify your identity and authority, and coordinate with the company responsible for a workspace. Tell us the account or company involved; do not email passwords or connection tokens.