Privacy Policy
For the private Join.To.IT Operations Google OAuth integration · Last updated: October 18, 2026
1. Purpose
Join.To.IT Operations is a privately operated, local-first application used by its authorized operator for project planning, resource allocation, data reconciliation, and operational management reporting. It is not offered as a public consumer service.
2. Google account data requested
When the operator authorizes the application with Google OAuth, the application requests only the scopes needed for its configured workflows:
- Google Sheets read-only (
spreadsheets.readonly): read data from selected, authorized planning spreadsheets. - Google Drive metadata read-only (
drive.metadata.readonly): discover and identify authorized files and access their metadata.
The application does not use these scopes to edit spreadsheets, modify Drive files, send emails, or post data to Google services.
3. How information is used
Data retrieved through Google APIs is used to validate planning sources, calculate and reconcile allocations, and prepare operational reports for the operator. The application may save relevant operational records and derived reports in the operator's local environment. When the operator separately authorizes a connected reporting workflow, selected derived reports may also be stored in the operator's designated cloud documents and reviewed by a connected AI assistant.
Google user data is not used to serve advertisements, build advertising profiles, or sold to third parties. The application is not made available to unrelated users.
4. Storage and security
OAuth credentials are stored using the operator's local credential storage, such as the macOS Keychain. Locally processed operational records are held in the operator's managed environment. Connected cloud services used by the operator may process data subject to their own terms and privacy notices.
5. Retention and deletion
Operational data and derived reports may be retained for project history and reconciliation until deleted through the operator's local system or connected storage. The operator can request deletion or review the retained data using the contact information below. Removing a Google OAuth grant stops future access but does not by itself remove previously generated local records or reports.
6. Revoking Google authorization
The operator can review and revoke Google account authorization at Google Account — Third-party connections. Revocation prevents new reads of the associated Google data unless consent is granted again.
7. Google API Services User Data Policy
Use of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
8. Contact
For questions about this private integration or requests concerning its data, contact dmytro.chervonenko@jointoit.com.