Effective date: June 21, 2026
Cookies are small text files placed on your device when you visit a website. They are widely used to make websites work, remember your preferences, and provide information to site owners.
DocsQA uses a minimal set of cookies and browser storage items needed to operate the platform, keep users signed in, run trials, and support embedded widget conversations. We do not use advertising cookies, marketing pixels, or third-party analytics cookies.
The DocsQA dashboard and marketing site use the following cookies and browser storage items:
| Name | Purpose | Duration | Type |
|---|---|---|---|
| byv_access_token | HttpOnly authentication cookie used by the API to authenticate dashboard requests. | 15 minutes | Essential |
| byv_refresh_token | HttpOnly authentication cookie used only on the refresh endpoint to renew your session without re-login. | 30 days | Essential |
| byv_trial_session | Stores your anonymous trial session token in localStorage so your trial chat persists across page reloads. | 24 hours | Functional |
| byv_trial_messages_* | Caches trial chat messages in localStorage for instant rendering on page load. | 24 hours | Functional |
Note: authentication tokens are stored in HttpOnly cookies. Trial items are stored in browser localStorage so the trial can continue across reloads.
We do not load any third-party advertising, analytics, or social media scripts on our platform. The only third-party network requests made by the DocsQA dashboard are:
Transactional emails we send (welcome, usage warnings, plan renewal reminders) contain a 1×1 pixel image hosted on our servers. When the email is opened, this pixel loads and records the open event. This helps us confirm delivery and understand whether important notifications are being received.
The tracking pixel records: the time the email was opened, and a non-identifying event UUID. It does not record your IP address or device details. You can disable email image loading in your email client to prevent this tracking.
If you are a visitor to a website that has embedded a DocsQA widget (not a DocsQA customer), the widget does not set HTTP cookies, but it may use browser localStorage on that website to keep a visitor ID, session ID, conversation ID, and recent chat history. This helps maintain conversation continuity if the page reloads.
| Name | Purpose | Duration | Type |
|---|---|---|---|
| byv_visitor_* | Stores an anonymous visitor ID for a specific widget so the service can count visitors and maintain continuity. | Until cleared by the browser or user | Functional |
| byv_session_* | Stores the current widget session/conversation ID for a specific widget. | Until cleared by the browser or user | Functional |
| byv_history_* | Stores recent widget messages locally so the chat can reopen with recent context. | Recent messages only; until cleared by the browser, user, or widget new-chat action | Functional |
The website owner who embedded the widget is responsible for disclosing its presence and any localStorage use in their own cookie/privacy policy, and for obtaining any consent required by the laws that apply to their website visitors.
Because we only use essential and functional storage items for the DocsQA platform itself, and do not use advertising or analytics cookies, there is no marketing-cookie consent banner on our platform. If you wish to clear stored data:
We may update this Cookie Policy as the platform evolves. When we do, we will update the effective date at the top. Significant changes will be communicated via email.
For questions about our use of cookies or browser storage, contact us at: