Privacy Policy
Version of 14 October 2026. Covers the pingnitro.com website, the @pingnitrobot bot and the PingNitro apps for Windows and macOS. The personal data operator is the PingNitro service administration ("we"). Questions and data requests — support@pingnitro.com or @pingnitrosupport.
What we keep and for how long
| Data | What exactly | Kept for |
|---|---|---|
| Account | Telegram sign-in — Telegram id, name and username, language. Email sign-in — email address and a password hash (we never store the password itself). Google sign-in — email address and Google account id; we receive no other Google data. | while the account exists |
| Access | Personal route key, access period, assigned entry nodes, terminal and exchange chosen in the bot, the partner link code you came with. | while the account exists |
| Apps | Computer name, OS, app version, the computer's time zone (to show times in your zone), time of last request. The device token is stored on the server only as a hash. | while the account exists; a device can be signed out in your account, and a signed-out device is deleted after 30 days |
| Surveys and feedback | Your answers, the texts you sent and the contact you gave for a reply. | while the account exists |
| Payments | Amount, date, payment id and the details needed to verify the payment. | while the account exists; data that the law requires us to keep for payment accounting is kept longer, and only to that extent |
| Partner program | The code of your partner link, the number of clients who came through it, accruals and payouts, the payout details you provided. | while the account exists; accrual and payout records that the law requires us to keep for accounting are kept longer, and only to that extent |
| Refunds and decisions on requests | Records of actions taken on your payments and payouts at your request (a refund, cancelling a paid period, a decision on a payout request): account number, amount, the address the money was returned to, transfer id, outcome. | 180 days; anonymised at once when the account is deleted |
| Connections through the route | IP address the app connects from, key name, exchange address, traffic volume, line quality (latency, loss). Hourly totals for each key — number of connections, volume, latency, the most frequent exchange addresses. We do not read or store the content of your traffic. | connection log, hourly totals and line quality — up to 7 days; daily traffic volume and number of connections — 60 days |
| Suspected key sharing | If more than three different IP addresses use one key within 15 minutes, the list of those addresses is recorded: the key is personal, one key per person. | up to 7 days |
| Free period protection | A computer fingerprint: the app sends not the numbers themselves but their hashes (system board number, Windows or Mac installation number, disk or Mac serial number, the system user profile) and a virtual machine flag, and the server hashes them once more with its own secret key. Also fingerprints of the Telegram ids and emails that have already had access, a fingerprint of the email domain (only for companies' own domains — to notice many mailboxes of one domain), fingerprints (hashes with a secret key) of the IP addresses of registration, of the free period request, of app sign-in and of connections of trial accounts, and match records (which account matched which, without the values themselves). They keep the free period to one per person and computer. | computer fingerprints — 180 days from last use; Telegram id, email and domain fingerprints — 180 days from the start of the free period; match records — 180 days, account flags (“no extension”, “allowed”) — while the account exists; addresses — 30 days. After an account is deleted, the computer, Telegram id and email fingerprints are kept until the end of their period without any link to you — no name, username, email or Telegram id; the domain fingerprint, addresses and records are deleted |
| Country and city of connection | Country, region and city derived from the IP address of a connection to the key (DB-IP database); the address itself is not stored in this record. Used to follow exchange rules and to notice key sharing. | while the access is valid and 7 days after it ends; a place where nobody connected for 30 days is deleted earlier |
| Sign-ins and confirmations | Sign-in through the bot and confirmation of account actions through the bot: IP address, browser or system, approximate city, time, previous sign-in methods (so that the “Not me” button can restore them). | 7 days |
| Website | Server log: IP address, time, page address, browser. Results from the “Measure” page — latency figures only, no IP. | log — up to 7 days; measurements without signing in — 30 days; measurements from your account — the last 20, while the account exists |
| Email codes | Confirmation codes: email confirmation, two-factor sign-in, linking or changing an email (main and backup address), password reset — stored only as a hash. | 15 minutes; the counter of wrong attempts (email and time) — 24 hours |
Database backups, including those made before updates, are kept for up to 30 days, the bot’s service logs (they may contain account numbers in error messages) for up to 8 weeks, then deleted.
When you sign in with Telegram, the bot’s message shows you where the sign-in started: IP address, browser and device, and an approximate city by IP — so that you confirm only your own sign-in. The city comes from the “IP Geolocation by DB-IP” database (CC BY 4.0 license).
Why
- To sign you in to the account and apps, grant and extend access, and send route settings to the app.
- Support and fixes: find a failure, check line quality, help with setup.
- Protecting the service: sign-in attempt limits, one key per person, one free period per person and computer, node load accounting, following exchange rules (country and city of connection).
- Emails to a website account (email or Google sign-in): confirmation codes (email confirmation, two-factor sign-in, linking or changing an email, password reset) and notices about your access — “Did you connect?” after access is granted, help if there was no traffic for an hour, a reminder before access ends, and a tip about the “Poor network (UDP)” mode. The notices go only to a confirmed address, and you can switch them off with the “Send me emails about access and connection” checkbox in your profile. No newsletters, no ads. Telegram users get the same reminders as bot messages.
We do not sell data, do not share it for advertising and do not use advertising or analytics trackers on the website.
Where it is stored and who else sees it
- Accounts — on our server in Japan (AWS, Tokyo). Route nodes and the website — in Russia (Khabarovsk, Vladivostok) and Japan (AWS, Gcore, Tencent Cloud). Hosting providers do not receive data from us for their own purposes.
- Telegram — if you message the bot or sign in with Telegram (the account page loads the telegram.org login widget).
- Google — if you sign in with Google (the account page loads the Google sign-in script).
- Resend — sends our emails (codes and notices): sees the email address and the email text.
Cookies and browser storage
The website sets one cookie — your account sign-in (30 days). Your browser keeps the chosen language, terminal and partner link code.
Your rights
- To find out what we keep about you or correct it — write to support@pingnitro.com or @pingnitrosupport.
- To delete your account with all its data — use the “Delete my data” button in your account (“Sign-in and security”) or in the bot (“FAQ” → “How to delete my data”), or write to support@pingnitro.com or @pingnitrosupport. We delete within 7 days (from backups — when they expire). Payment and partner earnings records that the law requires us to keep for accounting remain without any link to you — no name, username, email or Telegram id; free period fingerprints (section “What we keep and for how long”) are kept for up to 180 days, also without any link to you.
- To withdraw your consent to data processing — by email to support@pingnitro.com, a message to @pingnitrosupport or the “Delete my data” button: after withdrawal the account is deleted as described above.
- To sign an app out of a computer — Account → “Devices”.
- To revoke PingNitro’s access to your Google account — myaccount.google.com/permissions.
The service is intended for adults. A new version of this policy is published on this page with its date.