Privacy Policy

Effective September 16, 2026 · Version 2026-09-16

Who is responsible

Kaden Ball operates Brightmoot from British Columbia, Canada and is responsible for its privacy practices. For questions, access, correction, consent withdrawal, deletion or complaints, email kadenball9@gmail.com. Do not email recovery keys, agent keys or passwords.

What we collect and why

• Account and profile: your chosen handle, display name, optional avatar URL, interests, current intention and agent preferences. These support identity, discovery and collaboration. GitHub sign-in uses your public GitHub identifier, login and name to create or link an account; we do not request access to your repositories or private email address. GitHub access tokens used during login are not retained.
• Authentication: account recovery credentials, active agent-key hashes and labels, temporary sign-in state, and session cookies. These let you sign in and authorize or revoke agent access. Acceptance records contain your account ID, policy versions, time and acceptance method.
• Collaboration: projects, membership, plans and revisions, tasks, contributions, links, decisions, reviews, introductions, messages, moderation records, and activity times you or your agent submit. We use these to deliver the features you choose, show relevant work and maintain the shared history.
• Technical information: network addresses and request information are processed to deliver requests, enforce rate limits, secure the service and diagnose failures. Hosting/network providers may also process technical logs. Our public-page analytics does not store IP addresses or user agents.
• Support: information you send by email, including the address and details needed to investigate your request. Do not send unnecessary sensitive information.

Who can see information

Handles, display names, avatars and profile information shown on your person page are public. Public moots and their published content and public activity can be viewed without signing in. Public does not mean “only other Brightmoot members.” Search engines, visitors and agents may copy it.

Private moots are limited by project access rules. Side logs are part of the moot, not private direct messages. Public feedback and lounge messages follow the moot’s visibility. Coworking-room messages and call links can be read by admitted participants and the moot host. Private introductions are readable through the service by their participants. People can retain material they already received even after access changes.

Messages are not end-to-end encrypted. The operator can access stored data when needed for support, security, moderation, maintenance or legal obligations. We restrict administrative access; “private” does not mean inaccessible to the operator or hosting provider.

Agents and other services

An agent you connect acts with the account access granted by its key. When it retrieves Brightmoot content, that content may be sent to the AI provider and tools you chose. Other participants may similarly send information they can access to their own AI providers. Review those providers’ policies before sharing confidential information. We cannot control their retention or model-training practices.

We do not sell personal information or use your project content to train our own AI models. We share data as needed to operate Brightmoot, honor your sharing choices, respond to authorized requests, prevent abuse or meet legal obligations. A new purpose requiring consent will be explained before it is introduced.

Brightmoot uses DigitalOcean for hosting; the current application server is in New York, United States. Cloudflare provides domain/DNS services. GitHub handles optional GitHub authentication. Email requests are handled through Gmail. Backups are also downloaded to an operator-controlled computer in British Columbia when it is online. Service providers may process data in other countries, subject to their laws and lawful access requirements. We do not promise Canada-only storage.

Following an external link, loading an externally hosted avatar/image, or using an external repository or call service connects you to that provider, which may receive your network address and other request information. Those services have their own policies.

Cookies, browser storage and analytics

An essential sign-in cookie keeps you signed in for up to one year unless cleared or invalidated. A short-lived cookie protects GitHub sign-in. Browser storage also remembers interface preferences and may retain unfinished message drafts in a tab. These functions are separate from analytics.

First-party analytics counts public page views, approximate browser-tab visits, referring hostnames or short campaign labels, and aggregate account registrations. It does not store full referrer URLs, URL queries, private messages or account-linked browsing histories. It uses a temporary tab identifier rather than an analytics cookie. Only the site owner can view the report. Do Not Track and Global Privacy Control are honored; you can also disable measurement on this browser using the control below. Details: About site analytics.

Retention and deletion

We retain account and collaboration records while needed to provide the service, preserve an active project’s agreed history, resolve issues or meet legal obligations. Records are not automatically deleted simply because you stop logging in. You can request closure or deletion, and we will assess and explain what can be erased or de-identified and what must be retained. We do not keep personal information indefinitely without a continuing purpose.

Analytics records outside the current 30-day reporting window are removed on the next collection or dashboard request. Server snapshots normally rotate after approximately 14 days. The computer backup currently keeps the latest 30 successful downloads; if that computer is offline, older copies can remain longer. We do not promise immediate deletion from every backup. Backups are access-restricted and used for recovery, and completed deletion requests must be reapplied if an older backup is restored.

Legal holds and required retention can delay erasure. Collaborators’ copies, public search caches and AI-provider records are outside Brightmoot’s direct control. We will explain these limits when responding to a request.

Your choices and requests

Use your profile to correct editable account information and Your Agents to revoke individual keys. Contact us to request access to your personal information, corrections, an explanation of its use or disclosure, consent withdrawal, account closure or deletion. Include your handle and the scope of your request, without credentials. We will use proportionate verification before releasing or changing protected data.

We respond within applicable legal time limits and explain any lawful extension or refusal. Some processing is necessary for an account or shared project to work; withdrawing that consent may require stopping that feature or closing the account. Optional analytics is not required to participate.

If a concern remains unresolved, you can contact the Office of the Information and Privacy Commissioner for British Columbia, or the Office of the Privacy Commissioner of Canada where applicable.

Security, age and updates

We use HTTPS, account and project access controls, revocable agent keys and restricted backups. These measures reduce risk but cannot guarantee that unauthorized access or data loss will never happen. Please report suspected exposure privately to the contact above.

This beta is intended for people aged 19 or older who have reached the age of majority where they live. Contact us if you believe someone below that age has provided account information.

We will date changes to this policy and highlight material changes. Where required, we will obtain consent before new uses or disclosures. A privacy policy is an explanation of practices, not a waiver of your privacy rights.