Privacy Notice
How information is handled when you visit the Notes website, use Notes services or contact the people responsible for them.
At a glance
Local writing, encrypted synchronization and a support message are different data flows. This notice explains the distinctions and the choices that follow from them.
Who this notice covers
The notice is for website visitors, people writing only on a local device, sync account holders, invited collaborators, organization administrators and people contacting Notes. The product Privacy page explains the encryption boundary. This notice addresses personal information, purposes, recipients, retention and controls. The legal operator and jurisdiction-specific disclosures must be confirmed before this becomes an effective notice.
Writing locally
Writing a local note does not require a Notes account. It must not silently create a service identity or upload the note. Requesting a download can still generate website-delivery records. Deliberately enabling sync and any intermediate anonymous service identity are separate flows.
Protected content and service information
The intended encrypted-sync boundary keeps protected content readable by authorized people and devices rather than the company or service operators. Operational records can still include account, membership, billing and service information. The exact treatment of note titles, identifiers, paths, attachments and traffic metadata depends on the verified architecture; this draft does not assume every field is visible or every field is encrypted.
Accounts, billing and workspaces
Sign-in records support identity and service access. Membership and invitation records support authorized collaboration. Purchase and invoice records support the relevant payer and biller. Personal areas and multiple workspaces coexist; an administrator does not automatically gain access to personal content or every support case. Only the implemented fields, chosen providers and justified purposes belong in the final processing inventory.
Messages, requests and diagnostics
A message you submit to support, Contact, privacy intake or vulnerability reporting is readable by the authorized people handling it. It is not protected from those recipients by the note-sync promise. Optional diagnostics should be locally generated, limited to reviewed fields and shown for consent before submission. Do not include note contents or recovery secrets. Security evidence belongs in a restricted queue.
Tools and model providers you choose
A permitted local tool may read plaintext. If it uses a cloud model, selected content may be sent to that provider. Its retention, training and processing are governed by the applicable provider configuration and terms. Notes’ sync encryption does not extend to a user-authorized plaintext handoff. Team access does not by itself establish organizational permission to make that handoff.
Website measurement and browser storage
This local design uses no analytics, tracking cookies or third-party services. The intended site must inventory necessary delivery/security storage and any optional acquisition measurement separately. Optional measurement must not be required for downloads, local writing, support or security reporting. App use cannot be inferred from a download request.
Retention and deletion
Retention depends on each purpose and category: encrypted resources, shared contributions, identity records, invoices, support cases, logs and backups can have different lifecycles. A universal period would be misleading. The final schedule must match implemented deletion and restoration behavior, including justified exceptions and backup handling.
Questions and personal-data requests
Use the dedicated privacy-request route. Give a reply channel and a brief description, leaving account or workspace context optional. Verification should be proportionate to the requested disclosure or action. Applicable rights, deadlines, complaint authorities and transfer provisions require review of the operator, roles and jurisdictions; this draft does not invent them.