diff options
| author | Leitwolf11 | 2026-11-06 12:57:27 +0300 |
|---|---|---|
| committer | Leitwolf11 | 2026-11-06 12:57:27 +0300 |
| commit | 53fb8b8bde857025d12655ae53857fc30226b186 (patch) | |
| tree | d0963feb1dddeedbd0980eb242dcd7e3e7c923e6 /apps/api/ViGet/JavaProperties.cs | |
| parent | 8f18eba55a8980141bd7b989378cb557ae927e2e (diff) | |
| download | progmaweb-53fb8b8bde857025d12655ae53857fc30226b186.tar.gz | |
Ask for the Privacy and Security Policies at registration
progmasoft.com/privacy and progmasoft.com/security publish the two
policies in en-US, de-DE, ru-RU and he-IL, and the footer links both.
The Privacy Policy says what an account keeps and that Progmasoft keeps
an IP address for one purpose only: with a ViGet upload, to establish
where an upload that turns out to be malicious software came from and
to give it to the competent authorities. It says that no data, the IP
address included, is sold, rented or traded. The Security Policy covers
passwords, sessions, HTTPS, the ban on malicious software in ViGet and
how to report a weakness.
The registration form asks the person to accept both policies, and the
API refuses a registration without that acceptance, with a password
(acceptPolicies, a validation error of that field) or through Google:
the start of a Google registration without acceptPolicies=true goes
back to /register?google=policies-required, and the completion creates
no account unless the authentication state carries the current version.
An account keeps the version it accepted and the moment, in two new
columns that schema step 2 adds; accounts created before it keep null.
PolicyAcceptance.CurrentVersion and policyVersion on the web side name
the same date, and a web test reads the C# constant to keep them equal.
Diffstat (limited to 'apps/api/ViGet/JavaProperties.cs')
0 files changed, 0 insertions, 0 deletions