BYTEFOX TASKS SYNC

Privacy Policy

Last updated: 12 October 2026

Bytefox Tasks Sync is a personal automation operated by Maksim Rososhanskii for himself and his spouse. Personal lists and shared tasks are synchronised through a private n8n installation. Recurring payments remain disabled while recurrence behaviour is tested. This policy describes the data used by the automation and its supporting system.

Google data and permissions

The application requests the Google Tasks permission (https://www.googleapis.com/auth/tasks). It permits access to task lists and tasks, including their identifiers, titles, notes, dates, completion status, ordering, and other fields returned by the Tasks API. It also permits creating, updating, and deleting task lists and tasks.

The application does not request access to Gmail, Google Drive, Google Calendar, or other Google APIs. Authorisation produces OAuth tokens that allow the private automation to access Tasks on your behalf.

Purpose and use

Google Tasks data is used to synchronise tasks with the Craft spaces selected for this personal automation. Private spaces sync with the corresponding person's Google account; the shared space syncs with both accounts. Shared-space tasks are therefore visible to both participants.

Task identifiers, mappings, timestamps, and operation results may be retained to match tasks across services, avoid duplicate updates, and diagnose sync errors. The private synchronisation database stores agreed field values, pending operation details and conflicting values, which may contain task content. These workflows do not save successful, failed or manual execution payloads.

Google user data is not used for advertising, profiling, sale, or training general-purpose AI or machine learning models. The application's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Storage and protection

OAuth credentials are stored by n8n using its credential encryption mechanism. The automation database and operational records are stored on the owner's private server. The n8n interface is restricted to the owner's private network or VPN.

The system creates encrypted backups using restic and stores them in a private Cloudflare R2 bucket. Backups include the n8n database and application data. Encryption keys are not published on this website.

Transfers and third-party services

The sync necessarily sends task data to Google Tasks and Craft. Craft stores the synchronised content under its own service terms and privacy policy. Cloudflare R2 stores encrypted backup data. These platforms process data according to their respective policies.

The owner may inspect service records to maintain the automation, investigate errors, or respond to a deletion request. No public access to these records is provided. Data is not shared with unrelated third parties, except where required by law.

Retention and deletion

OAuth credentials, task mappings, operation records and conflicts are retained while needed for the connected automation, until the owner removes them. n8n uses automatic execution pruning, configured by its current defaults at 14 days or a limit of 10,000 saved executions. Some records, such as waiting or annotated executions, can be excluded from pruning; this is not a guaranteed deletion deadline for every record.

Backups retain 14 daily, 8 weekly, and 6 monthly snapshots. These are snapshot-selection rules, not a fixed maximum age for every copy. Data removed from the active system can remain in encrypted snapshots until those snapshots expire and the backup cleanup removes unreferenced data. Selective or immediate deletion from historical backups is not promised.

Contact jerthefox@gmail.com to request removal of your OAuth credentials, sync mappings, and relevant service records from the active system. The owner will confirm the scope and outcome of the request. Tasks already stored in Google Tasks or Craft are not removed by revoking access or deleting the automation's service data; manage those tasks in the respective service.

Revoking Google access

You can remove the application's access in your Google Account connections. Once Google access is revoked, the automation can no longer sync that account with Google Tasks. Revocation does not itself erase existing service records or backups. Contact the owner if you also want those active records removed.

This website

This static website does not collect task data, provide a sign-in form, or use analytics or advertising scripts. It does not set application cookies. Cloudflare serves the website and may process connection and security information to deliver and protect it. Following a link to another service subjects your visit to that service's policies.

Changes and contact

This policy will be updated before the automation introduces different data access or use. The date above identifies the current version. For questions or data requests, contact Maksim Rososhanskii at jerthefox@gmail.com.