Privacy notice
How your information is handled
Effective August 31, 2026
Information we receive
We receive the name, organization, email address, and password credential used to create your account, together with messages, model descriptions, PFLOTRAN files, source code, report templates, and other materials you choose to submit.
How information is used
We use this information to authenticate your account, run the requested workflow, diagnose and improve your submitted model, compile user-provided PFLOTRAN source code when requested, deliver results, respond to support messages, enforce service limits, and investigate errors or misuse.
Q/A records
When you use PFLOTRAN Q/A, we retain the question, technical answer or error status, date and time, originating IP address, retrieved-source references, and the account email when the session is signed in. Authorized administrators may review and delete these records for security monitoring, service improvement, and technical quality review.
PFLOTRAN Community Knowledge
Q/A, diagnostics, and simulation workflows may consult official PFLOTRAN documentation and public PFLOTRAN user or developer discussions. The retrieval layer sends only a short allowlisted set of general PFLOTRAN technical terms, such as a solver or module name, to public search pages. It does not send your full question, uploaded files, project description, email address, or account details. Retrieved pages are treated as untrusted reference material; attachments are not downloaded or executed.
Project isolation and access
Each account has its own workspace and each project has its own subdirectory. Project files are available only to the owning account and authorized administrators supporting the service. Do not upload passwords, private keys, access tokens, export-controlled information, or material you are not authorized to process.
Retention and deletion
Project files are normally retained for three months after a workflow ends. After that period, we may delete the project files to manage limited storage capacity. You may delete a project sooner, which removes its project directory and associated files. Deleting an account removes its projects, stored custom build, sessions, and account records, subject to short-lived operational backups or records required to investigate abuse. Intermediate files without reuse value are removed after a workflow finishes.
Email and service providers
Verification codes, task notices, download links, and support replies may be sent by email. Infrastructure and email providers process the minimum information needed to deliver those services.
Security and limitations
We use access controls, hashed credentials and tokens, restricted uploads, and per-project storage. No internet service can guarantee absolute security. This site is an evaluation service with limited computing resources and should not be used as the only repository for important files.
Contact
Use the Contact form for privacy questions or deletion requests.