1. Who we are
This website is run by Pingle Software LTD, a private company limited by shares, registered in England and Wales. Our company number and registered office are on our company details page. "We" and "us" mean Pingle Software LTD.
You can contact us through our contact page.
2. Summary
- The Pingle website uses three first-party cookies. That's all.
- No advertising, analytics or third-party cookies. Nothing loads from another company's servers.
- The
consentcookie is set only when you make a choice in our cookie notice, and it only remembers that choice. - Some pages also read a few settings from your browser to run a live demonstration. What they read stays in your browser (section 6).
- You can change your mind at any time with "Cookie settings" in the page footer.
The Pingle apps and the Telegram Mini App are covered in section 9.
3. What the law requires
Regulation 6 of the Privacy and Electronic Communications (EC Directive) Regulations 2003 ("PECR") says a website may store information on your device, or read information from it, only if:
- you have been given clear and comprehensive information and have consented; or
- one of the exceptions in Schedule A1 to PECR applies. Section 112 of the Data (Use and Access) Act 2025 added this schedule, in force since 5 February 2026.
The exceptions include technology that is strictly necessary for a service you asked for (Schedule A1, paragraph 4), such as recording your selections. They also include technology that adapts the website's appearance or functions to your preferences (paragraph 6). That exception applies only if you are told about it and given a simple, free way to object.
PECR covers more than cookies. It also covers local storage, and reading settings from your browser with scripts.
4. Our cookie notice
Our cookie notice offers three categories:
| Category | What our notice says | Can you turn it off? | What we actually use it for |
|---|---|---|---|
| Necessary | "Required for the site to work; cannot be turned off." | No | The consent cookie, which remembers your cookie choice |
| Functional | "Remember your choices — such as your colour scheme." | Yes | The notice lists the colour scheme here. See sections 5.2 and 5.3 for how the colour-scheme and language cookies work today |
| Marketing | "Not in use yet. Before we add any, we'll update our policy and ask you again." | Yes | Nothing. We use no marketing, advertising or analytics technology, whether or not you accept this category |
If we ever add marketing or analytics technology, we will update this policy first, ask you again, and use it only if you agree then: an answer given to this category before will not count.
Who is asked. The notice appears automatically to visitors from the UK, the EEA or an unknown country, based on the country our network edge works out from the IP address. Visitors elsewhere are not shown it automatically but can open it from the footer.
5. Cookies we use
5.1 Necessary
| Name | Type | Purpose | What it stores | Duration | Set by | Exception relied on |
|---|---|---|---|---|---|---|
consent | First-party HTTP cookie | Records your cookie choice so we respect it and don't ask again on every page | necessary plus the categories you accepted, separated by commas: necessary, necessary,functional, necessary,marketing or necessary,functional,marketing. No identifier | 180 days from your last choice | Our server, when you press Accept all, Reject all or Save | Strictly necessary (Schedule A1, paragraph 4): recording your selection |
Technical attributes: HttpOnly (scripts on the page cannot read it), SameSite=Lax, Path=/, and Secure whenever the site is served over HTTPS.
Why it is exempt. The site needs to remember your choice, or it would ask again on every page and could not honour a "Reject". The cookie contains no identifier and is used for nothing else. It is set only after you make a choice.
5.2 Colour scheme
| Name | Type | Purpose | What it stores | Duration |
|---|---|---|---|---|
theme | First-party cookie | Remembers your colour scheme (System, Light or Dark), so our server can send the page in that scheme without a flash | auto, light or dark | 180 days from your last choice |
The page's script writes this cookie in your browser only when you use the theme switch in the footer. Choosing System stores auto (follow your device's setting). It contains no identifier and is used for nothing else.
Earlier, the site also kept this setting in your browser's local storage (leptos-use-color-scheme). The page's script now deletes that entry if it finds it, and no longer creates it.
How it relates to the notice. Our cookie notice lists the colour scheme under Functional. At present, this cookie is written whatever you choose in the notice: switching Functional off does not stop or remove it. We treat it as adapting the website's appearance to your preference (Schedule A1, paragraph 6).
How to object. Do not use the theme switch: until you do, nothing is stored, and the site follows your device's light or dark setting. If you have already used it, delete the cookie in your browser's settings.
5.3 Language
| Name | Type | Purpose | What it stores | Duration |
|---|---|---|---|---|
lang | First-party cookie | Remembers the language you picked, so the home page (and the documentation's home) opens in it next time | ru, en, ar, fa or zh | 180 days from your last choice |
The page's script writes this cookie in your browser only when you pick a language in the language menu (in the footer, or on the sign-in page). Our server reads it only when you open the bare home address (/) or the documentation's home (/docs), to send you to that language; every other address opens in the language it names. It contains no identifier and is used for nothing else.
How it relates to the notice. Like the colour-scheme cookie, it is written whatever you choose in the notice. We treat it as adapting the website to your preference (Schedule A1, paragraph 6).
How to object. Do not use the language menu: until you do, nothing is stored, and the home page follows your browser's language (section 6.4). If you have already used it, delete the cookie in your browser's settings.
5.4 Marketing
None. We do not use advertising, retargeting, analytics, session-recording or social-media technology.
6. Reading information from your browser
6.1 The "What the site sees" connection check
To show what websites can learn about visitors, some of our pages, including the home page, work out how likely it is that you are using a VPN or proxy. This runs automatically when the page opens. The page:
- Sends a request to our checker at
ip.pingle-family.com. It returns your public IP address, country, city, network operator and approximate longitude. This is an ordinary web request. It stores nothing on your device and sends no cookies. Our Privacy Policy (section 4.2) explains what happens to the data. - Reads settings from your browser: your time zone, your clock's offset from UTC, your preferred languages, and your browser's own list of time zones for your country.
- Compares them in your browser to produce the result ("No signs", "Possible" or "In use") and a percentage.
Nothing from steps 2 and 3 is sent to us or stored. The reading happens on your device, and the result stays on your screen.
If you do not want this to happen, you can turn off JavaScript for our website, or block requests to ip.pingle-family.com, in your browser. The rest of the page still works.
6.2 Choosing an illustration for your region
One product illustration shows a local-services example for your likely region. To pick it, the page reads your browser's language and time zone and chooses a country from a short list. This happens only in your browser. Nothing is stored, and nothing is sent to us. If you turn off JavaScript for our website, the illustration shows its default example.
6.3 Country for the cookie notice
Our network edge adds your country (a two-letter code worked out from your IP address) to each request. We use it only to decide whether to show the cookie notice, and our web application does not store it. This involves no storage on, or reading from, your device.
6.4 Language of the home page
When you open the bare home address (/) or the documentation's home (/docs) with no saved language, our server reads the languages your browser sends with each request (the Accept-Language header). It opens the version in the first of our five languages your browser lists, in its order of preference; if none is listed, or your browser sends no list, you get English. Nothing is stored, and our web application does not keep the header.
7. How to change or withdraw your choice
- On our site: click "Cookie settings" in the footer. The notice reopens with your current choices. Change them and press Save, or press Reject all. Withdrawing is as easy as giving consent.
- In your browser: you can delete cookies and local storage for our site, or block them altogether. Your browser's help pages explain how. The site still works. You will just be asked about cookies again, the colour scheme will follow your device, and the home page will follow your browser's language.
We ask again when your consent cookie expires (after 180 days), or earlier if we change the technology we use.
8. Third parties
No third party stores or reads information on your device through our website. We host our fonts, scripts (including Anime.js and Chart.js) and images ourselves.
9. Apps and the Telegram Mini App
- Pingle VPN apps are not yet released. When they are, they will store your account credentials, settings and routing preferences on your device, because the app needs them to provide the VPN you asked for. We will describe any other technology the apps use in this policy before they are released.
- The Marketplace Telegram Mini App runs inside Telegram. Telegram's own policies cover the storage Telegram provides.
10. Changes
We will update this policy whenever we change the technologies we use, and ask for your consent again where needed. The date at the top shows when it was last reviewed.
11. Contact
Questions: through our contact page. For more about your rights, and how to complain to us or to the ICO, see our Privacy Policy.