Privacy-first Whiteboarding

How Boardesa keeps whiteboarding simple and local.

Boardesa is designed for quick visual work without accounts or uploads. This page explains the privacy ideas behind that choice and how to use the board responsibly.

Local-first drawing

The drawing surface runs in your browser. When you sketch, add text, draw shapes, choose a background, or export a PNG, those actions happen on your device. Boardesa does not require a server account to make the board useful, and the current drawing workflow does not need a cloud upload step.

Local-first does not mean permanent. Browser storage can be cleared by the user, browser, device cleanup tools, private browsing settings, or site-data controls. If a board matters, export a PNG and store it in a place you trust.

What local saves are good for

Local saves are best for short continuity: returning to a sketch, keeping a rough idea overnight, or pausing while you gather more information. They are not a replacement for backups, document storage, or a project repository. This distinction is important because it sets the right expectation for users and avoids pretending the product does more than it does.

Safe export habits

A PNG export is easy to share, which means it should be reviewed before it leaves your device. Remove names, email addresses, customer details, private links, credentials, account numbers, or internal identifiers unless they are necessary and safe to share with the recipient. A board that explains a process usually does not need real personal data.

When a board is used for support or documentation, replace sensitive examples with neutral labels such as "User", "Project", "Step 1", or "Setting". This keeps the explanation useful while reducing privacy risk.

Information that belongs outside the board

Some information is better kept in a secure system rather than on a drawing canvas. Do not use a whiteboard as the main place to store passwords, API keys, payment details, medical history, legal records, private addresses, or confidential customer data. If a diagram needs to refer to one of those things, use a generic label and keep the sensitive source in the appropriate private tool.

This habit also makes exported images easier to reuse. A board that says "Payment provider" or "Customer record" can often be shared with more people than a board containing exact account details. Less sensitive content usually makes the explanation clearer as well.

Analytics and advertising consent

Informational pages use Google consent settings with analytics and advertising storage denied by default. If a visitor chooses "Accept all", the site updates consent for analytics and advertising storage. The Privacy Policy and Cookie Policy describe this in more detail.

Google AdSense code may be placed on informational pages that have meaningful content and clear navigation. The whiteboard itself should remain focused on drawing, not on pushing users toward ads. For EEA, UK, and Switzerland visitors, AdSense personalized ad serving should use Google's Privacy & messaging CMP or another Google-certified CMP configured in the AdSense account.

Practical privacy checklist

Related pages

Read the Privacy Policy, Cookie Policy, or the practical Boardesa guide. You can also open a board and use it without creating an account.