Last updated: 2026-09-30
| 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 |
| Submitted files, scripts, intermediate data, renders | performing the render and returning results | 24 hours after last use |
| Job metadata (file sizes, frame counts, resolution, GPU seconds, timestamps, failure reasons, Blender warnings, client type) | billing, incident handling, improving the service | 1 year |
| 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.
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.
Payments are processed by Stripe. 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.
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.
Contact us to access, correct or delete stored data. Requests concerning data tied to an API key are honoured for the holder of that key.
Changes to this policy are posted on the Service.
JasmyLab Inc. · contact@jasmylab.com
JANCTION Render v0.2.1 · JasmyLab Inc.