Legal

Cookie Policy

Last updated: 6 October 2026

Change your cookie choice

You have not chosen yet.

1. Who we are

This Cookie Policy explains how David Lander, trading as “Jomioz” (“Jomioz,” “we,” “us,” or “our”), uses cookies and similar technologies on jomioz.com and related marketing pages.

  • David Lander, trading as “Jomioz”
  • Tax ID (NIF/NIE): Y8422959M
  • Address: Calle San Isidro, 2 - La Orotava - Tenerife - Spain
  • Contact: info@jomioz.com

Full imprint: https://www.jomioz.com/legal. How we use personal data more broadly is in our Privacy Policy. This page is the detailed notice for cookies and similar technologies (including localStorage, pixels, and tags).

2. What cookies and similar technologies are

Cookies are small text files stored on your device. We also use similar technologies such as localStorage, sessionStorage, pixels, and software development kits (SDKs) that read or write identifiers on your device or in your browser.

We group them as: (a) strictly necessary — needed to run the site or the product, keep it secure, or remember your cookie choice; (b) analytics — to understand how the website and the product are used, including session replay to reproduce errors; and (c) advertising measurement and attribution — to measure ads and related conversions. Analytics and advertising measurement run only after you accept, on the website and in the product alike.

4. Strictly necessary

These are used to operate the site, keep it secure, and remember your cookie choice. They do not require consent under EU/UK ePrivacy rules, but you can still block them in your browser — that may break language, forms, or sign-in.

  • Cookie-choice storage (localStorage key jomioz-cookie-consent and first-party cookie jomioz_consent, up to 180 days) — remembers Accept or Decline.
  • Hosting and security cookies set by our site host (Vercel) or the browser as part of delivering the page.
  • On the Jomioz product (app.jomioz.com and the mobile app), authentication, locale, and session cookies are necessary to sign you in and keep the Service working.

5. Analytics (after you accept)

If you accept, we use PostHog on the website and in the signed-in product to measure page views, feature usage and product-interest events (for example trial clicks). PostHog is configured to persist with localStorage and a cookie. In the product we also enable Sentry Session Replay, which records masked page activity so we can reproduce errors; it stays off until you accept.

Separately, we use Vercel Web Analytics and Speed Insights on the website for aggregated traffic and performance. They set no cookies, store nothing on your device and keep no persistent or cross-site visitor identifier, so they do not need consent under EU/UK ePrivacy rules; we rely on legitimate interests for those aggregate counts. They are not used for advertising.

Error reports sent to Sentry without session replay (technical error details, no cookies) are sent to keep the Service secure and reliable and are not switched by the banner.

6. Advertising measurement (after you accept)

If you accept, we may load Google Analytics, Google Ads (including conversion tags), Meta Pixel (Facebook), and Meta’s Conversions API (server-side events). Typical identifiers include _ga, _gid, _gcl_au, _fbp, and click IDs such as gclid or fbclid. Meta page views on the marketing site run only after you accept, and never when your browser sends Global Privacy Control.

After you create a Jomioz account, we send Meta a registration event. When you create an organisation, the 14-day trial starts with no card, and we send Meta a trial event. Those use the click id stored from your visit and a hashed email. We send them from our server and, on the product app, from the browser with the same event id so Meta counts each once. The product app does not send Meta a page view on ordinary screens. Those account events are sent only when you have accepted advertising cookies and your browser does not send Global Privacy Control. If you declined, or GPC is on, we do not send them and do not store the click id.

This helps us measure visits, trial clicks, and ad performance. Under the CCPA/CPRA this may be “sharing” for cross-context behavioral advertising. We do not sell personal information for money.

You can also use Google’s ad settings and Meta’s ad preferences, and industry opt-outs such as youradchoices.com or youronlinechoices.eu, in addition to declining on our banner.

7. Product analytics (the signed-in Service)

The Jomioz web app shows the same banner. PostHog product analytics and Session Replay in the signed-in Service, and the storage of campaign attribution, run only after you accept; we do not treat them as strictly necessary because the Service works without them. Signing in, security, language and billing do not depend on them. Server-side records the Service keeps to operate your account (for example subscription lifecycle events tied to your workspace, and security and audit logs) are part of providing the Service and are described in the Privacy Policy.

8. Technologies we use

Names and lifetimes can change when a vendor updates their tag. This table reflects what we intend to use today.

Name / techProviderPurposeLegal basisTypical life
jomioz-cookie-consent (localStorage); jomioz_consent cookieJomiozRemember Accept / Decline across jomioz.comNecessaryUp to 180 days
jomioz:attr:v1 (session/localStorage); jomioz_attr cookieJomiozCampaign / landing attributionConsent (not stored under Global Privacy Control)Session; ~90 days
PostHog cookie + localStoragePostHog (EU)Website and product analytics, after acceptConsentVendor default (often up to 1 year)
Sentry Session Replay (product app)SentryMasked recordings to reproduce errors, after acceptConsentSession
Vercel Analytics / Speed InsightsVercelAggregated traffic and performance (cookieless, no device storage)Legitimate interests (no consent needed: nothing is stored on your device)No cookie
_ga, _gid, _gcl_* and similarGoogleAnalytics and ads measurement after acceptConsentUp to ~2 years (vendor)
_fbp, _fbc and similarMetaMarketing pixel and registration / trial events, after acceptConsent (not under Global Privacy Control)Up to ~90 days (vendor)
Session / auth / locale cookiesJomioz (product)Sign-in, security, language in the ServiceNecessarySession or as needed for auth

9. How to change or withdraw, and Global Privacy Control

Use the controls on this page, or “Cookie preferences” in the website footer and the product menu, to accept, decline, or show the banner again. Declining or withdrawing stops PostHog and Session Replay and removes the attribution we stored; it does not affect processing before you withdrew. You can also delete cookies and site data in your browser settings. Blocking strictly necessary storage may stop the site or sign-in from working.

Global Privacy Control: if your browser or an extension sends the Global Privacy Control signal, we treat it as a request to opt out of the sale or sharing of personal information and of targeted advertising (CCPA/CPRA and similar laws). We then do not load Meta Pixel or Google Analytics / Ads, do not send Meta Conversions API or Google Ads conversion events, and do not store ad-click attribution, even if you accept analytics. The banner and this page show when the signal is detected. The signal applies to the browser it is sent from.

California and similar US state residents can also email info@jomioz.com with the subject “Do Not Sell or Share.”

Other browser “Do Not Track” signals are not consistently implemented; we treat the banner choice, Global Privacy Control, and a Do Not Sell or Share email as the controls that apply.

10. Changes and contact

We may update this Cookie Policy when vendors or our practices change. We will post the new version here and update the “Last updated” date.

Questions: info@jomioz.com. See also our Privacy Policy, Terms of Service, Subprocessors list, and legal notice.