Cookie Policy

What a cookie is here for

A cookie is a small file a site asks your browser to keep and send back. This page lists every category of cookie or browser storage that zeoob.com uses, and who sets it.

What is running right now

Running on this site right now, written by the site itself from the switches that load each script:

• Google reCAPTCHA — tells a person from a script on the contact form and the verification tool. Cookies: _GRECAPTCHA
• Google Analytics 4 — counts visits and which tools get used. Cookies: _ga, _ga_*
• Google AdSense — chooses and measures the ads. Cookies: __gads, __gpi, IDE, NID

The rest of this page describes each of those services and what it sets when it is in use.

Ours

• Browser storage, not cookies. Your drafts, your saved work as a guest, and small preferences such as which tab you last used and whether you have closed the cookie notice are kept in localStorage on your device. Nothing there is attached to a request the way a cookie is, and we do not send it anywhere. We will not claim it is unreadable, though: localStorage is readable by any script running on this site, ours included. What stops it leaving is that nothing we ship sends it — until you sign in and ask us to sync it, which uploads the projects you have saved so you can open them on another device. Guest drafts are never uploaded. One more thing lives there: a random code, created the first time you rate a tool and sent only with a rating, so that each browser can rate each tool once. It is not linked to you, and we keep only a one-way hash of it.
• A comment cookie. If you leave a comment, WordPress may store the name and email you gave so you do not retype them next time. It lasts a year and is set only if you comment.
• Login cookies. If you create an account and log in, cookies keep you logged in. They exist only while you have an account and are removed when you log out.

None of these follow you to another site, and none are used to build a profile of you.

Analytics

When analytics is on, it is Google Analytics 4, counting visits and showing which tools and pages are actually used — how we know which of the generators deserve the work. The list above says whether it is running as you read this.

It sets _ga and _ga_<id>. These are first-party cookies — set on zeoob.com rather than on a Google domain — which is worth saying plainly, because a site claiming it “sets no cookies of its own” while running Analytics is making a distinction that does not help anybody. They last up to two years and hold a random identifier, not your name.

What we look at is aggregate: page views, countries, devices, which tool was used. We do not use Analytics to identify a person, and the content of your mockups never reaches it.

You can opt out of Google Analytics across every site with Google’s browser add-on.

Advertising

When ads are on, they are served by Google AdSense, which sets cookies and may use them to choose which ads you see and to measure them. It sets first-party cookies such as __gads and __gpi, and third-party ones such as IDE and NID on Google’s own domains. Google’s policy governs that, and you can control much of it at My Ad Center.

The ad script is deliberately loaded late: a few seconds after the page, or as soon as you scroll, tap or type, so the page is usable first. There are no ads on the account pages, on the contact page, or on the legal pages, this one included.

The anti-bot check on our forms

When the anti-bot check is on, the contact form and the verification tool are protected by Google reCAPTCHA, which tells a person from a script. It sets _GRECAPTCHA on a Google domain, lasting about six months, and it reads signals about how the page was used in order to score the request.

It runs on those forms only, and it loads only once you start filling one in, so a visitor who only reads the page never gets its cookie. There is no reCAPTCHA on a tool page, so making and downloading a mockup never involves it. Google’s privacy policy and terms apply to it.

The cookie notice, and your choice

These services run whenever they are switched on; the site does not wait for an answer first. A short notice says so on your first visit and links to this page. Pressing OK or closing it only hides it: it records no choice and sets no cookie, and it remembers that you closed it in your browser’s storage, not in a cookie.

In the EEA, the UK and Switzerland, Google may also show its own consent message for the ads. It records your answer in two cookies of its own (FCCDCF and FCNEC) and passes it to AdSense.

To stop these cookies, use the controls below: block or delete cookies in your browser, install Google’s Analytics opt-out add-on, or turn off personalised ads at My Ad Center.

Turning them off

Every browser can block or delete cookies, usually under Settings → Privacy. What breaks, honestly:

• Making and downloading a mockup needs no cookie at all. Block everything and every generator still works.
• Blocking browser storage stops drafts being remembered, because that is where they live. Ratings still work; they are then counted per connection and browser instead.
• Blocking Google’s domains will stop the contact form and the verification tool from submitting whenever reCAPTCHA is on, because it cannot load. Write to support@zeoob.com instead and we will answer the same way.
• Blocking the ad script changes nothing except that the reserved space stays empty.

Questions

If something here does not match what you see in your browser’s inspector, tell us at support@zeoob.com — that is a bug in this page and we will correct it.