Ubli Privacy Policy

Last updated: November 9, 2026 Version: 1.4-en

About this English version. This English version corresponds to version 1.4 of the Ubli Privacy Policy in Portuguese (Política de Privacidade). If the two versions conflict, the Portuguese version prevails. Sections and items marked (US addition) were written for customers and users in the United States and have no equivalent in the Portuguese text. All other sections keep the same numbers and order as the Portuguese version, so both can be compared.


1. Introduction

Ubli ("we", "us", "our" or the "Platform") is committed to protecting the privacy and personal data of its users ("you" or "User").

Ubli is an omnichannel customer service platform that brings together, in one place, conversations from WhatsApp, Instagram Direct, Facebook Messenger, Telegram, email and website chat. It is sold as two independent products, Ubli CRM and Ubli API, and this Policy applies to both.

The Platform is operated by Vipserver Serviços de Hospedagem na Internet Ltda, a Brazilian company registered under CNPJ (Brazilian company tax ID) 37.669.411/0001-84, headquartered in Limeira, São Paulo, Brazil, as identified in the Terms of Service.

This Policy describes how we collect, use, store, share and protect personal information when you use either product. We try to describe what the Platform actually does, including the points we are still improving.

1.1 Legal Framework

Ubli is a Brazilian company, and its processing of personal data is governed by Brazilian law. This Policy complies with:

  • LGPD: Brazil's General Data Protection Law (Lei Geral de Proteção de Dados, Law No. 13,709/2018)
  • Brazilian Internet Civil Framework (Marco Civil da Internet): Law No. 12,965/2014
  • Brazilian Consumer Protection Code (Código de Defesa do Consumidor): Law No. 8,078/1990

Section 16 adds information required or recommended by the privacy laws of some US states.

1.2 Processing Agents: when we are the Controller and when we are the Processor

The LGPD defines each party's role by what it actually does, not by what the parties agree to call themselves: the Controller is whoever makes decisions about the processing; the Processor is whoever processes data on the Controller's behalf (LGPD art. 5, VI and VII). At Ubli there are two different situations, and it is important to know which one applies to you.

(a) Data of the Customer and of the account users: Ubli is the CONTROLLER

This is the data of whoever subscribes to the Platform: name, email, phone number, CPF (Brazilian individual taxpayer number) or CNPJ, billing data and access logs. We decide how this data is processed, and this Policy describes that processing.

(b) Data of the Customer's contacts: the CUSTOMER is the Controller and Ubli is the PROCESSOR

This is all the content the Customer brings into or generates inside the Platform: the Customer's contacts, the messages exchanged, media, notes, custom fields and service history.

The Customer decides which contacts are added, for what purpose and under which legal basis. Ubli only hosts and processes this data to make the tool work, following the Customer's instructions. In this scenario:

  • The Customer is responsible for telling data subjects what it collects and why, maintaining its own legal basis and privacy policy, and handling requests for access, correction and deletion
  • Ubli is responsible for processing this data only to provide the contracted service, keeping it secure, not using it for its own purposes, and giving the Customer technical support when the Customer needs to respond to a data subject

If you are a contact of a business that uses Ubli and you want to exercise your rights over your data, your request should be sent to that business, which is the Controller. If you contact us, we will forward your request and support the response, but the decision belongs to that business.

Being a Processor does not mean having no responsibility. Under LGPD art. 42, § 1, I, the Processor is jointly liable when it breaches the obligations of the law or fails to follow the Controller's lawful instructions. Ubli is responsible for the security and correct processing of what it hosts; the Customer is responsible for what it collects and why.

1.3 Customers Served by a Partner

Some Customers subscribe to Ubli through an authorized partner (reseller), who may offer the Platform under the partner's own brand and web address. In this case, the partner provides service and support to the Customer, and therefore has access to:

  • The Customer's account registration data (company name, users' names, emails and phone numbers, plan and subscription status)
  • Technical account information: connection status, message delivery failure logs, activity times and the indication that messages were exchanged
  • Account settings, such as service flows and the AI knowledge base, to provide support and adjustments
  • Help requests the Customer sends through the Platform's support button, which go to the partner

The partner does not have access to the content of the Customer's conversations with its contacts: texts, audio, images, documents and other media. The partner only sees that messages existed, not what was said.

Marketing communications and subscription notices for a Customer served by a partner may be sent from the partner's own email and WhatsApp.

Data Protection Officer (DPO, called "Encarregado" under the LGPD) contact:


2. Data We Collect

2.1 Data You Provide

2.1.1 When You Register an Account

We collect the following information when you create an account:

  • Full name
  • Email address
  • Mobile phone number (also used for the login verification code)
  • Company name
  • CPF or CNPJ (required to subscribe to paid plans and to process payments)
  • Password (stored irreversibly, using bcrypt)
  • Date and time of registration
  • Record of your acceptance of the Terms of Service and of this Policy, including the version accepted

Legal basis: Performance of a contract (LGPD art. 7, V)

2.1.2 Payment Data

When you subscribe to a paid plan, we collect:

  • CPF or CNPJ
  • Payment method chosen (PIX, Brazil's instant payment system; card; or boleto, a Brazilian bank payment slip)
  • Transaction data from Mercado Pago: payment ID, status, amount paid, date and method used

Important: Sensitive financial data (card number, bank details) is processed directly by Mercado Pago. Ubli does not store or have access to this information.

Legal basis: Performance of a contract and compliance with a legal obligation (LGPD art. 7, V and II)

2.1.3 How You Found Us

We record the path you took to reach us: the landing page, the referring website, the campaign parameters in the link (for example, utm_source) and, when applicable, the partner who referred you.

Purpose: to know which channels bring us customers and to credit the referral to the correct partner.

Legal basis: Legitimate interest (LGPD art. 7, IX)


2.2 Data Collected through Meta Platforms (Instagram and Facebook)

When you connect your Instagram Business account or Facebook Page to our CRM, we collect data through the Meta Graph API, in compliance with the Meta Platform Policy and Meta's Terms of Service.

2.2.1 Instagram and Facebook Profile Data

When you authorize the integration through OAuth, we collect:

  • Instagram username (@username)
  • Profile display name
  • Profile picture (public URL)
  • Instagram Business account ID
  • Name and ID of the linked Facebook Page
  • Access token (stored encrypted)

Purpose: to identify the connected account, display information in the CRM dashboard and allow messages to be sent and received.

Legal basis: Performance of a contract and consent (LGPD art. 7, I and V)

2.2.2 Instagram Direct and Facebook Messenger Messages

When messages are received or sent through Instagram Direct or Facebook Messenger, we collect:

  • Unique message ID (generated by Meta)
  • Sender and recipient IDs
  • Message content (text)
  • Attachments (images, videos, audio, stickers, when sent)
  • Date and time of the message
  • Direction (incoming or outgoing)
  • Delivery status

How we use this data:

  1. Receiving: messages arrive in the CRM through Meta's notifications (webhooks) and appear in the unified inbox.
  2. Replying: agents reply through the CRM, and the reply is sent to the contact through the Meta Graph API.
  3. History: messages are kept to maintain the service history, for the period in section 5.2.

What we do NOT do with Instagram and Facebook data:

  • We do NOT use messages for advertising or marketing
  • We do NOT sell or share message content with third parties
  • We do NOT use messages to train artificial intelligence models
  • We do NOT transfer this data to data brokers
  • We do NOT use Meta data to build user profiles for advertising purposes

Legal basis: Performance of a contract and consent (LGPD art. 7, I and V)

2.2.3 Meta Notifications (webhooks)

To receive messages in real time, Meta sends notifications to an address exclusive to the Platform, protected by HTTPS and by a verification token generated for each company.

Legal basis: Performance of a contract (LGPD art. 7, V)


2.3 Data Collected When You Use the Platform

2.3.1 Connection Data (WhatsApp and Telegram)

When you connect a WhatsApp number or a Telegram account:

  • Connected phone number
  • Connection name (set by you)
  • Connection type (WhatsApp via QR Code, Official WhatsApp API or Telegram)
  • Connection status and date and time of connections
  • Session credentials, kept on the server with restricted access, needed to keep the number connected
  • Temporary QR Code, generated only at the moment of connection

With a QR Code connection, the Platform does not import the conversation history from before the connection. Group messages only enter the Platform if the Customer turns on that option for the connection.

Legal basis: Performance of a contract (LGPD art. 7, V)

2.3.2 Messages and Media

For the Platform to work (inbox, history, search, flows, campaigns and reports), we store the content of the messages received and sent through the Customer's connections, together with the technical data of each one:

  • Content: text, images, videos, documents and audio
  • Unique message ID, sender and recipient
  • Direction (incoming or outgoing), date and time
  • Delivery status (sent, delivered, read, failed)
  • Message type

Media files are kept in our own storage, on the same server, with encryption at rest turned on. Each file is accessed through a unique, hard-to-guess address that does not require login: we recommend not sharing these addresses outside the Platform.

This data belongs to the Customer, who is the Controller (section 1.2), and is kept for the periods in section 5.2.

Legal basis: Performance of a contract (LGPD art. 7, V)

2.3.3 System Logs

For security, auditing and troubleshooting, we record:

  • Access logs: successful and failed logins, logouts, password changes and recovery, lockouts after repeated attempts
  • Logs of sensitive actions: data exports, deletion requests, permission changes, acceptance of terms
  • Technical logs: API requests, webhook deliveries, payment synchronization, sending of notifications
  • IP address and browser or device used, in access logs and sensitive action logs

Retention periods are in section 5.2.

Legal basis: Legitimate interest and compliance with a legal obligation (LGPD art. 7, IX and II)

2.3.4 Usage Data

To improve our services, we use usage statistics, such as number of messages, number of connections, use of features and performance metrics. In internal analyses and reports, this data is aggregated and does not identify individuals.

Legal basis: Legitimate interest (LGPD art. 7, IX)


2.4 Third-Party Platforms Used by Ubli

2.4.1 WhatsApp and Telegram

  • For QR Code connections, Ubli uses the Baileys (WhatsApp) and GramJS (Telegram) libraries. WhatsApp QR Code connections have been closed to new connections since October 29, 2026, and existing ones will be shut down by November 30, 2026, as set out in the Terms of Service (clause 11.4)
  • With the Official WhatsApp API, messages go through Meta's cloud platform (WhatsApp Cloud API)
  • In all cases, messages travel through WhatsApp's or Telegram's servers, which follow their own privacy policies, over which Ubli has no control

Recommendation: read the privacy policies of WhatsApp and Telegram.

2.4.2 Meta Platform (Instagram and Facebook)

  • Ubli uses the Meta Graph API to send and receive messages
  • Access is granted by the user through OAuth 2.0 (Facebook login)
  • We use the permissions: instagram_basic, instagram_manage_messages, pages_messaging, pages_manage_metadata, pages_read_engagement
  • The user can revoke access at any time at facebook.com/settings/?tab=business_tools

Recommendation: read the privacy policies of Instagram and Facebook.

2.4.3 Mercado Pago

  • Payments are processed by Mercado Pago
  • Ubli only receives the confirmation and transaction data, never card or bank data

Recommendation: read the Mercado Pago Privacy Policy.


3. How We Use Your Data

3.1 Purposes

3.1.1 Providing the Services

  • Create and manage your account
  • Connect and keep active the WhatsApp, Telegram, Instagram, Facebook and email connections
  • Receive, store, display and send messages and media
  • Run the flows, campaigns and bot rules you configure
  • Send notifications to the addresses (webhooks) you configure

3.1.2 Payments and Billing

  • Process payments for subscriptions and add-ons
  • Issue invoices (notas fiscais, Brazilian tax invoices)
  • Manage renewals
  • Detect and prevent fraud

3.1.3 Communicating with You

We use email and WhatsApp to:

  • Send the login verification code
  • Confirm your registration and guide your first steps during the trial period
  • Notify you about subscription expiration, renewal and payment
  • Notify you about usage limits, maintenance and important changes
  • Respond to your support requests

Customers served by a partner receive marketing notices from the partner's email and WhatsApp (section 1.3).

3.1.4 Security

  • Detect and prevent fraud and abusive use
  • Protect the integrity of the Platform
  • Comply with legal obligations and respond to requests from competent authorities

3.1.5 Improvements

  • Analyze Platform usage on an aggregated basis
  • Fix errors and develop new features

3.2 Artificial Intelligence Features

3.2.1 Customer Service AI (optional, turned on by the Customer)

When the Customer turns on an AI agent to reply to its contacts, the content of the conversations handled by the AI (texts and, when applicable, audio transcriptions and the reading of images and documents) is sent to the AI provider chosen by the Customer: Google (Gemini), OpenAI, DeepSeek, Anthropic or OpenRouter. The Customer may use its own access key for the provider.

  • Audio transcription is done by a service on our own server, without sending audio to third parties
  • We keep a record of the AI's interactions (what it received and replied, and the actions it took) for support and error correction, for the periods in section 5.2
  • If the AI is not turned on, conversation content is not sent to any AI provider
  • Each provider processes data under its own terms. We recommend that the Customer review the terms of the chosen provider

Legal basis: Performance of a contract, according to the Customer's instructions (LGPD art. 7, V)

3.2.2 CRM AI Assistant (help inside the Platform)

The CRM has a help assistant you can open to ask questions about using the Platform. When you use it, your question, the screenshots you attach and the audio you record (transcribed on our server) are sent to the AI provider DeepSeek, which processes the data outside Brazil (section 11).

  • The assistant does not read your conversations with your contacts
  • Avoid including third parties' personal data in your questions and screenshots
  • If you ask for human support through the assistant, the request goes to Ubli's support team or to your partner (section 1.3)

Legal basis: Performance of a contract, at your request (LGPD art. 7, V)

3.3 Marketing and Advertising

Ubli does NOT use your data to:

  • Sell contact lists to third parties
  • Use the content of your conversations (WhatsApp, Instagram, Facebook, Telegram, email or website chat) for any advertising purpose

What we do: we measure the effectiveness of our own ads, in two ways:

  1. In the browser, through tools loaded when you visit (section 8.2): third-party advertising tools record your visit to the website and the creation of your trial account. At registration, this includes the email you provided, transformed with a SHA-256 hash (an irreversible transformation; the readable email is not transmitted), sent to Google to attribute the registration to the correct ad. Hashed data is still personal data under the LGPD and remains subject to all the rights in section 6.
  2. From our server, without third-party cookies: when you reach the website through a Google ad, the link carries a click code (for example, gclid), which we keep in our own attribution cookie (section 8.2). If you create an account, we send Google only that code and the registration date, so Google knows that click turned into a registration. We do not send your name, email, phone number or any other account data.

The legal basis for the server-side sending is Ubli's legitimate interest in measuring the results of its own ads (LGPD art. 7, IX), with the minimum data possible. You may object to this sending at any time by writing to atendimento@ubli.io (section 6.7), and we will stop sending it.

We may send communications about new features and Platform updates. You can ask to stop receiving them at any time.

3.4 Messaging Recipients in the United States (US addition)

When a Customer uses Ubli to send WhatsApp (or other) messages to phone numbers in the United States, the Customer decides who receives those messages and is responsible for obtaining and keeping the recipients' consent as required by the Telephone Consumer Protection Act (TCPA) and similar federal and state laws, as well as by WhatsApp's own policies. This includes honoring opt-out requests. Ubli sends these messages on the Customer's instructions, as described in section 1.2. See also the Terms of Service.


4. Data Sharing

4.1 Who We Share Data With

Ubli does NOT sell personal data. We share data only with the providers and platforms below, to the extent necessary for each purpose:

CompanyServiceDataCountry where data is processed
HostDime BrasilDedicated server that hosts the PlatformAll Platform dataBrazil
Meta PlatformsWhatsApp (QR Code and Official API), Instagram Direct and Facebook MessengerMessages, media, numbers and profilesUnited States and other countries
TelegramTelegram channelChannel messages and mediaOther countries
Mercado PagoPayment processingName, CPF or CNPJ, email and amountBrazil and Latin America
ZohoSending Platform emailsEmail address, name and email contentOutside Brazil
Google (Firebase) and AppleMobile app notificationsContact's name or phone number and the beginning of the received messageUnited States
AI provider chosen by the CustomerCustomer service AI, only when turned on (section 3.2.1)Content of conversations handled by the AIUnited States or China, depending on the provider
DeepSeekCRM AI Assistant, only when you use it (section 3.2.2)Question, screenshots and audio transcriptionChina
Google and OpenAIAd measurement in the browser (section 8.2)Visit and registration events; SHA-256 hashed email (Google only)United States
GoogleServer-side ad measurement (section 3.3)Ad click code and registration dateUnited States
Contracted marketing service providerMonitoring of website and ad performanceThe same measurement events aboveUnited States (Google tools)
Authorized partnerService and support to Customers who subscribed through the partner (section 1.3)The data described in section 1.3Brazil

Transfers outside Brazil are explained in section 11.

4.2 Legal Obligations

We may disclose data when:

  • Required by law or court order
  • Necessary to comply with legal process
  • Necessary to protect the rights, property or safety of Ubli, its users or the public
  • There is an investigation of fraud or illegal activity

4.3 Webhooks and Integrations You Configure

If you configure webhooks, automations or integrations with external systems (for example, n8n or a management system):

  • Data will be sent to the addresses and systems you specified
  • You are responsible for ensuring the security of those destinations
  • Ubli is not responsible for processing carried out by third-party systems you configure

4.4 What We Do NOT Do

Ubli does NOT:

  • Sell personal data
  • Pass data to data brokers
  • Give the content of your conversations to marketing or advertising companies
  • Share data with third parties for their own commercial purposes

5. Storage and Security

5.1 Where We Store Data

  • The Platform runs on a dedicated server contracted from HostDime Brasil, in a data center located in Brazil
  • PostgreSQL for structured data (registration, contacts, messages, logs)
  • Redis for cache and temporary queues
  • Our own file storage for media, on the same server
  • Backups are kept on the server itself and in an external copy, on Ubli equipment located in Brazil, with an encrypted disk and access restricted to the technical lead

Some third-party services used by the Platform process data outside Brazil, as described in section 11.

5.2 How Long We Keep Data

Type of dataRetention period
Registration, contacts, messages, media and AI logsWhile the account is active, and 30 days after it is closed
Connection session credentialsWhile the connection exists
Meta access token (Instagram and Facebook)While the integration is connected; deleted upon disconnection
Technical logs (API, webhooks, notifications)Up to 90 days
Account access logs and sensitive action logs5 years
Payment data5 years after the last transaction
Tax documents issued5 years
BackupsUp to 30 days
Anonymized dataIndefinitely

5.2.1 What Happens When the Account Is Closed

An account is considered closed when it is canceled or when the trial period ends without a subscription. From then on:

  • For 30 days, the data remains stored and the account can be reactivated without loss of history
  • After 30 days, personal data is deleted as described in section 5.2.2
  • Before the account is closed, you can export your data (section 6.4)

Deletion request. You can also request deletion through the Platform itself at any time. The request remains open for 30 days so you can change your mind (you can cancel it during that period), and is only processed after that.

5.2.2 How Deletion Is Done: anonymization, not deletion of the record

Personal data is removed or replaced with markers that do not identify anyone:

  • Users: name, email and phone number anonymized; password invalidated; sessions, trusted devices and verification codes deleted
  • Company: name, email, phone number, CPF or CNPJ, legal name, full address and integration credentials deleted
  • Contacts: name, phone number, email, photo and social network identifiers deleted
  • Messages: content, caption, and sender's name and phone number removed, and media files deleted

Why the record itself is not deleted. Records such as tax invoices, payments, bills, subscriptions and audit logs must be kept by law and depend on a reference to the account to remain intact. For this reason the record remains, with no personal data, only anchoring those records.

What is kept, and why:

Record keptReasonPeriod
Tax invoices issuedTax obligation5 years
Payments, bills and subscriptionsTax and accounting obligation5 years
Access logs and sensitive action logsAccountability (LGPD art. 6, X) and defense in legal proceedings5 years

Backups are replaced within 30 days; after that period, deleted data also no longer exists in them.

Suspension of deletion. If there is a judicial or administrative proceeding or an audit in progress involving the account, deletion is suspended until it ends, under LGPD art. 16, I. You will be notified if this happens.

Deletion is irreversible. Once completed, there is no way to recover contacts, conversations or media.

5.3 Security Measures

5.3.1 Technical Measures

  • Encrypted connection: HTTPS with TLS 1.2 or 1.3 for all communications, with HSTS
  • Passwords: stored irreversibly, using bcrypt
  • Login verification code: sent by WhatsApp, SMS or email; the device can be marked as trusted for 30 days
  • Login session with short expiration and automatic renewal
  • Isolation between companies: each request is limited to the data of the user's company, with an automatic check of this isolation at every system update
  • Access profiles: administrator, agent and viewer, with permissions by area and restriction of conversations by agent, by number and by channel
  • Encrypted credentials: Meta access tokens and integration credentials for management systems and Mercado Pago are stored with AES-256 encryption
  • CRM API keys stored only in hashed form
  • Media files encrypted at rest
  • Lockout after repeated login attempts
  • Daily, encrypted backups

5.3.2 Organizational Measures

  • Restricted technical access: only Ubli's technical lead has access to the server, for maintenance and for support when requested by the Customer
  • Ubli's administrative panel has no access to the content of Customers' conversations
  • Logging of sensitive actions (logins, exports, deletions, permission changes)
  • Security audit of the code and infrastructure in progress since August 2026, in phases

Important: despite these security measures, no system is 100% secure. We recommend that you keep your own copies of any data you consider critical.


6. Your Rights (LGPD)

Under the LGPD, you have the following rights over your personal data. Residents of some US states also have the rights described in section 16.

6.1 Confirmation and Access (Art. 18, I and II)

  • Confirmation that we process your data
  • Access to the personal data we hold about you
  • A copy of your data in a structured format, upon request to the DPO

6.2 Correction (Art. 18, III)

  • Correct incomplete, inaccurate or outdated data
  • Update your registration information directly in the dashboard

6.3 Deletion (Art. 18, VI)

  • Deletion of unnecessary data or data processed in violation of the law
  • Closing your account with deletion of your data, as described in section 5.2

Exceptions: we may keep data when required by law (for example, tax data for 5 years) or when necessary to exercise rights in judicial, administrative or arbitration proceedings.

6.4 Portability (Art. 18, V)

  • Through the dashboard: export of contacts in CSV or Excel and of the conversation list in Excel
  • Upon request to the DPO: a full copy of the conversation history in a structured format
  • Transfer to another provider, when technically feasible

6.5 Information (Art. 18, VII and VIII)

  • Sharing: who we share your data with (section 4)
  • Refusal of consent: the consequences of not giving consent, when applicable

6.6 Withdrawal of Consent (Art. 18, IX)

When processing is based on consent, you can withdraw it at any time. Withdrawal does not affect processing carried out before it. For ad measurement, which does not depend on consent, see the right to object (section 6.7) and section 8.3.

6.7 Objection (Art. 18, § 2)

You may object to processing carried out on the basis of legitimate interest, stating your reason.

6.8 How to Exercise Your Rights

  1. Send an email to: atendimento@ubli.io
  2. Subject: "LGPD Request - [Type of Right]"
  3. Include: full name, registered email, CPF (for identity verification) and a description of your request

Response time: confirmation that we process your data is immediate, in simplified form; the full response is sent within 15 days from your request (LGPD art. 19).

No cost: we do not charge for handling LGPD rights requests.

Customers' contacts: if you are a contact of a business that uses Ubli, see section 1.2.


7. Meta Platform Data (Instagram and Facebook): Deletion and Control

7.1 Disconnecting the Integration

When you disconnect the Instagram or Facebook integration, either in the CRM (Channels page) or by revoking access in your Facebook settings:

  • The access token is deleted immediately
  • The CRM stops receiving new messages from that account
  • Conversations already received remain in the Customer's history, since the Customer is the Controller of that data, and follow the periods in section 5.2

7.2 Data Deletion Request through Meta (Data Deletion)

In compliance with the Meta Platform Policy, data subjects may request deletion of the data we received through the integration:

  1. Through Facebook: by removing the app in Facebook's Apps and Websites settings and requesting deletion of the data. Meta notifies us and the request is processed automatically.
  2. By email: to atendimento@ubli.io, with the subject "Meta Data Deletion".

What is deleted: the identification data received from Meta (username, display name, profile picture and account ID), as well as the access token. Messages exchanged with the business remain in that business's history, without these identifiers, because they belong to the business, which is the Controller (section 1.2). To request deletion of the messages, the data subject should contact the business they talked to.

Time frame: within 30 days of the request.

7.3 Compliance with the Meta Platform

Ubli commits to complying with the Meta Platform Terms and the Meta Platform Data Policy. In particular:

  1. Limited use: Meta data is used exclusively to provide the CRM service (receiving and replying to messages)
  2. No sale of data: we never sell, license or share data obtained through Meta's APIs with third parties for their own purposes
  3. No advertising use: message data is not used to build advertising profiles, for targeting or for remarketing
  4. No surveillance use: data is not used for surveillance, tracking or monitoring of people
  5. Security: access tokens are stored encrypted
  6. Deletion on request: we handle deletion and access revocation requests as described in sections 7.1 and 7.2
  7. Transparency: this policy is public and accessible at any time

8. Cookies and Similar Technologies

8.1 Essential Cookies

  • Authentication: keeps you logged in to the dashboard
  • Preferences: language and interface settings
  • Your earlier refusal: if you refused measurement in the cookie notice that existed until November 9, 2026, that refusal is still respected

Legal basis: Performance of a contract and legitimate interest (LGPD art. 7, V and IX)

The Platform does not work without them, so they do not depend on consent.

8.2 Audience and Ad Measurement

Our website (ubli.io) and the public screens of the CRM (crm.ubli.io: login, registration and password recovery) may load the following third-party tools:

ToolCompanyPurpose
Google Analytics 4GoogleAudience measurement and traffic source
Google AdsGoogleAd conversion measurement
ChatGPT Ads PixelOpenAIAd conversion measurement

One Google Analytics account and one Google Ads account belong to a marketing service provider contracted by Ubli and receive the same measurement events.

These tools are loaded when you visit, without a prior notice, so we can measure where visitors come from and which ads bring registrations. They have no access to the content of your conversations or to your customers' data inside the Platform, and they are not loaded on the internal CRM screens after login.

They are not loaded if you refused measurement in the cookie notice that existed until November 9, 2026, or on our English-language pages when your browser sends the Global Privacy Control signal (section 8.4).

Legal basis: Ubli's legitimate interest in measuring the results of its own ads (LGPD art. 7, IX). You can object at any time (section 6.7) by blocking these cookies in your browser (section 8.3), by turning on Global Privacy Control, or by writing to atendimento@ubli.io.

Our Own Attribution Cookies

Set by us on the .ubli.io domain:

CookieDurationPurpose
ubli_attr90 daysRecords the source of your first visit
ubli_oppref30 daysAd click identifier
ubli_ref90 daysIdentifies the partner who referred you

8.3 Managing Cookies

You can manage cookies in your browser's privacy settings, clearing or blocking non-essential cookies. Blocking third-party cookies stops the measurement described in section 8.2 without affecting your use of the website or the Platform.

  • Chrome: Settings > Privacy > Clear browsing data
  • Firefox: Settings > Privacy > Manage data
  • Safari: Preferences > Privacy > Manage website data

8.4 Do Not Track (US addition)

Some browsers send a "Do Not Track" signal. Because there is no common industry standard for how to respond to it, our website does not change its behavior when it receives that signal. Our English-language pages do honor the Global Privacy Control (GPC) signal: if your browser sends it, we treat it as a refusal and the third-party ad measurement tools described in section 8.2 are not activated. In all other cases, the third-party ad measurement tools described in section 8.2 are loaded when you visit, and you can object to them at any time as described in section 8.2.


9. Children's and Minors' Data

Ubli is not intended for people under 18 years of age.

  • We do not knowingly collect data of people under 18 as users of the Platform
  • If we learn that an account was created by a minor without proper authorization, we will delete the data, notify the legal guardian (if identifiable) and close the account

United States (US addition). Consistent with the rule above, which is stricter, the Platform is not directed to children under 13, and we do not knowingly collect personal information from children under 13, as provided in the US Children's Online Privacy Protection Act (COPPA). If you believe a child under 13 has given us personal information, contact atendimento@ubli.io and we will delete it.

Data of Customers' contacts who may be minors is the responsibility of the Customer, who is the Controller (section 1.2), and must be processed in their best interest, as required by LGPD art. 14.


10. Changes to this Policy

10.1 Updates

Ubli may change this Policy to comply with new laws, implement new features, improve security, or correct and clarify the text.

10.2 Notice of Changes

Significant changes are announced 30 days in advance, by email to your registered address and by a notice in the dashboard. Minor changes (corrections and clarifications) only update the date at the top of the document.

If you do not agree with a change, you can close your account and request deletion of your data, without penalty.

10.3 Version History

  • Version 1.0 (October 28, 2025): initial version
  • Version 1.1 (March 12, 2026): sections on Instagram Direct, Facebook Messenger and compliance with the Meta Platform
  • Version 1.2 (August 12, 2026): Controller and Processor roles, ad measurement tools and how deletion is done
  • Version 1.3 (September 25, 2026): accurate description of message storage; partners; AI features; complete list of companies that receive data and international transfer; 30-day period after the account is closed; cookie notice; response times and incident notice times adjusted to the LGPD and to ANPD regulations
  • Version 1.3-en (November 9, 2026): English version of version 1.3, with additions for the United States (sections 3.4, 8.4, 16 and the notes in sections 1.1, 6, 9 and 11)
  • Version 1.4 and 1.4-en (November 9, 2026): end of the cookie notice; ad measurement in the browser is now based on legitimate interest, with the right to object, and the related international transfer on the contractual safeguards offered by the providers

11. International Data Transfer

The Platform is hosted in Brazil, but some data is transferred outside the country, because the services that make it possible run on servers abroad. The transfers, and the LGPD grounds that allow them, are:

TransferDestinationLegal ground (LGPD art. 33)
WhatsApp, Instagram, Facebook and Telegram messagesMeta (United States and other countries) and TelegramNecessary for the performance of the contract (art. 33, IX, together with art. 7, V)
Mobile app notificationsGoogle (Firebase) and Apple, United StatesNecessary for the performance of the contract (art. 33, IX)
Platform emailsZoho, outside BrazilNecessary for the performance of the contract (art. 33, IX)
Customer service AI, when turned on by the CustomerProvider chosen by the Customer, in the United States or ChinaNecessary for the performance of the contract, according to the Customer's instructions (art. 33, IX)
CRM AI Assistant, when you use itDeepSeek, ChinaNecessary for the performance of the contract, at your request (art. 33, IX)
Ad measurement in the browserGoogle and OpenAI, United StatesSafeguards of compliance with the LGPD offered by the providers in their data processing terms (art. 33, II)
Server-side ad measurement (click code)Google, United StatesTransfer to a country or organization with Google's own contractual safeguards; this point is under legal review

Payment data is processed by Mercado Pago in Brazil and in other Latin American countries.

Users outside Brazil (US addition). If you use Ubli from the United States or any other country outside Brazil, your personal data is transferred to and processed in Brazil, where the Platform is hosted, and is also processed by the providers listed in section 4.1, in the locations shown there and in the table above. Brazilian data protection law may differ from the law of your state or country. The protections described in this Policy apply to your data wherever it is processed.

If we start using new services abroad, this section will be updated before the transfer begins, as described in section 10.


12. LGPD Compliance

12.1 Legal Bases

Type of dataLegal basis (LGPD)Article
Registration dataPerformance of a contractArt. 7, V
Payment dataPerformance of a contract and legal obligationArt. 7, V and II
How you found usLegitimate interestArt. 7, IX
Messages and mediaPerformance of a contractArt. 7, V
Instagram and Facebook messages and profilesPerformance of a contract and consentArt. 7, V and I
Customer service AI and AI AssistantPerformance of a contractArt. 7, V
System logsLegitimate interest and legal obligationArt. 7, IX and II
Aggregated usage dataLegitimate interestArt. 7, IX
Ad measurement in the browserLegitimate interestArt. 7, IX
Server-side ad measurement (click code)Legitimate interestArt. 7, IX

12.2 Processing Agents

Each party's role changes depending on the data being processed. The details are in section 1.2; the table below summarizes them:

Data processedControllerProcessor
Customer's registration, billing and access dataUbliProviders contracted by Ubli
Contacts, messages and media of the Customer's own customersThe CustomerUbli and its sub-processors

Ubli's sub-processors are the companies listed in section 4.1, which process data only to the extent necessary to provide the service.

12.3 Data Protection Officer (DPO)

  • Role: receive complaints and communications from data subjects, provide clarifications, give guidance on data protection and act as the point of contact with the ANPD (Brazil's National Data Protection Authority)
  • Email: atendimento@ubli.io
  • Subject: "Personal Data Protection"

12.4 Data Protection Impact Assessment (RIPD)

Ubli prepares Data Protection Impact Assessments (Relatórios de Impacto à Proteção de Dados Pessoais) when it implements features that process sensitive data, when it significantly changes its processing practices, or when requested by the ANPD.

12.5 Security Incidents

In the event of a security incident that may cause relevant risk or harm to data subjects, Ubli notifies the ANPD and the affected data subjects within 3 business days of becoming aware of the incident, as required by ANPD regulations (Resolution CD/ANPD No. 15/2024).

The notice describes the nature of the incident, the data and data subjects affected, the risks, the measures taken and the measures you should take. Data subjects receive it at their registered email.

When the incident affects data of a Customer's contacts, Ubli, as Processor, notifies the Customer without delay, so that the Customer can meet its obligations as Controller.

12.6 End of Processing

Processing ends when its purpose has been achieved, when the processing period ends (section 5.2), when consent is withdrawn (if applicable) or by order of the ANPD. We keep data after processing ends only in the cases allowed by LGPD art. 16, such as compliance with a legal obligation or Ubli's exclusive use of anonymized data.


13. Questions, Complaints and Contact

13.1 Privacy Questions

13.2 Complaints

If you believe your rights have been violated, please contact us first at atendimento@ubli.io: we will try to resolve the matter directly. If you are not satisfied, you may file a complaint with Brazil's National Data Protection Authority (ANPD):

13.3 Customer Support


14. Glossary

TermDefinition
LGPDBrazil's General Data Protection Law (Lei Geral de Proteção de Dados, Law No. 13,709/2018)
Personal DataInformation related to an identified or identifiable natural person
Data SubjectThe natural person to whom the personal data refers
ControllerWhoever makes decisions about the processing of data (section 1.2)
ProcessorWhoever processes data on the Controller's behalf
Sub-processorA company hired by the Processor to help provide the service
Data Protection Officer (DPO)The person responsible for the company's data protection channel (called "Encarregado" under the LGPD)
ProcessingAny operation performed on data (collection, storage, use, sharing, deletion)
ConsentA free, informed and unambiguous authorization given by the data subject
AnonymizationA process that makes it impossible to identify the data subject
CookiesSmall files stored in the browser
ANPDBrazil's National Data Protection Authority (Autoridade Nacional de Proteção de Dados)
APIApplication Programming Interface
WebhookA notification sent automatically to another system when an event occurs
HashAn irreversible transformation of a piece of data into a code
Meta Graph APIAn interface provided by Meta for integration with Instagram and Facebook
OAuth 2.0An authorization protocol used to grant secure access to third-party accounts
CPF / CNPJBrazilian tax identification numbers for individuals (CPF) and companies (CNPJ)

15. Final Provisions

15.1 Language

This Policy was written in Portuguese (Brazil) and is also available in English at https://ubli.io/en/privacy. In the event of any conflict between the versions, the Portuguese version prevails.

15.2 Acceptance

By creating an account and using Ubli, you state that you have read and understood this Policy, that you are aware of your rights under the LGPD, and that you are over 18 years of age or have authorization from a legal guardian.

15.3 Relationship with the Terms of Service

This Policy supplements Ubli's Terms of Service. In the event of a conflict between the documents, the provision most protective of personal data prevails.

15.4 Effective Date

This Policy took effect on October 28, 2025. Version 1.4 and this English version (1.4-en) were published on November 9, 2026.


16. Notice to California Residents and Residents of Other US States with Privacy Laws (US addition)

This section applies to residents of California and of other US states with consumer privacy laws (for example, laws that give rights to know, access, correct and delete personal information). It supplements the rest of this Policy. The terms "personal information", "sell", "share" and "service provider" have the meanings given by those laws. If a state law gives you rights that are not described here, we will honor them as that law requires.

16.1 Personal Information We Collect

In the last 12 months, we have collected the following categories of personal information. The sections in parentheses describe each item in detail.

CategoryExamples from this Policy
IdentifiersName, email address, phone number, company name, CPF or CNPJ (Brazilian tax ID numbers), IP address, Instagram username and account IDs, Facebook Page name and ID, cookie identifiers, ad click codes such as gclid, SHA-256 hashed email (sections 2.1, 2.2, 2.3.3, 3.3, 8.2)
Customer recordsName, phone number, CPF or CNPJ, and payment transaction data (sections 2.1.1, 2.1.2)
Commercial informationPlan, subscriptions, add-ons purchased, payment method, amounts paid and payment history (sections 2.1.2, 3.1.2)
Internet or other electronic network activityAccess logs, browser or device used, landing page, referring website and campaign parameters, visits and registration events on our website, API requests, webhook deliveries and aggregated usage statistics (sections 2.1.3, 2.3.3, 2.3.4, 8.2)
Audio, electronic and visual informationAudio recordings and screenshots you send to the CRM AI Assistant (section 3.2.2)
Communications content processed on the Customer's behalfMessages, media, contacts, notes and service history that Customers bring into the Platform, and AI interaction logs (sections 1.2, 2.2.2, 2.3.2, 3.2.1). Ubli processes this content as a service provider/processor (section 16.7)
Sensitive personal informationAccount login (email) together with the password, which is stored only in irreversible form; and government-issued tax identification numbers (CPF or CNPJ) (sections 2.1.1, 2.1.2)

We use sensitive personal information only for the purposes described in this Policy, such as providing the service, account security, billing and complying with legal obligations, and not to infer characteristics about you.

16.2 Sources

We collect personal information:

  • Directly from you, when you register, subscribe, configure the Platform, contact support or use the AI Assistant
  • Automatically, from your browser or device when you visit our website or use the Platform (logs and cookies)
  • From Meta, when you connect Instagram or Facebook (section 2.2)
  • From Mercado Pago, about your payments (section 2.1.2)
  • From authorized partners, when a partner referred you (sections 1.3 and 2.1.3)
  • From our Customers, for the content they bring into the Platform (section 1.2)

16.3 Business Purposes

We use personal information for the purposes described in section 3: providing the services, payments and billing, communicating with you, security and fraud prevention, improvements, the AI features you or the Customer turn on, and measuring our own ads. We disclose personal information to the categories of recipients listed in section 4.1 (hosting, messaging platforms, payment processing, email, app notifications, AI providers, ad measurement, our marketing service provider and authorized partners) for those purposes. Retention periods are in section 5.2.

16.4 No Sale of Personal Information

Ubli does not sell personal information for money, and does not give the content of conversations to advertising companies (sections 3.3, 4.1 and 4.4). We do not knowingly sell or share personal information of consumers under 16 years of age.

Ad measurement tools. The third-party advertising tools described in section 8.2 (Google Analytics, Google Ads and the ChatGPT Ads pixel from OpenAI) are used only to measure our own ads. They are loaded when you visit, and you can opt out at any time by turning on Global Privacy Control in your browser (we treat it as an opt-out, section 8.4), by blocking third-party cookies, or by writing to atendimento@ubli.io. You can also ask us to stop the server-side sending of the ad click code described in section 3.3 by writing to atendimento@ubli.io.

16.5 Your Rights

Subject to the conditions and exceptions of the applicable state law, you have the right to:

  • Know what personal information we collect, use and disclose, the categories of sources, the purposes and the categories of recipients
  • Access the specific pieces of personal information we hold about you, including a copy in a portable format (see also section 6.4)
  • Correct inaccurate personal information
  • Delete personal information we collected from you, subject to the legal retention obligations described in sections 5.2 and 6.3
  • Opt out of the use of the ad measurement tools described in section 16.4
  • Not be discriminated against for exercising any of these rights: we will not deny you the service, charge you a different price or provide a different quality of service because you exercised them

16.6 How to Submit a Request

  • Email: atendimento@ubli.io, with the subject "US Privacy Request - [Type of Right]"
  • Deletion: you can also use our data deletion request page at https://ubli.io/exclusao-dados, or request deletion through the Platform (section 5.2.1)
  • Ad measurement tools: turn on Global Privacy Control in your browser, block third-party cookies, or write to atendimento@ubli.io

Verification. To protect your data, we verify your identity before responding. We will ask you to confirm information we already have, for example by writing from your registered email address or confirming details of your account. We use the information you provide for verification only for that purpose. If we cannot verify your identity, we will tell you why.

Authorized agents. You may use an authorized agent to submit a request on your behalf. We will ask the agent for proof of your written permission and may ask you to verify your own identity directly with us, unless the agent holds a valid power of attorney under applicable law.

Response time. We respond within the time frame in section 6.8 and, in any case, within the period required by the applicable state law. If your request is denied, we will explain why and, where the applicable state law provides for it, how you can appeal the decision by replying to our response.

No cost. We do not charge for handling these requests.

16.7 When Ubli Acts as a Service Provider

When Ubli processes messages, media, contacts and other content on behalf of a Customer (section 1.2, item b), Ubli acts as a service provider/processor for that Customer. If you are a contact of a business that uses Ubli and you want to exercise your privacy rights over that content, please send your request to that business. If you contact us, we will forward your request to the business and support it in responding.


Data Protection Officer (DPO) contact: atendimento@ubli.io

Ubli: data protection and privacy first