Cookie Policy

Cookies are small text files stored on your device when you visit a website. They allow the website to remember information about your visit, such as your login state and preferences.

Cookies can be "session" cookies, which are deleted when you close your browser, or "persistent" cookies, which remain until they expire or you delete them manually. Cookies set by the website you are visiting are called first-party cookies. Cookies set by other services embedded in the page are called third-party cookies.

We may also use browser storage mechanisms — localStorage and sessionStorage — to store small pieces of data on your device. These are not cookies, but serve a similar purpose and are covered in this policy.

Verimly only uses essential cookies on the platform itself. These are strictly necessary for the platform to function — they handle authentication and remember your consent choice. We do not use advertising, analytics, or any optional tracking cookies on verimly.com.

The table below lists every cookie set on the Verimly platform.

In addition to cookies, Verimly stores one item in your browser's local storage. This is not a cookie and cannot be read by third parties — it is only accessible by verimly.com.

The key stored is "theme", which remembers your light or dark mode preference across visits. This data is stored persistently in localStorage and is essential to the platform experience.

Verimly powers public event storefronts for independent organizers. These storefronts are separate from the Verimly platform and may use different cookies depending on what each organizer has configured.

When you visit an event storefront, a cookie consent banner will appear listing the specific cookies that storefront uses. Organizers may optionally connect their own analytics tools (such as Google Analytics) or advertising pixels (such as Meta Pixel). These third-party scripts are only loaded after you give explicit consent via the banner.

The organizer is the data controller for cookies placed on their storefront. Each storefront links to its own cookie policy for full details on what is collected and why.

Essential storefront cookies include:

• cc_cookie — stores your consent preferences for that storefront (essential, first-party)
• vly_session_id — anonymous visitor session ID stored in sessionStorage (not a cookie)
• sf_cart_ref_{slug} — your cart reference stored in localStorage for checkout continuity
• sf_checkout_contact_{slug} — pre-filled contact info stored in localStorage to speed up checkout

If the organizer has connected Google Analytics, the cookies _ga and _ga_* may also be set with your consent. If Meta Pixel is connected, _fbp and _fbc may be set with your consent.

Verimly does not set any third-party cookies on the platform itself (verimly.com). Third-party cookies may appear on event storefronts only when the organizer has configured them and you have given consent.

Currently supported third-party integrations available to organizers:

• Google Analytics — sets _ga and _ga_* cookies for anonymous usage analytics (analytics category)
• Meta Pixel — sets _fbp and _fbc cookies for advertising measurement (marketing category)

Both integrations are optional and disabled by default. They are only activated if the organizer explicitly connects them through their workspace settings, and only loaded when you consent via the cookie banner.

You can update your cookie consent at any time by clicking "Manage preferences" in the cookie banner on any storefront. Platform cookies on verimly.com are all essential and cannot be disabled without breaking the service.

Most browsers also let you control or delete cookies through their settings. Common options include:

• Blocking all cookies — note this will prevent you from signing in to Verimly
• Deleting cookies on browser close — session cookies will be removed automatically
• Allowing cookies from specific sites only — you can whitelist verimly.com
• Using private/incognito mode — cookies and localStorage are cleared when the window closes

Instructions for managing cookies vary by browser. Refer to your browser's help documentation for details.

We may update this Cookie Policy from time to time to reflect changes in the cookies we use or for other operational, legal, or regulatory reasons. The date at the top of this page shows when it was last revised.

We will notify you of any material changes by posting the new policy on this page and, where appropriate, by notifying you via email or through the platform. We encourage you to review this policy periodically.

If you have questions or concerns about our use of cookies or this Cookie Policy, please contact us: