Privacy Policy

1. Operator and scope

The legal identity of the operator, privacy contact and controller/processor responsibilities are pending final verification. This draft describes the current product’s data paths. The final notice must also specify the applicable legal bases, retention periods and request procedures.

2. Accounts, workspaces and plan records

Email-based sign-in is handled through Supabase Auth. Account records can include an email address, a profile name if provided, account identifiers and timestamps. Workspaces hold names, membership roles and ownership information used to authorize access.

Plan assignments, periods, status, overrides and usage counts are associated with accounts or workspaces. A payment gateway has not been confirmed for this draft; payment-specific data handling will be added after the final arrangements are supplied.

3. Capsule content and AI processing

Capsules can hold the text you submit, sender context, recipient names or roles, requested decisions, evidence, risks, boundaries, presentation details and generated or validated results. Saved records and versions are kept in the service database with ownership and record identifiers.

When you request AI generation or validation, relevant text is sent to the OpenAI API. The current active creation flow is text-only. Provider processing and retention are separate from BriefCapsule’s own saved records.

Processing locations, provider retention, account-specific data-use controls and contractual arrangements still require verification. The final notice will distinguish the service’s saved records from provider-side processing.

4. Sharing, downloads and activity records

Publishing a delivery page or creating a share link makes the permitted Capsule content available according to the sender’s access settings. Take care with links and exported files containing personal or confidential information.

The service records operational events such as delivery-page views, downloads, blocked access and password verification, along with record identifiers, timestamps and source or share-channel metadata. These records support access controls and workspace activity reporting.

Preparing a destination export does not automatically transmit the Capsule to that destination’s AI. If a sender or recipient submits it to another service, that service’s processing rules apply. Copies outside BriefCapsule cannot be removed by revoking a BriefCapsule link.

5. Browser storage and website analytics

Authentication uses browser cookies. Password-protected delivery can set a temporary signed access cookie. The text-creation form also uses sessionStorage to restore an unfinished draft and submission retry information in the current browser tab; this can include your Capsule input.

Google Tag Manager and Google Analytics are currently loaded on the website. A fresh-browser review observed analytics cookies and a measurement request before any consent interaction. A consent-management interface has not yet been implemented. See Cookie Information for the current inventory and the outstanding consent work.

Analytics may receive page addresses, referrers and technical browser data. The final tag configuration needs a review of authenticated and delivery routes so that sensitive identifiers or query details are not included in analytics events.

Hosting and service providers may receive technical request information, such as network addresses, browser details, requested URLs and errors, when delivering or operating the service. Their specific log settings and retention periods require final confirmation.

6. The three-question Home experience

The Home reflection experience does not ask for a name, email address or account. It uses a random identifier kept in memory for each page load, without adding a feature cookie, fingerprint or persistent browser identifier, and sends its event requests without account cookies.

The section records a participation start only when viewed, question views, Yes/No answers and completion, together with the question version and server timestamps. Historical Skip events remain in the data. Reports use participation attempts and answers, not a count of unique people.

Responses are stored in Supabase and reported through the existing restricted administrator report. No automatic retention period for these records has been confirmed. Separate website analytics and hosting request data must be considered independently of this account-independent experience.

7. Contact messages

The current Contact page offers email links rather than a message-submission form. Clicking a link opens your email application; sending a message shares your email details, message content and any attachments with the selected inbox through email providers.

The mailbox provider, support-message retention and dedicated privacy request contact are still to be confirmed. Do not include information that is unnecessary for your enquiry.

8. External services and processing locations

The current implementation uses Supabase for authentication, database records and storage, Vercel for application hosting, OpenAI for requested AI processing, and Google Tag Manager/Google Analytics for website analytics. Email service arrangements and any future payment provider remain to be verified.

This list must be completed with the operator’s processor agreements, subprocessors, hosting locations and any required international-transfer safeguards. A database region alone would not establish that all processing stays in Europe.

9. Retention and deletion

Final retention periods for accounts, saved Capsules and versions, activity records, Home reflection responses, support messages, logs and backups are pending. Browser draft storage, saved service records, shared downloads and AI-provider records have different lifecycles.

Clearing a browser draft affects that browser copy. Disabling or expiring a link affects future access to that link. Neither action automatically removes previously exported copies, recipient-held content or provider-side records. Deletion timing and exceptions must be verified before the final notice is approved.

10. Requests and final privacy review

Depending on the applicable law, you may have rights relating to access, correction, deletion, restriction, portability, objection and complaints to a supervisory authority. The final notice will identify the responsible operator, contact method, procedure and applicable authority.

Use the current Contact page for enquiries while those details are being finalized. This draft does not replace the final privacy notice or a consent-management mechanism.