Privacy

Privacy notice

SharedBrief is operated by SnuffleLabs LLC. Contact us at support@sharedbrief.com for privacy questions or data requests.

SharedBrief stores your email address, account identifier, briefs you choose to create, their publication and sharing settings, allowed recipient email addresses, and readership records. We process this information to run your account, show selected content to allowed readers, and show the owner who opened a brief and approximately how long they viewed it. Do not publish confidential material or personal information about someone else without permission.

Drafts, documents and reader records are available only to their owner and authorized members of the account or workspace, except for published documents shared with readers. A published brief may be open anonymously to anyone with its unlisted link, require email verification, or be restricted to email addresses chosen by its owner. Search engines and recipients may copy content they can access. Unpublishing stops access on SharedBrief; deleting a brief removes it and its associated view records.

For view counts we set a first-party browser identifier and store a one-way hash tied to a brief and day. We also record each visit's start time, approximate visible time, broad device type, and approximate city, region, and country when our host provides them. An email-verified visit is associated with the reader's verified address. The brief owner can see these records. We do not store the reader’s IP address or full browser identifier in our application database. Hosting and authentication providers may process network data to operate and secure their services.

Authorized account or workspace members can retrieve detailed reader activity and captured responses through a connected AI service such as Claude or ChatGPT. Those tool results are then processed by that service under its own data practices. The embedded app can also exchange reader records with its chat host; app-only tools keep those exchanges out of model context, but not out of the host. Requests for detailed reader records should be explicit.

We use Supabase for authentication and data storage, Vercel for hosting, and PostHog to measure whether people create, publish, and share briefs. PostHog receives event names for visits, sign-in, connection and document actions, an account identifier for creator actions, a one-way brief identifier, and first-party browser identifiers. We connect anonymous browser activity to your account after sign-in, distinguish test activity, and use coarse optional client hints to understand web and desktop usage when available. Raw client hints are not retained in analytics. We do not send brief content or email addresses in these events. The browser integration uses first-party storage; pageviews are captured only on the public homepage, help, privacy, and terms pages on our production domains. Pageview URLs exclude query strings and fragments; referral sources retain only the referring origin. Private brief, dashboard, and authentication pages are excluded from pageview tracking. Session recording and interaction autocapture are disabled. PostHog may process network information when it receives events.

Stripe processes payments and manages subscriptions for paid plans. We store billing account identifiers, subscription status and paid coverage dates to provide plan access. Payment details are entered directly with Stripe; SharedBrief does not store card numbers.

A brief owner may require your name, email or phone before reading. These responses are stored with the brief and shown to its owner and authorized members of its workspace, including alongside reader activity. They are self-reported and do not verify your identity or subscribe you to email. A visible notice on the reader page and before the reader-details form explains that visits are tracked and links here. Protected readers receive a first-party access cookie lasting up to one day. Passcodes are stored as salted hashes. To limit repeated unlock attempts, we store a one-way hash derived from the brief and network address, not the raw IP, with an attempt window used for rate limiting.

The sign-in page loads Google Identity Services to offer Google One Tap. Google may process network and account information to display the prompt. Returning users who previously consented may be signed in automatically. We use short-lived first-party cookies to validate sign-in and remember when automatic sign-in should be paused after logout or account switching.

Reader data retention and deletion

Reader visit records, verified reader emails and captured name, email and phone responses are retained until the related brief is deleted or we fulfill a verified deletion request for those records. They do not automatically expire when a brief is unpublished or its access link expires. Deleting a brief deletes its associated visits and captured responses from the active database. Owners can delete briefs from their dashboard. This does not remove copies already downloaded or independently retained by recipients.

You do not need a SharedBrief account to request access to or deletion of your reader data. Email support@sharedbrief.com with the subject “delete my reader data”, the brief link, and the email or other details you provided. For an anonymous visit, include the approximate visit date and time so we can help locate it. We verify the request before disclosing or removing records; we may be unable to identify an anonymous visit from the information available. Do not send passwords or passcodes. We will explain what we can identify and delete, and any records that must be retained for security or legal obligations. Do not assume a request is completed until we confirm it.

Account data remains while your account exists. Contact support@sharedbrief.com for account or product analytics data access and deletion requests. Infrastructure backup and provider log retention follows the applicable providers’ practices; removal from the active service does not promise immediate erasure of all provider backups or copies previously shared with a document owner or a chat host.

Unsaved editor changes may be stored temporarily in your browser tab to help recover work after navigation. They are scoped to the signed-in account and brief, and are cleared when saved, explicitly discarded, or when the tab session ends.

This notice will be updated as our data practices change.

For privacy questions, contact support@sharedbrief.com.