Free Guest Beta Privacy Notice

No accounts, payments or sale of data

The Beta does not ask you to create an account or provide a login, password or payment/card details. We do not sell guest data. No advertising or analytics tracker is added by this Beta site. Anonymous sessions do not mean that network metadata cannot identify a visitor.

Session cookies and identifiers

Guest Studio uses random guest and entrance-security identifiers in essential Secure, HttpOnly, SameSite=Strict session cookies. The server uses the guest identifier, not your IP address, to associate your session with its temporary workbench. Request-forgery protection and the ACI application's security cookie may also be used. Keep your browser session private; do not share cookies or tokens. An expired identifier cannot restore a previous workspace.

Temporary project, input and output files

Inputs, uploads and generated outputs are processed in isolated temporary guest resources to provide the selected engineering workflow. Uploads are treated as untrusted. Do not submit sensitive personal information or confidential project material in this Beta. A confirmed Finish or session expiry removes the temporary worker resources and associated workspace files. They are not retained for 30 days or offered as a backup service. Sessions have a 60-minute maximum and 20-minute inactivity limit; closing a tab is not immediate deletion.

If safe cleanup cannot be confirmed after a failure, the workbench is quarantined and not reused. If deletion fails, deletion is not confirmed: resources remain inaccessible to later guests and admission is paused for operator review. We do not claim that a quarantined workspace has been deleted or promise an unverified cleanup deadline. Unsaved work may be lost on restart. Download files you need before Finish or expiry.

Operational and security metadata

To operate and protect the service, we process limited technical metadata such as timestamps, service status, errors and abuse/rate-limit signals. Network infrastructure may process or log IP addresses and connection/request metadata. IP is not a guest identity or authorization credential. Routine application access logging and guest-container output logging are disabled in the release configuration; operational service logging remains enabled. Project contents, passwords, session cookies, tokens and request bodies must not be written to routine logs.

Routine Beta operational/security logs under our control have a maximum 30-day retention policy, with automatic rotation/cleanup and storage limits that may remove them sooner. Copies under our control must follow the same policy. Temporary project files have the shorter session lifecycle above. This is not a statement that every infrastructure provider stores all metadata for exactly 30 days.

Hosting and Cloudflare

The service runs on hosted server infrastructure and uses Cloudflare for network delivery and protection. Cloudflare may process connection/security metadata, including IP addresses, under its applicable service terms and privacy practices. Its independently applicable retention is not set by our server's journal configuration. See Cloudflare's Privacy Policy. We do not invent a provider retention duration or promise that our 30-day server policy overrides it.

Support and your requests

For a privacy or support enquiry, contact support@structdesignhub.com. Information you voluntarily send by email is separate from the anonymous in-app workspace and is not automatically erased by Finish. Avoid sending passwords, cookies or sensitive engineering data. Because there is no account, do not assume we can identify or recover an expired workspace from your name or IP.