What Anaxus stores, and how it is protected.

Anaxus is a collaboration space for a research team. It stores the group's working record: projects, tasks, team members, requests and approvals, dates, messages, and links to files the team chooses to add.

It is not built to store protected health information (PHI), and members are asked not to enter any. That means no patient names, record numbers, dates of birth, images or anything else that identifies a patient. Study data that contains PHI belongs in the system your institution has approved for it.

We do not claim that Anaxus is HIPAA compliant, and it does not hold a security certification. If what you plan to store requires either one, Anaxus is not the right place for it.

Each department gets its own workspace, with its own database and its own address on anaxus.app. One department's records are never stored in another department's database.

Departments at different institutions never share a server.

This website is separate from every workspace. It stores no department data and cannot read any.

Members sign in to their department's workspace with the Google or Microsoft account their institution manages. A department can also allow sign-in with an email and password, which each member sets up from a link sent to their email.

Each workspace has its own sign-in. Signing in to one department's workspace does not sign you in to another, unless you link them yourself. Where linking is turned on, a member of several workspaces can link them in Settings. One sign-in then opens each of them, and Home lists that member's own tasks, deadlines and requests from each. A link can be removed at any time.

Inside a workspace, members can see the group's projects and people. That is on purpose: it is how people find projects and join them. Nobody outside the workspace can see any of it.

Coordinators and owners manage roles, review requests and change settings. Being faculty does not grant those permissions automatically. Someone has to assign them.

Sign-ins and changes to settings are logged with who made them and when.

A group can have a public page. It lists published papers and posted preprints only. Projects that are active, submitted, internal, withdrawn or rejected never appear there, no matter how a setting is set.

A person can also have a public profile page. It is off until they turn it on, they choose each item it shows, and the same rule applies: published papers and posted preprints only.

A person's email address appears publicly only if they have chosen a public contact address.

Each workspace's database is backed up. We test the backups by restoring them, so a bad backup is found before it is needed.

This site is a set of static pages served through Cloudflare. It has no analytics and no advertising trackers.

The request form sends what you type to us when you press Send, and we use it only to reply to you. The form uses Cloudflare Turnstile to block automated spam.

If this page does not answer your question, or your institution needs a security review, email [email protected].