BrioLane Privacy Policy
Last updated: November 13, 2026. This policy covers BrioLane at briolane.win, its business workspace, and the publishing, messaging, email and assistant channels you connect (YouTube, Facebook/Instagram, TikTok, Douyin, Bilibili, Telegram, Discord and mailbox). For privacy questions or requests, use our public contact page; include “Privacy request” and a way for us to reply. Do not send passwords or access tokens.
Google and YouTube data at a glance
This summary describes BrioLane’s optional YouTube connection. The detailed policy and permissions follow below.
- Data accessed
- Connected channel ID and name; video metadata, status and available statistics; requested channel/video analytics; when comment replies are enabled, public comments, author channel IDs and reply records; granted scopes and OAuth credentials. We do not request Gmail, Google Drive, Google contacts or your Google password.
- Purpose
- Identify your channel, upload videos you select and approve, check publishing results and display requested performance reports, and publicly reply to new viewer comments only after the channel owner explicitly enables this feature.
- Sharing
- Authorized workspace users and service providers receive only information needed for these features. Google receives videos and metadata you choose to publish. We do not sell Google user data, share it for targeted advertising, or use it to train general-purpose AI models. Connecting YouTube alone does not send channel data or OAuth credentials to AI providers.
- Protection
- HTTPS protects data in transit, stored OAuth credentials are encrypted on the server, and workspace roles restrict access.
- Retention
- We keep connection credentials while needed for the connection; disconnecting removes those local credentials. Stored channel metadata and reports are retained for requested features and must be refreshed or deleted as required by YouTube policy. Historical records require a separate deletion request.
- Deletion and revocation
- Use our contact page to request deletion of stored Google data, including your workspace and channel details. After verifying your authority, we will remove authorized Google data within seven days. You can also revoke access in Google account security settings. Revocation does not itself delete historical records or videos on YouTube.
Facebook Messenger, Facebook Pages and Instagram data
When a business connects a Facebook Page or a linked Instagram professional account, BrioLane accesses the account identifiers, granted permissions and credentials needed for the selected feature. For Facebook Messenger and supported Instagram private messages, we store message text, message identifiers, timestamps and Page-scoped or account-scoped sender identifiers to maintain the business’s inbox, identify the correct conversation and prevent duplicate replies. A private message does not by itself give us the sender’s email, phone number, physical location or marketing consent.
Messages are used to display conversations, support customer service and send replies within the platform’s permitted reply window. When the workspace requests AI drafting or enables automated reception, relevant message text, recent non-internal conversation history, operator instructions and approved customer-facing business facts are sent to its selected AI provider to generate a reply. Channel access tokens are not sent to that model, and internal notes are excluded from this reception context. BrioLane does not use these messages to train general-purpose AI models. The selected provider’s processing terms also apply; businesses must assess those terms before enabling AI processing of customer information.
For approved Facebook Page video publishing, Meta receives the selected video, caption and publishing metadata. Authorized workspace members and service providers process information needed for these features. BrioLane does not sell Meta-derived personal information. Access is restricted by workspace membership and roles, HTTPS protects transfer, and stored channel credentials are encrypted on the server. Meta processes information under its Privacy Policy.
Connection credentials are kept while needed for an active connection. Message and publishing history is retained for the requested customer-service, reporting and recovery features, subject to deletion requests and applicable retention obligations. Disconnecting removes BrioLane’s stored connection credentials and stops future use of that connection, but does not automatically delete historical messages or content already held by Meta. Actions already in progress may still finish.
Request deletion of Facebook and Instagram data
- Use the public contact form and describe your request as “Meta data deletion”. Include a reply contact and enough information to identify the relevant business workspace, Page or Instagram account. If you are a customer of a connected business, identify that business and the conversation to help us locate your records. Do not send passwords, access tokens or a copy of every message.
- The BrioLane team handles requests manually, verifies your identity or authority to request the data, and identifies the records covered by your request. We may ask for further information needed for that verification.
- After verification, we remove the covered stored Meta-derived records unless retention is legally required, explain any such exception and notify you of the result through your supplied contact method. Restricted backups and restored copies must respect completed deletion requests.
You can also disconnect the channel in BrioLane settings and remove BrioLane’s access through the relevant Meta account’s app or business-integration settings. Revocation alone does not erase historical BrioLane records; deletion here does not erase copies of messages, posts or videos held by Meta or other participants. This contact process is a deletion-instructions service, not an automatic deletion callback.
Information we collect
- Account and workspace information: sign-in email, name, workspace membership, permission settings and authentication records. Passwords are stored as hashes.
- Information you submit: contact details, company, country, sales platform, enquiries, consent choices, business settings, customer records, messages and instructions.
- Content you provide or create: uploaded images, audio and video, creative briefs, scripts, storyboards, generated media, filenames and related processing records.
- Connection and operational records: connected account identifiers, granted scopes, encrypted OAuth credentials, publishing receipts, external video IDs, errors and usage records.
- Browser information: authentication/session storage, a visitor identifier, referral information and page/form events. These support sign-in, attribution and service improvement. Hosting providers may process network and security logs.
Google and YouTube data and permissions
BrioLane uses YouTube API Services. Google sign-in is handled by Google; BrioLane does not ask for or store your Google password. Connecting YouTube is optional. We request the following scopes for the features you choose:
youtube.readonly: read connected channel ID and name, and video metadata, visibility, processing status and available statistics, so you can identify the correct destination and check publishing results.youtube.upload: upload a video you select with its reviewed title, description and privacy setting to your connected channel.youtube.force-ssl: read and reply to public viewer comments on your connected channel's videos when you choose comment reception. Google describes this scope broadly; BrioLane does not use this feature to delete videos, ratings, captions or comments. The connection action explicitly asks you to consent to public automated replies and AI allowance use. After that consent, new channel connections start reception enabled by default; you can turn it off at any time under Customers and Messages → Comment reception. Updating authorization does not override a prior off state or safety pause.yt-analytics.readonly: read channel/video performance reports, such as views and watch time where available, for your workspace reports.
We store channel identifiers, granted permissions and OAuth refresh credentials to maintain the connection, plus video IDs, publishing outcomes and requested report data to show results. OAuth credentials are encrypted on the server and are not exposed to browser code. We do not request access to Gmail, Google Drive or your Google contacts for this integration.
How information is used and shared
We use information to operate your workspace, respond to enquiries, draft customer replies, generate or edit requested content, publish approved videos, show reports, troubleshoot failures and protect accounts. Marketing updates require separate consent. We do not sell personal information or Google user data, use Google data for targeted advertising, or provide it to data brokers.
Our hosting, storage and processing providers handle information necessary to deliver the service. When you request AI generation, relevant instructions and selected content are sent to the selected AI/media provider. An explicitly selected experimental model may have different retention or improvement terms; do not submit confidential or personal information to a trial whose terms do not permit it. Connecting YouTube alone does not send your OAuth credentials or channel data to an AI model. If you consent to automated comment reception during connection or turn reception back on, the public comment text is sent to our MiMo reply-generation provider to prepare a response; OAuth credentials are never sent to that provider. Processed comment records are removed after 30 days; unresolved generation or sending records are retained for support and outcome reconciliation and may be included in your deletion request.
BrioLane’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not used to train, improve or fine-tune general-purpose AI or machine-learning models. Access by people is limited to authorized workspace users and necessary support/security work, with consent or where required by law.
When you publish or send content, the destination platform receives the content and metadata needed for that action. Your selected YouTube visibility determines its audience. Google processes information under the Google Privacy Policy. BrioLane does not place third-party advertising on these public pages; external destinations have their own policies.
Storage, retention and security
Workspace access is limited by account role and workspace membership. HTTPS protects data in transit; server-side encryption protects stored provider credentials. Operational records support error recovery and prevent duplicate publishing. No security system can guarantee absolute protection.
We retain information while needed for the requested service, account security, transaction records or legal obligations. We do not intend to retain Google API data indefinitely: it must be refreshed or deleted as required by YouTube policy. You may request deletion of stored Google/YouTube data even while keeping your BrioLane account. Deletion requests are handled by the BrioLane team after verifying your authority over the workspace; this is not an automatic self-service deletion feature. We will remove authorized Google data within seven days of a verified request or as otherwise required by applicable policy. Backups are restricted and any restored copy must respect completed deletion requests; records required by law may be retained only for that purpose.
Disconnect, revoke access and request deletion
- In BrioLane, open channel connections and disconnect YouTube. This removes locally stored connection credentials and blocks future scheduled actions for that connection. Actions already in flight may still finish.
- You can separately revoke BrioLane’s Google access in Google account security settings. Local disconnection does not itself revoke the permission at Google.
- For deletion of stored channel metadata, reports and other Google data, submit a Privacy request with your workspace and connected channel details. We may ask you to verify ownership before deleting records. Revoking access alone does not delete historical workspace records.
Disconnecting BrioLane or requesting deletion here does not delete videos already on YouTube. Manage those videos directly in YouTube Studio. You can also request access to or correction of your personal information, withdraw marketing consent, or request account/workspace deletion through the contact page. Reply STOP to supported marketing messages to withdraw that consent.
Other platform channels
TikTok: on an authorized publication, the video, title, chosen visibility and supported AI and publishing metadata are sent to TikTok. Unaudited Direct Post clients face private-visibility and account restrictions specific to TikTok. We keep publishing receipts, external IDs and errors to verify outcomes and prevent duplicate posts. Connection does not guarantee publishing eligibility.
Douyin and Bilibili: handled the same way once the connection is available and you authorize it — account identifier, granted scopes, encrypted credentials, publishing receipts and available statistics. A platform that is not configured or that you have not authorized is never called.
Telegram and Discord: the business assistant can receive your goals and answers through official bots. Those platforms see the message content, and we keep the conversation and result records needed to continue the task. Bot credentials are encrypted on the server and used only for the matching platform.
Voice, narration and voice samples
Narration is synthesized by the chosen speech provider (Xiaomi MiMo, ElevenLabs): the narration text, language and voice identifier are sent to that provider, and the returned audio, usage and verification records are stored in your workspace.
Custom voice processing may send your uploaded voice sample to the selected voice provider and store generated previews in the workspace. Treat recordings as sensitive: upload only your own voice or one you have explicit permission to use. Revoking a presenter profile blocks new uses through it but does not delete source files, previews or provider copies. Request deletion through our contact page; already submitted requests and exported videos are not automatically recalled.
Email in and out
Received email (sender, subject, body and attachment metadata) is stored in the workspace inbox for replies and customer records; we also keep classification, reply and handling records so we can explain what was done.
For your connected mail service, authentication secrets such as the SMTP password are encrypted on our servers and are not returned to browser code. Connection metadata such as server address, port and sender identity is stored for configuration and may be shown to authorized workspace users. Credentials are used for authorized connection checks and sending. Message bodies are kept in the workspace per conversation.
AI processing and model providers
For generation, drafting, analysis or an enabled automation you have authorized, relevant instructions and selected text, images, keyframes, audio or video may be sent to the provider selected for that feature. Available integrations include DeepSeek, Xiaomi MiMo, OpenAI, Google Gemini, Z.AI, Groq, Volcengine Ark, Seedance/Hugging Face, Agnes and ElevenLabs; availability and configuration vary. This is a capability list, not a claim that every provider receives your data or that every integration is active. Voice verification may also involve an enabled transcription service. Public web research sends only the research topic and language/region to a search provider (Tavily by default) and caches the returned titles, links and short excerpts per workspace; that text is an external reference, not a business fact.
We do not train general models on your content, and we do not have people read your conversations line by line to "improve the model"; authorized staff look only at what is necessary when troubleshooting or when you ask us to verify something. Providers process data under their own terms, so check the retention terms before choosing an experimental model.
AI-generated video and narration may require AI disclosures or labels. BrioLane sends supported AI flags when publishing, and platforms may apply their own labels or watermarks. An exported file is not guaranteed to contain a visible AI label. Check and add disclosures required for your intended use before sharing it.
Processors and international transfers
Hosting, storage, email and model calls are handled by the following providers, only to deliver the features you asked for: Cloudflare (front-end hosting), our own application servers (API and queues), Resend (email in and out), the model providers listed above, and the platforms you choose to connect (Google, Meta, TikTok, Douyin, Bilibili, Telegram, Discord), and a web search provider (Tavily by default) when public research is enabled.
These services may process data outside your country, including in the United States, the European Union and China. The destination depends on the feature, configured provider and its processing arrangements. Cross-border processing remains subject to applicable law and required safeguards. Ask through our contact page for details relevant to your intended use before submitting sensitive information.
Retention
Account, workspace, message and email records are retained for the requested service, recovery, security and applicable legal obligations, subject to deletion requests. The YouTube comment cleanup targets eligible comment-reception records older than 30 days measured from publication time; this is not a promise that all platforms’ comments or customer records are deleted 30 days after handling. Publishing and usage records support verification and accounting. Google and YouTube deletion requests follow the process and verified-request deadline described above.
Backups are retained in a limited way, and data covered by a completed deletion request is not restored from them; records we must keep by law are kept only for that purpose.
Your rights and complaints
You can ask for access, correction, deletion, a copy, or object to or restrict processing, and you can withdraw marketing consent at any time (reply STOP or contact us). Send requests through the public contact page marked "Privacy request".
Where applicable, you may complain to the Philippine National Privacy Commission (NPC) or your competent privacy authority. Rights under GDPR, CCPA or other laws depend on their scope and your circumstances. We aim to respond within 30 days of receiving a request and follow any mandatory legal deadlines, identity checks and permitted extensions; we will explain an extension or a lawful refusal where required.
Children
BrioLane is for businesses and sole traders, not for children, and we do not knowingly collect children's personal data. If you find such information, tell us through the contact page and we will delete it.
Security and incident notice
Traffic uses HTTPS, stored credentials are encrypted on the server, access is limited by workspace role, and key actions are recorded. If a security incident affects your data, once confirmed we tell you the scope and what to do through the workspace or the contact details you gave us. No system can guarantee absolute protection.
Changes and contact
We update this page when our practices change. Material changes affecting Google data use require appropriate notice and consent. Questions or complaints about this policy: contact BrioLane.