Privacy & data

Meta-analysis360 helps you run systematic-review workflows (planning, search, screening, and related steps). This page explains—in plain language—what data touches the service, why, and what you can expect. It is not legal advice; ask your institution or counsel if you need binding compliance text.

When you use the workspace, you may enter research questions, protocol text, search strings, reference lists, screening notes, and similar content. That content is stored so your projects work across sessions and devices (where cloud saving is enabled).

Treat anything you paste as sensitive research material: only share what you are allowed to process under your ethics, contract, or grant rules.

Some features send a limited slice of your workflow (for example planning fields, titles, or abstracts needed for a task) to Google Gemini to generate suggestions. Google operates its own privacy programme for those services.

AI output is assistive only—you remain responsible for scientific decisions, registration, and publication choices.

We use trusted providers (for example Google or GitHub) so you do not send a separate password to Meta-analysis360. We store account identifiers and session records needed to keep your data separated from other users’ projects.

We use essential cookies to keep you signed in and protect routes from abuse. These are not used for advertising.

If we add optional analytics later, we will describe it here and—where the law requires it—ask for consent before turning on non-essential tracking.

• Use the product only with data you are entitled to process.
• Sign out on shared computers; clear browser data if you used local-only screening storage.
• For subscription or account questions, use the contact path shown on the site.

We may update this page as features or providers change. The “Last updated” date at the top reflects the latest revision.