ChemDFT

Privacy Policy

What ChemDFT collects, where your data lives, which sub-processors are used, and how to export or delete your information.

In short: We collect only what is needed to authenticate you and run your calculations. We do not sell personal data, do not use tracking cookies, and do not show ads. Your scientific files stay yours and you can export or delete your account at any time.

BETA. Last updated 10 November 2026 (version 2026-11-10). Contact: tab@chemdft.com.

What we collect

  • Account details: When you sign in with Google, we store your internal account ID, name, email address, profile image (if provided and stored), sign-up source (“self” for beta users), the terms version accepted, and the timestamp of acceptance.
  • Scientific data: Projects, molecular structures, uploaded files (e.g. XYZ, CIF, PDB, MOL, SDF), calculation requests, job configurations, results, and their provenance records.
  • Feedback reports: If you send feedback from within the app, we collect your account ID and email, category type, title, text details, attachment count and total size, current page path, app version, language, and browser user agent. Feedback text and report metadata are stored in the authentication database until account deletion. Attached files are never stored on ChemDFT servers or databases; they are transmitted directly via transactional email to the team mailbox at tab@chemdft.com and remain only inside that mailbox.
  • Contact form messages: If you use our public contact form, we collect your name, email address, organisation (if provided), selected topic, message text, and a technical cryptographic hash of your client IP address (used strictly for rate limiting and abuse prevention). The purpose of collection is to answer your message and prevent spam abuse. Only the operator (Tabriz Ahmadli) sees your message. Emails are delivered via Resend over HTTPS; automated abuse protection is provided by Cloudflare Turnstile. Message emails are kept in the operator mailbox for up to 12 months unless an active conversation continues. The technical rate-limiting database record (which contains zero message text or personal data, storing only the hashed network identifier and status) is deleted after 90 days. You may request deletion or a copy of your contact communications at any time by emailing tab@chemdft.com.
  • Operational and security records: Session tokens, IP address, and browser user agent used strictly for authentication, abuse prevention, and rate-limiting. Logs of sign-up attempts record only a cryptographically hashed reference to email addresses. Audit events record internal account IDs without personal names or emails.
  • ORCID: Only if you choose to link an ORCID iD in Settings: we store your authenticated ORCID iD and (if ticked) display name. We store no ORCID access tokens.

We do not sell personal data and we do not display advertising.

Where data lives and sub-processors

  • Website frontend: Hosted on Vercel serverless platform.
  • Authentication database: Hosted on Neon (managed PostgreSQL) in AWS region us-east-1.
  • Scientific backend and storage: Amazon Web Services (AWS) in us-east-1 (FastAPI backend, primary PostgreSQL database, S3 object storage for calculation artifacts and uploads, and EC2 on-demand compute worker).
  • Transactional email: Resend (an email service operating over HTTPS used exclusively to deliver in-app feedback reports and public contact form messages to the team mailbox).
  • Abuse protection: Cloudflare Turnstile (a privacy-preserving verification service used exclusively on the public contact form to prevent automated spam abuse without tracking cookies).
  • Identity providers: Google OAuth (for authentication) and ORCID (optional authentication and citation attribution).
  • AI providers: Only if the AI Scientist feature is enabled for your account. AI is disabled by default for new accounts during the beta (CHEMDFT_AI_FOR_NEW_USERS=false). No project data, molecules, or conversational text are sent to any AI provider unless AI is explicitly active for your account and you submit a prompt to the AI Scientist (routing to NVIDIA hosted models or Moonshot AI/Kimi).

Cookies

  • Session cookie: An essential, encrypted HttpOnly cookie (better-auth.session_token, with __Secure- prefix on HTTPS) that maintains your signed-in session. SameSite=Lax.
  • Terms cookie: chemdft_terms_accepted=true (SameSite=Lax, temporary 10-minute cookie set before Google OAuth redirect to record consent during sign-up).
  • ORCID cookies: chemdft_orcid_binding and chemdft_orcid_next (HttpOnly, SameSite=Lax, Secure when hosted, temporary 10-minute cookies used solely to prevent login CSRF during ORCID linking).

ChemDFT sets no advertising cookies, no analytics cookies, and no third-party tracking cookies.

Your control: export and deletion

  • Export: Settings → General → Your data → Download. You receive a ZIP archive of JSON files containing your account profile, projects, structures, jobs, and calculation results with provenance.
  • Delete: Settings → General → Delete account. When confirmed by typing your email:
    1. Running computational jobs in projects you own are requested to cancel.
    2. Content of owned, unshared projects is purged; project records are renamed to “Deleted project” with slug “deleted-<id>” to preserve foreign keys in immutable audit records.
    3. Stored input files and calculation artifacts are deleted from AWS S3 object storage.
    4. Your project memberships, AI user preferences, BYOK credentials, and ORCID links are permanently deleted.
    5. Your personal organization is renamed to “Deleted workspace”.
    6. Your user account is irreversibly anonymised (email set to deleted-<id>@deleted.invalid, name to “Deleted user”, and account disabled).
    7. Your stored feedback reports are deleted from the authentication database.
    8. Your active sessions, linked Google accounts, and credentials are permanently removed from the Better Auth database.
    Backups: automated daily PostgreSQL database dumps in AWS S3 expire after 30 days. Feedback emails already delivered to the team mailbox exist outside the database; write to tab@chemdft.com for mailbox deletion requests. Projects shared with other researchers remain with the co-members; only your access ends.
  • Contact: To access, correct, or request deletion of your personal data, or for any privacy question, contact Tabriz Ahmadli directly via our Contact form or at tab@chemdft.com.

Also read the Terms of Use and the Beta notice.