Cookie Policy
This page is being prepared. For questions about VizGuard cookie policy, please contact us.
Effective date: [Insert date]
Controller: Vizguard [Insert legal entity name], [Insert registered address], EU
This Cookie Policy explains how Vizguard uses cookies and similar technologies on its website, application, and related online services. Vizguard offers a no-code visual and accessibility testing platform that includes workflow recording, screenshot capture, browser-based interactions, reporting, and account-based access for teams and agencies.
This policy should be read together with the Vizguard Privacy Policy.
1. What cookies are
Cookies are small text files placed on a device when a user visits a website or uses an online service. Similar technologies can include local storage, pixels, tags, software development kits, and session storage.
These technologies help websites remember settings, keep users signed in, measure usage, improve performance, and support security.
2. How Vizguard uses cookies
Vizguard may use cookies and similar technologies to:
- keep users signed in to the application;
- maintain secure sessions and protect accounts;
- remember settings and interface preferences;
- support workflow recording and product functionality in the web application;
- understand how visitors use the marketing site and product;
- measure performance and improve reliability;
- support waitlist, signup, contact, and onboarding flows.
This use is consistent with Vizguard’s account-based SaaS model, browser-driven workflow recording, and hosted platform experience described in the available product materials.
3. Categories of cookies
Vizguard may use the following categories of cookies:
Strictly necessary cookies
These cookies are required for core website and application functionality. They may be used for authentication, session management, load balancing, security, fraud prevention, and remembering privacy choices.
Because Vizguard provides authenticated access to workflow management, browser-based testing, reports, and account functions, some strictly necessary cookies are required for the Service to operate correctly.
Preference cookies
These cookies remember settings such as language, UI preferences, dismissed notices, or dashboard choices.
Analytics cookies
These cookies help measure how users interact with the website or product, such as page visits, feature usage, traffic sources, and performance trends. They help improve onboarding, product design, and support for the types of users Vizguard targets, including SaaS teams and agencies.
Where required under EU law, analytics cookies will be used only after valid consent.
Marketing cookies
These cookies may be used to measure campaigns, track referrals, or support lead generation activities such as waitlists, demos, newsletters, and product marketing.
Available materials describe public beta signup, waitlist activity, and marketing efforts around product launch, so these cookies may be relevant on the marketing site if enabled.
Where required under EU law, marketing cookies will be used only after valid consent.
4. Legal basis
For strictly necessary cookies, Vizguard relies on legitimate interests or equivalent legal grounds permitted for essential service delivery.
For analytics, marketing, and other non-essential cookies, Vizguard will rely on consent where required by the GDPR, the ePrivacy rules, and applicable national laws in the EU.
Users can withdraw or change consent preferences at any time through the cookie settings tool or by adjusting browser settings, although disabling certain cookies may affect functionality.
5. Third-party cookies
Vizguard may allow selected third-party providers to place cookies or similar technologies when they provide services such as analytics, authentication, hosting support, embedded content, payment processing, scheduling, or customer communications.
Vizguard’s product materials refer to integrations and operational workflows involving APIs, CI/CD, and issue tracking, and the live service may also rely on external vendors for common SaaS functions such as traffic measurement or support operations.
Any third-party provider will process data under its own privacy and cookie terms unless otherwise stated.
6. Cookie retention
Some cookies expire when the browser session ends, while others remain on the device for a longer period so settings or preferences can be remembered across visits.
Actual cookie durations depend on their purpose and technical configuration. Vizguard should maintain an up-to-date cookie table on its website once the production setup is finalized.
7. Managing cookies
Users can manage cookies in several ways:
- through Vizguard’s cookie banner or preference center;
- by changing browser settings to block or delete cookies;
- by using privacy controls offered by certain devices or browsers;
- by withdrawing consent for non-essential cookies.
Blocking strictly necessary cookies may prevent access to login, session security, or core application functions.
8. Cookie table
The table below is a template for the final published version and should be completed with the exact cookies used in production.
| Cookie / Tool | Type | Purpose | Duration | Provider |
|---|---|---|---|---|
| [Insert cookie name] | Strictly necessary | Authentication and session security | [Insert duration] | Vizguard |
| [Insert cookie name] | Preference | Save interface or consent settings | [Insert duration] | Vizguard |
| [Insert cookie name] | Analytics | Measure site or product usage | [Insert duration] | [Insert provider] |
| [Insert cookie name] | Marketing | Track campaign attribution or waitlist signup | [Insert duration] | [Insert provider] |
9. Updates to this policy
Vizguard may update this Cookie Policy from time to time to reflect legal, technical, or operational changes. The latest version will be posted on the website with an updated effective date.
10. Contact
For questions about this Cookie Policy, contact:
Vizguard
[Insert legal entity name]
[Insert address]
[Insert privacy email]
11. Practical notes before publishing
Before publishing this policy, the following items should be confirmed in the live product and website stack:
- whether the marketing site uses analytics tools, ad pixels, or newsletter tracking;
- whether the app uses third-party authentication, billing, support chat, or session monitoring tools;
- the exact list of cookies, durations, providers, and whether they are first-party or third-party;
- whether consent is collected separately for analytics and marketing cookies in each relevant EU jurisdiction;
- whether any workflow recording or in-app telemetry features rely on browser storage beyond essential session functionality.
The current product materials support a cookie policy that assumes authenticated SaaS usage, web application sessions, workflow recording, waitlist or signup flows, and product analytics needs, but they do not identify the exact production cookie inventory, so the final cookie table must be completed from the live implementation.