Legal

Cookie policy

Last updated 16 October 2026

How we use cookies

BYTEWORKS DIGITAL SERVICES S.L. uses cookies and similar storage on voloomcad.com. This notice is the cookie policy required under the ePrivacy Directive and Spanish LSSI-CE. See also the privacy & user policy.

You can change your choice at any time: .

Strictly necessary

These run the service. They do not need consent. We do not use them for advertising.

  • voloom_session — first-party, HttpOnly, about 30 days. Keeps you signed in after the email link. Set when you open that link. It does not wait for Accept.
  • A print you asked to customize is stored on the sign-in link on our server, then copied into your library when the link is opened. That is part of signing in, not an analytics cookie, and it is not kept in browser storage.
  • voloom:consent — first-party local storage. Remembers Accept or Reject so we do not ask on every visit.

First-party audience measurement

This is not a cookie. On each page view our API counts the path and, for that UTC day only, whether we have already seen this visitor. For people who have not signed in and have not accepted analytics, we hash a truncated IP with the browser string and a salt that expires with the day. We do not store the IP or the hash after that. A Global Privacy Control signal skips the hash. After you sign in we count the account instead of the hash. After you Accept we also set the visitor id below, so changing network does not mint a second unique that day.

Free tool limit

This is not a cookie either. Without an account, the free tools at /tools allow 3 runs a month. Our API counts them against a one-way hash of your truncated IP, your browser string, and the month. Nothing is written to your device, and the count is deleted the day after the month ends. Signing in removes the limit.

Analytics (optional)

Only if you Accept. We load product analytics after that choice — never before. We send page views and product events (sign-in, generate, checkout, download, share, viewer controls). We do not send the text of your prompts. With Accept we also load the Meta Pixel so we can measure ad sign-ups; the browser cookie does not include your email.

Google Analytics 4 (measurement id G-WFWEMG1KXE) from googletagmanager.com. Google LLC (United States) is the processor. Transfers rely on the EU–US Data Privacy Framework or Standard Contractual Clauses. Advertising features and Google signals are off.

PostHog (project 306578, EU Cloud at eu.i.posthog.com). PostHog Inc. is the processor; EU hosting keeps event data in the EU. With Accept we also enable heatmaps, dead-click capture, and session replay. Replay masks every form field (including prompts) and any element marked for masking.

Meta Pixel (Facebook) from connect.facebook.net when a pixel id is configured. Meta Platforms Ireland Limited is the processor for EEA users. We use it for conversion measurement (sign-up, first successful prompt, and paid plan), not for building retargeting audiences from Reject visitors. On those events our API also sends a hashed email to Meta's Conversions API so the same action can be attributed when the Pixel is blocked. If you accept, we store the Meta click ids on the account so a later prompt or payment can be tied to the ad.

  • voloom:visitor — first-party local storage, until you Reject. Distinguishes browsers for our own daily counts after Accept. Deleted if you Reject.
  • _ga — Google, about 2 years. Distinguishes browsers.
  • _ga_WFWEMG1KXE — Google, about 2 years. Session state for this property.
  • ph_* — PostHog cookies and local storage for distinct id, session, and replay. Cleared when you Reject.
  • _fbp / _fbc — Meta, about 3 months / click window. Browser id and click id for ad attribution. Cleared when you Reject.

Rejecting analytics never loads those scripts. Changing from Accept to Reject stops capture and deletes the Google, PostHog, and Meta cookies we can reach. Notices: policies.google.com/privacy, posthog.com/privacy.

Other storage

The app also keeps a few first-party preferences in local storage (history panel open, a pending plan after sign-in). Those are not tracking cookies.

Contact

Questions about cookies: info [at] voloomcad.com.