From 8260c7cc0ac709b61eae72c896c6951df93765d6 Mon Sep 17 00:00:00 2001 From: esefxdz Date: Sun, 18 Oct 2026 13:41:57 +0300 Subject: [PATCH] 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 --- PRIVACY_POLICY.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/PRIVACY_POLICY.md b/PRIVACY_POLICY.md index cb21628..15cb92d 100644 --- a/PRIVACY_POLICY.md +++ b/PRIVACY_POLICY.md @@ -1,6 +1,6 @@ # Privacy Policy -**Last updated:** September 2026 +**Last updated:** October 2026 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: -- 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). ## What our server sees @@ -27,14 +27,14 @@ Support ads (the "Support us" button) extend an active session by 30 minutes and ## 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 - 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 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