Why storage is used
buildnboost Ventures Private Limited uses cookies and similar browser storage to operate CommentKit. Cookies accompany requests to the website; local storage and session storage are read by code running on the relevant site.
Sessions and request protection support authentication and application security. Appearance and sidebar values remember interface preferences. URL campaign and referral values help us understand where signups originated. These purposes are distinct; not every stored value is an authentication need.
What is stored
Website session
commentkit-session
Connects requests to your session, including sign-in, verification flows and temporary form state. Campaign and referral values supplied in page URLs can also be held in the session and attached to a signup.
Duration: The configured session lifetime is 120 minutes of inactivity; activity can renew it.
Request protection
XSRF-TOKEN
Helps the website verify that form and application requests came from the current browser session.
Duration: Uses the website session’s configured lifetime.
Remembered sign-in
remember_web_*
Allows the dashboard to recognize a remembered sign-in. It is set by the authentication flow, not by the embedded SDK.
Duration: Up to 400 days, unless cleared or invalidated sooner.
Appearance
appearance
Stores light, dark or system appearance in a cookie and local storage so the choice can be used before the page renders.
Duration: The cookie lasts up to 365 days. The local-storage value stays until changed or cleared.
Sidebar preference
sidebar_state
Remembers whether the workspace sidebar is open or closed.
Duration: Up to 7 days.
Temporary playground
commentkit-session (existing website session)
The HttpOnly website session connects this browser to a temporary playground identity. Its feedback and uploaded files are stored on our servers. The playground SDK keeps bearer credentials and pending changes in memory, not local or session storage. The old commentkit:demo:website:v1 local-storage entry is removed when the playground page opens.
Duration: Playground access ends two hours after creation even if the website session continues. Active content is deleted by the scheduled cleanup or creator reset. Hiding the controls keeps the server session; a collaborator leaving ends their access without deleting the shared feedback.
Widget session
commentkit:session:<project>
Session storage on the host website holds the SDK’s project-specific sign-in token and user information so a refresh can keep you signed in. The website playground uses memory-only SDK persistence instead.
Duration: For the browser tab’s session, or until sign-out, authentication expiry or clearing site data.
Widget offline queue
commentkit:offline-queue:<project>
Local storage on the host website holds pending comment changes so they can be retried after connectivity returns. In the website playground these pending changes remain in memory and can be lost on refresh.
Duration: Until the pending work is processed, the widget signs out or clears an expired session, or you clear site data. Clearing it can discard unsynced work.
Website performance measurement
Our website uses Cloudflare Web Analytics. A JavaScript beacon sends page-visit and performance measurements to Cloudflare through our website’s /cdn-cgi/rum endpoint. These measurements include page paths, referring links, country, browser and device details, and page-load timings.
According to Cloudflare’s Web Analytics documentation, this analytics service does not use cookies or local storage to collect usage metrics. Clearing cookies alone does not stop these measurements. Cloudflare’s network also processes request information, including IP addresses, for website delivery and security, as described in our privacy notice.
Other services and websites
Choosing Google sign-in or Dodo Payments checkout takes you to a service with its own cookies and privacy practices. Websites that embed CommentKit can also use their own storage and tracking technologies. Their notices apply to those technologies.
Email delivery, open and click information is described in our privacy notice. It is separate from this browser-storage list.
Your browser controls
You can inspect, remove or block cookies and site storage in your browser. Sign out before using a shared device. Clearing data can sign you out, reset preferences and remove comments that have not synced. Blocking required session storage can prevent parts of the service from working.
Change your appearance from the website’s theme control. For questions about attribution, storage or privacy choices, contact [email protected]. We will update this notice when our use of these technologies changes.