Privacy Policy

Data and purposes

We process account information such as email, name, profile image and sign-in identifiers, along with tasks, projects, notes, comments, files and AI conversations you provide. We use these to deliver the service, manage access and sharing, and display work history.

When you use an integration, we process its necessary permissions, tokens and selected connected-service data. Paid features involve subscription and payment information. Technical records may include IP addresses, request times and errors for maintenance and service security.

Access and providers

Application data and uploaded files are stored on the service’s own Linux server. Clerk provides sign-in. Stripe processes payments when used. Notifications and connected integrations may use their respective providers. These providers may process data outside your country under their own terms.

Other users have access according to project or team sharing and permissions. Authorized administrators may process data for support, security and recovery. When you assign work to AI, the necessary content and selected context may be provided to your chosen AI provider. Do not provide others’ secrets or data without permission.

Google Drive: access and use

Google Drive backups are an optional administrative integration connected with explicit authorization from the Google account. We request only https://www.googleapis.com/auth/drive.file: access to files created by the application and folders or files selected and authorized through Google Picker. We do not request access to your entire Drive.

We process the connected account’s email or display name, folder and file identifiers, names and metadata, and OAuth credentials. We use them to display the connection, select a destination, upload backups, download them to verify integrity, and manage gitDone archives. An access check creates, reads and removes a small test file.

A backup contains the site database, uploaded files, configuration and site version and may include personal data, conversations and integration secrets. Selecting Google Drive as a destination sends this data to Google and stores it in the selected Drive. The administrator must protect the account and folder sharing. Encryption for new archives is enabled through the separate archive password setting.

Google Drive: storage, sharing and limits

OAuth Client Secrets and refresh tokens are stored encrypted on the server. For folder selection, Google Picker in the authorized administrator’s browser receives a short-lived access token. The authorization allows automatic backups without an open browser.

Data obtained through the Google Drive integration is used only for the backup functions described here. We do not sell it, use it for advertising or provide it to train general AI or machine learning models. Access and transfer are limited to providing and protecting this function, legal obligations or actions explicitly authorized by the user. Our use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including the Limited Use requirements.

GitDone manages only archives and folders marked as its own. The last successful archive for each week is kept indefinitely; last-10 keeps the ten most recent successful archives. This policy does not delete unrelated personal files from Drive.

Disconnecting, deletion and requests

Disconnect account removes saved connection credentials from the active configuration and disables the destination. You can also revoke access in your Google Account’s third-party connections settings. Disconnecting or removing a destination does not delete existing archives; these are managed separately in Drive and may contain older connection data.

Other data is kept while needed to provide, secure and maintain the service’s history, or to meet applicable legal obligations. Contact lyousy@gmail.com to request access, correction, deletion, restriction or portability of personal data under applicable law. Include existing archives in your request if you also want data removed from those copies. You may lodge a complaint with the competent data protection authority.

Cookies and changes

We use cookies for sign-in and security, your selected language and the temporary OAuth connection flow. Display preferences may be stored in browser local storage. Blocking these can affect the related features.

Updates to this policy are published at this address with an updated date. Before using Google data for a new purpose outside the existing authorization, we will notify affected users and obtain the required consent.