Technology should have a reason to be here.

Dryvn uses cookies and similar browser technologies to operate the service, provide features you choose to use, understand how the website performs, and improve the experience. This page explains what is in use and what choices you have.

Last updated: August 26, 2026

OVERVIEW

Cookies in plain language

Browser technologies serve different purposes. Dryvn separates technologies needed to operate and secure the service from optional analytics used to understand and improve the public website.

Some first-party browser technologies are necessary for Dryvn to work securely.
Optional analytics remains off unless a real analytics property is configured and the visitor grants Analytics permission.
Third-party services such as Google Calendar may use their own browser technologies when you use those features.
Necessary payment technology may be used only when a payment flow is actually introduced and initiated.
You can accept, reject, or later change optional analytics through Cookie settings.
Dryvn does not currently use advertising, behavioral-targeting, or retargeting technologies.

Use technology deliberately. Know why it exists. Classify it, disclose it, and load it according to the appropriate choice.

Technologies currently in use

Dryvn maintains one browser-technology registry for the public inventory, consent behavior, analytics initialization, and future integration review. The inventory below is generated from that registry and reflects the technologies enabled in this deployment.

Strictly necessaryOperate + secure2 disclosed technologies
FunctionalProvide chosen functionality1 disclosed technology
AnalyticsUnderstand + improveAvailable when configured and accepted
MarketingAdvertising technologies, if usedNot currently used

Technology	Provider	Category	Purpose	Where used	Control
Dryvn consent preference	Dryvn	Strictly necessary	Remember the visitor’s optional browser-technology choices.	Public website	Always active
Dryvn session and security mechanisms	Dryvn	Strictly necessary	Authenticate users, protect requests, refresh sessions, and maintain secure account access.	Authenticated Dryvn application	Always active when using the service
Google Calendar Appointment Scheduling	Google	Functional	Allow prospective customers to schedule a Dryvn demo.	/contact	Loads with the scheduling page

Known first-party and provider-controlled storage

dryvn_consent: Local storageUntil cleared or the consent version changes
Credential session, refresh marker, and CSRF cookies: First-party cookiesSession or as set by the authentication service
Provider-controlled: Third-party browser technologyControlled by Google

Third-party providers control their own implementation and may change individual cookie names. Dryvn does not invent a fixed provider-cookie list where it cannot reliably guarantee one.

No invisible third-party technology. A technology should have a defined provider, purpose, category, load location, and consent rule.

Strictly necessary technologies

Strictly necessary technologies support functions such as authentication, secure sessions, request protection, routing, service state, and remembering the visitor's consent choice. They remain available because disabling them may prevent a requested service or security control from working.

The authenticated Dryvn application uses credentialed cookies and related session markers to maintain and refresh access and support cross-site request-forgery protection. Access and refresh tokens are not stored in browser local storage.

Rejecting optional analytics does not prevent sign in, account security, trial use, subscription access, or other necessary service operations.

Embedded services

Dryvn uses Google Calendar Appointment Scheduling on the Contact page to let visitors book a demo. The scheduling interface is served directly by Google inside a cross-origin embedded frame. Google may use cookies or similar technologies required to provide its scheduling service.

The scheduler loads immediately on the Contact page under the current product decision. Booking details may be included in Google Calendar and meeting confirmations, and a Google Meet link may be generated.

Dryvn does not add analytics tracking to the information entered inside the Google booking interface and does not inspect the iframe contents.

Book a Dryvn demo Google Privacy Policy

Google Analytics

Dryvn's public website supports Google Analytics to understand how visitors use the website, which pages are useful, how people navigate, and how the website performs. This helps Dryvn improve the experience and understand the effectiveness of its marketing.

Google Analytics is optional. It loads only when a real Measurement ID is configured for the deployment and the visitor has granted Analytics permission. Without both conditions, the external analytics script is not loaded.

Analytics permission grants analytics storage only. Advertising storage, advertising user data, and advertising personalization remain denied.

What Dryvn does not send to marketing analytics

Dryvn does not intentionally use Google Analytics to send workforce records, authentication credentials, booking-form contents, prospect form contents, tenant identifiers that directly identify a customer, or other application data that belongs inside the Dryvn platform.

Marketing page locations sent to Analytics omit query strings and fragments. The analytics foundation is limited to public marketing routes and is not automatically extended into the authenticated Dryvn HCM application.

No employee or contractor records
No names, email addresses, phone numbers, or form contents
No authentication tokens or credentials
No Google Calendar appointment selections or booking fields
No sensitive application activity
No advertising audiences or behavioral profiles

Advertising and marketing technologies

Dryvn does not currently use advertising pixels, behavioral-targeting cookies, retargeting audiences, or cross-site advertising measurement. The internal architecture supports a Marketing category so any future technology must be classified and disclosed before it is introduced; the absence of a public toggle reflects that no such technology is currently active.

Payment technology

When Stripe payment functionality is configured, Stripe payment and fraud-prevention technology loads only where a customer initiates the relevant checkout or billing transaction. It is not loaded across ordinary marketing pages.

Technology needed to execute and secure a requested payment is strictly necessary for that transaction and remains separate from optional analytics. Rejecting Analytics does not prevent a customer from paying for Dryvn.

Your choices

Visitors can accept optional Analytics, reject optional technologies, or reopen Cookie settings later. Browser controls may also be used to clear first-party storage or block third-party storage, although blocking technologies needed for an authenticated or explicitly requested feature may affect that feature.

A saved choice prevents the first-visit banner from repeatedly appearing. Analytics defaults to off until permission has been granted.

How Dryvn governs third-party technology

Third-party scripts and embeds must not be added casually. Before a technology is introduced, Dryvn should identify the provider and business purpose, define the data and consent category, limit where it loads, update the central registry and this disclosure, review Content Security Policy, and test behavior when optional permission is denied.

Identify provider and business purpose
Define the information and consent category
Limit the pages or service context where it loads
Update the central browser-technology registry
Review browser-security policy and external origins
Verify that sensitive information is not transmitted
Test the experience with optional permission denied

Future technologies

Dryvn may introduce additional technologies as the website and service evolve. When their use materially affects this notice or the choices available to visitors, this page, the technology registry, and the relevant controls will be updated.

Potential future purposes may include payment security, service diagnostics, support, product analytics, feature delivery, or customer communications. This statement does not authorize undisclosed tracking or make those technologies currently active.

Changes to this Cookies Notice

We may update this notice as Dryvn, its browser technologies, or applicable requirements change. The latest version will be published on this page with an updated revision date. A material change to optional categories or purposes can be handled through the consent-policy version so an updated choice can be requested where appropriate.

Questions about cookies or browser technologies

Dryvn is operated by AAALABS TECHNOLOGIES LTD, company number 17270081, registered in England and Wales. Use the Contact page if you have questions about the technologies described here or how optional Analytics choices are applied.

Contact Dryvn