Privacy-first research tooling

NanoScreen Privacy Policy

NanoScreen is built around a simple principle: user privacy comes first. We believe researchers should be able to screen studies efficiently without sending sensitive files, notes, or decisions to third-party servers.

Effective date: March 30, 2026

1. Scope

This Privacy Policy explains how the NanoScreen Chrome extensions, including NanoScreen Manual Study Screening Tool and NanoScreen AI-assisted NanoScreen, handle information. It is intended for users, institutions, and reviewers who want a clear statement of how screening data is processed when using these extensions. This page is also linked from the NanoScreen family website for transparency and convenience.

2. Core privacy commitment

NanoScreen is designed to process screening work locally. Study files, screening criteria, PICO fields, notes, decisions, and keyword lists are handled on the user's device within the browser context of the extension. We do not collect, sell, rent, or transmit this screening content to our servers for analytics, advertising, profiling, or resale.

3. What information NanoScreen processes

To perform its functions, NanoScreen may process the following information locally on the user's device:

  • uploaded screening files such as CSV or Excel files;
  • study titles and abstracts contained in those files;
  • reviewer-entered criteria, including Inclusion/Exclusion fields or PICO fields;
  • reviewer names, notes, justifications, and screening decisions;
  • highlight keywords used for visual guidance during screening; and
  • local extension settings needed to support the user interface and workflow.

This information is processed to enable the tool's screening features and is not collected by us as a remote dataset.

4. What NanoScreen does not collect

  • We do not collect uploaded study files on remote servers.
  • We do not collect researcher notes, decisions, or screening criteria for centralized storage.
  • We do not use tracking pixels, advertising SDKs, or behavioral analytics tools inside the extensions.
  • We do not sell personal data, research data, or usage data.
  • We do not use screening data to train remote models.

5. Local processing and AI

For the AI-assisted NanoScreen extension, AI-supported screening is designed to operate using Chrome's native on-device Nano capabilities, subject to browser availability and user environment. The goal of this design is to keep processing local to the browser environment rather than sending screening content to external AI APIs.

6. No remote code

NanoScreen does not rely on remotely hosted executable code to change how the extensions function after installation. We believe users and reviewers should be able to trust that the code reviewed for publication in the browser store is the same code used to operate the extension. This local and store-reviewed approach is part of our privacy-first philosophy.

7. Permissions

NanoScreen requests only the permissions needed to provide screening functionality. Permissions are used for local file handling, interface features, and the extension workflow. They are not intended for advertising, unrelated tracking, or hidden data extraction. If a feature opens a support page, homepage, or store page, that happens only when the user clicks a visible link or button.

8. Data storage on the user's device

Some settings or workflow data may be stored locally in the browser or extension storage so the tool can remember the current session, reviewer inputs, or interface preferences. This storage is used solely to support the user experience and remains under the user's local browser environment unless the user deliberately exports files or shares them externally.

9. Exports and user control

Exported CSV or Excel files are created only when the user chooses to export. The user remains in control of whether to save, share, transmit, or store those files elsewhere. NanoScreen does not automatically upload exported files to our servers.

10. Children's privacy

NanoScreen is intended for research, academic, and professional screening workflows. It is not directed to children, and we do not knowingly collect children's personal information.

11. Changes to this policy

If this Privacy Policy is updated, the revised version will be posted at this page with an updated effective date. Any future revisions will continue to reflect our privacy-first approach and our commitment to transparent disclosure.

12. Contact

If you need a privacy contact email or want this policy adapted for a specific institutional review or browser store submission, you can add your official support or contact address here before publishing the page.