We store account identifiers needed for authentication, including name, email, username, verification state, sessions and linked OAuth providers. Password credentials are handled through the authentication system and are not exposed in public researcher profiles.

Projects, workflows, saved entities, analyses, notes, team memberships and audit events are stored so the workspace remains persistent and reproducible. Personal workspace data is private by default. Team access follows workspace roles and project visibility.

DEVNU Science records limited page-view telemetry to understand product usage: the page path without query parameters, a hashed anonymous visitor identifier, coarse device class, external referrer hostname, an edge-provided country code when available, and the signed-in account ID when applicable. We do not store raw IP addresses, full browser user-agent strings, scientific inputs, search sequences or page query strings in analytics. Browsers with Do Not Track enabled are excluded. Detailed page-view telemetry is retained for approximately 180 days.

A researcher profile is public only when its visibility is set to public. Research drafts are private and do not become publicly accessible until submitted and approved through moderation. Public profile links and approved research records may be indexed by search engines.

Some tools query external scientific services such as EMBL-EBI, UniProt, RCSB PDB, AlphaFold, Reactome, Ensembl, NCBI and Crossref. The tool interface identifies provenance. Sequence similarity workflows may send the submitted sequence and selected search parameters to EMBL-EBI or NCBI depending on the selected BLAST program. Do not submit confidential, regulated or sensitive sequences to a public provider.

When enabled, OAuth or OpenID Connect receives the identity information required to authenticate or link your account from the chosen provider. DEVNU Science does not need your Google, GitHub or ORCID password. Connected-provider credentials are used only for authentication or verified researcher identity unless a future feature clearly asks for additional permissions.

Access is permission-based, invitation tokens are stored as hashes, and activity logs retain security and research provenance events. Data may be retained while an account or workspace remains active and where necessary for integrity, moderation, abuse prevention or legal obligations.

Privacy or account requests can be sent to [email protected].