Skip to content
  • Product
  • Switch
  • Pricing
  • FAQ
  • Blog
  • Download
EN English PT Português (Brasil)
Sign in Try free
Menu
  • Product
  • Switch
  • Pricing
  • FAQ
  • Blog
  • Download
  • Sign in
English Português (Brasil)

Privacy Policy

Last updated: November 9, 2026

This Privacy Policy explains what personal data Bundle collects, why, who we share it with and the choices and rights you have. It covers the Bundle website (bundle.direct), the web app (app.bundle.direct), the desktop apps for macOS, Windows and Linux, and the mobile apps for Android and iOS (together, "Bundle").

1. Who we are

Bundle is operated by BIG SMALL CONSULTORIA EM TECNOLOGIA DA INFORMACAO LTDA, CNPJ 39.930.216/0001-91, Brasília, DF, Brazil, a company organized under the laws of Brazil ("we", "us"). For the account data and service data described below, we are the controller under Brazil's General Data Protection Law (Lei nº 13.709/2018, "LGPD") and, where it applies, the EU/UK General Data Protection Regulation ("GDPR").

Content that people put into a workspace (messages, pages, files and so on) belongs to that workspace. Where a company or team uses Bundle for its members, that organization decides who joins and what is shared, and for that content we act on its behalf and according to its instructions (as an operator/processor).

Contact and data protection officer (encarregado): contato@bundle.direct. For help with the product, write to support@bundle.direct.

2. What we collect

Account data

  • Your email address and name. If you sign in with Google, Google shares your name, email address and profile photo with us (the openid, email and profile permissions only; we get no access to your Gmail, Drive, contacts or calendar). If you sign in with Apple, Apple shares your name and either your email address or an Apple private relay address. If you sign in with a one-time email code, we email the code to the address you enter.
  • Sign-in sessions: when each session was created, the IP address and the browser or device it was created from, so you can review and sign out of sessions from Settings.
  • Your preferred language.

Profile data

What you choose to add to your profile in a workspace, such as a display name, photo, title, status, phone number and time zone. Other members of that workspace can see it.

Workspace content

The content you and your teammates create and share in Bundle: workspaces, channels, messages and threads, reactions, stickers, pages and databases, comments, uploaded files and images, invitations, meeting links, and settings. We store it to provide the service, and it is visible to the people (and agents) who have access to it under your workspace's settings. Pages you publish to the web are visible to anyone with the link until you turn publishing off.

Meet (voice and video meetings)

Audio, video and screen sharing in meetings are relayed in real time to the other participants through Cloudflare's real-time media service and are not stored, except in the two cases below, which everyone in the meeting can see:

  • Recordings. A member can record a meeting; everyone in it sees that it is being recorded. The recording is made on that member's device and, when they stop, posted as a file in the meeting's thread, where the conversation's members can play it.
  • Live captions. While anyone in the call has captions on, each participant's app sends short clips of its own microphone (a few seconds each, only while someone is speaking) to our servers, which transcribe them with Cloudflare Workers AI (OpenAI's Whisper model, run by Cloudflare). The audio clips are not stored. If server transcription isn't available, the apps transcribe on the device and send only the text. The caption lines are shown to the people in the meeting and kept as the meeting's transcript on its message in the conversation.

We also keep basic records of a call (who joined, when, and the meeting link's title and host).

Device data for notifications

If you allow notifications, we store your device's push token, platform (iOS, Android, web or desktop), app version, language and time zone, so we can deliver notifications in your language and respect do-not-disturb schedules. Tokens are removed when you sign out of that device or when the push service reports them as no longer valid.

Usage analytics and session replays (your choice always wins)

  • Website, web app, desktop app, Android and iOS apps: the website uses Google Analytics 4 and the apps use Google Analytics 4 / Firebase Analytics. Both also use Microsoft Clarity (described below). They follow the same choice: one switch covers analytics and session replays. What happens before you choose depends on where you are, which we take from the country of your connection (as our hosting provider, Cloudflare, reports it; we don't store it):
    • In the European Union and European Economic Area, the United Kingdom, Switzerland and Canada (and whenever we can't tell the country), we ask first: the website shows a consent banner and the apps a prompt. Nothing is collected and no analytics cookies are set unless you allow it.
    • Everywhere else, including the United States and Brazil, analytics is on by default: the website shows no banner, and the app shows "On (you can turn this off)" in its settings.
    • If your browser sends a Global Privacy Control or Do Not Track signal, analytics stays off wherever you are (this is how we honor opt-out signals such as those recognized under California law). iOS and Android have no such signal, so there it depends on the country alone.
    You can turn analytics on or off at any time ("Privacy choices" in the website's footer, "Usage analytics" in Settings → Preferences on the web and desktop, or in the mobile apps' settings). Once you've chosen, we never override your choice.
  • In every case, advertising features are off: no advertising identifier, no ad personalization and no Google signals. The app records only coarse events (for example, that someone signed in and with which method, that a workspace was created, or that a message was sent in a kind of channel, that a meeting, an import or an email was started or sent) and generic screen names. It never sends message text, names, email addresses or workspace identifiers to analytics. When you're signed in, analytics, session replays and crash reports know you only by a pseudonymous identifier (a one-way hash of your internal account ID), never by your name or email address.
  • Microsoft Clarity (session replays and heatmaps): with the same choice, Clarity records how pages and screens are used (taps, clicks, scrolling, page layout and which screen is open, plus device, browser and approximate location from the IP address, which Clarity doesn't store) so we can see where the product is confusing. In the web, desktop and mobile apps, Clarity uses strict masking: all text, images and everything typed is masked on your device before anything is sent, so recordings show only the shape of the screen, never messages, emails, documents, names or email addresses. On the website, which has no personal content, Clarity uses Microsoft's balanced masking (numbers, email addresses and anything typed are masked). Clarity is off and nothing is recorded unless analytics is on for you, and turning analytics off stops it and removes its cookies.

Crash reports

The Android and iOS apps send crash reports through Firebase Crashlytics (device model, operating system and app version, the technical state of the app when it crashed, and reports of unexpected errors such as a failed server request) so we can fix bugs. Error descriptions are stripped of email addresses, links, quoted text and identifiers before they're sent, and you're identified only by the pseudonymous identifier above. In the web and desktop apps, unexpected errors are reported in the same stripped form as Google Analytics "exception" events, and only when analytics is on.

Technical logs and security

Like any online service, our servers process technical data such as IP addresses, request times, user agents and errors to run, secure and debug Bundle, and to limit abuse (for example, rate limits on sign-in attempts are keyed by IP address). Guests joining a meeting by link may be asked to pass Cloudflare Turnstile, a privacy-preserving check against bots.

GIFs

If GIFs are enabled in your workspace, the GIF picker searches KLIPY directly from your device: KLIPY receives your search terms, your IP address and a random identifier that is not linked to your name or email, and GIF images load from KLIPY's servers.

Local storage on your device

The apps keep a copy of your workspace data on your device so Bundle works offline and starts quickly, plus your sign-in session and preferences. The website stores only your analytics choice. When analytics is on, Google Analytics and Microsoft Clarity set their own cookies or device identifiers (for example _ga, _clck and _clsk on the web). Signing out clears your session from the device.

3. AI agents

Workspaces can add AI agents as members. An agent can read and post only in the channels, conversations and pages it has been added to, like any other member, and every agent has a human sponsor in the workspace. Agents that run on an external runtime connect to Bundle with an access token created by the workspace; the content they can access is sent to that runtime, which is operated by the workspace or a provider it chooses, under that operator's own terms and privacy policy.

AI thread summaries

Bundle can show a short AI-written summary ("TL;DR") at the top of a thread. It is written automatically when a thread reaches five replies (and again after every five more), or when someone who can read the thread asks for one. To write it, Bundle sends the text of the thread's messages (the first message and its replies, up to the most recent 200, with the display name of each author and the names of any attached files) and the name of the channel to Modelflare (modelflare.dev), a model gateway, which passes the request to the AI model that writes the summary (currently Anthropic's Claude Haiku). Files themselves, email addresses and messages outside that thread are not sent. The summary is stored with the thread and shown only to people who can read the thread; threads in private channels and direct messages are summarized only for their members. Workspace owners and admins can turn summaries off in the workspace settings, which also deletes the summaries already written. We do not use your content to train AI models, and no thread is sent anywhere while summaries are off or this feature is not configured.

AI meeting notes

After a meeting that has a transcript (someone had captions on), Bundle sends the transcript (each speaker's display name and what they said) to the same model gateway to write meeting notes: a summary, action items and decisions. The notes are stored on the meeting's message and shown to the conversation's members. Meeting notes follow the workspace's AI summaries setting: nothing is sent while it is off.

4. Why we use your data, and our legal bases

  • To provide Bundle (create your account, sign you in, store and deliver workspace content, run calls, send notifications and sign-in and invitation emails): performance of a contract with you (LGPD art. 7, V; GDPR art. 6(1)(b)).
  • To keep Bundle secure and reliable (logs, rate limits, abuse prevention, crash reports, debugging): our legitimate interests in operating a safe service (LGPD art. 7, IX; GDPR art. 6(1)(f)).
  • Usage analytics and session replays: wherever we ask first (on the website and in the apps), your consent (GDPR art. 6(1)(a); LGPD art. 7, I), which you can withdraw at any time. Where analytics is on by default: our legitimate interest in understanding how the website and features are used (LGPD art. 7, IX; GDPR art. 6(1)(f)), which you can object to at any time by turning analytics off ("Privacy choices" on the website, or the app's settings).
  • Service messages (for example, important changes to these terms or to your account): performance of a contract and legitimate interests. We do not send marketing email.
  • Legal obligations and the exercise of rights in legal proceedings (LGPD art. 7, II and VI; GDPR art. 6(1)(c)), for example keeping access records as required by Brazil's Marco Civil da Internet (Law 12.965/2014).

We do not sell your personal data, and we do not use it for advertising.

5. Who we share data with

We share personal data only with the service providers that run Bundle for us, under contracts that limit their use of it:

  • Cloudflare, Inc. (United States): hosting and storage of the service and its data (Workers, D1 database, R2 file storage, Durable Objects), sending sign-in and invitation emails, real-time audio and video relay, transcription of live captions (Workers AI), and bot protection.
  • Google LLC (United States): Google sign-in, Firebase Cloud Messaging for push notifications (which carries the notification's title and text), Google Analytics / Firebase Analytics (only as described above) and Firebase Crashlytics.
  • Microsoft Corporation (United States): Microsoft Clarity session replays and heatmaps, only when analytics is on and with the masking described above.
  • Stripe, Inc. (United States) and its affiliates: subscription payments for paid workspaces (card and billing details, which are sent directly to Stripe and never stored by us, the billing email and address, invoices and tax IDs).
  • Apple Inc. (United States): Sign in with Apple and, for iPhone and iPad, push notification delivery.
  • KLIPY: GIF search, only when you use the GIF picker.
  • Modelflare (model gateway) and the AI model provider it routes to (currently Anthropic, PBC, United States): writing AI thread summaries and meeting notes, only for workspaces that have them on (see section 3).

We may also disclose data when required by law or a valid order from a competent authority, to protect the rights, safety and property of our users or others, or as part of a merger or acquisition (in which case this policy keeps applying to your data). Within a workspace, your profile and the content you share are visible to the other members and agents who have access to it.

6. International transfers

Our providers process data in the United States and other countries where they operate, which may not offer the same level of protection as Brazil or your country. We make these transfers on the bases allowed by the LGPD (art. 33), including standard contractual clauses and the performance of our contract with you, and, for data from the EU/UK, the safeguards the GDPR provides (such as standard contractual clauses or adequacy decisions).

7. How long we keep data

  • Account data: while your account exists. When you delete your account (Settings → Account), we delete your sign-in methods, sessions and devices, deactivate your memberships, and replace your name, photo, email and other profile details with "Deleted user".
  • Workspace content: until it is deleted by its author or the workspace, or the workspace is deleted. Messages and pages you posted in a shared workspace belong to that workspace and stay there after you leave or delete your account, shown as from a deleted user.
  • Meeting recordings, transcripts and notes: like other workspace content, until the recording or the meeting's message is deleted, or the workspace is deleted.
  • AI thread summaries: until the thread is summarized again, a reply in it or the thread itself is deleted, or the workspace turns summaries off.
  • Push tokens: until you sign out of the device, the token stops working, or you delete your account.
  • Logs and security records: for as long as needed for security and debugging, and access records for at least six months where Brazilian law requires.
  • Analytics data: according to the retention settings of Google Analytics, at most 14 months.
  • Session replays: Microsoft Clarity keeps recordings for 30 days (longer only for recordings we mark as favorites, which we use rarely) and heatmap data for up to 13 months.
  • Crash reports: Firebase Crashlytics keeps crash and error reports for 90 days.

8. Your rights

Under the LGPD (art. 18) you may ask us to confirm whether we process your data; access it; correct incomplete, inaccurate or outdated data; anonymize, block or delete unnecessary or excessive data or data processed against the law; port it to another provider; delete data processed on the basis of consent; know who we share it with; know what happens if you do not consent; withdraw consent; and object to processing. If the GDPR applies to you, you also have the rights of access, rectification, erasure, restriction, portability and objection, and the right to withdraw consent at any time.

You can do many of these things yourself in the app: edit your profile, manage sign-in methods and sessions, export pages as Markdown and delete your account. For anything else, write to contato@bundle.direct. We may need to confirm your identity first, and we will answer within the time the law requires. If your request concerns content in a workspace run by an organization, we may refer you to that organization. You also have the right to complain to Brazil's data protection authority (ANPD, gov.br/anpd) or to the supervisory authority where you live.

9. Security

Data is encrypted in transit (HTTPS/TLS) between your device and our servers, and stored on Cloudflare's infrastructure, which encrypts it at rest. Sign-in uses short-lived access tokens, one-time codes or your Google or Apple account, so Bundle never stores a password for you. Access tokens for external agents are stored only as hashes. Bundle is not end-to-end encrypted: our systems can process workspace content in order to provide the service. No system is perfectly secure; if a security incident creates a relevant risk to you, we will notify you and the authorities as the law requires.

10. Children

Bundle is a work tool and is not intended for children. You must be at least 18 years old to create an account. If you believe a child has given us personal data, contact us and we will delete it.

11. Changes to this policy

We will update this policy as Bundle changes. The date at the top shows the latest version. If we make significant changes, we will tell you in the app or by email before they take effect.

Terms of Service

Made by the team at BIG SMALL

  • Product
  • Switch
  • Pricing
  • FAQ
  • Talk to us
  • What 15 people pay
  • Download
  • Blog
  • Sign in
  • Try free
English Português (Brasil)

© 2026 BIG SMALL

Google Play and the Google Play logo are trademarks of Google LLC.

  • Privacy Policy
  • Terms of Service
  • Security
  • AI connector
  • Leaving Bundle
  • If Bundle stops
  • Support

Analytics

May we use Google Analytics and Microsoft Clarity (visit counts, heatmaps and masked session replays) to improve this site? Nothing is loaded and no cookies are set unless you allow it.