Visum Privacy Notice
Version: 1.1
Effective date: the date Visum 0.1.1 Alpha is first made publicly available in the official RO Company GitHub Release
1. Who is responsible
The data controller for the update, download and support services described here is Rohan Nand Chawla, trading as RO Company, of 2 Ocklye Cottages, Glenmore Road, Crowborough, East Sussex, TN6 1TW, England, United Kingdom.
Privacy contact: privacy@rocompany.co.uk
2. Plain-language summary
Visum Developer, Visum Player, Visum Engine and the Visum CLI process visual models locally on your Mac. They contain no advertising or automatic crash-report upload. Captures, recordings, crops, labels, training, tests and .visum execution stay local unless you deliberately export, publish or submit selected material. You may separately choose whether to share bounded anonymous diagnostics.
3. Information kept locally
Depending on the features you use, Visum may process and store locally:
- images, recordings and screen, window or region captures you choose;
- crops, labels, sequences, expected results and training settings;
- projects, model files, provenance, lineage and rights records;
- local training, validation, test, error and performance records;
- typed Confector actions, permission decisions and local audit records;
- recent-project and shared-library locations; and
- the legal-document version and fingerprint you accepted.
This information is used only to perform the operations you request, restore your work between sessions, protect artifact integrity and record relevant local permissions. It remains in locations on your Mac controlled by you until you delete the corresponding project, library entry, exported file or application data.
4. macOS permissions
Screen Recording permission is used only when you request screen, window or region capture or sharing. Accessibility permission is used only when an authorised Confector execution needs it. You control and can revoke these permissions in macOS System Settings. Revocation disables the related feature.
5. Updates and downloads
Visum Developer and Visum Player check their signed update feeds when they launch and every six hours while running. The CLI and AI Skill check only when you or an authorised AI workflow runs a Visum update command. Visum does not send a system profile with update checks. A request necessarily exposes ordinary connection information such as IP address, date, time, requested file and basic HTTP metadata to the website, content-delivery and GitHub infrastructure serving the feed or download.
These limited logs are used for security, delivery, abuse prevention and service reliability. They are retained according to the relevant infrastructure provider’s settings and policies and are not combined by Visum with captures, projects or model content.
6. Optional anonymous diagnostics
On first use, Visum Developer and Visum Player ask whether you want to share anonymous diagnostics. The CLI keeps diagnostics off unless you enable them explicitly. You can change this choice later.
When enabled, routine diagnostics are limited to a random installation identifier; Visum, Engine and model versions; task category; duration; success, failure, cancellation, approval, denial or correction state; bounded item counts; error codes; Apple Silicon architecture; and the major macOS version. Routine diagnostics do not contain captures, recordings, crops, project content, model output, labels, filenames, filesystem paths, prompts or typed text. Failed submissions remain queued locally and are discarded if you disable diagnostics.
RO Company uses these records to identify reliability, performance and model-quality problems. Routine diagnostic records are retained for no longer than 90 days unless a longer period is required to investigate security abuse or establish, exercise or defend legal claims.
7. Explicit model-improvement submissions
Visum may offer Help Improve This Result or the equivalent CLI command. This is separate from anonymous diagnostics. Nothing is sent unless you deliberately select the files, provide a correction and confirm that you have the right to share that material with RO Company for Visum evaluation and model improvement.
A submission contains only the selected visual or structured files, the correction, relevant product/model versions, integrity hashes and the recorded rights attestation. Selected material may nevertheless contain personal, confidential or special-category information visible within the file. Review it carefully before submitting it. Submitted examples are retained for up to 12 months while they are reviewed. An example accepted into a governed evaluation or training dataset may be retained with its provenance for the life of that dataset and resulting model, subject to applicable legal rights.
8. Support, issues and security reports
If you email support, privacy or security contacts, or open a GitHub Issue, you choose the information supplied. It may include your contact details, device or software details and the content of your report. Do not submit captures, credentials, personal data or confidential project material unless necessary and authorised.
RO Company uses reports to answer requests, investigate defects or security issues and maintain the product. Public GitHub Issues are visible to others. Vulnerabilities should be reported privately to security@rocompany.co.uk.
9. Exporting and publishing
Files you export can contain the media and metadata described by their manifest. Review them before sharing. Publishing to a future Visum Models service will be an intentional online operation governed by a separate publisher agreement and service-specific privacy information before that service opens.
10. Legal bases and sharing
Where UK data-protection law applies, update delivery and requested support are processed as necessary to provide the service you request or pursue legitimate interests in secure and reliable software. Optional diagnostics and model-improvement submissions are processed following the separate affirmative choice you make for each purpose. Legal or security records may be processed to comply with law or establish, exercise or defend legal claims.
RO Company does not sell personal data. Limited connection, update, diagnostics, submitted-example and support information may be handled by infrastructure providers used for the website, GitHub distribution, diagnostics storage, email and security. Information may be processed outside the United Kingdom subject to the provider’s applicable safeguards.
11. Your rights
Depending on the law and circumstances, you may have rights to be informed, access, rectification, erasure, restriction, portability, objection and safeguards relating to automated decisions. Contact privacy@rocompany.co.uk to exercise a right. You may complain to the UK Information Commissioner’s Office or another competent supervisory authority.
Local project data is under your direct control and can normally be managed by deleting the relevant local files. RO Company cannot access or recover local data that was never sent to it.
12. Security, retention and changes
Visum validates supported package structures and integrity records. Updates are protected by HTTPS, Apple Developer ID/notarisation checks and a separate Sparkle EdDSA signature. No security measure eliminates all risk.
Support and security records are retained only as long as reasonably needed for the request, security, legal and product-maintenance purposes. A material change to in-app data use will be explained before it begins and, where required, will request fresh agreement.
Last updated: 29 August 2026
