AskVady
Cookies and browser storage
Updated: 2026-11-15
Who operates the platform?
- Controller / service provider
- UAB „PROTURBO“
- Company registration number
- 302719435
- Address
- Žirmūnų g. 135-40, LT-09120 Vilnius, Lithuania
- Privacy contact
- info@askvady.com
Essential functions, without an “accept all” button
This version has no built-in advertising or audience analytics trackers. Account security, returning to a requested page and remembering a language you explicitly choose use the technologies below. The information notice does not ask you to consent to analytics, and closing it does not record consent.
If optional tracking is added later, it must remain off until you choose it, with equally accessible refusal and withdrawal. This notice does not authorize future tracking.
What the platform stores in your browser
| Name / type | Purpose and activation | Duration |
|---|---|---|
bv_sessionFirst-party cookie | Keeps you signed in after a successful login. It is inaccessible to page JavaScript. | Customer: up to 7 days; administrator: up to 12 hours. Signing out invalidates the current session. |
bv_localeFirst-party preference cookie | Remembers Lithuanian or US English after you explicitly choose a language link. It does not identify a cross-site visitor. | Up to 1 year, or until you remove it. |
bv:account-returnTab session storage | Returns you to the internal page you requested after login or account setup. It contains a permitted page path and a timestamp, and may temporarily include an invitation token when you join a team. It does not contain your password. | Tab session; the application only uses it for up to 30 minutes and clears it after returning. |
bv:push-device-accountLocal storage | After you enable notifications, remembers the account ID associated with this browser’s notification subscription. It helps disconnect the previous account when someone else signs in. It contains no visitor messages. | No automatic browser expiry. Removed on sign-out, when an account change is detected, or when you clear site storage. Turning off one company’s notifications does not remove this shared marker. |
push-worker.js · /komandaService worker | The team workspace may register this notification handler when sending is available. Registration does not grant notification permission. It does not intercept page requests or cache private pages, conversations or offline data. | Remains registered until the browser removes or unregisters it; it can be updated by the website. Signing out cancels the notification subscription but does not unregister the handler. |
| Web Push subscription and notification permission Browser-managed storage | Created only after you choose to enable notifications and grant browser permission. The subscription contains a delivery address and encryption keys; permission is controlled in your browser or phone settings. | Until cancelled, expired by the browser or push service, or removed in browser settings. Sign-out or an account change initiates cancellation. Turning off one company stops its server-side subscription; other enabled companies and browser permission can remain. |
The information notice itself stores no dismissal flag in cookies or browser storage.
Optional team notifications
Notifications are optional and require your explicit choice for each device and company. You can turn them off in the team workspace, or revoke permission in your browser or phone settings. A notification contains a generic alert and internal company/conversation identifiers for opening the right page, not a visitor’s name or message. Reading the conversation still requires authorized access.
The server stores the delivery address and subscription keys encrypted, linked to your account, company and sign-in session. Sign-out or access revocation removes the binding; session expiry stops delivery, and expired records are removed by the delivery cleanup. Queue records contain event identifiers, attempt counts and delivery status, expire within 1 hour and are removed when cleanup runs. A general last-successful-send timestamp remains until replaced; security audit retention follows the platform’s retention settings. The browser’s push provider also processes technical delivery information. Actual providers, processing locations and retention must be checked before production use.
Chat on a business’s website
The current chat keeps its conversation access token in page memory, not a tracking cookie or persistent browser storage. The business receives the conversation on the server; this is separate from browser storage. Its website can have its own cookies and privacy rules.
Closing or starting a new chat does not erase the server-side conversation. The business’s privacy notice must explain retention and your contact options.
Security checks and payments
When configured, Cloudflare Turnstile loads on account forms to prevent abuse and processes technical browser signals. Cloudflare infrastructure may also apply security mechanisms depending on deployment settings. Checkout opens the payment provider’s page only when you request a payment; its own storage information applies there.
The exact production security-cookie inventory must be verified on the deployed domains before launch. The application does not load a Stripe checkout script or optional advertising tracker merely because you view a public page.
Your controls
You can remove cookies and site storage in your browser. Blocking the sign-in cookie prevents authenticated use; removing the language preference resets the remembered language. You can still read the public pages without agreeing to advertising cookies.
For personal-data processing and your rights, see the privacy notice.