Cookie Policy
1. What cookies are
Cookies are small files that a website stores on your device. Similar technologies, such as local storage and pixels, do the same job. This policy covers all of them.
A first-party cookie is set by us. A third-party cookie is set by a provider that supplies a tool to us.
2. Who sets them
SwiftSoft Labs LLC ("we", "us") sets the cookies that run the service. The providers listed in section 4 may also set cookies or read data from your device when they supply their tool to us.
3. Cookies we need
We use cookies and similar technologies that the service needs to work and to stay secure. You cannot switch these off in the service, but you can block them in your browser, and the service may then not work. All are first-party cookies on our own domain:
- `insforge_access_token` and `insforge_refresh_token`: keep you signed in. `insforge_code_verifier`: protects the sign-in with Google or GitHub.
- `bb_consent`: remembers whether you accepted or rejected non-essential storage in our banner, for 180 days.
- `bb_org`, `bb_project` and `bb_workspace`: remember the organization, project and workspace you picked. `bb_sidebar`: remembers the sidebar layout. `bb_theme`: remembers light or dark mode (also kept in local storage).
- `bb_social_oauth`: protects the social account connection for a few minutes.
- `bb_persona`: remembers the role you picked at sign-up until your account is set up, up to 7 days.
Your browser also keeps unsaved post drafts in local storage and a pending AI draft (`bb_ai_pending_draft`) in session storage. They stay on your device until the draft is saved or you clear them.
**Attribution cookie.** `bb_vid` holds a random visitor ID for 60 days when someone opens a BroadBeam short link, so a later sign-up or payment can be credited to the campaign or partner. In the European Economic Area, the United Kingdom, Switzerland, or when we cannot tell your country, we set it only after you accept in our banner.
4. Cookies and tools from other providers
We group the providers by what their tools do:
- Strictly necessary: These are needed to run the service and keep it secure, for example to keep you signed in or to complete a payment. They do not need your consent.
- Performance and analytics: These show us how the service is used and where it fails, so that we can improve it.
Strictly necessary
- GitHub Sign-In. Sign in with GitHub. Data: GitHub account ID, name, email address and picture. Location: United States. Agreement: https://github.com/customer-terms
- Google Sign-In. Sign in with Google. Data: Google account ID, name, email address and picture. Location: United States. Agreement: https://business.safety.google/processorterms/
GitHub and Google set their own cookies only on their own sign-in pages, when you choose to sign in with them. They set nothing on our site.
Performance and analytics
- PostHog. Page views on public marketing pages. Data: Random session ID, page URL and country. Location: United States. Agreement: https://posthog.com/dpa. PostHog sets no cookies. It keeps the random ID in your browser's session storage (`ssl-marketing-distinct-id`), which is cleared when you close the tab. In the European Economic Area, the United Kingdom, Switzerland, or when we cannot tell your country, it runs only after you accept in our banner.
- Sentry. Error monitoring. Data: Error reports with request path and browser details; IP address, cookies and auth headers are filtered out. Location: United States. Agreement: https://sentry.io/legal/dpa/. Sentry sets no cookies.
**Customers' sites.** The BroadBeam tracking script that customers may add to their own websites stores the same random `bb_vid` ID in local storage on those sites. Each customer is responsible for any consent its visitors' laws require.
Our other providers (Vercel, InsForge, OpenRouter, Resend and Amazon Web Services) work on our servers and set nothing on your device.
5. Your choices
Our banner has two buttons. Accept allows `bb_vid` and PostHog page views. Reject keeps only what the service needs: it removes `bb_vid` and stops PostHog page views. You can change your choice by clearing the `bb_consent` cookie, which shows the banner again.
You can also block or delete cookies in your browser settings. Blocking them may stop parts of the service from working. Each browser explains how in its help pages.
6. How long cookies last
A session cookie is deleted when you close your browser. A persistent cookie stays on your device until it expires or you delete it. The lifetime of a provider's cookie is set by that provider and is described in its own policy.
7. Changes and contact
We may update this policy. Questions go to legal@swiftsoftlabs.com.