Scope
This Privacy Policy applies to the Finished? website, Blender add-on, official Telegram bot, and related render-monitoring service.
Information we process
- Telegram account details — your Telegram user and chat identifiers, display name, username when available, and interface language. These let the bot connect your account and deliver updates.
- Connected-device details — a device name and basic Blender or add-on version information used to pair and maintain a connection with your workstation.
- Render status details — the project name, render progress, timing, render state, and technical settings such as engine, resolution, samples, and output format.
- Security details — hashed pairing codes and hashed device credentials used to protect the connection between your add-on and the service.
Why we use it
Finished? processes this information only to pair your device, monitor renders started through the add-on, send Telegram updates, maintain service security, and troubleshoot reliability issues. We do not use your data for advertising or sell it to third parties.
What we do not collect
Finished? does not upload or store your .blend files, rendered image sequences, or render outputs. It is a monitoring service, not cloud rendering or file storage.
Where information goes
Render updates are sent through Telegram so they can appear in your chat. The service also uses server infrastructure to process pairing and render status data. We limit information shared in Telegram updates and do not include device credentials or local file paths in those messages.
Retention and control
We keep only the information needed to operate the service, maintain active render status, and provide limited render history where available. You can disconnect a device from Finished? to revoke its connection. Data controls and support contact details will be added as the public support channel becomes available.
Security
Finished? uses authentication tokens to connect a device to the service. Server-side credentials are stored as hashes where possible, and the product is designed to avoid exposing tokens, pairing secrets, or local workstation paths in Telegram messages and ordinary logs.
Changes to this policy
We may update this policy when the product changes. The current version and its update date will always be published on this page.