Security & privacy, clearly documented.

Privacy by design

SideNote Pro is a native Windows application and a client for AI services you choose and configure. BediniLabs does not operate an AI backend for it, and there is no SideNote Pro account, cloud profile or hosted conversation service.

When a request is submitted, it goes from the application to the AI provider configured in its settings. BediniLabs is not in that path, and does not receive prompts or responses as part of AI generation.

With a local provider such as Ollama or LM Studio running on the same machine, the request goes to localhost and processing can remain on that machine. What SideNote Pro controls is where a request is sent; it does not supply the local model.

The Privacy Policy sets all of this out in full, and BYOK and privacy explains what bringing your own key does and does not change.

Local data and credentials

Application data is stored on the device, under the Windows user’s Local App Data location. It is not uploaded to BediniLabs and is not synchronised between devices.

What a request contains

Nothing is sent to the provider until a request is submitted. A request then carries what it needs: the message and the system prompt, relevant earlier messages from the same conversation within the configured context window, and anything attached or captured for it, such as images, text extracted from documents, text from a selected-text action, or the excerpts local search selected from an indexed folder. A request that is only typed text sends only typed text.

One request is easy to overlook: when a long conversation is compacted, the summary is produced by the configured provider, so older messages are sent to it for that purpose.

A clear service boundary

Three separate parties can be involved when SideNote Pro is in use, and they see very different data. The application makes network requests to two destinations, and they are entirely separate: the AI endpoint configured in its settings, and the BediniLabs licensing service.

1. SideNote Pro, on your Windows device

   Holds

   Settings, conversation history, attachments and extracted document text, folder indexes, the usage ledger, provider credentials, licensing state, and the device key used to sign licensing requests.

   Connects to

   The AI endpoint you configured, and the BediniLabs licensing service.

2. The AI provider you configure

   Receives

   The requests submitted to it, and the API key that authenticates them.

   Governed by

   The provider’s own terms and its privacy, retention and usage policies. BediniLabs does not control or audit those practices, and billing for API usage is between you and the provider.

3. The BediniLabs licensing service

   Handles

   Trial authorization, activation, entitlement refresh and device deactivation. For those it processes licensing and device information: the licence, its registered devices, trial and entitlement dates, and the purchase email. Trial authorization also sends an identifier derived from the Windows installation, and only that derived value is transmitted.

   Never receives

   Prompts, responses, attachments, screenshots, filenames, folder contents, usage figures or AI provider API keys. AI requests do not pass through it, and it is not a proxy for any provider.

Buying a licence online also involves Stripe, which processes the payment, and Brevo, which delivers the licence email. Neither receives conversations or AI provider credentials. Purchase and licensing data in the Privacy Policy sets out what each one handles.

No application telemetry

The SideNote Pro application does not contain telemetry, product analytics, advertising identifiers or marketing SDKs. It does not report usage, feature interaction, crash statistics or device information to BediniLabs.

The usage figures the application shows are recorded in a ledger on the device: daily token counts and local cost estimates by provider and model. The ledger holds no prompts, responses, filenames, document contents, images or API keys, and it is not sent to BediniLabs.

Documentation for your review

Organisations evaluating SideNote Pro for Business or Enterprise use can ask BediniLabs for the material a security, IT or procurement review needs. Tell us what your process requires, and we will confirm what we can provide.

• Security & privacy documentation

  A written account of how the application handles data, credentials and network connections, consistent with the published Privacy Policy.

• Architecture and data-flow information

  What runs on the device, which endpoints the application contacts, and what each connection carries.

• Software Bill of Materials (SBOM)

  SBOM available on request for organisational evaluations.

• Technical product documentation

  System requirements, provider configuration and licensing behaviour, building on the public setup and usage guides.

• Security questionnaire support

  Answers to your organisation’s security or vendor questionnaire, based on the documented architecture.

• Procurement & vendor review support

  Vendor information for supplier onboarding, and quotation and invoicing for Enterprise purchases.

• DPA or data-processing documentation where applicable

  Whether a DPA is relevant depends on the deployment. What BediniLabs handles is licensing and purchase information, not conversation content.

• Deployment & environment requirements

  The Windows version the application requires, how it is distributed, and the network destinations it needs to reach.

To request documentation, email [email protected] with your organisation’s name and what your review needs.

This material is prepared by BediniLabs and describes how SideNote Pro is built and how it handles data. Documentation is provided for customer review and does not represent a third-party certification or independent audit.