Yes. Your account only ever sees the shared reference-genome library (read access) and your own personal output directory. GFPlatform enforces this on the server side — it isn't just hidden in the interface.

The shared library currently includes Arabidopsis thaliana, Beta vulgaris, Chenopodium quinoa, Glycine max, Oryza sativa, Solanum lycopersicum, Solanum tuberosum, Sorghum bicolor, Spinacia oleracea, Vitis vinifera, and Zea mays — see the Genomes tab for the full taxonomic breakdown. Ask a lab admin to add more to the shared directory.

Yes — the Proteome, CDS, Genome, and GFF fields accept any file path your account can reach, including files you've placed in your own workspace directory.

By default, yes — registration requires an educational email address (.edu or an academic ac.<country> domain). Lab admins can allowlist specific non-.edu addresses on request.

Yes — the whole pipeline runs inside a container with every dependency (HMMER, IQ-TREE, MCScanX, MEME, and more) pinned, and every run parameter captured in a single config file.