diff options
author | Saturneric <[email protected]> | 2023-07-19 09:32:58 +0000 |
---|---|---|
committer | Saturneric <[email protected]> | 2023-07-19 09:37:48 +0000 |
commit | beca2cf7ecea88aef649fd9b8fdea8ecfa2a95b7 (patch) | |
tree | aafbbe9ce58b6c7225c1ccf235fb36afde86d4ce | |
parent | Update README.md (diff) | |
download | GpgFrontend-beca2cf7ecea88aef649fd9b8fdea8ecfa2a95b7.tar.gz GpgFrontend-beca2cf7ecea88aef649fd9b8fdea8ecfa2a95b7.zip |
fix: update documents
-rw-r--r-- | PrivacyPolicy.md | 75 | ||||
-rw-r--r-- | README.md | 3 | ||||
-rw-r--r-- | SECURITY.md | 66 |
3 files changed, 79 insertions, 65 deletions
diff --git a/PrivacyPolicy.md b/PrivacyPolicy.md index 1ad79d96..2a72b301 100644 --- a/PrivacyPolicy.md +++ b/PrivacyPolicy.md @@ -1,47 +1,60 @@ # Privacy Policy of GpgFrontend -This application respects and protects the personal privacy of all service users. In order to provide you with more -accurate and personalized services, this application will use and disclose your personal information in accordance with -the provisions of this privacy policy. However, this application will treat this information with a high degree of -diligence and prudence. Except as otherwise provided in this privacy policy, this application will not disclose or -provide this information to third parties without your prior permission. This application will update this privacy -policy from time to time. +At GpgFrontend, we respect and uphold the privacy rights of all our users. To +deliver more precise and personalized services, we utilize and disclose your +personal information following the stipulations of this privacy policy. Rest +assured, we handle such information with utmost diligence and care. Except as +explicitly specified in this privacy policy, your information will not be +disclosed or provided to third parties without your prior consent. This privacy +policy is subject to updates periodically. -When you agree to this application service use agreement, you are deemed to have agreed to the entire content of this -privacy policy. This privacy policy is an integral part of this application service usage agreement. +By agreeing to the GpgFrontend Service Agreement, you implicitly consent to the +entirety of this privacy policy. This privacy policy is integral to the +application's service agreement. -## Scope of application +## Scope of Application -1. When you use this application to upload your public key to your designated key server, the information on your - computer automatically received by this application includes only the public key content of your key pair. +1. When using GpgFrontend to upload your public key to a designated key server, + the only information this application automatically collects from your + computer is the public key content of your key pair. ## Use of Information -1. This application will not store information outside the scope of application in any form on any server. -2. This application will not provide your information to any unrelated third-party key server that has not been - designated by you. -3. This application also does not allow any third party to collect, edit, sell or disseminate your information for free - by any means. If any user of this application platform engages in the above activities, once discovered, this - application has the right to terminate the prosecution of the user and prohibit the user from using this application. +1. GpgFrontend will not, under any circumstance, store any information beyond + the defined application scope on any server. +2. Your information will not be provided to any unrelated third-party key server + not specifically designated by you. +3. GpgFrontend prohibits any third party from collecting, editing, selling, or + disseminating your information for free by any means. Should any user of the + GpgFrontend platform engage in such activities, upon detection, we reserve + the right to pursue legal action and discontinue the offending user's access + to the application. ## Information Disclosure -In the following cases, this application will partially disclose your personal information based on your personal -wishes: +Under the following circumstance, GpgFrontend will partially disclose your +personal information based on your explicit wishes: -1. With your prior consent, disclose the public key information of your designated key to a third-party key server; +1. With your prior consent, the public key information of your designated key + can be disclosed to a third-party key server. -## Information storage and exchange +## Information Storage and Exchange -1. The information collected by this application about the public key specified by you will be stored on the key server - specified by you. Such information and materials may be sent to your country or region or outside the country/region - where the information and materials are collected by this application, and be accessed and stored outside that - country/region. And show. +1. The information that GpgFrontend collects about your specified public key + will be stored on your designated key server. This information may be + transferred to, accessed, stored, and displayed in countries or regions + outside of where you initially provided the information. -## Changes to this privacy policy +## Changes to this Privacy Policy -1. If I decide to change the privacy policy, I will post these changes in this policy, on the website, and where we - deem appropriate, so that you can understand how this application collect and use your personal information, who can - access this information, and where Under what circumstances will we disclose this information. -2. I reserve the right to modify this policy at any time, so please check it frequently. If there is a major change to - this policy, I will notify it through a website notice. +1. Should we decide to modify this privacy policy, we will post these changes + within this policy, on our website, and wherever we deem appropriate. This + will enable you to understand how GpgFrontend collects and uses your personal + information, who has access to this information, and under what circumstances + we may disclose it. +2. We reserve the right to alter this policy at any time, so we encourage you to + review it frequently. In the event of significant changes to this policy, we + will notify you through a notice on our website. +3. This privacy policy is governed by the most recent version available. + Therefore, it is advisable to stay updated with the latest version of the + privacy policy. @@ -263,8 +263,7 @@ link](https://gpgfrontend.bktus.com/#/translate-interface). GpgFrontend currently supports a wide array of languages including: -- Chinese (Simplified): 'zh_CN' -- Chinese (Traditional): 'zh_TW', 'zh_HK' +- Chinese - Spanish: 'es_ES', 'es_MX' - French: 'fr_FR', 'fr_CA' - German: 'de_DE', 'de_AT', 'de_CH' diff --git a/SECURITY.md b/SECURITY.md index d7fefbbb..9253d93f 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -2,12 +2,12 @@ ## Supported Versions -The application white check mark is still in support, without it means there -version will no longer have an update including security fixture. That's because -currently I have a job and a hard learning plain, which means I don't have too -much time to dealing with this project now, sincerely, I am sorry for that. -Maybe this situation will get better in the future. So it is recommended to use -the latest version. +Only versions with a white check mark are currently being supported. Versions +without it will no longer receive updates, including security fixes. This is +primarily due to my existing commitments to work and learning, leaving me with +limited time to dedicate to this project. I sincerely apologize for any +inconvenience this may cause. The situation may improve in the future. Hence, +it's recommended to always use the latest version of the application. | Version | Supported | | ------- | ------------------ | @@ -17,37 +17,39 @@ the latest version. ## Platform & Library Support -According to security concern and my limiting time to contributing, GpgFrontend -will gradually drop the support of some old platforms. Furthermore, GpgFrontend -will try to use newer libraries when it's more secure or taking another -advantages. +In light of security considerations and limited time available for contribution, +GpgFrontend will gradually cease to support certain older platforms. +Furthermore, GpgFrontend will aim to utilize newer and more secure libraries +whenever possible. -Starting from v1.0.0, x32 operating system was no longer support. Mainly because -I have limit time and the fact that x32 machine is getting less and less in the -pc market, so I plan to stop spending tons of time dealing with lots of complex -problem which might made me crazy. x64 is just enough, or you can use gpg4usb. +As of version v1.0.0, we no longer support x32 operating systems. This decision +stems from time constraints and the dwindling usage of x32 machines in the PC +market. Consequently, I plan to cease dealing with complex issues associated +with this system. x64 should suffice for most users, or alternatively, gpg4usb +can be used. -Starting from v2.0.1, Ubuntu 16.04 was no longer support. Mainly because Ubuntu -16.04 LTS's lifetime had come into an end at during that time. Keep using this -version of Ubuntu is not safe anymore. +As of version v2.0.1, we no longer support Ubuntu 16.04, as the LTS life cycle +of this version had ended by then. Continuing to use this version of Ubuntu is +therefore not safe. -Starting from v2.1.0, macOS 10.15 was no longer support. Mainly because this OS -will no longer support by GitHub Action in the near future. Also, I think this -version is old enough to drop it out, and Apple might not longer to support it -soon. +From version v2.1.0 onwards, we no longer support macOS 10.15, due to its +impending discontinuation by GitHub Action. Considering its age, and the +likelihood of Apple discontinuing support soon, it seems prudent to drop it. -Starting from v2.1.1, Ubuntu 18.04 is no longer support. Mainly because Ubuntu -18.04 is not support by GitHub Action any more since April 3. So, all the build -will move to Qt6, since Ubuntu 20.04 is supported by Qt6. +As of version v2.1.1, we no longer support Ubuntu 18.04, as it isn't supported +by GitHub Action since April 3rd. Thus, all builds will transition to Qt6, since +Ubuntu 20.04 is compatible with Qt6. -Starting from v2.1.2, Qt5 API will be removed from source, which means that the -whole project will use Qt6 API and won't be able to compile under Qt5. I will -consider removing deb package build. +Starting from v2.1.2, the Qt5 API will be removed from the source code. This +implies that the entire project will now utilize the Qt6 API and will no longer +compile under Qt5. Consideration is being given to removing the deb package +build as well. ## Reporting a Vulnerability -If you want to report a vulnerability, it's not good to raise an issue in -public. You should email [email protected] to contract me. In the email, You can -describe the vulnerability you have just discovered and request a hot-fix. Or -you can just provide a git patch to fix it and send it to me using the email. -This is a better way to solve the vulnerability as quick as possible. +In case you wish to report a vulnerability, please avoid raising an issue +publicly. Instead, contact me directly via email at [email protected]. In your +email, please describe the vulnerability you've discovered and request a hot-fix +if necessary. Alternatively, you could create a git patch to resolve the issue +and send it to me via email. This approach would expedite the resolution of any +vulnerabilities. |