Privacy Policy

Last updated: 2026-11-10

1. What we collect

Data	Purpose	Retention
API key (stored as a hash)	identify the user, manage quota and credit	while the key is in use
IP address of requests	free-tier limits, abuse prevention	90 days
Share pages (the image/video, title, note and optionally the script of results you chose to publish with render_share)	Showing the public page /r/ and the gallery	Until you unshare (render_unshare) or the operator removes it
Submitted files, scripts, intermediate data, renders	performing the render and returning results	24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total)
Job metadata (file sizes, frame counts, resolution, GPU seconds, timestamps, failure reasons, Blender warnings, client type) and, on the /start page, which steps were reached and how long the finish button was on screen before the page was left (short tags only; no key, IP address or file name in these records)	billing, incident handling, improving the service	1 year
Email address (only if you choose to register one)	sending the result links when a final render finishes; telling you when a render is on hold because the account is short of GPU time	until you unsubscribe or remove it (every email has a stop link)
A token for the key last connected on this browser (a cookie sent only to the connection page /connect; stored hashed, it holds no key or email)	letting you continue with the same key, credit, free time and past renders when you connect from another AI app, without signing up; also when you open /start (the studio) or the pricing page on the same browser (the browser gets a revocable token of its own, never the key)	180 days after the last connection; "forget it on this browser" on the connection page or revoking the key stops it
Billing records, payment identifiers and amounts reported by the payment provider, the email entered at checkout	billing, receipts, support	as required by law (7 years as accounting records)

Card numbers and other payment details are handled by our payment provider (Stripe); we never see or store them.

2. How we use it

To provide the Service, bill, prevent abuse, handle incidents, improve the Service and comply with the law. The contents of your scenes and renders are never used for machine learning or any purpose other than providing the Service.

3. Sharing and processors

Payments are processed by Stripe. Notice and sign-in emails are sent through Resend (we pass the address and the email text). Rendering runs on our own hardware; at busy times it may run on GPUs rented from third-party providers under contract with us, in which case your files and renders pass through their machines (in an isolated environment per job, deleted afterwards). We do not share data with anyone else unless the law requires it.

4. Security

Your files are processed only inside an isolated environment with no network access and minimal privileges, which is destroyed after the job. API keys are stored hashed. Connections use TLS. See the Security page.

5. Your rights

Contact us to access, correct or delete stored data. Requests concerning data tied to an API key are honored for the holder of that key.

6. Changes

Changes to this policy are posted on the Service.

Contact

JasmyLab Inc. · contact@jasmylab.com

Browser entry measurement

The first source category, public page path, timestamp and a random session ID are kept temporarily in sessionStorage for a 30-minute attribution window, then sent with key creation to aggregate render success. The ID contains no identifying information and does not track another tab or a later 30-minute window. This measurement stores no full referrer URL or query parameters and uses no cookie. It expires after 30 minutes or when the tab closes, and is disabled when Do Not Track or Global Privacy Control is enabled. The source recorded against a key follows the usage-log retention period.