2 Commits
Author SHA1 Message Date
esefxdzandClaude Opus 5 f28379f73f Merge branch 'docs/privacy-policy-accuracy'
Android CI / android (push) Canceled after 0s
Co-Authored-By: Claude Opus 5 <[email protected]>
2026-10-18 13:47:36 +03:00
esefxdzandClaude Opus 5 8260c7cc0a docs(privacy): correct the policy the app actually links to
The sidebar opens this file, so it is the copy users read, and it had
drifted from the service it describes.

- the device ID is stored on the phone and reused between sessions; the
  policy implied it was per-session
- "we do not sell or share any data with third parties" sat in the same
  document as the AdMob section that explains Google collects data for
  ad delivery; narrowed to what is true
- dropped the service name and journalctl invocation from the log
  paragraph; operational detail nobody reading a privacy policy needs

Now byte-identical to the copy on the website.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-10-18 13:41:57 +03:00
+4 -4
View File
@@ -1,6 +1,6 @@
# Privacy Policy # Privacy Policy
**Last updated:** September 2026 **Last updated:** October 2026
ReVoltVPN is a free VPN service built and operated by ReVolt Team. ReVoltVPN is a free VPN service built and operated by ReVolt Team.
@@ -12,7 +12,7 @@ When you first open the app, we show a brief summary of this policy before you c
We collect the minimum required to operate the service: We collect the minimum required to operate the service:
- A randomly generated device ID created on your phone. This is not linked to your identity in any way. - A randomly generated device ID created on your phone. It is stored on your device and reused between sessions, and it is not linked to your identity in any way.
- Your connection duration and data usage for the current session, linked to your device ID. This is used solely to enforce the per-session quota (see below). - Your connection duration and data usage for the current session, linked to your device ID. This is used solely to enforce the per-session quota (see below).
## What our server sees ## What our server sees
@@ -27,14 +27,14 @@ Support ads (the "Support us" button) extend an active session by 30 minutes and
## Operational logs ## Operational logs
Server logs are written to the systemd journal (`journalctl -u hivemind`). These logs include truncated device IDs (first 8 characters only), session start/stop events, and error messages. Logs stay on the server and are accessible only to the server operator via local console; retention follows the server's systemd journal settings. We also maintain an aggregate total of all data ever transferred (in GB) for capacity planning — this counter is not tied to any individual device. Server logs are written to the system journal. These logs include truncated device IDs (first 8 characters only), session start/stop events, and error messages. Logs stay on the server and are accessible only to the server operator via local console; retention follows the server's journal settings. We also maintain an aggregate total of all data ever transferred (in GB) for capacity planning — this counter is not tied to any individual device.
## What we do not collect ## What we do not collect
- We do not collect your name, email, or any personal information. - We do not collect your name, email, or any personal information.
- We do not log your internet traffic, browsing history, DNS queries, or destination IPs. - We do not log your internet traffic, browsing history, DNS queries, or destination IPs.
- We do not inspect or store the content of your traffic. - We do not inspect or store the content of your traffic.
- We do not sell or share any data with third parties. - We do not sell your data. We do not share it with anyone, apart from what Google's ad SDK collects for ad delivery — see “Ads & Consent” below.
## Ads & Consent ## Ads & Consent