Website accounts and support
Website notice · Updated 22 October 2026. Contact: [email protected].
Accounts are optional
The personal beta downloads and runs without a website account. You can send private support messages without signing in. An account is optional for conversations linked to your account. The account service stores your email, optional display name, password hash and session records. The browser receives a short-lived access token in page memory and an HttpOnly refresh cookie. The language setting may be stored in your browser. Sign out on shared computers.
Email confirmation
Website registration requests a transactional confirmation email through the configured mail service. The confirmation link expires after 30 minutes and works once. The server stores a hash of the link token, its expiry, use and delivery status, linked to your account. Signed-in users can request another email after a short cooldown; the newer link replaces earlier links. Existing accounts are not automatically marked confirmed.
Messages
Choosing Send saves your subject and message in a private support database. If you are signed in, the conversation is linked to your account email and display name. Otherwise a random browser identifier is created; no email or password is required. Only that browser (or the signed-in account holder) and authorized administrators can read the conversation. Reading or answering another account's conversation requires additional administrator verification. Replies appear in Messages; this is not a live chat and no email reply notification is currently sent.
Do not submit passwords, API keys, confidential client material or unnecessary personal information. There are no file attachments. Messages are not sent to an AI provider for automated replies.
Guest browser access
Sending a guest message creates a host-only, Secure, HttpOnly, SameSite cookie on api.3dklyn.com for up to 30 days. It is needed to reopen your private conversation in the same browser. Only a hash of its random token is stored on the server. Clearing browser cookies, using another browser or expiry removes guest access; it does not itself delete the saved messages. Do not use guest support on a shared browser for sensitive matters.
Storage and deletion
The support service stores messages on the 3DKLYN server separately from account credentials. It checks sign-in with the account service and does not store your account password. Administrator authenticator secrets are encrypted and recovery codes are stored as hashes. Request limits use hashed identifiers.
You can delete your own conversation in Messages after confirmation. This removes it from the active support database; it does not itself erase infrastructure backups. No automatic message-expiry period is configured. Contact support about a broader deletion request or any backup copy. Account deletion and deletion of local plugin files are separate actions.
Hosting and downloads
The website uses HTTPS and its hosting and security infrastructure processes connection information to deliver pages and protect the service. The download counter stores an aggregate count of completed full-file responses, including repeat downloads. It does not identify individual downloaders. Optional first-party analytics is described below. No advertising pixels or third-party analytics service are included.
This website notice supplements the separate plugin privacy notice and supplied-document storage notice. Those earlier editions remain unchanged.
Optional traffic analytics
Choose Allow analytics to help us measure which sources bring visitors and downloads. Declining does not restrict downloads, support or plugin use. You can reopen these choices at any time. Global Privacy Control and Do Not Track disable optional analytics.
After consent, we store a random identifier in a Secure, HttpOnly, host-only cookie on api.3dklyn.com, restricted to the analytics API, for up to 30 days. Only a hash of that identifier is stored in the analytics database. Your analytics choice is saved in this browser's local storage for 180 days, including when you decline. The identifier is not a verified person and is not matched across devices.
We record page-visit events, completed installer responses prepared by the browser, and clicks to the external Donate page. We store the source, medium, campaign and post labels from tagged links and a category derived from the referring hostname. We do not retain the full referring URL, page query string, IP address or user agent in the analytics database. Request-abuse controls and infrastructure logs are separate. Do not put personal information in campaign labels.
First-source and last non-direct-source reports use event-time source labels. We do not join this analytics identifier with account identities, emails, support messages or plugin activity. Download events do not verify installation or saving the file. A Donate click does not verify a payment. Donatello checkout receives no analytics identifier from this feature.
Optional analytics uses consent. Data is stored in a separate database on the 3DKLYN server and is accessible only to authorized administrators with additional verification. Traffic events and inactive browser records are removed after 90 days through hourly maintenance and on service startup. Withdrawing consent erases this browser's linked traffic records and clears the analytics cookie; your refusal preference remains. Clearing cookies without withdrawing consent does not itself erase previously stored records. Contact support for privacy requests.
Manual donation records
The analytics panel has no automatic Donatello connection or payment verification. An authorized administrator may manually record a received payment's reference, amount, currency, date and known source to maintain voluntary-support records. No donor name, email, message or card details are requested by this feature. Source labels supplied manually are not presented as automatic attribution. Manual records are retained in this panel for 90 days from entry and can be marked void without counting them in totals. Statutory financial records, if separately held, have their own applicable retention requirements. Contact support to ask about a record.