Back

Privacy policy

Last updated: October 16, 2026.

This is a courtesy translation of the Portuguese original. If the two versions differ, the Portuguese version prevails. Read the Portuguese version.

This policy describes how Bridnote handles personal data to create accounts, authenticate users, protect the application and deliver the note-taking functionality. It is written in plain language, focused on transparency, security and data subject rights.

The rules for using the service, account responsibilities and conditions for notes and attachments are in the terms of service.

Controller and contact

The controller of the personal data processed by Bridnote is Gabriel Alves de Araujo, the individual responsible for the project. To exercise your data subject rights or ask questions about this policy, write to engenheiroaraujo@outlook.com.br.

As a small-scale processing agent under ANPD Resolution CD/ANPD No. 2/2022, Bridnote does not appoint a data protection officer. Requests from data subjects are received and answered at the email above.

Data processed

Bridnote processes the data needed for the account, the notes and the attachments sent by the user to work. This includes first name, last name, primary email, recovery email when provided, phone number when provided, hashed password, session data (IP address, browser and device of each session), basic preferences, operational tokens, the content and tags of the notes created by the user and files attached to notes.

Category Examples Main use
Registration First name, last name, email, optional phone number and recovery email. Create, identify and recover the account.
Authentication Hashed password, session, IP address, browser and device of each session, confirmation, reset and recovery tokens. Sign in securely, validate sensitive actions and show the session history.
Security 2FA method, temporary challenges, encrypted TOTP secret when enabled. Protect the account against unauthorized access.
Content Title, text, color, tags, archive or deletion state of the notes and files attached by the user. Deliver the main note-taking functionality.
Attachments Original name, type, size, storage identifier, checksum and uploaded file. Allow upload, download, removal and security scanning of attachments.

Purposes

The data is used to confirm registration, authenticate the account, keep the session, recover the password, set up and validate two-factor authentication, manage the recovery email, save and organize notes, record security events and allow exporting or deleting the account.

Necessity and minimization

Bridnote seeks to process only the data compatible with its features. Information such as phone number, recovery email and two-factor authentication depends on user configuration. Note data is created and controlled by the user within the application.

Security

Passwords are stored as hashes, operational tokens are stored as hashes and expire, and authenticated pages use an HTTP-only session and protection against form submissions from other sites. In production, cookies must be transmitted with secure settings. When app-based authentication is enabled, the TOTP secret is stored encrypted.

The title and content of regular notes, as well as their attachments, are stored in a form readable by the service, protected by access control, an authenticated session and encrypted transmission, and not by end-to-end encryption. This allows text search and the display of notes on any device.

Notes marked as protected have their title and content encrypted on your device, with a passphrase that only you know: Bridnote cannot read them, search them or hand them over to third parties, and exports them exactly as it stores them, encrypted. The attachments of those notes are also encrypted on the device, including name and type, and therefore do not go through antivirus scanning. The color, tags and state (pinned, archived, trash) of those notes remain visible to the service. Without the passphrase and without the recovery key, there is no way to recover the content of a protected note.

Attachments are limited by size and allowed type. PDF and DOCX files go through antivirus scanning before being stored; images and text files are not scanned. When the scan cannot be completed safely, the upload is refused.

The system also records audit events, such as sign-in, password change, data export, account deletion and relevant failures. These records prioritize internal identifiers, action, entity, result and event date, avoiding storing passwords, tokens, hashes or note content in logs.

Sharing and third parties

Bridnote does not sell personal data and does not use note data for advertising. The application, the database and the attachments are stored on servers of a hosting provider located in Brazil. Operational emails, such as registration confirmation, password reset and authentication codes, are sent through Mailtrap, an email delivery service run by a foreign company. To do so, the recipient's email address and the message content are shared with that service and may be processed outside Brazil.

Retention and deletion

Account, note and attachment data is kept while the account exists or while it is needed to deliver the requested features. Expired or already used tokens may be removed by internal routines. When the account is deleted, the data associated with the user is removed according to the application's database rules, and the physical attachment files linked to the account are also removed from the application's storage. The hosting provider keeps weekly backups of the application, the database and the attachments for up to 6 weeks. Because of that, the data of a deleted account may remain in those backups until they expire; after that period, the oldest backups are permanently deleted.

Data subject rights

Authenticated users can access, correct and update account data in My account, export their data in a structured format and delete their own account in the Privacy and data section. These features help exercise rights provided by the LGPD, Brazil's data protection law, such as access, correction, portability and deletion of data. Requests that cannot be made through the account itself, such as confirmation of processing or information about sharing, can be sent to the controller's email.

Cookies and preferences

Bridnote uses an essential session cookie to keep authenticated browsing secure. Simple preferences, such as light or dark theme and whether the filters panel is open, may be saved locally in the browser. The functional cookie bn_lang remembers the chosen language for up to one year. For details, see the cookie policy.

Updates to this policy

This policy may be updated when there are new features, new security controls or relevant changes in data processing. Important changes must be published on this page to keep transparency with users.