CTSources · Privacy
Privacy policy
This policy describes the intended Google Sheets connection in CTSources, a private application operated for personal use. The integration is under development. This informational website itself does not collect Google authorization codes or tokens.
Data accessed and its purpose
When the connection is enabled and authorized, CTSources reads configured spreadsheet ranges using the operator’s existing Google account permissions. Relevant content includes published symbols, entry conditions, prices, position percentages, protective stops, profit targets and source-update information.
These data are used to prepare source snapshots for the operator’s CTTrader ideas portfolio. The Google permission requested is spreadsheets.readonly. It permits read access to spreadsheets available to the authorizing account; the application restricts its own requests to its configured source. It does not use this permission to edit spreadsheet content.
Processing and sharing
Spreadsheet content is intended to be parsed deterministically by CTSources and supplied to the operator’s CTTrader service for portfolio evaluation and management. The planned Google Sheets integration does not send spreadsheet content to a language model.
Google user data are not sold, used for advertising, or used to train general-purpose AI models by this integration. Separately configured newsletter or market-data acquisition does not expand the Google Sheets permission granted here. Any future change in Google data use must be disclosed before that change is enabled.
Credentials, storage and retention
When enabled, the backend retains OAuth credential state, including the refresh token needed for unattended access, in operator-controlled private persistent storage. Credentials are intended to remain outside public pages, container images and source control. Google passwords are entered with Google, not collected by these pages.
Configured source snapshots and operational records may be retained in operator-controlled application storage for the source connection and related portfolio workflows. The operator controls retention and removal when that information is no longer needed. Separately recorded trading decisions and accounting history may remain in CTTrader after the source connection is removed.
Revoking access and removing data
The operator can revoke the connection through Google Account third-party connections. Revocation prevents further authorized reads but does not itself delete information already stored in the private stack. To remove stored connection credentials or source information, contact the application operator. Any retained accounting history is handled separately from source credentials.
Google API data policy
CTSources’ use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
This public website
Cloudflare serves these static informational pages. They contain no application login, data-entry forms, advertising scripts or analytics scripts. They are separate from the private backend and its authorization callback.
Contact and changes
For questions about this private integration or requests concerning its stored data, contact the application operator using the user-support email displayed on the Google authorization consent screen.
This policy will be updated if the application’s Google data handling changes. Review the effective date above and the policy presented when authorizing the application.