Privacy at a glance
The browser tools calculate on your device. Projects, datasets and saved analyses are stored in this browser when you choose to save them. Scientific data is sent to a separate analysis/report service only when you explicitly request a server operation and consent to that upload. Ads and marketing analytics are disabled in the supplied build.
Who to contact
SCIOVANTA is the publisher name used by this platform. Legal operator details require owner review before public launch. For privacy enquiries: Contact details coming soon. Describe the account or interaction concerned; avoid including confidential research records or patient identifiers in the initial message.
Browser calculations and saved work
Dissolution comparisons, release fitting, browser ANOVA, calculators and the browser scientific workflows process the values you enter locally. Saved projects, numeric datasets, analyses, optimization histories, favorites and recent methods use the browser’s local storage. Theme preferences are also stored locally. The optional transfer between DoE and Bayesian optimization uses session storage.
Local storage persists between visits until you remove it or the browser clears it. It is not cloud synchronization. Another person using the same browser profile may be able to access saved work. Export a workspace backup before clearing site data. Downloaded files and backups remain wherever you save them until you delete those copies.
Optional server processing
The original Python analysis and formatted-report features require a separately configured service. A server action sends the selected measurements and settings to that service after explicit upload consent. In the supplied implementation, scientific request bodies are processed in memory rather than written to the account database, application analytics or scientific-body logs. This describes application behavior, not a guarantee about every hosting provider’s infrastructure.
Generated server reports use temporary, account-bound download links. The default report lifetime is one hour; the actual server configuration controls expiry. Expiry cleanup or a server restart removes those temporary reports. Browser analysis and downloaded local files have a different lifecycle.
Accounts, sign-in and report credits
Where account services are enabled, the application stores the email address, hashed sign-in/session tokens, credit balance, credit-ledger entries, order references and report-job status. Optional profile details are a display name, institution and research focus. A Google connection stores the provider name and stable account identifier; verified identity is checked on the server. Scientific measurements are not stored in the account database. Passwordless email sign-in shares the address and sign-in message with the configured email provider.
If hosted checkout is enabled, payment information is entered on the payment provider’s checkout. The application exchanges the account identifier, email and order/credit information needed for the purchase; its account database does not store payment-card numbers. Provider records are governed by that provider’s own notice. This page does not enable payments or email delivery.
Cookies and storage controls
The optional account service uses Secure, SameSite=Strict cookies: a browser-bound email login cookie (up to 15 minutes), a session cookie (up to 24 hours), and a CSRF-protection cookie (up to 24 hours). Google sign-in additionally uses a Secure, HttpOnly, SameSite=Lax browser-binding cookie for up to 10 minutes so the identity-provider redirect can return to this site. Its transaction is single-use. Sign-out clears the session and CSRF cookies. Cookie restrictions can prevent account functions while local research tools remain usable.
When configured and chosen, Google sign-in redirects you to Google and requests only openid, email and profile. The application receives your verified identity and display name, not permission to read Gmail or Drive. Identity tokens are verified for signature, issuer, audience, expiry and the sign-in nonce; they are not saved in the account database. Signing in with an existing email does not silently link accounts. Link Google explicitly while signed in. Account export includes profile and linked identity metadata; confirmed deletion removes them from the active database.
You can remove locally saved work using your browser’s site-data controls. Deleting browser data does not delete downloaded backups or a separately enabled server account. Account export and confirmed account deletion are available on the account page when that service is configured.
Retention and deletion
Browser records remain until removed or cleared. Optional account records remain until account deletion. Confirmed deletion removes account identity, ledger, sessions and available temporary reports after active report jobs have finished. Unlinked order/event hashes may remain to prevent payment replay. Deletion from the active database does not immediately erase older storage pages, provider records or operator backups.
Infrastructure logs and backups follow the actual host’s and operator’s retention arrangements. This notice does not invent a fixed retention period for those systems. Contact the operator about the information and deployment concerned.
Hosting, external services and sharing
Hosting services receive connection information such as IP addresses, request paths and browser details to deliver and protect the site. The application may use temporary in-memory request limits. Self-hosted fonts and scripts avoid loading a public font CDN. There are no enabled advertising or marketing-analytics scripts in the supplied configuration.
No public support mailbox is configured in this build. A single domain email contact will be published after its forwarding has been verified. Do not send patient-identifiable or confidential raw research data through a public support channel. The research tools are not intended for submitting patient records.
Optional server error monitoring
If the server is configured for error monitoring, technical error reports may be sent to Sentry, an error-monitoring provider. This application excludes scientific input values, request bodies, query strings, cookies, headers, user records and dynamic exception messages from those reports. Reports retain an error class and application code locations. The provider receives the server’s network connection information. Browser tracking, visitor analytics and performance tracing are not enabled by this monitoring configuration.
This notice describes the supplied configuration and requires owner and legal review before public launch, including the chosen provider, retention and operator details.
Your enquiries and changes to this notice
You may ask the operator about access, correction or deletion of information you have supplied and about the handling of a specific account or support interaction. The applicable process depends on the information held and the requirements that apply to the operator. Material changes to the application’s data handling will be reflected in an updated notice and date.
Publication status
DRAFT - requires author and legal review. This completed notice describes the current software configuration. Operator review of the deployed providers, retention arrangements and applicable requirements remains necessary before a public commercial launch.