DASH AI / PRIVACY
Privacy notice
Effective date:
This notice explains the information handled by the Dash website, Dash desktop studio and related purchase and licensing services. The publisher is Archyy Studio. For privacy questions or requests, contact support@archyy.live.
Camera, images, prompts and generated output
Camera permission is requested when you enable a camera. When you use an enabled AI editing workflow, the studio sends selected camera frames, appearance-reference images, prompts and run settings to the Dash GPU runtime you configure. That runtime processes the inputs, including pose and face information used to drive character motion, and returns generated frames to the studio.
A runtime may be on your own machine or another machine reached through a connection or private tunnel. Media leaves your PC when the configured runtime is remote. A local studio interface does not by itself mean that all processing stays on your PC. The operator of a separately configured GPU or cloud service may also handle media, files and service logs under its own practices.
Live workflows use input and output buffers during processing. Offline video workflows can create output files and preprocessing files on the runtime machine. Runtime caches, saved outputs and logs are separate from website purchase records. Check the storage, access and deletion arrangements of your chosen runtime before sending personal or sensitive media.
Website purchases and payment verification
For a purchase through the Dash website, Dash stores the contact email you enter, an order reference, checkout request identifier, amount and currency, the purchase-acknowledgment version, creation and payment timestamps, invoice identifiers, payment URL and verification status. A derived IP-address identifier is stored to limit repeated checkout requests. These records are used to create and reconcile an invoice, verify payment, provide a receipt and associate the purchase with its license.
Website crypto checkout is handled by Exnode. Dash sends the transaction amount, currency, order reference and return/callback details to Exnode; you choose payment details on its payment page. Dash receives invoice information and payment status from Exnode. Exnode processes the information you provide to it under its own terms and privacy practices. Do not send Dash wallet private keys, recovery phrases or payment passwords.
Microsoft Store purchases use Microsoft's purchase and account services. The Dash Store release is still in preparation. Its desktop entitlement bridge reads the running app's Windows package identity and the active, trial and expiration status reported by Windows StoreContext on that computer. It does not collect Microsoft account identity, payment details or customer identifiers, and does not persist a Dash-managed Store-license cache.
The website's Exnode checkout is a separate purchase route. This notice does not replace Microsoft's privacy notice or establish that the website license-key workflow is available for a Store purchase.
License and device records
Website license services store purchase entitlements, license-key hashes and hints, encrypted purchase-license key material, sign-in session records and activation status. When device activation is available and you use it, the service also receives an app-generated device identifier, your chosen device label, a public key and its fingerprint, verification challenges, and lease/status timestamps. These records link a registered device to an entitlement and support activation, renewal and deactivation.
The desktop activation client stores its device key and cached license lease in your Windows user profile's Dash application-data directory. On Windows, this activation data is protected using the current user's Windows data-protection facility. The preview uninstaller preserves activation data and any Dash browser data left in that profile. Uninstalling the app is not a request to delete website purchase or license records.
Browser storage, cookies and network requests
- The website keeps a checkout retry identifier and the entered purchase email in browser session storage so a retry can refer to the same invoice. Receipt links can also remain in browser history.
- Purchase-license pickup uses an order-specific session cookie that expires after 72 hours. Website license sign-in uses a session cookie that expires after 30 days; signing out ends the active sign-in session. Server session tokens are stored as hashes. These cookies are marked Secure, HttpOnly and SameSite=Lax.
- The current public account interface uses a license key for sign-in. Legacy email sign-in records may also be retained where that service was used; its email links expire after 10 minutes and its sessions after 30 days.
- Hosting and database providers handle website requests and application records. Requests expose network information such as an IP address and browser information to the service receiving the request. Application abuse controls use derived IP identifiers.
- The main website loads fonts from Google and embedded demonstration videos from a CloudFront delivery address. Loading these resources sends a request to those providers, which can receive network and browser information. Their own privacy practices apply.
Clearing browser storage removes data held by that browser, but does not delete server purchase, license or device records. Authentication expiry limits access; it does not itself erase database records.
Operator notifications and other recipients
The website sends checkout-started and verified-payment notifications to the operator's configured Telegram chat. These messages include the purchase contact email, product and amount, order reference, Exnode invoice identifier, status and event time. Telegram and people with access to that chat can receive this information. Notification delivery state is also recorded in the website database. These messages are separate from receipt and license sessions and can remain after those sessions expire.
Other recipients depend on the feature used: website hosting/database providers, Exnode for website payments, Microsoft for Store purchases, a configured GPU or cloud runtime operator for media processing, and the business mailbox provider for support correspondence. If legacy email sign-in is used, its mail-delivery provider receives the email and sign-in message. Support correspondence includes the information you choose to send.
The website implementation hashes authentication tokens and encrypts retained purchase-license key material. Contact emails, transaction records and device labels remain associated with their records; they are not anonymous. The security of a separate GPU connection and runtime depends on its configuration and operator. This notice does not promise that every connection, provider or stored record has the same protection.
Retention and your choices
Purchase, license and device records persist until manually deleted. There is currently no automated deletion schedule for these records, operator Telegram messages or support correspondence. Cookie and token expiry is an access limit, not a promise that associated records are deleted. Runtime media, outputs, caches and logs have the retention arrangements of the runtime you use.
You can stop camera capture, disable camera access in your browser or Windows settings, disconnect the studio from a runtime, sign out of the website and clear browser storage. Where enabled, account device controls can deactivate a registered device; deactivation changes license status and does not delete purchase history. Stopping or closing the desktop interface does not necessarily stop a separately rented GPU or remove its files.
To request access, correction or deletion of information held by the Dash publisher, email support@archyy.live. Include enough information to locate your record, such as the purchase contact email and order reference. Ownership may need to be verified. Requests are handled manually, taking account of applicable recordkeeping requirements; there is no automatic deletion button or promised response deadline. Do not include a complete license key, private device key, session cookie or wallet secret.
Changes and contact
This notice will be updated when Dash's data handling changes. Check the effective date above. The publisher's business contact is support@archyy.live; the publisher website is archyy.live. For product questions, see Dash support.
Hosted website character demo
Preview camera opens a local preview only when you choose it, and camera selection becomes available after access is allowed. The demo page shows whether hosted processing is available. Local camera setup can be used while cloud processing is unavailable.
The optional website demo uses the operator’s Vidu web account through a private server. The purchased Dash desktop studio uses JoyAI, so this hosted preview does not establish desktop quality, speed or hardware requirements. Preview camera is local and video-only. After you accept the sharing notice and choose Start, your selected camera sends video directly to Vidu’s video service over encrypted WebRTC, and the service returns edited video to your browser. The operator’s computer is not part of that connection. The microphone is disabled. Video connections can expose connection IP addresses to the service.
You may choose a character image or use the hosted demo character. Image selection and its preview stay local: the browser decodes the image and makes a fresh JPEG no larger than 1 MiB and 1536 pixels on its longest edge. Only after you accept the sharing notice and choose Start does the private server upload that image to the operator’s Vidu account for use as the reference. The backend holds image bytes in memory for preparation and does not persist them in its storage. Vidu may retain the uploaded image after the 30-second live session under its own practices. Removing the local image or stopping the demo does not establish deletion from Vidu; remote deletion has not been verified.
Account credentials remain on the private server; your browser receives only temporary video-session credentials. A separate HttpOnly cookie, derived visitor and IP identifiers, session IDs and timestamps help limit use. Video and reference-image bytes are not stored in the website database. Limited use and shutdown records may remain for rate limiting. Leaving or hiding the page stops local camera capture and requests shutdown. Image preparation is limited to 15 seconds before the live claim; the browser and private server then enforce the separate 30-second live-session limit, including its connection setup. Vidu processing and retention follow its own practices.
The website displays edited video in its output canvas. The optional Dash AI watermark is off by default; choose its setting before starting a preview. That choice applies to the preview and its saved image and video. Changing the setting after a preview applies to the next preview. During a started preview, your browser prepares a video of the output in local memory. Download video saves that file to your device only when you choose it; the recording is not uploaded to Dash. Its format depends on your browser. Download it before starting another preview or leaving the page, which clears the local recording. Save frame separately downloads a PNG. Operational usage records are retained separately from media and purchases; stopping the camera does not delete downloaded files or provider records.