Bardo Web – Privacy Policy

Last Updated: August 10, 2026
Effective Date: August 10, 2026

TypexAI designs Bardo Web to minimize data collection. Most user data stays on the user's device or in the user's browser. Bardo Web does not sell personal data, does not show advertising, and does not use user content for AI training.

1. What Bardo Web Collects

Bardo Web collects only limited anonymous product analytics.

This may include:

  • approximate total number of users;
  • number of visits per day;
  • basic aggregated usage counts needed to understand whether the product is working and growing.

This analytics is anonymous and aggregated. It is not used to identify users, profile users, follow users across websites, analyze private notes, or build advertising audiences.

Bardo Web does not collect:

  • private notes;
  • drafts;
  • lists;
  • Personal Space content;
  • passwords;
  • recovery keys;
  • speech recordings;
  • OCR source files;
  • exported files;
  • behavioral profiles;
  • advertising identifiers.

2. No Accounts and No Personal Tracking

Bardo Web's core note-taking features do not require users to create an account.

TypexAI does not use Bardo Web to create personal profiles, assign advertising IDs, or track users across other websites.

Bardo Web does not use advertising cookies, behavioral tracking pixels, heatmaps, session recording tools, or fingerprinting for profiling.

If browser storage is used, it is used mainly to make the app work locally, save settings, store local data, or remember the user's chosen mode.

An account is only ever created if a user chooses to enable the optional Bardo Sync feature. That account is not used to build personal profiles or track users across other websites, and it is not required to use Bardo Web. See Section 5 (TypexAI Cloud — Bardo Sync).

3. Anonymous Analytics

Bardo Web may use privacy-preserving anonymous analytics to count:

  • how many users use Bardo Web in total;
  • how many visits happen per day.

These analytics are intentionally limited. They are not designed to answer what a specific person wrote, opened, clicked, created, deleted, imported, exported, or searched.

Anonymous analytics may be inaccurate because users can clear browser data, use private browsing, switch devices, block requests, or enable Sensitive Mode.

Bardo Web does not use Google Analytics, Meta Pixel, advertising trackers, session replay, heatmaps, or behavioral profiling tools.

4. User Content Stays Local

Bardo Web is designed so that notes, text, drafts, lists, Personal Space content, and related data remain under the user's control.

TypexAI does not store private Bardo Web note content on its servers in a form TypexAI can read.

TypexAI does not read, analyze, synchronize, sell, share, or use private user content for advertising, analytics, AI training, profiling, or product metrics.

Content created in Bardo Web remains local unless the user chooses to export it, copy it, share it, upload it, send it somewhere else, or enable the optional Bardo Sync feature. If Bardo Sync is enabled, an end-to-end encrypted copy of certain content may be stored in the cloud purely so it can be available on the user's other devices. TypexAI cannot read that content — see Section 5 (TypexAI Cloud — Bardo Sync) for full detail.

5. TypexAI Cloud (Bardo Sync)

5.1 What Bardo Sync Is

Bardo Sync is an optional feature that lets a user's personal workspace follow them between devices. It is entirely separate from Bardo Web's default local browser storage, which continues to work on its own whether or not Sync is ever turned on.

Bardo Sync is off by default. Nothing is sent to TypexAI Cloud unless a user deliberately creates a Sync account and turns the sync engine on.

Creating a Sync account and enabling the sync engine currently requires an active Bardo Plus subscription. A user can still log into an existing Sync account without an active subscription — for example, to restore access on a new device or to reactivate a lapsed subscription.

5.2 The Sync Account

There is no email, phone number, or personal information involved in creating a Sync account.

When a user creates a Sync account:

  • the user chooses a sync password of at least 10 characters;
  • the browser generates encryption keys and encrypts the user's vault locally, before anything is sent anywhere;
  • TypexAI's server issues a random 16-digit account number and does not attach any personal information to it.

The 16-digit account number is the only way to identify the account, and it cannot be recovered if lost — users are responsible for saving it. Sync stays paused after account creation until the user explicitly turns it on.

Logging in uses a cryptographic challenge-response exchange (ECDSA P-256). The sync password itself is never transmitted to, or received by, TypexAI's servers — it never leaves the user's browser. Access tokens issued on login last 30 days. On login, local data already on the device is merged with the cloud copy rather than being overwritten.

The vault encryption key is not kept in the browser indefinitely. After a page reload, the vault re-locks and the user must re-enter their sync password to unlock it again.

5.3 What Bardo Sync Does and Does Not Synchronize

Bardo Sync only synchronizes content from a user's personal (non-Private-Space) workspace, specifically: notes, to-do lists, note comments, note attachments, projects, categories, kanban boards, drawings, music tracks, calendar events and day notes, and editor blocks. Larger files, such as attachments, drawings, and audio, are stored as encrypted blobs; smaller content is stored as inline encrypted data.

Bardo Sync never sends the following to the cloud, under any circumstances:

  • Personal Space content (any note, to-do, or comment marked private);
  • private attachments;
  • app settings;
  • AI API keys stored in the app;
  • Organization workspace content;
  • local sync bookkeeping data such as the outbox, sync cursor, or session state, which never leaves the device and contains no user content.

If Sensitive Mode is enabled, all network traffic to TypexAI Cloud is blocked outright and Bardo Sync does not run — see Section 8 (Sensitive Mode).

5.4 Encryption

All Bardo Sync content is encrypted on the user's device before it is sent anywhere. TypexAI's servers never receive an unencrypted copy.

  • The sync password is turned into an encryption key locally using Argon2id, a memory-hard key derivation function, combined with HKDF-SHA256.
  • Content itself is encrypted with XChaCha20-Poly1305 before upload.
  • Login uses an ECDSA P-256 challenge-response exchange, so the password is never transmitted.
  • Content integrity is verified using SHA-256 hashes of the encrypted data.

Because of this design, TypexAI's servers store only: the user's private key in wrapped (encrypted) form, needed for authentication; an encrypted "vault root" value used only to let the client itself confirm a password is correct; and fully encrypted note, project, and attachment content.

TypexAI's servers see, in unencrypted form, only the technical metadata needed to operate the sync service:

  • the 16-digit account number and an internal account identifier;
  • collection names, such as "notes" or "projects" — never their contents;
  • opaque record identifiers;
  • timestamps, revision numbers, and deletion flags;
  • content size and a hash of the encrypted data — never the data itself;
  • key-derivation parameters (salt and settings), which are useless without the user's password;
  • a public cryptographic key;
  • a device identifier, a device name (such as browser type), and when that device last connected;
  • a hash of the access token, not the token itself.

TypexAI's servers cannot read note text, attachments, drawings, audio, or the user's sync password.

5.5 Account Sign-Out and Deletion

Signing out of a device revokes that device's access token and clears the local session on that device only. Data in the cloud remains available so that other signed-in devices keep working normally.

Deleting a Sync account requires the account number, the sync password, and explicit confirmation. When an account is deleted, TypexAI removes the Sync profile, all encrypted records and file blobs, and all registered devices from its servers. Notes already stored locally in the browser are not deleted by this process — this is stated clearly in the app at the time of deletion.

5.6 How Synchronization Works

Changes made on a device are queued locally and synchronized roughly every 20 seconds, and whenever the browser window regains focus. Each cycle downloads any changes from the cloud, uploads local changes, and checks again for anything new.

If two devices edit the same item, the most recently modified version wins. If changes happen to share the exact same timestamp, TypexAI uses an internal revision counter as a tiebreaker. Deletions are recorded as "tombstones" — a deletion marker with no content attached.

If a device is offline, changes queue locally and sync automatically the next time the device reconnects.

Using Bardo Sync across multiple devices combines the content from each device rather than replacing one device's data with another's. For example, 100 notes on one device and 50 different notes on a second device will normally result in roughly 150 notes after they sync, unless the same note was edited independently on both devices.

5.7 Storage Limits

Each Sync account currently has 1 GB of cloud storage, with a maximum size of 50 MB per individual file. Users are warned when they reach 80% of their storage quota.

Access tokens are valid for 30 days. A login challenge, used only during the sign-in process itself, expires after 5 minutes.

To prevent abuse, TypexAI applies rate limits to account registration, login, and sync activity, based on both IP address and account.

5.8 Bardo Sync and Bardo Plus Billing

Bardo Sync's encrypted cloud storage and Bardo Plus subscription billing are handled by separate systems. Subscription payments are processed through Stripe and TypexAI's own billing system — not through the Sync cloud infrastructure, and not alongside any note content.

To confirm that an active Bardo Plus subscriber is entitled to use Sync, TypexAI links the two systems using a verified access token together with a one-way cryptographic hash of the Sync account's internal identifier — never the 16-digit account number itself, and never any note content.

5.9 Where Bardo Sync Data Is Hosted

Bardo Sync's encrypted data (metadata and encrypted content) is hosted using Supabase, a third-party infrastructure provider, in a dedicated project used only for Bardo Sync. Encrypted files (such as attachments, drawings, and audio) are stored in a private storage bucket on the same infrastructure.

Bardo Plus subscription billing is handled separately through Stripe and TypexAI's own billing systems, as described in Section 5.8.

All encryption and decryption happens locally in the user's browser, using open-source cryptographic libraries. TypexAI's cloud infrastructure is never in a position to decrypt user content, regardless of who hosts it.

5.10 Logging

Bardo Sync does not generate its own product analytics or event logs. The server records only what is operationally necessary: when a device last connected, and rate-limiting counters (which may include IP address) used to prevent abuse.

TypexAI's cloud infrastructure provider may separately generate its own general infrastructure service logs, as any hosting provider does to keep its systems running and secure; these are not product analytics and are not used by TypexAI to analyze user behavior.

The general, anonymous Bardo Web product analytics described in Section 3 operate independently of Bardo Sync and do not draw on Sync data in any way.

6. OCR and Speech-to-Text

Bardo Web may include text recognition and speech-to-text features.

OCR is processed locally using the Tesseract OCR engine, where supported. Images and documents used for OCR are not sent to TypexAI servers.

Speech-to-text uses the browser's Web Speech API, where supported. Audio is sent to your browser vendor's speech recognition service for transcription. TypexAI does not receive, store, or process speech audio or transcripts on its servers.

Speech-to-text is not available when Sensitive Mode is enabled.

Performance and language support may depend on the browser, device, and available network connection.

7. Personal Space and Password Responsibility

Bardo Web may include a protected area called Personal Space.

Personal Space is designed so that access depends on the user's password or local protection method.

TypexAI does not know the user's Personal Space password and cannot recover it.

If a user loses or forgets the Personal Space password, TypexAI cannot reset it, decrypt the data, or restore access.

Users are responsible for remembering their password and keeping any necessary backups or exports.

The same principle applies to a Bardo Sync password and Sync account number: TypexAI does not know either one, cannot recover them, and cannot decrypt or restore Sync data without them. See Section 5.2.

8. Sensitive Mode

Bardo Web may include a Sensitive Mode for users who want stricter privacy.

When Sensitive Mode is enabled:

  • anonymous analytics are not collected by Bardo Web;
  • local-first behavior is prioritized;
  • fewer non-essential signals are sent by the app;
  • all network traffic to TypexAI Cloud (Bardo Sync) is blocked, and sync does not run while Sensitive Mode is on;
  • deleted local data cannot be restored by TypexAI.

Sensitive Mode does not create a cloud backup. If the user deletes local data, clears browser storage, resets the browser, changes devices, or removes the app data, the data may be permanently lost.

If the user turns off Sensitive Mode and does not delete local data, Bardo Web returns to the normal mode. In normal mode, anonymous aggregate analytics may resume from that point forward, and Bardo Sync may resume if it was previously enabled.

Sensitive Mode cannot prevent all technical information from being processed by browsers, networks, hosting providers, or infrastructure services that are required to load the website.

9. Local Storage and Data Loss

Bardo Web relies on the browser, device, and local storage environment.

Users are responsible for keeping backups, exports, and copies of important content.

The following actions may permanently delete locally stored data:

  • clearing browser data;
  • deleting site storage;
  • resetting the browser;
  • uninstalling the browser;
  • using private browsing mode;
  • changing devices;
  • deleting local files;
  • deleting Bardo Web data manually.

TypexAI usually cannot restore lost content because TypexAI does not keep a server copy of private Bardo Web content. If Bardo Sync was enabled, content that had already synced remains recoverable from the cloud; content that never synced, or that lives in Personal Space, cannot be recovered by TypexAI under any circumstances.

10. Import, Export, and Sharing

Bardo Web may allow users to import, export, copy, download, or share content.

After content leaves Bardo Web, the user is responsible for where it is saved, sent, uploaded, stored, or shared.

TypexAI is not responsible for third-party apps, browsers, devices, cloud drives, messengers, email providers, websites, or platforms used with exported content.

Users should avoid exporting sensitive data to places they do not trust.

11. Technical Delivery of the Website

Bardo Web is delivered through the internet at https://bardonotes.org/.

Hosting, domain, CDN, browser, network, security, or infrastructure providers may process basic technical request information needed to load and protect the website. This may include IP address, request headers, timestamps, browser data, error logs, or security-related network information.

TypexAI does not use this technical delivery data to read private notes, build advertising profiles, or track users across websites.

Some technical processing is necessary for the website to load, remain available, prevent abuse, and maintain security.

12. Support Contact

If a user contacts TypexAI by email or another support channel, TypexAI may receive the information the user chooses to send.

This may include:

  • email address;
  • message text;
  • screenshots;
  • attachments;
  • device or browser details;
  • technical issue descriptions.

TypexAI uses support messages only to respond, provide help, investigate issues, handle legal or safety matters, or communicate with the user.

Users should not send private notes, Personal Space passwords, Bardo Sync passwords or account numbers, recovery keys, sensitive documents, or confidential content unless necessary.

13. No Sale of Personal Data

TypexAI does not sell personal data from Bardo Web.

TypexAI does not share Bardo Web user activity with advertisers, data brokers, behavioral analytics companies, or profiling services.

Bardo Web does not use private user content for advertising, AI training, or third-party targeting. This includes Bardo Sync content, which TypexAI cannot read in the first place.

14. Children and Young Users

Bardo Web is a general productivity tool.

Bardo Web does not require accounts and is not designed to knowingly collect personal information from children.

If a parent, guardian, or user believes that personal information was sent to TypexAI by mistake, they may contact TypexAI using the contact details below.

15. Security

Bardo Web reduces privacy risk by limiting what is collected and keeping user content local where possible, and by end-to-end encrypting content that a user chooses to sync.

However, no browser, device, website, password system, local storage system, encryption system, or export method can be guaranteed to be completely secure.

Users are responsible for protecting their own devices, browsers, passwords, files, exports, backups, and local data.

16. Future Changes

TypexAI may update Bardo Web and this Privacy Policy when features change.

Bardo Web currently offers optional, end-to-end encrypted cloud sync (Bardo Sync, Section 5) and a paid Bardo Plus subscription, both described in this Policy. If Bardo Web later adds further features — such as online AI processing, additional analytics, or other new services involving new data processing — this Privacy Policy will be updated to explain what data is processed.

TypexAI will not treat this policy as permission to silently introduce advertising tracking, behavioral profiling, or user content analysis.

17. Changes to This Privacy Policy

TypexAI may update this Privacy Policy from time to time to reflect product changes, legal requirements, security improvements, or operational updates.

When changes are made, the updated version will be published with a revised Last Updated date.

Contact Us

For questions about this Privacy Policy, contact:

Support: support@typexai.dev
Legal: legal@typexai.dev
Partnerships: partners@typexai.dev
Copyright / DMCA: dmca@typexai.dev