Privacy

Scientific datasets stay on your device.

VennScope is designed so that list parsing, set calculations, intersection inspection and figure rendering occur in your browser.

Standard analysis

Dataset contents entered or selected in the application are not sent to the VennScope server for analysis. VennScope does not require an account and does not require users to provide a name or email address to analyse sets or generate a local export.

Verified export records

If a user chooses to register a verified export, the final exported file is hashed locally. VennScope sends only the resulting SHA-256 fingerprint and limited technical metadata needed to create the export record: application version, output format, pixel dimensions, DPI and acknowledgement version. Dataset identifiers, dataset names, figure title and the exported file itself are not sent to the verification endpoint.

Verification

When a file is checked on the Verify page, its SHA-256 fingerprint is calculated locally. Only that fingerprint is queried against the verification registry; the selected file is not uploaded.

Data minimisation

The application-level verification database is intentionally designed not to store the user's name, email address, dataset identifiers, figure title, browser user-agent or IP address. Hosting and network infrastructure providers may process connection information as part of providing and securing the service under their own applicable terms and privacy documentation.

Retention

Verified export records are retained to provide integrity verification and to document the version of the export acknowledgement in force when the export was registered. This policy will be reviewed before the public v1.0 release and any fixed retention period required by applicable law or operational policy will be stated here.

Identifier metadata and online mapping

Identifier-type and organism labels are stored with local project data and are not transmitted for standard analysis. VennScope v0.16 includes an optional online mapping workflow. Mapping never starts automatically: the application names the external service and requires an explicit confirmation before transmission.

In the v0.16 mapping beta, selected identifiers are sent directly from the user's browser to the UniProt ID Mapping service for supported conversions. The other datasets, current figure and VennScope project file are not included in that mapping request. Mapping results and provenance remain in the browser unless the user saves a project or downloads a mapping/export file.

External database providers may process network connection information according to their own privacy and service policies. Do not use online mapping for confidential identifiers unless you are permitted to submit them to the selected external service.

Local PWA storage

The service worker may cache VennScope application files so the installed web application can operate offline. It does not intentionally cache user datasets or generated export files.