Your data, clearly explained.

LivePilot and platform data

LivePilot is a desktop application provided by Neotecos Software. It runs on your macOS computer and contacts YouTube, Twitch or Kick directly. The Windows version is not available yet. It does not send broadcast video, connected-account data, credentials, diagnostics or thumbnails to a Neotecos server.

You create event names, titles, descriptions, schedules, templates and imported thumbnails. Platform API data includes account and channel IDs and names, OAuth tokens, stream keys and ingest addresses, category IDs, remote broadcast or stream IDs, publication results and API diagnostic data.

Consent and connections

Before a connection, LivePilot explains the requested access and requires acceptance of this policy. It records the accepted version locally and asks again when that version changes materially. It opens OAuth and policy links in your system browser. It never asks for, reads or stores your platform passwords.

YouTube API Services

LivePilot uses YouTube API Services after you authorize the https://www.googleapis.com/auth/youtube scope through Google. It reads your channel identity and the live-stream resources needed to prepare a destination. At your direction, it creates or updates broadcasts and streams, binds them, sets the title, description, schedule, visibility and other YouTube options you select, and uploads a thumbnail you select.

It stores the channel identity, OAuth tokens, stream keys and ingest details, remote resource identifiers, API responses and diagnostics locally for those functions. Your event titles, descriptions, schedules, templates and imported thumbnails originate from you. Google’s handling of data is described in the Google Privacy Policy; use of LivePilot’s YouTube features is also subject to the YouTube Terms of Service.

Twitch

LivePilot requests channel:manage:broadcast and channel:read:stream_key. It reads the account and channel identity and stream key. At your direction, it updates the title, category, tags, language and supported channel settings for your existing Twitch channel. It does not create a separate Twitch event, upload thumbnails or transmit video.

See the Twitch Privacy Notice and Twitch Terms of Service.

Kick

LivePilot requests user:read, channel:read, channel:write and streamkey:read. It reads the account and channel identity, stream key and ingest details. At your direction, it updates the title, category and custom tags of your existing Kick channel. It does not schedule an event, upload thumbnails or transmit video.

See the Kick Privacy Policy and Kick Terms of Service.

Disconnect, revoke and delete

Disconnect only suspends use of an account in LivePilot. It keeps the local authorization, account name, locally created content and publication state. Reconnect always opens a new authorization flow and obtains a new remote token; it does not reuse the stored token.

Revoke and delete, available after disconnecting, attempts to revoke the platform permission and always clears local API data: OAuth tokens; account and channel IDs and names; account settings; stream keys and ingest details; remote publication IDs; API snapshots, errors and categories; and applicable YouTube creation checkpoints. If remote revocation cannot be confirmed, local deletion still completes and LivePilot links to the platform permission settings. It does not delete content already hosted on a platform.

Historical publications retain their state and display the platform with “Unknown account”, without actions. Internal references and a platform ID may remain so local plans and history preserve their structure. Your events, titles, descriptions, schedules, templates and imported thumbnails remain until you delete them separately.

If permission is withdrawn outside LivePilot, the app checks active accounts on launch and periodically while it is running. When it confirms revocation and cannot renew authorization, it removes the same local API data. It cannot detect a change while closed or without a successful check. Use Google permissions, Twitch Connections, or Kick’s account controls to remove permission yourself.

Storage, encryption, sharing and contact

LivePilot stores account data locally in a SQLite database on your computer. OAuth access and refresh tokens, stream keys and other platform secrets in its secret store are encrypted before being written to that database. The encryption uses XChaCha20-Poly1305 with a unique random nonce for each stored value. The encryption key is randomly generated and protected by your LivePilot password; the password is processed with Argon2id and is not stored or sent to Neotecos, YouTube, Twitch or Kick. The encryption key is held only while the app is unlocked for the current session. The locally stored policy-acceptance version is not encrypted because it is not a platform secret.

When LivePilot first needs access to protected connections, it asks you to set a password. It asks for that password when the app is opened again. You can change it while the vault is unlocked without losing the protected connections. If you forget it, neither Neotecos nor the platforms can recover it. You may reset it in the app: this permanently deletes the encrypted secrets, connected-account identity and other local platform API data, while retaining your locally created events, titles, descriptions, schedules, templates and imported thumbnails. Resetting a password does not revoke permission on the platforms or delete content already hosted there; use the platform controls linked above to revoke permission.

Platform API calls use HTTPS. LivePilot does not sell platform data, use it for advertising or analytics, or train AI models with it. Local backups and diagnostic files can retain earlier copies; use device protection and remove permissions if you suspect exposure.

For privacy questions, contact dev@neotecos.com. Postal address for notices: Neotecos Software, P.O. Box No. 1032, 19005 Guadalajara, Spain. Material changes to this treatment are reflected here and can require a new acceptance in the app. Read the Terms of Use.