1. Introduction

GitSet.dev ("we," "our," "us") is committed to protecting your privacy. This Privacy Policy outlines how we collect, use, and safeguard your information when you use GitSet.dev, including when you authenticate through OAuth with GitHub.

By using GitSet.dev, you consent to the practices described in this Privacy Policy. If you do not agree with any part of this policy, please refrain from using our services.

2. Information We Collect

GitSet.dev collects limited information to provide services effectively and securely. This includes:

Authentication Data: When you log in via OAuth, GitSet.dev collects the necessary information for authentication. This includes your GitHub username, repository access rights, and other metadata provided by GitHub via OAuth.

3. Use of Your Data

We use your data solely for the purpose of providing the functionalities offered by GitSet.dev. This includes the generation of text outputs for README files, .gitignore files, commit messages, tags and releases management, repository assessments, comment removal from code, as well as the management of OAuth authentication.

While using GitSet.dev, the platform does not store or retain any data associated with its features, including README generation, commit message suggestions, .gitignore creation, tag and release management (creation, editing, or deletion), and repository assessments. These activities generate text content on the fly, and any data entered by the User will not be stored or backed up beyond its immediate usage.

Temporary Processing Data: When using features like the Code Decommenter, the code you submit is temporarily processed in memory only for the duration of the comment removal operation. This code is not stored, logged, or retained after processing is complete.

4. Data Security

We take reasonable precautions to protect your information, including the use of encryption and secure access protocols. However, as with all online services, we cannot guarantee complete security against potential breaches.

Logs and Authentication Records: GitSet.dev does maintain logs for user authentication activities solely for purposes of security and compliance. These logs contain information about the User's login sessions and authentication attempts, and are not used for any other purpose.

5. Third-Party Services

GitSet.dev relies on third-party services, including GitHub OAuth, for authentication. By authenticating with GitHub, you consent to Github's Policies and Terms. We encourage you to review GitHub's privacy practices to understand how your data may be used outside of our platform.

AI Processing Data: Our service uses Google Gemini AI for text generation. While GitSet.dev does not store any interactions with the AI, it's important to note that Google may collect and retain this data according to their policies. For more information about how Google handles this data, please refer to their Privacy Policy and Gemini Privacy Notice.

6. Use of Cookies and Tracking Technologies

GitSet.dev uses cookies to improve your experience, particularly for maintaining authentication sessions and improving the quality of service. Cookies are small data files stored on your device that help us analyze how the platform is used and allow us to enhance our features.

You may disable cookies through your browser settings, but doing so may affect your ability to use certain features of the platform.

7. Revocation of Access

Users may revoke access granted to GitSet.dev at any time from Settings page on GitSet.dev, navigating to the "Connected Accounts" section, and selecting "Revoke GitHub Access". Additionally, users can manage OAuth applications directly through GitHub's settings. TO REVOKE ACCESS, CLICK ON 'GITSET.DEV' IN THE LIST OF AUTHORIZED APPLICATIONS, SELECT THE THREE DOTS, AND CHOOSE 'REVOKE'. CONFIRM YOUR ACTION.

TO REVOKE ACCESS, FOLLOW THE INSTRUCTIONS DETAILED UNDER "REVOCATION OF ACCESS" IN THE TERMS OF SERVICE.

8. Data Retention

GitSet.dev does not retain any user-generated content beyond what is necessary for authentication and basic logging purposes. If you lose access to any AI-generated text, such as a commit message or README, GitSet.dev cannot retrieve that information.

9. Changes to the Privacy Policy

GitSet.dev reserves the right to modify this Privacy Policy at any time. Any changes will be posted on this page, and the revised policy will take effect immediately upon posting. By continuing to use the platform after such updates, you accept the revised terms.