Trust

Workspace isolation

Each workspace’s data is isolated at the database level using PostgreSQL row-level security and workspace-scoped policies. The application also checks access permissions.

Security practices in the code

Passwords are hashed with Argon2id. Session cookies are HttpOnly, preventing browser scripts from reading them. Audit logging records supported account and workspace actions. These controls are not a claim of certification.

Real data and honest states

The product’s design policy requires empty and error states to explain their cause and next action without fabricating data. Results must come from uploaded content and actual computation. Missing measurements are described as unavailable; sample numbers are not substituted for real results.

Who operates your data

This service is self-hosted by the organisation that operates this deployment. Account and workspace records use PostgreSQL; files use configurable, operator-controlled object storage, including an S3-compatible endpoint when configured. The software supports multiple isolated workspaces; which workspaces this deployment serves, and the region it runs in, are set by the operator.

Data the service handles

The service handles account and profile information; bibliometric datasets, manuscripts and screenings uploaded by you or your teammates; usage and audit logs; and AI consent and disclosure records.

AI processing and disclosure

A platform administrator configures one AI provider for the deployment, using an OpenAI-compatible endpoint, which may be self-hosted. Features must be enabled individually against their disclosures. The current deployment records this approval at administrator level, not as blanket personal consent from every user; changing a disclosure requires renewed approval. Workspace feature-consent records also exist. Provider region, retention and training terms depend on the configured provider. AI is not necessarily the only external service this deployment uses; any others are set out in the terms of the organisation that operates it.

Retention

Retention periods are operator-configurable; consult the administrator and operations documentation for the applicable defaults. Artifact expiry and dataset retention timestamps determine availability where implemented. Backup expiry and legal-hold handling follow the operator's own operational policies; this draft does not promise immediate removal from every backup.

Your account controls

In Settings → Privacy & data, request a data export, correct your display name and preferred language, or request account deletion with a cancellable 14-day grace period. A workspace ownership transfer may be required before deletion. To change your email or ask about your data rights, contact your workspace administrator.