FastDCF

Local accounts store the username, password, role, and optional email address you provide. Google sign-in accounts also store the Google subject identifier and the email address returned by Google.

Account records are stored on the server in the application data directory and remain there until an administrator deletes them.

The site uses a single authentication cookie named session_id to keep you signed in after login. This is an essential cookie used for core account functionality.

Session data is kept in server memory and is removed when you log out. Sessions may also end when the server restarts.

The dashboard also uses browser session storage for temporary UI state such as active batch runs and recent calculation snapshots. That data stays in your browser session and is not used for advertising or cross-site tracking.

The registration form processes the identifier and password you submit to create a user account. If you register with an email address, that address is associated with your local account.

The contact form stores the email address you enter, your message, the submitting user name when available, your IP address, and your browser user-agent string.

Contact messages are stored on the server and remain there until an administrator deletes them.

The contact and registration pages use Cloudflare Turnstile to reduce automated abuse. The widget is configured in an interaction-only mode, so most visitors will not see a visible verification block unless Cloudflare requires additional interaction.

When Turnstile is used, verification data and related browser signals are sent to Cloudflare so the server can validate the submission.

This deployment does not enable Turnstile pre-clearance. Turnstile therefore uses a one-time verification token for form submission and does not set Cloudflare's cf_clearance cookie as part of this flow.

The login page can load Google Identity Services to support Google sign-in. If you use that optional sign-in method, Google processes the authentication flow and returns identity data to this application.

The site also loads some frontend assets from third-party providers, including Google Fonts, Plotly CDN, and jsDelivr.

If you have a privacy question or want to request deletion of data you submitted through this service, use the contact page.