Create PRIVACY-POLICY.md
This commit is contained in:
commit
60fc12a332
1 changed files with 70 additions and 0 deletions
70
PRIVACY-POLICY.md
Normal file
70
PRIVACY-POLICY.md
Normal file
|
@ -0,0 +1,70 @@
|
|||
Last Updated
|
||||
On: February 3rd, 2024
|
||||
By: Ategon
|
||||
|
||||
All Authors: recursive_recursion, Ategon
|
||||
|
||||
# Privacy Policy
|
||||
|
||||
This privacy policy describes how Programming.dev ("programming.dev", "we", "us", "our") collects, protects and uses information provided to us when you use our services including:
|
||||
- Our websites such as programming.dev or bytes.programming.dev
|
||||
- APIs for our websites
|
||||
- Any other place we collect information from you and link this Privacy Policy
|
||||
|
||||
By joining and contributing to our services, you acknowledge that it is running on early release software. Although we take reasonable precautions to maintain the security of personal data provided to us we cannot guarantee that the software is free from defect that will expose any or all of that personal data.
|
||||
|
||||
If you do not agree with all of our policies and practices, do not use our services. If you have any questions or concerns, contact us at info@programming.dev.
|
||||
|
||||
# Site Usage by Children
|
||||
|
||||
Our services are all directed to people who are at least 16 years old. We do not knowingly collect personal information from people under the age of 16. If you are under the age of 16, please do not use our services. If we learn that personal information from people who are less than 16 years old has been collected, we will deactivate the account and take reasonable measures to delete the data from our records.
|
||||
|
||||
# What do we use your information for?
|
||||
|
||||
Any information we collect from you may be used in the following ways:
|
||||
|
||||
- To provide the core functionality of our services such as being able to comment on other people's posts or subscribing to communities when you are logged in.
|
||||
- To aid in moderation of our services, for example to detect vote manipulation.
|
||||
- To send you information, notifications about other people interacting with your content or sending you messages, or notifications for new posts created, if you opt in to any of these options in the settings. We may also use it to respond to you about inquiries, and/or other requests or questions.
|
||||
|
||||
# What information do we collect?
|
||||
|
||||
- **Basic account information:** If you register on one of our services you may be asked to enter a username and password. You may also additionally enter information such as a e-mail address, a matrix user, a display name, a location, a birthday, a language, and a biography, and upload a profile picture and banner image. You may also additionally enter information into additional custom fields. All of these apart from the password and e-mail are always listed publicly.
|
||||
- **Posts, comments, subscribing, voting, reactions, and other public information:** When you perform an action on one of our services such as create or edit a post, comment, or vote, the date and time the action is taken at is stored as well as the content and any media attachments on them such as pictures and videos. All of this is publicly available information due to the nature of federation as they are delivered to the communities they are posted on and any instance federated with that community using the activitypub protocol. This means they are delivered to many different servers and copies of them are stored there.
|
||||
- **Direct messages:** All direct messages sent are unencrypted and may be delivered to other servers if the user you are sending a message to is on a service other than one provided by us. We make a good faith effort to limit the access to direct messages to only authorized persons butother servers may fail to do so so it is important to review who and what service you are sending messages to. Keep in mind that operators of our services and any receiving services may view direct messages and that recipients may screenshot, copy, or otherwise re-share them so it is recommended to not share any sensitive information.
|
||||
- **IPs and other metadata:** When you log in, we may record the IP address you logged in from, the time and date you logged in at, as well as the name of your browser application. We also have server logs which include the IP address of every request to our server.
|
||||
|
||||
Your IP address and email remains private to our services. However, due to the nature of federated services, all of your engagement (profile, posts, comments, messages, votes, etc.) on our services should be considered public and you are responsible for taking appropriate precautions in how you interact with our services. It is highly recommended that you do not share any publicly identifying information on our sites, products, or services.
|
||||
|
||||
# How do we protect your information?
|
||||
|
||||
We implement a variety of security measures to maintain the safety of your personal information when you enter, submit, or access your personal information. Among other things, your browser session, as well as the traffic between your applications and the API, are secured with SSL, and your password is hashed using a strong one-way algorithm. You may also enable two factor authentication to further protect your account.
|
||||
|
||||
# What is our data retention policy?
|
||||
We will make a good faith effort to:
|
||||
- Retain server logs containing the IP address of all requests to this server, in so far as such logs are kept, no more than 1 day.
|
||||
- Retain the IP addresses and name of your browser application associated with logins for no more than 1 day.
|
||||
|
||||
You may irreversibly delete your account at any time. However, this does not guarantee all instances will be notified or respect the deletion of your public data.
|
||||
|
||||
# Do we use cookies?
|
||||
|
||||
We use cookies for specific functionalities, which includes cloudflare clearance and JWT (JSON Web Token) authentication purposes.
|
||||
|
||||
- Cloudflare clearance: Cookies provided by cloudflare to store the proof of passing a cloudflare challenge.
|
||||
- JWT: A token to allow you to access and interact with our services after logging in.
|
||||
|
||||
These cookies do not store personally identifiable information and are necessary for the proper functioning of our services. By continuing to use our services, you consent to the use of these essential cookies.
|
||||
|
||||
Please note that you can manage or disable cookies through your browser settings. However, disabling these essential cookies may impact the functionality and security of services.
|
||||
|
||||
# Do we disclose any information to outside parties?
|
||||
|
||||
We do not sell, trade, or transfer your personal information to outside parties. This does not include trusted third parties who assist us in operating our services, so long as those parties agree to keep this information confidential.
|
||||
|
||||
Your public content may be downloaded by other servers using the activitypub protocol, as well as direct messages to the servers of the receipients.
|
||||
|
||||
When you log in to your account on a service not provided by us, it may access your public information as well as password when logging in.
|
||||
|
||||
# Do we Make Updates to this Privacy Policy?
|
||||
We may update this privacy policy from time to time. When we do, we will change the "Last Updated" date and author at the top of the page to indicate the date and author of the most recent changes. If we make changes we may notify you by posting a notice of such changes or by sending you a notification. We encourage you to review this Privacy Policy periodically for any modifications.
|
Loading…
Add table
Reference in a new issue