Privacy notice
This page explains how SystemaDock and Theory Vision Online handle your workspace, temporary demo sessions, account information, and payments.
The temporary-demo terms below apply to the dedicated 24-hour demo when available. Other trial or account access follows the terms shown in the account portal.
Updated October 9, 2026 · Applies to systemadock.com and Theory Vision Online
The 24-hour demo is temporary. Register before the pass expires to keep eligible work. If you do not register, demo files, projects, and autosaves are deleted after expiry.
Some technical records remain. An opaque demo identifier and timing records enforce the demo limit. These records do not contain your document content.
Choose when to share. Public sharing and third-party tools can expose the content you send to them. Review what you are sharing before using those features.
1. Temporary 24-hour demo
You can try the software without an account. Your pass starts automatically when guest access opens. No signup or renewal button is required. Refreshing or reopening the demo does not reset the timer. A compact timer shows the remaining time; you can open its details without repeated dialogs interrupting your work.
Demo work is held in a temporary workspace to let you edit and use the software during that 24-hour window. It is not permanent account storage. At expiry, temporary work is cleared and guest access opens a fresh pass automatically during October. If you have not registered, the service removes the demo workspace, including its files, projects, and autosaves.
Cleanup runs periodically, normally every 15 seconds while the service is running. A task already in progress may need to finish before its workspace can be removed; cleanup retries afterward. Service interruption can delay cleanup until the service resumes.
Register before expiry to use the available guest-to-account transfer flow for eligible work. Do not rely on registration after expiry to recover a deleted demo. Registration does not automatically purchase a subscription.
An opaque browser/demo identifier, start time, deadline, and cleanup status remain separate from workspace content to enforce the time limit. This is technical metadata, not saved demo documents. Files you download to your own device remain under your control.
2. Registered accounts and saved work
Google sign-in provides the identity information needed to authenticate and associate you with an account. Your chosen username, account status, and membership information support account access and service features. The sign-in screen identifies the permissions requested.
When you save work to a registered workspace, the service stores the content required to provide that workspace. This can include documents, project files, images, notes, and settings you choose to save.
Registered account storage follows the service's account and access rules. This notice does not promise indefinite storage or a fixed deletion or backup period. Keep your own exports of important work.
3. Payments and subscriptions
Stripe processes subscription and tip payments when you use its checkout or billing portal. Payment and subscription records are used to confirm payment, grant the appropriate access, and manage billing. Stripe handles the payment details entered into its forms under its own privacy practices.
Billing records may need to remain for accounting, dispute handling, or applicable obligations even when workspace access ends. Review the amount and subscription terms shown at checkout before paying.
4. Cookies and technical information
The service uses cookies and session identifiers for sign-in, access control, security, and the demo timer. The 24-hour demo does not introduce browser fingerprinting. Blocking or clearing necessary cookies can disrupt sign-in, demo access, or work transfer.
Hosting and service systems can process technical request information such as an IP address, browser information, request time, and errors to deliver the service and investigate problems. Demo timing metadata and operational records are distinct from your workspace content. This notice does not specify a fixed retention period for those records.
5. Administrator access and privacy commitment
SystemaDock's stated policy is to limit routine member information shown in the administrator dashboard to usernames and payment information, alongside service activity totals. Member document content should not be part of routine administrator statistics.
That dashboard policy is separate from the technical information processed by authentication, hosting, storage, and payment systems to operate the service. It is not a claim that those systems receive only a username and payment amount, or that server operators are technically unable to access stored data. Necessary support and security access should be limited to the work required to operate or troubleshoot the service.
6. Third-party sign-in and optional tools
Google handles its sign-in process, and Stripe handles its payment process. Hosting and storage providers also process the data needed to serve the application.
When you invoke an external research, mathematics, simulation, or other connected tool, the query or content needed for that request may be sent to its provider. Do not include sensitive information in a request unless you intend to send it. Provider availability and data handling follow that provider's terms and privacy practices.
This privacy page itself uses no external fonts, analytics scripts, tracking pixels, or embedded third-party media. Following an external link opens another service with its own practices.
8. Your choices and privacy requests
You can choose whether to use the demo, register an account, save content, invoke external tools, or share work. Use the available account controls to manage your account and the billing portal to manage subscriptions. Account deletion and subscription cancellation are separate actions; review both if you want to end use of the service.
For questions about stored information, access, correction, or deletion, use the Help or support option available in the account portal. A request may require account verification before changes can be made. Payment, security, and other necessary records may be retained separately from deleted workspace content.
9. Changes to this notice
This notice may be updated as the service changes. The date at the top identifies the latest revision. Read the current notice and any feature-specific terms when making decisions about your work.