Privacy

This website

This site is a set of static pages describing YTS Control and linking to its published builds. As shipped, it contains:

• No analytics or product measurement of any kind
• No tracking pixels, beacons or session replay
• No advertising or marketing cookies
• No third-party embeds, widgets, chat tools or social scripts
• No account system, contact form, newsletter or comment feature

Web fonts are compiled into the site and served from the same origin, so viewing a page does not cause a request to a font provider.

Nothing on this site sends us anything about your visit. The only information that reaches the developer is what you choose to put in an email to one of the two published addresses — and mail you send is, necessarily, read and kept in a mailbox. Both published addresses are aliases handled by a mail provider, which processes messages in transit as any mail provider does. Please do not include passwords, licence keys or private network captures in an email.

Questions about this note go to contact@ytscontrol.com.

Hosting and outbound links

Whoever hosts or fronts this site can see the ordinary information present in any HTTP request — your IP address, the page requested, your user agent and the time — and may retain it in standard server or CDN logs. That is a property of web hosting rather than something this site chooses to collect, and it is outside the code in this repository.

Where this site links to a published build, the link goes to the public releases repository on GitHub, and GitHub’s privacy practices apply to that request. The Npcap link goes to npcap.com, which is likewise operated separately. While the commercial trial is being prepared, no release link is offered here at all.

• Npcap download page (opens in a new tab)

Regional pricing and currency

The pricing card can suggest which currency to show you. To do that, the server reads one request header supplied by the hosting platform. It carries an approximate two-letter country code and nothing else, it is used only to choose a display currency, and it is gone when the page finishes rendering.

• No browser location permission is requested, and the Geolocation API is not used
• No latitude, longitude, street address or city is collected, and no city is shown
• Your IP address is not read, logged or stored for pricing
• There is no database, log or file of visitor countries, and no location history
• No third-party geolocation service is called

That is not a claim that no network address is ever processed anywhere. Delivering a web page inherently depends on network addressing, and whoever hosts or fronts this site sees an IP address in the ordinary course of answering a request, as described above. What this site does with it for pricing is nothing.

Converting the price into another currency needs an exchange rate, which comes from a public reference-rate service at api.frankfurter.dev. That request is made by the server, cached for hours at a time and shared across visitors: your browser never contacts the rate provider, and the request carries no information about you. A reference rate is a published daily figure rather than a dealing rate, so any local amount shown beside the price is an estimate. The checkout is what confirms the actual currency, exchange rate, taxes and charged amount.

If you change the region or currency by hand, that choice is remembered in your browser’s local storage under yts.pricing.region and yts.pricing.currency. The two values stored are a region identifier such as GLOBAL_USD and an ISO currency code such as USD — no country, no address, no coordinates, no history. They stay on your device, are never sent back to this site, and clearing your browser storage removes them. Neither is a cookie, and neither is used to identify or measure you.

None of this decides what you pay. A displayed region or currency is a display preference: it is not proof of where you live, it is not a licence check, and it cannot set a price. The payment provider validates billing location, currency and tax itself.

The application

YTS Control runs on your computer and works on the network it is connected to. Its configuration — device identities, aliases, speed limits and domain rules — is written to a settings file on that machine, with a backup copy named settings.backup.json kept alongside it.

YTS Control stores settings and licensing information in the current user’s local application-data directory. On Windows that is a per-user application-data folder inside your user profile; on Linux, a per-user data folder inside your home directory. The exact folder name is not printed here: it is the application that decides where its own directory lives, and a path published on a website can only go stale or be wrong for the build you installed.

Automatic remote update checks are disabled in the current release, which the Preferences page states directly. To find out whether a newer version exists, visit the public releases page yourself.

What the application can observe on your network

While network control is active, YTS Control observes traffic on the local network segment in order to report per-device bandwidth and destination-domain metadata. That information is used to render the interface and to apply the rules you configure. It is not sent anywhere.

HTTPS is not decrypted. Where the network exposes them, domain names are read from DNS lookups, TLS server names and HTTP host headers. Page contents, searches, messages, form data, passwords and authentication tokens inside encrypted connections are not readable.

Use YTS Control only on networks and devices that you own or are authorised to administer. Observing other people’s traffic without authorisation may be unlawful where you live, and it is not what this software is for.

Four different kinds of information

The commercial release introduces licence activation, which means YTS Control will make a network request that earlier free builds never made. Because of that, this page keeps four categories apart, and does not claim that nothing ever leaves your computer:

• Network monitoring data — devices, bandwidth, addresses and domain activity. Read on your own network, used to draw the interface, and not transmitted.
• Local settings — aliases, limits and domain rules, written to a file on your own machine.
• Licence validation data — the small amount of information a licensing provider needs in order to confirm that a licence key is valid.
• Payment information — handled entirely by the future Merchant of Record during checkout, in a browser, and never by YTS Control.

Licence activation

Licence activation is part of the commercial release. It is not implemented in the currently published application, and no licensing provider has been selected yet, so this section describes what activation is expected to involve rather than what it does today. None of it is named after a specific provider, because there is not one to name.

A production licensing provider may process:

• The licence key you enter
• A hashed installation or device identifier
• The application version
• The platform category, such as Windows
• An activation identifier
• The licence status
• Validation timestamps
• The network address inherently used to make the request, as with any HTTP request

Validating a licence does not require sending anything about the network you manage. Specifically, none of the following is needed for activation:

• Discovered devices on your local network
• Monitored-device IP addresses
• Hardware (MAC) addresses
• Domain Activity records
• Blocked domains
• Packet contents
• Traffic history
• Device aliases
• Wi-Fi network names
• Router credentials, which YTS Control never asks for in the first place

When a provider is chosen, this page will be updated to name it and to describe what it retains. Until then, treat the list above as the intended boundary rather than as a finished description of a live system.

Payment

Purchasing is not open yet. When it opens, checkout will be operated by a Merchant of Record — a separate company that sells the licence, handles payment and issues the receipt.

Payment-card details are entered with that company and are processed by it, not by YTS Control and not by this website. The application does not see, store or transmit card data, and this site has no payment form of its own. The provider has not been selected yet, so none is named here; its own privacy terms will apply to whatever it collects, and this page will link to them once it exists.

Screenshots on this site

The screenshots come from the maintainer’s own network and are prepared before publication: hardware (MAC) addresses in the device table are blurred, and the desktop background behind the installer window is cropped away. Private RFC 1918 addresses in the 192.168.1.0/24 range remain visible because they are default, non-identifying local addresses and are central to what the images demonstrate.