Privacy
Updated October 21, 2026. This notice applies to the independent JST-2 Studio at jst-2.com, not to Viggle’s own services.
Account and sign-in information
When you use Google or GitHub, we receive your provider account identifier, name, email address, email-verification information and profile image when supplied. We use these to create and authenticate your account. We do not ask for your Google or GitHub password, access to your email messages, Drive files or private repositories.
Authentication records, provider tokens and session records are stored server-side in PostgreSQL hosted by Neon. Essential HTTP-only cookies maintain your session. Authentication may record IP addresses and user-agent information for session management and rate limiting.
Prompts, results and credits
We store scene and motion prompts, asset names, task status, generated-result links and credit transactions to provide your workspace and account history. Character images and prompts are sent to Viggle’s API for generation. Our application forwards uploaded character images without permanently storing their original bytes; an image hash is retained to prevent duplicate submissions. Do not upload images or personal data you are not authorized to share. Provider-hosted results are subject to Viggle’s retention rules; scene tasks are generally readable for about 72 hours, while character and motion export links are signed for one hour and can be refreshed while the provider retains the asset. Our account and task records are not automatically deleted when provider download links expire.
Payments and service providers
When payments are enabled, Stripe handles payment details on its hosted Checkout page. Our server uses Stripe’s SDK to send your email address, account identifier and order details, so a verified payment can be assigned to your account. We store Stripe customer and payment references, order records and credit transactions; we do not collect or store payment-card details. Hosting and requests are handled by Vercel; database records by Neon; generation by Viggle; and payments by Stripe. These providers may process information in countries other than your own.
Use and retention
We use account data to provide sign-in, generation, accounting, fraud prevention and support. We do not sell Google or GitHub account data or use it for advertising. Operational hosting logs may record requests. Account, task and financial records are retained to operate the service and resolve disputes; financial records may need to remain for applicable legal obligations.
Optional Google Analytics
With your permission, we use Google Analytics 4 to measure visits, page views, referring websites and aggregate device information. Google receives technical connection information when analytics is enabled. We do not load Google Analytics before you opt in. We do not send your email, account ID, generation prompts, payment details, URL query strings or fragments. Advertising storage, advertising personalization and Google Signals are disabled; automatic form and link tracking is disabled.
Analytics cookies have a 90-day lifetime. Your consent choice is stored locally in your browser. Use “Analytics preferences” at the bottom of any page to accept or reject optional analytics. Withdrawing consent stops collection, removes this site's Google Analytics cookies and reloads the page; it does not erase data previously collected by Google. Refusing analytics does not affect login, generation, payments or the 3D viewer.
Your choices and contact
You can sign out at any time and revoke access through your Google or GitHub account settings. Revoking provider access does not itself delete records already stored by JST-2 Studio. To request access, correction or deletion, contact the site operator at support@jst-2.com. Identity verification may be required before acting on a request.