← Back to Bellwick

Privacy Policy

What the Bellwick website and invited beta collect, why that information is used, and how meeting data is handled.

Effective November 9, 2026

This website

bellwicksoftware.com describes Bellwick and lets you request beta access through a short form or by email. It has no analytics, advertising, or cookies. If you arrived through a link with campaign tags (such as utm_source) or from another site, the page keeps those tags and the referring address in your browser's session storage until you close the tab, and sends them with your request so dD Creative can see which links bring people to the beta. The hosting provider may process ordinary request details, such as IP addresses and request times, to serve the site.

Beta requests

If you send the request form, dD Creative receives your name, email address, which computer you use, what you write about your work, and the referral details described above, and may send you an automatic confirmation email. If you email a beta request, dD Creative receives your email address, your name if you provide it, and the message you send. This information is used to reply and run the beta. It is not used for newsletters, advertising, or unrelated marketing.

Beta access records

The existing beta service keeps minimal operational records when an invitation is used or a release is downloaded. These records use a private invite identifier and may include the event, release version, and time received. They do not store the raw access code, IP address, or meeting content. Hosting logs are separate and may contain ordinary connection details.

Access records are used to understand whether an invitation reached the installer step. Optional version reports help show which beta versions testers are running. These records are kept in a separate event store operated by dD Creative, not sent to a third-party analytics service.

The beta service may use a functional cookie to keep an invited download session active. That cookie belongs to the beta service; this Bellwick website does not set it. Existing beta signup records can also include the name, email, message, and referral information supplied through a signup form.

Service providers and sharing

Contact and beta records are handled through dD Creative's email, database, and hosting providers as needed to deliver messages and run the beta. Personal information is not sold, rented, traded, or shared with third parties for their marketing. Contact and beta records are not posted publicly.

Retention and deletion

Contact and beta records are kept until you request deletion or they are no longer needed to run the beta. Email the address below to request deletion of your contact record and associated beta records.

Your meeting data

Bellwick processes meetings on your Mac or Windows computer by default. Audio, transcripts, notes, and the search index are stored there. Bellwick does not send meeting usage analytics or crash reports. Setup downloads, beta enrollment, update checks, and optional version reports use the network without sending meeting content.

Optional AI sharing is available in the Mac beta and is off by default. If you enable it, Bellwick shows the material to be sent to the service you configure. You review it and confirm each send. Depending on the task and your approval, that material may include a question and excerpts or one meeting transcript, along with details such as meeting titles, dates, meeting types, participant names, speaker labels, and timestamps. The receiving service's own policies govern its handling of that material.

See Trust for the data flow and beta review details.

Update checks

Mac beta release builds check for a newer version without sending your beta code. You can turn this check off. The documented Windows beta updater sends your beta code and installed version to the existing beta service shortly after launch, about every six hours while running, and when you check manually. The Windows update check has no off switch. Neither check sends meeting content.

Optional version reports

In builds that support it, version reporting is off by default and separate from update checks. If enabled, your beta code authenticates the request. The stored report contains a private invite identifier, the running version, the platform, and the time the service received it. It does not contain the raw access code, a device identifier, or meeting content.

The first report and reports for a new version can be sent immediately, followed by about one report a day while Bellwick is running. These times show roughly when the app was running. You can turn reporting off at any time. A report shows the version the app says it is running; it does not prove that an update finished or that the app works.

Contact

For privacy questions or a deletion request, email beta@bellwicksoftware.com. Material changes to this policy will be dated here.