Last updated: April 28, 2026 · Liganx Beta
When you submit a docking job, Liganx stores the inputs you provide so we can show you results: the PDB ID (or uploaded PDB file), the chain, the mutation list, the compound SMILES strings, and any names you attach to compounds. We also store the docking outputs we compute from those inputs — Vina/Vinardo scores, ProLIF interaction fingerprints, ADMET descriptors, the docked pose files, and the cross-docking validation cache. Job records are keyed to a random share ID, not to a user account.
Liganx works without an account — you can run a job, view the matrix, and open a pose without signing in. Accounts are optional: signing in with an email lets us keep your job history and raise your free-run limit, and nothing more is required to use the app. We run no third-party analytics tracker on the matrix or pose-detail pages, and we don't read referer headers for cross-site tracking. The only network requests our frontend makes are to our own API (api.liganx.com) for jobs and to RCSB / PubChem for structure and compound lookups when you autocomplete in the new-job form.
Anyone with a job's share URL can view its inputs and outputs. Treat share URLs like passwords for confidential work — don't paste them into public channels if your SMILES are proprietary. We don't have a password-protected sharing mode yet; that's tracked as a future feature. If you need to remove a job from our database, email the contact below with the share ID and we'll delete it.
Job metadata lives in a Supabase Postgres database in US-East-1. Pose files are stored on Fly.io's persistent volume in IAD (Ashburn, Virginia). Raw RCSB PDB caches and FoldX/PDBFixer derivatives live on the same Fly.io VM. Pod GPU docking workers run on RunPod infrastructure; receptor and ligand files are sent there for the duration of a single docking call and discarded after the result returns. No data leaves North American jurisdictions in the current deployment.
Liganx uses one piece of browser local storage: your dark/light theme preference. No cookies, no tracking pixels, no third-party scripts. Vercel (our frontend host) and Fly.io (our backend host) may collect request logs that include IP addresses for normal operational purposes; we don't query those logs except to debug outages.
Questions, deletion requests, or anything else: email hello@liganx.com. See also our Terms of Service.