Velora Legal

Cookie Policy

How Velora uses cookies, local storage, SDKs, pixels, device identifiers, and similar technologies across the website, marketplace, dashboards, mobile apps, widgets, and white-label experiences.

Last Updated

March 9, 2026

Applies To

Website visitors, marketplace users, business customers, staff users, and mobile app users

This Cookie Policy explains how Velora and certain partners use cookies and related technologies when you visit Velora-operated websites, use booking widgets, access the dashboard, interact with white-label pages hosted by Velora, or use Velora mobile experiences and integrations.

Because Velora supports both direct Velora properties and customer-configured experiences, some technologies are set by Velora and some are set by integrations chosen by a business customer.

Policy Snapshot

  • Some cookies are strictly necessary for login, security, booking continuity, and core product operation.
  • Optional analytics, advertising, and integration cookies may vary by page, customer deployment, and consent settings.
  • Velora may also use local storage, device identifiers, SDKs, and push tokens in addition to browser cookies.
  • Blocking essential technologies can break login, booking, and checkout functionality.

Section 01

What these technologies are

Cookies are small text files placed on your browser or device that allow websites and applications to recognize a device, remember information, and perform functions across sessions.

Velora may also use local storage, session storage, tags, pixels, scripts, software development kits, device identifiers, push tokens, and log-based signals that serve similar purposes even if they are not technically browser cookies.

Section 02

Why Velora uses them

  • Authenticate users and maintain secure sessions.
  • Protect accounts, detect fraud, prevent abuse, and support incident response.
  • Remember language, interface, booking, cart, or workflow preferences.
  • Preserve progress through booking, registration, and payment flows.
  • Measure performance, diagnose errors, and understand how users interact with the product.
  • Enable optional analytics, attribution, advertising, remarketing, and integration features.

Section 03

Categories of technologies we may use

  • Strictly necessary technologies used for core website, marketplace, dashboard, payment, booking, authentication, load balancing, and security functions.
  • Preference technologies used to remember language, locale, display settings, saved choices, recent searches, or workflow continuity.
  • Performance and analytics technologies used to understand traffic, feature usage, funnel behavior, reliability, and product adoption.
  • Communications and engagement technologies used to measure the delivery or effectiveness of emails, notifications, booking journeys, and campaigns.
  • Advertising and attribution technologies used by Velora or by a business customer to measure campaigns, retarget users, or optimize acquisition where permitted and configured.

Section 04

Managing cookies and similar technologies

  • Adjust browser settings to block or delete cookies.
  • Use device settings to reset mobile advertising identifiers or limit tracking where available.
  • Use in-product controls, consent banners, or unsubscribe links where provided.
  • Disable non-essential integrations at the business or workspace level if you administer a Velora deployment.
Blocking all cookies or local storage may break login, booking, checkout, language preferences, and security checks.

Section 05

Updates and contact

We may update this Cookie Policy when Velora changes its technology stack, consent practices, integrations, or legal obligations.

Questions about this Cookie Policy may be sent to support@velora.app.