Private deploy: content and IP responsibility
Japan private delivery: textbook/exam-bank overview and customer-side primary responsibility for content IP.
Audience: Private-deploy IT / ops / SI / customer operations · Market: Japan
Goal: At deploy/go-live, make clear that the system supports platform-licensed and school-made speaking textbooks and exam banks, and that IP and dispute primary responsibility sits with the content provider (usually the customer org/ops).
Org-admin readable guide: Speaking textbooks and school exam banks.
Capability summary (same shape as SaaS)
| Capability | Notes |
|---|---|
| Platform-licensed content | After contractual entitlement, teachers can assign |
| School-made content | School textbooks / exam bank; that org only |
| Declaration and review | IP declaration before submit; after the agreed review flow, content may become formally assignable |
On the deploy checklist, “content” means who reviews and who bears infringement risk is clear in the contract—not only that services start.
Responsibility (confirm with the customer before go-live)
Binding terms are the contract / Terms / runbook. This article is not legal advice.
- The customer / organization has primary responsibility for textbooks and exam banks they make, import, or claim a right to use (IP, portrait/privacy, instructional compliance, etc.).
- Review (platform, implementer, or customer-internal workflow) is publish eligibility and policy fit—not legal due diligence or a “non-infringing” warranty.
- Third-party claims from customer content are in principle borne by the customer under the contract (including any indemnity toward platform/implementer).
- Implementer / platform supply software and deploy services; they do not automatically assume IP disputes over customer-uploaded content merely because “the system was installed”.
- Contracts should include warranty, indemnity, takedown/stop-provide rights, and content disclaimers. Governing law and dispute clauses should be counsel-reviewed for Japan.
SaaS often uses “platform final review”. If private deploy switches to customer-internal final review, name the review party in the contract and ops manual so staff do not assume “if the system can publish it, the platform guaranteed legality”.
Go-live checks (content)
- Contract covers IP and indemnity for school-made content
- Ops knows IP declaration is required before submit/publish
- Org admins were pointed to Speaking textbooks and school exam banks
- Complaint / takedown contacts are named (customer ± implementer)