Data & permissions
Privacy policy
This policy covers Supplier Price Tracker, a private self-hosted n8n workflow, and its public information site at tracker.school-psychologist.com. The operator can be contacted at mikethepsy@gmail.com.
1. What the tracker is for
The workflow is intended to organize supplier and product information, record supplier prices, and maintain tracking records using Google Sheets and Google Drive. It is intended for the operator and explicitly authorized users.
2. Google data and permissions
Google Sheets — broad spreadsheet access
https://www.googleapis.com/auth/spreadsheetsThis permission can read, change, create, and delete Google Sheets spreadsheets accessible to the connected account. It is not restricted to a single tracker file. The intended purpose is to read supplier and product records and write price observations and tracking results.
Google Drive — broad file access
https://www.googleapis.com/auth/driveThis permission can read, download, create, change, and delete Drive files accessible to the connected account, including files unrelated to price tracking. The intended purpose is to find and manage files used by the workflow. Selecting a tracker file in n8n does not narrow the OAuth permission.
The consent screen shows the permissions actually requested. The permissions above describe broad access that may be requested by the configured n8n credentials; the precise scopes depend on that configuration. If the request differs from this disclosure or seems unnecessary, do not authorize it and contact the operator.
Depending on configured nodes and granted scopes, the workflow can process spreadsheet cells, spreadsheet and file identifiers, file names and metadata, and file contents used by the workflow. Broad access also permits actions on unrelated accessible files. OAuth access and refresh tokens allow n8n to call Google APIs without repeatedly asking for consent; you do not give this static site your Google password.
3. Where processing happens
OAuth authorization takes place with Google. The authorization callback belongs to the operator’s n8n installation, not this information site. Tokens are handled as credentials in that n8n environment. Workflow records can pass between Google APIs, the n8n host, and any destinations the operator configures in workflow nodes. Local or self-hosted processing does not mean that data stays only on one device: Google stores Sheets and Drive data, and configured services may receive workflow data.
This static site has no login, forms, Google API calls, analytics scripts, advertising, or application cookies in the supplied bundle. Its files do not contain n8n credentials or private supplier records. When hosted, Cloudflare processes web requests and may process technical information such as IP addresses, request details, and service logs under the operator’s hosting configuration and Cloudflare’s privacy policy. Emailing the operator also involves email providers.
4. Use and disclosure
The intended use of Google data is the supplier tracking workflow described here, including its operation and troubleshooting. This workflow is not intended to sell Google data, use it for advertising, or train generalized AI models. The operator must keep workflow destinations consistent with that purpose. Google, the n8n hosting environment, configured workflow services, and people with access to those environments may process or access data as their roles and settings allow. Contact the operator for the current workflow destinations before connecting an account if that information affects your decision.
5. Storage, retention, and security
Data may remain in Google Sheets and Drive, n8n credentials, workflow execution history, logs, exports, and backups. Retention depends on the settings and deletion practices of the operator and relevant providers. No fixed retention period, automatic deletion schedule, specific encryption configuration, or security certification is represented by this policy. Self-hosting alone is not a guarantee of security. The operator is responsible for configuring host access, credentials, logging, backups, and other safeguards.
6. Stop access or request deletion
- Open Google Account connections, select the tracker’s connection, and remove its access.
- Ask the operator to disable related workflows and remove the associated Google credentials from n8n.
- For existing data, contact mikethepsy@gmail.com and identify the records or account concerned without sending secrets.
Revocation does not delete previously copied records. Google files, execution records, logs, exports, and backups require separate review and deletion where applicable. The operator can explain available deletion options and any records that cannot yet be removed; this policy does not promise immediate removal from all backups or provider systems.
7. Your choices and policy changes
You may decline authorization or stop using the workflow. Features that need Google access will then be unavailable. This policy may change when the workflow or its handling of data changes; the effective date above identifies this version. Contact the operator with questions before granting access.