1. Scope
This notice covers visorn.dev, the Visorn desktop app and the licence and account services used for paid extensions. It does not replace the privacy notice of a service you choose to connect, such as your model provider or Paddle.
2. What stays on your machine
Your files, projects, extension settings and the contents of the Task Orchestrator task board are stored locally by default. Normal local use of the app does not upload those files or the board to Visorn.
The light / dark choice on this website is stored in your browser's localStorage under the
key visorn-theme. It is not sent to the server.
3. When data leaves your machine
When you run an agent task, Visorn sends the selected content to the model provider you configured so that the provider can generate a result. For Task Orchestrator this includes the task text, its sub-tasks and recent executor or reviewer reports. That text leaves your machine and goes to that provider.
Visorn does not control what the provider does with it. The provider's terms and privacy notice apply, and the provider bills you directly for that usage. Only send content you are allowed to send to that provider.
4. Sign-in
Account sign-in is handled by Firebase Authentication. Firebase processes the identifiers supplied by the sign-in method you choose. Visorn receives the account identifier needed to associate an account with its licence records. Signing in is required to buy a paid licence; running the Task Orchestrator board does not require it.
5. Licence and purchase state
When the paid licence service opens, licence checks will run through Cloudflare at
https://license.visorn.dev. To validate a paid licence, the service will process purchase
state and licence records, account and device identifiers, hashed refresh tokens, and hashed IP-based
rate-limit identifiers. These will be used to activate the licence, enforce the device limit, support
the offline receipt lease and prevent abuse.
The receipt lease is up to 30 days offline with a re-check every 14 days. Those records exist to run that validation, not to profile your files or task content.
6. Payments
Paddle is the seller of record and handles payment data and applicable taxes. Visorn does not receive or store your card number. Visorn receives the information needed to confirm an order and keep licence records, including order status, an order identifier, the Paddle customer ID and the buyer email address supplied with the order. Paddle's own privacy notice applies to the payment data it collects.
7. Hosting and security metadata
This site and its licence infrastructure are served through Cloudflare. Cloudflare may process standard HTTP request metadata — such as IP address, user agent, requested URL and timestamp — to deliver pages, apply security controls and rate limits, and keep the service available.
This notice does not promise that no data is ever collected. Some processing is unavoidable to serve a page, sign in, validate a licence or take a payment.
8. Purposes and retention
Data is processed for these purposes: providing accounts and sign-in, validating licences and device limits, maintaining purchase and accounting records, preventing fraud and abuse, meeting legal obligations, and answering support requests.
Records are kept only as long as needed for those purposes and for the periods required by applicable accounting, tax and other legal obligations. Because those requirements depend on the order and the law that applies to it, this notice does not state a single fixed retention period for every record.
9. Your requests
To ask about your account or licence data, use the public support / contact form (GitHub) and describe the request. Do not attach identity documents, card numbers, bank details or other sensitive material to a public issue. We will arrange a private channel to verify the request and discuss the details.
Depending on the law that applies to you, you may have rights to access, correct, delete or object to the processing of your personal data. Those statutory rights are not affected by this notice.
10. Changes
This notice may be updated as the product or the services behind it change. The date at the top shows the current version.
11. Contact
Questions about this notice go through the public support / contact form (GitHub). For the commercial terms, see the terms of sale and use; for refunds, see the refund policy.