Point your iPhone camera at the code. It opens VNTG on the App Store.

Open the download page instead

Legal

Cookies Policy

Last updated November 4, 2026

Jump to a section
  1. The short version
  2. 1What this policy covers
  3. 2What cookies and similar technologies are
  4. 3We set no cookies
  5. 4We count visits, with no cookie and nothing stored
  6. 5What we do count
  7. 6The contact form
  8. 7Third-party content, and when it loads
  9. 8What we do not do
  10. 9Your choices
  11. 10Changes to this policy
  12. 11Related policies and contact
  • Applies to: the VNTG website at https://www.vntg.app (the “Website”). It does not cover the VNTG apps, which do not use cookies (see §1).
  • Provider: VNTG Hub LLC (“VNTG”, “we”, “us”, “our”), 575 Fifth Avenue, 14th Floor, New York, NY 10017, USA
  • Companion: how we handle your data overall is in our Privacy Policy.

The short version

  • This website sets no cookies. None. Not for advertising, not for analytics, not even to remember a preference. Nothing is written to your browser when you read these pages. We do count visits (§4), but with nothing stored on your side. The one thing that behaves like a tracker is the pixel on the private pages we send to a named person, and §5 says exactly what it records.
  • Because we set nothing, there is no cookie banner to dismiss and nothing to consent to. If that ever changes, we will ask first where the law requires it, and update this page.
  • We count visits ourselves, with no cookie and nothing stored in your browser, and with no analytics product and no third party involved. We can tell which pages are read and which buttons are tapped. We cannot tell who you are, and the code that counts you as one visitor is thrown away every night (§4).
  • On the public pages, nothing reaches another company unless you act: tapping a download button, which we count without identifying you; opening a video on YouTube; sending the contact form. Three things happen with no action from you, all of them to our own domain: opening a page sends the visit count of §4, our server logs the request your browser makes, as any web server does, and opening one of the private pages we send directly tells us it was opened (§5).
  • We do not show you ads, track you across other sites or apps, build a profile of you, or sell your data. Same as the app.

1. What this policy covers

This policy explains cookies and similar technologies on the VNTG website (vntg.app), including the marketing pages, the tutorials and these legal pages.

The VNTG apps do not use cookies. They are native applications: they keep settings and an anonymous identifier on your device, as described in our Privacy Policy, and they load no web-tracking technology. If you only use VNTG through the app, this policy does not affect you.

2. What cookies and similar technologies are

A cookie is a small text file a website stores on your device so it can recognize your browser and remember information between pages or visits. “Similar technologies” include local storage, session storage and tracking pixels (a tiny image whose only job is to record that something was opened). We use “cookies” in this policy to cover all of them.

3. We set no cookies

Verified against the live site on 2026-11-01:

  • No cookies, first-party or third-party. No response from the site, including the redirect that handles download links, sets one.
  • No local storage, no session storage, no database in your browser. The site keeps nothing between pages or visits.
  • No tag manager, no consent tool, no third-party tracking script. The site is a static, hand-built site with no third-party JavaScript file of any kind. The only scripts are a few lines inline on the page. One of them reports a visit to our own domain, exactly as §4 describes; none of them stores anything in your browser, and none of them belongs to another company.
  • No third-party fonts. Fonts and images are served from our own domain.

One exception to be explicit about, because §2 deliberately defines “cookies” widely enough to include pixels: the private pages we send to a named person carry a tracking pixel, and §5 describes it. No public page on this site carries one.

If you remember an earlier version of this page that listed strictly necessary, functional and analytics cookie categories, promised a consent banner and a cookie settings link, and said we honor Global Privacy Control, that text described a setup this site does not have. It has been removed. An older version also mentioned advertising and targeting cookies and the NAI and DAA ad-industry opt-outs; we have never run ads, and that text is gone too.

The Website counts its own visits. Not with an analytics product: there is no Google Analytics, no Meta pixel, no tag manager and no third-party script here. It is a few lines of script already on the page that send one short message to our own domain when you open a page, and one more when you tap a button we count.

Each message records this, and nothing else:

  • which page you opened, as a path such as /pricing;
  • for a tap, which button it was, as a plain label such as store-hero, or the domain a link is taking you to;
  • the domain of the site you came from, when you arrived from somewhere else. The domain only, never the full address, and nothing at all when you come to us directly;
  • the campaign tag the link carried, if it had one (utm_source);
  • whether you are on a phone or a desktop, and which system;
  • the language your browser asks for;
  • the time;
  • a short code that stands for “one visitor today”, described next.

The visitor code. To tell five visits by one person from one visit by five people, our server turns your IP address into a short one-way code, mixed with a secret and with today’s date. The code cannot be turned back into your address; we never store the address itself; and because the date is part of it, the code is a different one tomorrow. So we can count visitors within a day, and we cannot recognize anyone the day after. That is the trade we chose on purpose. People sharing one address, a household or an office, count as one visitor, which we prefer to a code that reads more of your browser than this one needs.

What that lets us see, and what it does not. We can see that a page was read, which pages are read most, which site sent a visit and which buttons get tapped. We cannot see who you are, we cannot follow you from one day to the next, we cannot follow you to any other site, and we build no profile. Nothing in these records links to a person, an account or an app install.

Do Not Track is honored. If your browser sends the Do Not Track signal, the script sends nothing at all. We also drop what we recognize as bots and link previewers, so they are not counted.

Where it goes, and for how long. The records go to our own backend, the same provider that carries the contact form (§6), and nowhere else. No third party receives them. We delete records older than 400 days, automatically.

Why there is still no banner. This counter writes nothing to your device: no cookie, no local storage, nothing that can be read back on a later visit. There is no stored data for you to consent to or to withdraw (§9). We run it on the basis of our legitimate interest in knowing whether the site does its job, and we have held it to the smallest set of data that answers that question.

What we learn about the product itself, we learn inside the app, from the anonymous analytics described in our Privacy Policy.

5. What we do count

Besides the visit counter of §4, these narrow measurements, none of which uses a cookie.

Download buttons. Every button that sends you to the app store goes through a short link on our own domain, which counts the tap. (So a tap is counted twice over: once by §4 as a button label, and once here by the link itself, which is also what counts a scan of a QR code.) We record which link was tapped, the kind of device (phone or desktop, and which system), whether you were browsing inside another app, the language your browser asks for, and the time. We do not record your IP address, we set no cookie, and there is nothing in the record that points back to you.

Private pages we send to a named person. When we send someone a private link directly, for example a press page prepared for one publication, the page contains a hidden single-pixel image that loads when the page opens and records the same coarse details as above. Being straight about the part that matters: the link is unique to the person we sent it to, so an open tells us that they opened it, which is the point of it. We use it to know whether what we sent arrived and was read. It stores nothing in your browser, we do not record your IP address, we build no profile, and we share it with nobody. Our public pages carry no such pixel.

Server logs. Our web server, and the service that handles the download redirects, keep standard request logs: the IP address of the request, the browser user agent, what was requested, and when. They exist to run the site, keep it secure and diagnose faults, they are not fed into any analytics, and we keep them no longer than 12 months.

6. The contact form

If you write to us through the form at vntg.app/contact, we receive the name, email address, topic and message you type. The submission also carries your browser user agent, the page you wrote from, and a one-way hashed version of your IP address, which exists only to stop spam and abuse: we do not store the address itself and the hash cannot be read back. We use your email address to reply and for nothing else, we do not add you to a mailing list, and we keep these messages no longer than 24 months. The form posts to our cloud backend provider, which processes it on our behalf; details are in our Privacy Policy.

7. Third-party content, and when it loads

On the public pages, the site makes no request to another company until you ask it to. The private pages of §5 are the exception: the pixel there is a request to our own domain, which redirects to the service that counts it.

  • Video. A page with a video shows a still image we host ourselves, inside a link. We embed no player, so nothing reaches YouTube while you are on this site, before or after you click. Clicking opens the video on YouTube in a new tab, and from that point YouTube’s own privacy and cookie policies apply, not ours.
  • The contact form, when you submit it, reaches our cloud backend provider (§6).
  • Download buttons send you through our own domain to the app store (§5).
  • Links to our social accounts in the footer are plain links. Nothing from those platforms loads while you are on our site, and nothing is sent to them unless you click.
  • App store badges, fonts, images and video posters are served from our own domain.

8. What we do not do

Consistent with our Privacy Policy, the Website does not:

  • use advertising or targeting cookies, or run ads at all;
  • track you across other websites or apps, or use any advertising identifier;
  • fingerprint your browser or device;
  • build a profile about you, or make decisions about you automatically;
  • sell or share your information with advertisers, ad networks or data brokers.

9. Your choices

  • There is nothing stored to consent to. We set no cookies and no other non-essential storage, the private pages of §5 included, so there is no banner and no choice of yours to record or withdraw. If we ever add anything non-essential, we will ask for your consent first where the law requires it, list it here, and give you a way to change your mind.
  • Do Not Track. If your browser sends it, the visit counter of §4 sends nothing. It is the one signal that switches a measurement of ours off, and we honor it even though nothing is stored on your device.
  • Browser settings. You can block or delete cookies for any site in your browser. Nothing on this site depends on them.
  • Opt-out signals. We set nothing that a signal such as Global Privacy Control could switch off, and we do not sell or share your data, so there is nothing for it to act on.
  • Video. Clicking a video opens it on YouTube in a new tab, where their policies apply. Staying on this page sets nothing: we embed no player, so there is nothing here to switch off.

10. Changes to this policy

We will update this policy if the Website changes or the law does. Three statements matter most, the ones in §3, §4 and §5: if we ever add a cookie, any browser storage, or a third-party analytics or advertising tool, or if the counter in §4 starts recording anything beyond the list it gives, this page and our Privacy Policy change at the same time. We will update the “Last updated” date and, for material changes, give a more prominent notice on the site.

VNTG Hub LLC, 575 Fifth Avenue, 14th Floor, New York, NY 10017, USA. Email: privacy@vntg.app Questions about cookies or this policy: the form at vntg.app/contact, or, if you use the app, Settings → Support.

Contents