Security

JANCTION Render renders every uploaded .blend, script or 3D file only inside an isolated environment created for that job and destroyed afterwards, so it cannot reach other users' data or our internal systems. Files are deleted 24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total) and are never used for training.

Render isolation

Each render runs in a disposable environment with no network access, no administrative privileges, and limits on CPU, memory, time and how much it may write. The only things readable inside are Blender itself and that job's own files; other users' data and the server's configuration are out of reach. The environment is destroyed when the job ends. Isolation is layered and reviewed regularly.

Scripts embedded in .blend files

.blend files are opened with auto-execution disabled, so text blocks that run on load and Python driver expressions do not run. Files are only ever read inside the disposable environment described above.

Keys and connections

All traffic is encrypted (HTTPS). API keys are stored as hashes and are never accepted in URLs. Key creation, uploads and job submission are rate-limited. AI apps connect through OAuth with a consent page that shows the destination, and the tokens they receive expire. If a key leaks, revoke it (POST /v1/keys/revoke, janction-render revoke-key) or disconnect apps one by one (/v1/connections, janction-render connections).

Data

Inputs, intermediate data and results are deleted 24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total). Logs keep sizes, timings, failure reasons and the end of Blender's output for that job, and are deleted with the job. Nothing is used for training. Share pages (render_share) exist only for results you chose to publish, and they are reviewed before they appear in the gallery.

Abuse

Render environments cannot reach the network, so using the GPUs for cryptocurrency mining and the like does not work. There are time limits per job, per key and per network, and jobs that time out or fail still count the time they used. Scripts that try things rendering never needs are stopped, logged and reported to the operators.

External security review

On 2026-10-01 and 10-02 an independent tester ran black-box tests against the public API, the MCP endpoint and the OAuth flow in four rounds plus a final audit. Everything rated High or Medium was fixed and re-tested the same day.

Data retention and deletion

What	Kept until	Who can see it
Uploaded scenes and assets (.blend, scripts, 3D files, images)	Deleted automatically 24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total)	Only the key that uploaded them (for processors, see Third parties below)
Intermediate data during a render	Destroyed with the container when the job ends	Only inside that container
Results (images, videos) and download links	24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total); links stop working at the same time	The key owner and anyone they give a link to
Share pages (render_share)	Until render_unshare	Public; the gallery only after review
Operational logs	Sizes, timings, failure reasons and the app type only (no contents; page views are logged without IP)	The operator
API keys	Stored as hashes until revoked (POST /v1/keys/revoke)	The plain key is returned once, at creation
Backups (the ledger: key hashes, job and billing records, operational and audit logs)	Taken nightly and deleted after 14 days. Scene and result files are not in them; after DELETE /v1/me/data the records stay in these copies until then	The operator
OAuth tokens	30 days by default, or until revoked	That app
Third parties	Processors only. Payments are processed by Stripe (card data never reaches us). Resend sends notice and sign-in emails (it gets 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, and your files and results then pass through their machines (in an isolated environment per job, deleted afterwards). Nothing is shared with anyone else unless the law requires it (section 3 of the privacy policy)	—

All traffic is TLS. Nothing is used for training.

What is not covered

No isolation is perfect. For confidential production work, contact us before uploading. The service has no availability guarantee.

Reporting

Found a vulnerability? Tell us at contact@jasmylab.com (responsible person: Hiroshi Harada). We acknowledge within 2 business days. A serious issue (one that reaches other users' data or keys, or escapes the render isolation) is fixed, or the feature switched off, within 7 days. We tell the reporter when it is fixed and credit them in /changelog if they wish. We appreciate testing that does not touch other users' data.