Bardo 1.1 Anonymous Analytics Data Collection Policy

Effective date: This policy takes effect with the release of Bardo 1.1.
Last updated: June 23, 2026

1. Overview

With the release of Bardo 1.1, anonymous usage analytics powered by the open-source service Umami have been introduced in the app.

This document explains what Bardo collects through anonymous analytics, when analytics are sent, what is never collected, how users can exercise control over analytics, and how collected data is used.

Bardo may send anonymous usage events to our self-hosted Umami analytics server. These events help us understand how the app is used, which features provide value, which parts of the experience may be unclear, and what should be improved in future releases.

Anonymous analytics are used exclusively to improve Bardo's design, stability, performance, reliability, and overall product experience.

Bardo does not use anonymous analytics to read user notes or private content, to build advertising profiles, to sell data to third parties, or to track users across other applications or websites.

2. When analytics are sent

Analytics are only sent when all of the following conditions are met:

  • Analytics are enabled in the application build.
  • The user has provided explicit consent during first launch or through the application settings.
  • Anonymous Analytics are enabled in the application settings.

Users may enable or disable anonymous analytics at any time by navigating to:

Settings → Security → Advanced Privacy → Anonymous Analytics

When analytics are disabled, Bardo immediately stops sending analytics events and clears the local analytics queue. Bardo does not transmit a separate event upon disabling analytics.

3. Where analytics are sent

Bardo sends analytics events to our self-hosted Umami analytics server over HTTPS.

Umami is an open-source analytics service. Our analytics infrastructure is self-hosted, which means analytics events are sent to a server controlled exclusively by us, rather than to any third-party advertising or analytics network.

The analytics endpoint may use Umami API routes such as /api/send or /api/batch.

4. What Bardo may collect through anonymous analytics

Bardo applies a strict data minimisation principle in accordance with Article 5(1)(c) of the General Data Protection Regulation (GDPR). Only the following specific events and attributes are collected.

App launch

Bardo may record that the app was opened. No additional information is collected on launch.

Note and content actions

Bardo may record that a user:

  • created a note;
  • deleted a note;
  • created a folder;
  • created a task;
  • created a to-do list;
  • created a presentation.

These events record only that an action occurred. They do not include the title, content, or any other detail of the item created or deleted.

Personal Space actions

Bardo may record that a user:

  • opened Personal Space;
  • created a folder in Personal Space;
  • opened a folder in Personal Space;
  • used to-do lists within Personal Space.

No folder names, list titles, or item content are transmitted.

Built-in productivity features

Bardo may record that a user:

  • used the timer feature;
  • used the calendar feature;
  • used Ghost Notes.

No calendar data, reminder content, timer values, or note content are transmitted.

Editor insertion actions

Bardo may record that a user inserted one of the following content types into the editor:

  • a presentation;
  • a location block;
  • handwriting input.

Bardo does not transmit the content of these insertions, including any location coordinates or handwritten text.

Translation feature

Bardo may record that a user used the translation feature. This may include:

  • the source language selected;
  • the target language selected.

Bardo does not transmit the text submitted for translation or the translated output.

Connection graph

Bardo may record that the connection graph screen was opened.

Tools

Bardo may record which built-in tool was used. No input or output content of any tool is transmitted.

Appearance settings

Bardo may record:

  • which theme was selected by the user;
  • which theme is actively applied;
  • which font was selected by the user;
  • which font is actively applied;
  • which application language was selected by the user.

Cloud sync

Bardo may record cloud sync actions, including:

  • enabling cloud sync;
  • performing a manual sync;
  • restoring from cloud backup;
  • enabling cloud data encryption;
  • deleting cloud sync data.

For cloud sync events, Bardo records only the provider type, such as Supabase or WebDAV. Bardo does not transmit the contents of cloud-synced notes, files, or any other private data.

AI feature usage

Bardo may record limited information about AI feature usage, including:

  • the AI provider used;
  • the model identifier;
  • whether the model is local or remote.

Bardo does not transmit the text of AI prompts or AI responses.

Lumen Agent

Bardo may record that the Lumen Agent feature was used and which Lumen Agent style was selected by the user.

DarkDrop and DarkCode

Bardo may record that a user:

  • created a DarkDrop code;
  • scanned a DarkDrop code;
  • used a standard QR code within DarkDrop;
  • used DarkCode within DarkDrop;
  • used the standalone DarkCode feature.

These events record only that the action occurred. No content encoded in or decoded from a code is transmitted.

Bardo Plus events

Bardo may record the following events related to Bardo Plus:

  • the Bardo Plus screen was opened;
  • a purchase flow was initiated;
  • a purchase was successfully confirmed;
  • a prior purchase was restored;
  • Bardo Plus subscription status is active.

Bardo may also record that a Bardo Plus feature upsell was displayed. Upsell events may include which feature triggered the prompt, such as: DarkCode, special export, search, project graph, Ghost Notes, auto-cleanup, or the main menu.

Bardo may record usage of the following specific Plus features: DarkCode, Retell, and auto-cleanup.

Bardo does not transmit exact payment details or subscription payment identifiers through anonymous analytics.

5. Technical metadata added to analytics events

Our analytics framework collects limited technical metadata. Depending on the type of event, this data may include:

  • the application version (currently Bardo 1.1), to ensure compatibility and help troubleshoot issues;
  • an event timestamp (to understand when actions occur);
  • a Bardo User-Agent string containing the application version and platform information (e.g., operating system).

Certain user preferences, application settings, and subscription states are not sent automatically with every event, but are instead transmitted strictly within the context of specific, dedicated events:

  • the selected interface language (only transmitted during specific language change or configuration events);
  • the selected application theme (only transmitted during specific theme setting events);
  • Bardo Plus subscription status (indicated solely by the occurrence of a dedicated subscription status event, containing no additional personal identifiers).

6. IP address notice

Bardo does not intentionally include the user's IP address in the analytics payload.

However, because analytics events are transmitted over HTTPS, the server receiving the request may technically observe the originating IP address as part of standard server operation. This is an inherent characteristic of internet-based communication and is not specific to Bardo.

7. What Bardo does not collect through anonymous analytics

Bardo does not transmit the following data through anonymous analytics:

  • note text;
  • note titles;
  • note content of any kind;
  • task content;
  • to-do list content;
  • contents of encrypted notes;
  • file names or file contents;
  • exported content;
  • passwords or PIN codes;
  • encryption keys;
  • the user's real name or display name;
  • the content of AI prompts or AI responses;
  • cloud-synced content;
  • app lock or PIN usage patterns;
  • location coordinates or location data;
  • handwritten input content;
  • text submitted to or returned from the translation feature;
  • the content of any DarkDrop or DarkCode payload;
  • exact payment details or subscription identifiers.

8. Purpose of anonymous analytics

Anonymous analytics are collected for the following specific purposes:

  • to understand which features are used and provide value to users;
  • to identify and improve parts of the app that may be unclear or underused;
  • to improve application performance and reliability;
  • to prioritise future development and updates;
  • to evaluate whether new Bardo 1.1 features function as intended;
  • to improve the user experience without accessing user-created content;
  • to detect and resolve product-level issues.

Analytics are not used to sell user data, access user content, track users across unrelated services, or build advertising profiles of any kind.

9. User control

Users may enable or disable anonymous analytics at any time by navigating to:

Settings → Security → Advanced Privacy → Anonymous Analytics

When anonymous analytics are disabled, Bardo immediately stops sending analytics events and clears the local analytics queue. Disabling anonymous analytics does not affect the use of any other Bardo feature.

10. Legal basis for processing

For users in the European Economic Area (EEA) and in the United Kingdom, the processing of anonymous analytics data is based on explicit user consent as provided under Article 6(1)(a) of the GDPR, obtained through the opt-in mechanism described in Section 2 and Section 9 of this policy.

Users may withdraw consent at any time by disabling anonymous analytics in the settings described above. Withdrawal of consent does not affect the lawfulness of processing carried out prior to withdrawal.

11. Data sharing

We do not sell anonymous analytics data.

We do not use anonymous analytics data for advertising tracking.

Anonymous analytics data is used solely by TypexAI / Bardo to operate, maintain, improve, and develop the Bardo application.

Because Bardo uses a self-hosted Umami configuration, analytics events are sent to our own analytics server rather than to any third-party advertising or analytics network.

12. Data retention

Because analytics data is designed to be fully anonymous and cannot be linked to any individual, user account, email address, real name, or payment identity, it is not subject to a fixed retention period and may be retained indefinitely for historical analysis and product improvement purposes.

We may not always be able to identify or isolate analytics events belonging to a specific individual unless sufficient technical information is provided.

13. Children and younger users

Bardo is designed to protect private user content. Anonymous analytics do not include note content, file contents, passwords, PIN codes, encryption keys, AI prompt text, AI response text, or any personally identifying content.

In Estonia, pursuant to the Personal Data Protection Act (PDPA), the minimum age for providing consent to data processing in the context of information society services is thirteen (13) years. For users below this age, consent must be provided by a parent or legal guardian.

Parents, guardians, and younger users may disable anonymous analytics at any time in:

Settings → Security → Advanced Privacy → Anonymous Analytics

14. Changes to this policy

We may update this policy when Bardo changes, when new analytics events are added or removed, when analytics behaviour changes, or when legal or technical requirements change.

If we make significant changes to how analytics work, we will update this document and update the effective date accordingly. Where appropriate, an in-app notice may be provided.

15. Contact

If you have questions about this policy, Bardo analytics, or our privacy practices, you may contact us at:

Legal: legal@typexai.dev
Support: support@typexai.dev

Back to Bardo