Repository navigation
two prrivacy quesstions #821
Before you ask
Your question2 on privacy: • IP address exposure: IP is visible to Google and all services Vela contacts (same issue as any un-VPN'd app) you have syggestions on this ? thanks for the good app ! Vela versionNo response |
Replies: 1 comment 1 reply
|
Both are right, and both are the same for any app that talks to Google without an account. The IP: every service Vela contacts sees it, Google included. Vela has no proxy setting of its own and follows the system's, so a VPN, or Orbot in VPN mode, is the answer there. The cookies, and why there are any: Google's pages refuse to work without them. The first request from the EU lands on a consent wall and gets nothing until a consent cookie (SOCS and CONSENT) is sent back, so Vela seeds those two itself; they carry no identity, only "consent given". The other is Google's own session cookie, which it sets on every reply, logged in or not, and some of its endpoints answer with less or nothing when it is missing; that is the one that can tie a session's requests together. Vela keeps two of those and makes them short. Searches, suggestions and directions use one that lives only in memory and starts over every time Vela starts. Opening a place and the few hidden pages use a browser-style one kept on disk, and Settings > Privacy > Google session renews it every week by default, every day, or on every launch, with a button to renew it now; set it to every launch if the linking within a session is what bothers you. PRIVACY.md in the repository has the whole table, request by request. |
Both are right, and both are the same for any app that talks to Google without an account. The IP: every service Vela contacts sees it, Google included. Vela has no proxy setting of its own and follows the system's, so a VPN, or Orbot in VPN mode, is the answer there. The cookies, and why there are any: Google's pages refuse to work without them. The first request from the EU lands on a consent wall and gets nothing until a consent cookie (SOCS and CONSENT) is sent back, so Vela seeds those two itself; they carry no identity, only "consent given". The other is Google's own session cookie, which it sets on every reply, logged in or not, and some of its endpoints answer with less or nothing…