SBORKA N8N

Privacy Policy

Last updated: September 30, 2026

This policy explains how Sborka Project (“we”, “us”) handles information through Sborka n8n, our self-hosted internal automation service connected to Google Drive.

1. Information we access and process

When you authorize a Google connection, the application receives OAuth credentials, including access and refresh tokens. Depending on the permissions granted and the workflows you use, it may access:

• Google Drive file and folder metadata, such as names, identifiers, locations, links and permissions.
• File contents when a workflow reads, downloads, copies, uploads or otherwise processes a file.
• Account information returned by Google when required to identify or operate the authorized connection.
• Workflow execution information, including inputs, outputs, timestamps and error details.

The application does not receive your Google Account password. The permissions requested are displayed by Google during authorization.

2. How we use information

We use this information to run authorized internal workflows, including creating project folders, organizing documents, copying files and transferring relevant data between configured business systems. We also use execution information to troubleshoot errors and maintain the service.

A workflow may create, modify, move or delete files and folders when that action is configured and permitted by the connected account.

3. Storage and access

OAuth credentials are stored in the self-hosted n8n credential store. Workflow data may also be stored in execution history, connected business systems and infrastructure backups. Access is limited to authorized personnel who operate, maintain or use the relevant workflows.

Administrators may inspect workflow data when necessary for troubleshooting, security or operational support.

4. Sharing and transfers

Data may be sent to Google and to other business systems explicitly configured in an authorized workflow, to perform that workflow’s intended function. Infrastructure providers may process stored data on our behalf as part of hosting and backup services.

We do not sell Google user data, use it for advertising, or use it to train general-purpose AI or machine learning models.

5. Google API Limited Use

Sborka n8n’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy , including the Limited Use requirements, and the applicable Google Workspace API User Data and Developer Policy .

6. Retention and deletion

OAuth credentials are retained while a connection is needed. Execution records and backups are retained according to the configured service retention settings. Business documents created or copied by workflows remain in their destination systems until deleted there.

You may request deletion of your connection credentials and associated stored workflow data by contacting us. Some records may need to be retained to meet legal obligations or resolve security issues. Backup copies are removed through the applicable backup retention cycle.

7. Revoking access

You can revoke the application’s access through your Google Account connections . Revocation prevents further access through that connection; it does not automatically delete existing files or previously stored workflow records. Contact us to request their deletion.

8. This public website

These informational pages do not contain analytics scripts, advertising trackers or application-set cookies. Hosting and network providers may process technical request information, such as IP addresses and access logs, to deliver and protect the website.

9. Changes and contact

We may update this policy when our workflows or data handling practices change. The current version is published on this page.

For privacy questions or deletion requests, contact Sborka Project: lesha@sborkaproject.com.