Brandios legal

Privacy Policy

Last updated: October 24, 2026

Brandios (brandios.ai) is a product of NextVibe Tech L.L.C-FZ, a company registered with Meydan Free Zone, Dubai, United Arab Emirates (“Brandios”, “we”, “us”). NextVibe Tech L.L.C-FZ is the data controller for the personal data described in this policy. You can reach us any time at info@brandios.ai.

Brandios turns one short clip you film of yourself into an ongoing social media presence: we generate videos and posts featuring your digital twin, and — only with your authorization — publish them to your connected social accounts and read how they perform. This policy explains exactly what data that involves, how long we keep it, and how you delete it.

1. Data we collect

Account data — name, email address, phone number (if you add one to your contact lines), password or social sign-in identifier, workspace settings.
Your reference clip and twin data — the short video you record during enrollment, which contains your face and voice. From it we derive your twin: appearance and voice characteristics used to generate videos of you. When you record it, we compare the face and voice reading the three words on screen with the face and voice in the rest of the clip, on the servers that run Brandios, to confirm one person recorded it; the measurements taken for that comparison are discarded as soon as it answers and never stored. We treat this as sensitive (biometric-adjacent) data; see section 5.
Your photos: the photos you add to your twin so the pictures we make can show you. We compare the face in each one with the face in your reference clip, on the servers that run Brandios, to confirm they show the same person; the measurements taken for that comparison are discarded as soon as it answers and never stored. We treat these photos as sensitive data too (see section 5).
Brand profile data — the voice, audience, topics, and preferences you configure, plus content you provide (voice notes, ideas, drafts).
Social platform data— when you connect an account, we receive, at your direction and via each platform’s official API: your basic profile (name, handle, avatar, page/account IDs), OAuth tokens (for LinkedIn and TikTok these stay with bundle.social, which connects both for us; see section 3), your own posts, and engagement metrics on them (reach, likes, comments, shares). Through these connections we access only your own accounts and content. Separately, we study public posts by other people, as described next.
Public posts we study: once a week we collect a sample of public posts on LinkedIn, Instagram, Facebook, TikTok and X about the professions our customers work in, through Apify and the X API. For each post we keep its text and link, when it was posted, its hashtags and how many likes, comments, shares and views it had, the author’s public handle and follower count, and how the post did against the author’s usual posts; for a video, what is said and shown in its first seconds. We use them to learn which kinds of openings work, and the strongest few are shown to our AI as examples of a strong opening, never to be copied. We never contact the authors, and we never sell or share these posts. Each is deleted 120 days after we collected it.
Payment data — handled by our payment processor; we store subscription status and invoices, never full card numbers.
Usage and device data — log data, approximate location from IP, and product analytics used for security and to improve the service.
Support conversations — when you open Help in the app: what you write to us, any file or screenshot you attach, your name, email, account and brand identifiers and your plan, and which app pages you were on. Our support chat runs on Intercom, and if you allow it (see section 12) its messenger stores identifiers in your browser so the conversation stays yours across visits: a session cookie that lasts a week, a device identifier that lasts about nine months and is extended each time you visit, and an anonymous id that does not expire on its own. Signing out of Brandios clears the session.
Error reports and screen recordings — when something goes wrong, a technical report of the error (what failed, where in our code, and your account ID). In the Brandios web app we also record how pages are used (page layout, clicks, scrolling, and navigation) so we can see what led to an error. These recordings mask all text you read or type and block all pictures and videos, so they never show your content, your face, or your voice.
Waitlist: if you join the waitlist on brandios.ai and confirm your email address, that address, the campaign tags of the ad or link that brought you to the page (if it had any) and, if you answer them, what you do, where you post most and what stops you posting more. We also keep when you confirmed, and when we sent you our follow-up email. When Brandios opens we add the personal discount code we email you. If you ask to join but do not confirm, we keep your address and those campaign tags, marked unconfirmed, until Brandios opens (see section 6).
Emails and calls with us: if you reply to one of our emails, we keep your reply, and if you book a call with us (our emails to the waitlist and to founding members offer one), your booking (your name, email address, time zone, the time you pick and anything you write when you book) and any notes we make from the call.
Visits to this website: our site analytics, Opinly, counts each visit to brandios.ai and the page, search or campaign that brought it, without cookies (see section 12). While the site runs ad tags, Meta and Google see your visit too, unless you turn ad tracking off (section 4).

2. How we use your data

To provide the service: generate your twin videos, write posts in your voice, and schedule content.
To publish content to your connected accounts — only content you have approved or that falls within the approval rules you set.
To run your learning loop: we analyze the performance of your own posts so next week’s plan improves.
To message you for approvals and service updates in a Telegram chat, if you link one.
To email you about your account and your plan: when your free trial is about to end or has ended, when a payment fails, and when your plan stops. These go to the account owner and are part of the service, so they can’t be turned off while you have an account. They carry no advertising.
To bill you, secure the service, find and fix errors, comply with law, and respond to support requests.
To answer you in the Help chat. An AI assistant (Fin) answers first, from our help articles, and tells you it is an AI; it hands the conversation to a person when it cannot help, when you ask for one, or when the question is about billing, your account or your data. A person can always read the conversation.
To email you about the launch and early access, if you joined the waitlist: first an email with a link to confirm your address (and a new one each time you ask for it) and, if you have not confirmed a day later, one reminder with the same link; then, once you confirm, one email a day later from our founder (with a few optional questions about you, if you have not answered them yet, and the offer of a short call), the day Brandios opens, and a few updates before. Every email after you confirm has an unsubscribe link.
To read and answer your replies to our emails, and to hold the calls you book with us (booked through Calendly, held on Google Meet). We never record calls.
To see which of our ads bring people to this website and who joins the waitlist from them, and to show our ads to people who have visited it (section 4). Ad tracking is on unless you turn it off; visitors from the EEA and the UK are asked first (section 12).
To email you the invite to the private early-supporter group on Telegram, if you buy a plan on our early-access page. You pay on Stripe’s page, not ours. Stripe sends this website the details of every completed checkout, including your email address, name and billing address, and the website then asks Stripe which discount your plan carries. When Stripe sends you back to our thank-you page, the website asks Stripe whether that checkout was paid, and how much before tax, to show the right page. It stores none of it: when your plan carries the early-supporter discount, it uses your email address only to send the invite, and otherwise it drops the details. If a step fails, our server log notes your plan’s Stripe reference (never your name, email or address) so we can put it right. Joining the group is up to you, on Telegram.
To set up your Brandios account, if you buy a plan on our early-access page. Stripe also sends the Brandios app the completed checkout. The app keeps the email address you paid with, next to your plan’s Stripe reference, asks our sign-in provider Clerk to make an invite for that address, and emails you its link to make your account (Clerk emails it instead if our own email service is switched off). If you already have a Brandios account where you verified that address, the plan is added to it instead and no invite is sent; if that account already pays for a plan, we cancel and refund the new one. See section 6 for how long the app keeps the address.

We do not sell, license, or purchase personal data, we do not share it with data brokers, and we do not use data received from any connected platform for advertising, surveillance, eligibility determinations (such as housing, employment, insurance, or credit), or to discriminate against anyone. Legal bases where GDPR or similar laws apply: performance of our contract with you, your consent (twin enrollment, chat messages, marketing, and ad tracking for visitors from the EEA and the UK), and legitimate interests (security, product analytics, error monitoring, measuring and showing our ads everywhere else, and answering your messages and holding the calls you ask us for).

3. Platform-specific commitments

Brandios uses the official APIs of the platforms below. LinkedIn and TikTok are reached through bundle.social, a publishing service that connects them for us with its own approved apps; see their paragraphs. For every platform: we access only the data needed for the features you use, we use it only to provide those features to you, we never sell or transfer it to third parties (including data brokers or ad networks), and we delete it when you disconnect the platform, when you delete your Brandios account, or when it is no longer needed — whichever comes first. For LinkedIn and TikTok, section 6 says what bundle.social still keeps after that. Your learning loop runs on your own accounts only: data from your accounts is never used to profile, train models for, or otherwise benefit any other customer, and we never use platform data to infer sensitive characteristics about anyone (such as health, political views, religion, ethnicity, or sexual orientation).

Meta (Facebook & Instagram)

We receive your Page / professional account identifiers, tokens, your posts, and their insights via Meta’s Graph API, and we publish content to your accounts at your direction. Our use of Meta Platform Data follows the Meta Platform Terms and Developer Policies. You can request deletion at any time — see Data deletion; disconnecting Brandios from your Facebook or Instagram settings also triggers deletion of the related platform data.

You connect LinkedIn through bundle.social (BUNDLE Sp. z o.o., Warsaw, Poland), which acts for us: the permission you grant on LinkedIn goes to its app, and it keeps the sign-in LinkedIn gives it, so Brandios never holds your LinkedIn token. Through it we access your profile identifiers and the Pages you manage, publish the posts you approve to your profile or to the Page you choose, and read their engagement, in line with LinkedIn’s API Terms of Use. We delete the LinkedIn member data we hold on request, when you disconnect LinkedIn, or when no longer required. Disconnecting also has bundle.social stop using your account; section 6 says what it keeps. LinkedIn is not responsible for Brandios.

X (Twitter)

We publish posts you approve and read your own posts and engagement via the X API, under the X Developer Agreement & Policy. If you delete a post on X, we delete our stored copy within 24 hours. We do not match X data with other data sources to build profiles, and we do not use X data off-platform beyond providing the service to you. We also read public posts on X about our customers’ professions through the X API, as section 1 describes, and keep them no longer than 120 days.

TikTok

You connect TikTok through bundle.social too: the permission you grant on TikTok goes to its app, which TikTok has audited for posting, and it keeps the sign-in, so Brandios never holds your TikTok token. Through it we publish the videos and photo posts you approve to your TikTok account, to Everyone unless you choose another audience for a post (or to Followers where TikTok does not allow Everyone on your account), with the comment, Duet and Stitch settings you choose, or send a post to your TikTok inbox as a draft to finish in the TikTok app when you ask for that, and we read your own posts’ metrics. A post carries TikTok’s AI-generated content label when you turn the label on for it. Disconnecting TikTok has bundle.social stop using your account; section 6 says what it keeps.

Google

You can sign in to Brandios with Google. Brandios’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. You can revoke Brandios’ access at any time in your Google security settings.

Chat messages

Approval messages and service updates go to a Telegram chat only if you link one. Sending STOP in the chat stops every message we send there, and START turns them back on; you can also unlink the chat in settings, or email us. WhatsApp is not available yet. If we add it, we will message you there only if you opt in, message and data rates may apply, and WhatsApp is a Meta service with its own privacy policy.

Only service providers (processors) acting under contract for us, and only what each needs; the exceptions are Meta and Google for our ads, which you can turn off, and, for a call you book with us, Calendly’s booking page and Google, all at the end of this section. Each provider is bound to protect your data at least as strictly as this policy. We may also disclose data if the law requires it, or as part of a merger or acquisition in which the recipient honors this policy.

These providers receive your reference clip, your voiceprint, or media derived from them, the sensitive data described in section 5: Segmind (renders your twin videos), MiniMax (cloned your voice and spoke your narrations in it until 17 October 2026, and holds a clone made before then until it is deleted, at the latest when you delete the twin or your account), Munsit (did the same for Arabic until 17 October 2026, from a short cut of your recording that was deleted straight after), Fish Audio (speaks your narrations, and each line your twin says on camera in Arabic, in your voice: it receives your enrollment recording and its transcript with each request, and keeps neither once the request is done, holds no voice model of you and does not train its models on your voice. It also reads a script aloud in an English presenter voice we designed, from the script’s text, with no recording of you; it does not say how long it keeps that script. Its company address is in the United States, and it does not yet say where it processes the audio), ElevenLabs (creates the music and sound effects in your videos and, while Fish Audio speaks for you, transcribes your enrollment recording to cut out its pauses and filler words, and transcribes every take of a narration or line spoken in your voice to check that take; it keeps none of that audio once the transcript is done and does not train its models on your voice. It also transcribes your recording, its room noise removed, to time its sentences for training your voice model (keeping none of that audio once the transcript is done), and reads aloud a script written in Emirati, Gulf, Saudi or Levantine Arabic in an Arabic presenter voice we designed, from the script’s text, with no recording of you. It does not train its models on those scripts, and does not say how long it keeps them), Modal (runs our voice changer for the presenter voices: it receives your enrollment recording to remove its room noise; that cleaned recording and its transcript, to train a voice model of you that we keep in our own storage; and, for each presenter read, that model and your cleaned recording, to turn the read into your voice. It fetches each file through a link that expires and keeps none of the files once the job is done; it keeps each job’s request, which holds your transcript’s words, for up to 7 days, encrypted), OpenAI (writes and analyzes content, generates images, and transcribes audio, including your enrollment recording), WaveSpeed (removes the background from a twin video of you when our main service for that cannot, and animates listing photographs for a property tour), Cloudflare (stores your media and the reference files your videos are rendered from), bundle.social (publishes your posts and twin videos to your LinkedIn and TikTok accounts and keeps your sign-in to both; based in Poland, it keeps its database in Germany and stores the media it publishes, and its database backups, in the United States; see section 3), Render (runs the Brandios servers), and Telegram (delivers drafts and twin videos for approval and carries your replies, only if you link a chat).

Our remaining providers never receive your face or voice, unless you email us a photo, video or voice note yourself: Neon (application database), Clerk (sign-up and sign-in, and the invite to make your account when you buy a plan on the early-access page), Stripe (payments and billing, and the waitlist’s discount codes, each kept with the reference number of your place on the list, never your email), Vercel (web app hosting), Novu (notifications about your account, in the app and by email), Apify (collects publicly available social data for the profiles you identify as yours or add as inspiration, and the public posts we study, section 1), Firecrawl (fetches web pages and runs web searches for topic context), Mapbox (draws the map in a project promo from a listing’s coordinates), Pexels (licensed stock footage of a city for a market video, licensed photos shown with you in a twin video and on its explainer cards, short licensed clips cut in between your sentences in a twin video, and the photos and clips a narrated twin video shows over your voice; it receives only a city’s name or a few search words written from the video’s script), our own Real Estate Lab (answers with market figures for the areas you follow), Sentry (error reports and the masked screen recordings described in section 1, stored in the European Union), Better Stack (server logs), Resend (sends our emails to you, keeps the waitlist and sends its emails and the early-supporter group invite, and delivers the messages you send through the contact form on brandios.ai to our inbox), Microsoft (Microsoft 365 holds our inbox: everything you email us, including the contact form’s messages, your replies to our emails and anything you attach), Calendly (books the calls you ask us for: your name, email address, time zone, the time you pick and anything you write when you book; stored in the United States), Opinly (counts visits to brandios.ai, the page, search or campaign that brought each one, and the buttons and links pressed; when you type your email address into the contact form it receives that too, as soon as you leave the field, so we can tell which visit a message came from. It does not read the waitlist form), and Intercom (runs the Help chat in the app, our help articles, and the Fin assistant that answers first; stored in the United States).

While we run ads, this website uses Meta’s and Google’s ad tags, unless you turn ad tracking off; visitors from the EEA and the UK are asked first (section 12). While ad tracking is on, Meta and Google receive your visit straight from your browser: the pages you open, your browser and device, your IP address, whether you asked to join the waitlist and confirmed your place, and, if you buy a plan on the early-access page, that you did, what it cost before tax, and the checkout’s Stripe reference. When you ask to join the waitlist, and again when you confirm, our server also tells Meta itself, so a sign-up is counted even where its tag is blocked: it sends your email address in hashed form (scrambled one way, which Meta matches against the addresses it already holds), your IP address and browser, the page, and the identifiers Meta’s tag and our ads’ links give your browser. Google’s tag does not receive your email address. For this they are not our processors: each uses what it receives under its own terms and privacy policy, including to measure and show ads.

A call you book with us is held on Google Meet, and the booking goes into our Google Calendar. Google receives your name and email address, the time of the call, anything you write when you book, and the call itself as it happens (your picture and voice, if your camera and microphone are on). For this Google is not our processor: it handles what it receives under its own terms and privacy policy. We never record calls. You book the call on Calendly’s own booking page, which also sees your visit there, such as your IP address and browser, and handles that under its own privacy policy.

The social networks you connect (Meta, LinkedIn, X, TikTok, Google) are not in this list: they are not processing data on our behalf — you direct us to publish to and read from your own accounts there, and each handles your data under its own terms. See section 3.

5. Your face, voice, and twin

We create your twin only after your explicit consent during enrollment, and only from a clip of you. Photos can be added to a twin only after its clip, and only when they show the same face as the clip. Creating a twin of someone else requires their documented consent and is otherwise prohibited.
Your reference clip and derived twin model are used solely to generate content you direct — never to train models for anyone else, and never sold, leased, or traded.
Since 20 October 2026, for your twin’s recording, including one made before that date, we also keep a noise-removed copy of it and, once it is trained, a voice model made from it, whether or not you pick a presenter voice, plus any samples you play with Hear it, in our own private storage, used only to make a presenter’s read sound like you. All of them are deleted when you record your twin again, remove your clip, delete your twin or delete your account.
Deleting your twin (or your account) deletes the reference clip, its photos and every derived model, within 30 days of account closure at the latest. In any event we destroy this data no later than three years after your last interaction with Brandios, and sooner once it is no longer needed for the purpose you consented to.
Where the law requires it (for example the EU AI Act), AI-generated videos of your twin are disclosed as artificially generated.

6. Retention

Platform data (posts, metrics, tokens): deleted when you disconnect the platform or delete your account; refreshed copies are kept only as long as features need them.
What bundle.social holds for you (your LinkedIn and TikTok sign-ins, the posts it published, the media it fetched for them and their metrics): when you disconnect an account, bundle.social stops using it. When you delete your Brandios account, bundle.social also removes your accounts from its service, cancels any post still scheduled there and deletes your profile pictures. It keeps the rest as a deleted copy, with your sign-ins encrypted, and does not use that copy to act on your accounts except for security or legal reasons. For now it erases that copy only when Brandios closes its own account with bundle.social; write to info@brandios.ai and we will ask bundle.social to erase yours sooner.
Reference clip, photos & twin model: per section 5.
Public posts we study (section 1): deleted 120 days after we collected them, with the examples kept from them.
Account and billing records: for the life of the account plus the period required by tax and commercial law.
Logs and analytics: short, rolling windows.
Changes our team makes by hand (credits given, the end of a trial moved, a refund decided, a ban added or lifted): a record of who made each change, when and why. A record about your account is kept while your account exists and deleted with it. A ban on an IP address keeps that address in its record after the ban is lifted, with no end date, so we can see what was blocked before.
Notices we send you (in the app, in chat and by email): our record of each is kept while your account exists and deleted with it.
Error reports and screen recordings: up to 90 days, then deleted automatically.
Support conversations: kept while your account exists, so we can see what you already asked us; deleted when you delete your account — see Data deletion.
Messages sent through the contact form on this website, and your replies to our emails: kept in our inbox while we are dealing with them and for up to two years after, so we remember what was asked. Ask us at info@brandios.ai and we delete the exchange sooner.
Calls you book with us: never recorded. Your booking stays in Calendly and in our calendar until our yearly clean-up after it is two years old, so at most three years; any notes we make stay in our email for up to two years. Ask us and we delete them sooner.
The waitlist: nothing is kept on the list until you confirm your email address. If you never do, we keep your address and the campaign tags that brought you on a separate list, marked unconfirmed, which never receives our launch emails; we send it the one reminder, and delete it when Brandios opens. The confirmation email and the reminder stay in our mail provider’s record of sent emails. Once you confirm, your address, the campaign tags that brought you, your answers and your discount code are kept until you ask us to delete them. Unsubscribing stops the emails at once; to come off the list entirely, write to info@brandios.ai. The code stays in Stripe with only that reference number, and the emails we sent you after you confirmed (the follow-up and the one with your code) stay in our mail provider’s record of sent emails.
The early-supporter invite: this website stores nothing from your checkout; if a step fails, your plan’s Stripe reference is in our server log for its short, rolling window, and the invite email stays in our mail provider’s record of sent emails.
A plan bought on the early-access page: the Brandios app keeps the email address you paid with until the plan is on your Brandios account. If it never gets there, the app keeps the address until the plan ends or the account it was bought for is deleted. While the app works on the purchase, the address is also in our job queue’s record of each step, for up to 7 days after that step; Clerk keeps its own record of the invite, and the email with its link stays in our mail provider’s record of sent emails. The record of the purchase itself (the plan and its Stripe references, without your address) is deleted with your account once the plan is on it; otherwise it is kept as our record of the sale.

7. Data deletion — how to delete your data

This section doubles as our deletion instructions for all connected platforms:

In the app: Settings → General → Your data → Delete account deletes your account, twin, reference clip, and all stored platform data. It also deletes your support conversations: we remove your contact from Intercom, which removes every conversation with it (Intercom can restore them for 7 days, then destroys them). And at bundle.social it removes your LinkedIn and TikTok accounts, cancels any post still scheduled there and deletes your profile pictures; what bundle.social still keeps, and how to have it erased, is in section 6. Posts already live on LinkedIn or TikTok stay there until you delete them there.
Per platform: disconnect a platform in Settings → Accounts (or revoke Brandios from the platform’s own app settings — e.g. Facebook/Instagram “Apps and Websites”, Google security settings). We then delete the data received from that platform. For LinkedIn and TikTok, the permission you granted belongs to bundle.social’s app: disconnecting stops its use, and removing that app in LinkedIn’s or TikTok’s own settings withdraws the permission itself.
By email: send a deletion request to info@brandios.ai from your account email. We confirm completion within 30 days.

8. Your rights

Depending on where you live (including the EEA/UK under GDPR, California under CCPA/CPRA, and the UAE under the Personal Data Protection Law), you may have the right to access, correct, delete, restrict or object to processing, receive a portable copy, withdraw consent at any time, and complain to your supervisory authority. We do not sell personal information as defined by the CCPA. We do not “share” it either, with one exception: what Meta and Google receive for our ads on this website (section 4) may count as “sharing” for cross-context behavioral advertising under the CCPA. You can opt out: while the site runs ad tags, Ad tracking at the bottom of every page turns it off, and a Global Privacy Control signal from your browser keeps it off unless you turn it on there yourself. We never discriminate against you for exercising your rights. Brandios does not make automated decisions about you that produce legal or similarly significant effects. Exercise any right via info@brandios.ai.

9. International transfers

We operate from Dubai, UAE, and use processors in other countries. Where data moves across borders from regions that require it, we rely on appropriate safeguards such as standard contractual clauses.

10. Security

Data is encrypted in transit, access is scoped and logged, OAuth tokens are stored encrypted, and twins can only ever be triggered from their owner’s account. No system is perfectly secure; if a breach affects you, we will notify you and the relevant authorities as the law requires.

11. Children

Brandios is for adults building a professional presence. It is not directed at anyone under 18, and we do not knowingly process children’s data.

12. Cookies and browser storage

The app uses no advertising cookies. This website uses them while it runs ad tags, unless you turn ad tracking off; visitors from the EEA and the UK are asked first. This section names every item, because a short list is worth more than a banner that says “we value your privacy”.

This website (brandios.ai)

Apart from the ad tags below, it sets no cookies. It stores your light or dark choice under brandios-theme, written when you press the theme button, and your ad-tracking choice under brandios-ad-consent, if you make one; both stay on your device until you clear them or your browser does (Safari, for one, clears them after a week without a visit, and the site then starts again from its default). To know whether to ask you first, it checks which country your connection comes from, and keeps nothing of it. When you open a link from one of our waitlist emails (to confirm your place, answer our questions or unsubscribe), it is kept with that tab under brandios-waitlist-link, in the tab’s own storage, which your browser deletes with the tab. If ad tracking is on and you buy a plan, the thank-you page notes under brandios-purchase-reportedfollowed by your checkout’s Stripe reference, in the same tab storage, that it told the ad tags about the purchase, so a reload does not count it twice. Our site analytics, Opinly, keeps a random visitor id under _opinly_anon, the campaign that brought you under _opinly_utm and a note that your first visit was counted under _opinly_first_visit_sent in your browser’s storage, and _opinly_session for the open tab. If you type your email address into the contact form, Opinly also keeps it under opinly_identified_email. None of these is a cookie, and none follows you to other websites. The fonts are served from this domain, so no font provider sees your visit. The contact form and the waitlist post to our own server.

This website: ad tags, unless you turn them off

While we run ads, the site uses Meta’s and Google’s ad tags. Visitors from the EEA and the UK are asked on their first visit, and nothing of theirs loads before they answer; for everyone else they are on unless you turn them off. While they are on:

Meta Pixel sets _fbp, an identifier for your browser, and _fbc (90 days) when you arrive from one of our ads on Facebook or Instagram.
Google’s tag sets _gcl_au (90 days), _ga and _ga_ followed by an id (up to 400 days), _gcl_aw (90 days) when you arrive from one of our Google ads, and stores _gcl_ls in your browser’s storage.
Meta and Google can also set cookies on their own domains, such as fr on facebook.com, and IDE and GCL_AW_P on doubleclick.net. Those are theirs, under their own policies.

Turn ad tracking off or on any time under Ad tracking, at the bottom of every page while the site runs ad tags. Turning it off removes the items above from this website and stops our server telling Meta about a waitlist sign-up you start in that browser (section 4). Our server tells Meta of your confirmation only if ad tracking was on where you asked to join, and the browser you confirm in has not turned it off and is not still waiting for your answer. While ad tracking is on in the browser you confirm in, Meta’s tag there reports it too. The cookies on Meta’s and Google’s own domains are cleared in your browser’s settings. If your browser sends a Global Privacy Control signal, ad tracking stays off unless you turn it on there yourself.

The app (app.brandios.ai): needed to work

These carry no choice, because the app cannot run without them:

Signing in: our sign-in provider Clerk sets __session, __client_uat and __clerk_db_jwt, plus short-lived cookies during a sign-in, and keeps its configuration under __clerk_environment. Without them you cannot stay signed in.
Blocking bots: Cloudflare sets __cf_bm and _cfuvid on Clerk’s own domain when it screens a sign-in request.
What you did in the app: your unfinished brand setup and the step you reached, a post you are writing in your own words until you use it, the last kind of post you added, the first-week pace you chose, whether the one-off sample and the trial-ended note have been shown, which suggestions you dismissed, and a two-minute marker while a follower count is being read. These stay on your device and are never sent anywhere.
The notification bell: Novu keeps its connection and appearance state on your device.

The app: only if you say yes

The app asks you once, on your first signed-in page, and stores the answer on that device. You can accept both, refuse both, or allow one and not the other; nothing here is switched on before you answer, and until you do, neither of these runs:

The help chat: Intercom stores three identifiers so a conversation you start can continue when you come back. Say no and the chat is not loaded at all; you can still reach us at brandios.ai/contact.
Screen recordings of errors: while a recording is being held in memory (section 1), Sentry keeps a note of it in the tab’s storage, which the tab discards when you close it.

Change your mind any time in the app under Settings, General, Your data. You can also refuse or delete all of it in your browser’s own settings; the sign-in cookies above are the ones the app stops working without.

13. Changes to this policy

We will post updates here and, for material changes, notify you in the app or by email before they take effect.

14. Contact

NextVibe Tech L.L.C-FZ, Meydan Grandstand, 6th Floor, Meydan Road, Nad Al Sheba, Dubai, United Arab Emirates (Meydan Free Zone trade licence 2420457.01) · info@brandios.ai