コンテンツにスキップ
shortdramamaker

法律上の

セキュリティとデータの取り扱い

最終更新日 Nov 8, 2026

この文書は英語で書かれており、英語版が正式なものです。

Your scripts and unreleased episodes are commercially sensitive. This page describes what we do to protect them, in plain terms, and what we do not claim.

1. Account protection

Passwords are stored as PBKDF2 hashes with a per-user salt; we never store or log plaintext passwords.

Sessions use HttpOnly, Secure, SameSite cookies with signed payloads, and are invalidated server-side on sign-out or when an account is suspended.

Administrative access requires either the ADMIN_TOKEN secret or an account with the admin role; admin write operations are recorded in the audit log.

2. Data in transit and at rest

All traffic is served over TLS 1.2 or above; HTTP is redirected and HSTS is enabled.

Assets are stored in object storage with per-account path isolation. They are served through our own authenticated /api/files/ endpoint, never from a public bucket URL.

Database backups are encrypted at rest and retained for 30 days.

3. Isolation between customers

Every query is scoped to the authenticated account. There is no shared project namespace.

Generation providers receive the minimum input required for a job — shot prompt and reference images — not your account identity or billing data.

Your content is not used to train models unless you explicitly enable it in account settings.

4. Payments

Card data never touches our servers. Card checkout is hosted by Creem, a PCI-DSS compliant merchant of record, and we receive only a transaction reference and status.

WeChat Pay and Alipay are handled entirely inside their own apps; we receive a signed callback containing the trade state and amount, never your credentials.

Crypto payments are verified on-chain against a per-order address and amount; we do not custody your funds.

Webhook payloads are signature-verified before any credit is granted.

5. What we do not claim

No service is perfectly secure. We do not claim ISO 27001 or SOC 2 certification.

We do not offer a contractual uptime SLA on the self-serve plans. Enterprise agreements can include one.

We cannot protect content you publish publicly or share via an expiring link that someone else has already downloaded.

6. Reporting a vulnerability

Email [email protected] with reproduction steps. We acknowledge within two business days.

Please do not test against other customers’ accounts, run denial-of-service tests, or access data that is not yours.

We do not currently run a paid bounty programme, but we credit researchers who report in good faith.

この文書について質問がありますか? [email protected] に書きます。このページは英語で提供されています。翻訳は便宜上提供されており、英語版が優先されます。