Acceptable Use Policy
Last updated: 2026-10-24
Acceptable Use Policy — YT-KB (O1 and O2)
Status: Approved 2026-09-19 — Amit confirmed the content is reviewed and cleared for publication. This AUP is Exhibit A to legal/01-msa-o1.md and an Attachment to legal/02-tos-o2.md. Its structure follows the restriction sections of the Common Paper Cloud Service Agreement and Bonterms Cloud Terms (both CC BY 4.0); its content-scoping rules (Sections 3–4) are specific to this product and come from the legal read (decisions/0005-legal-assessment.md) and the engineering guardrails already shipped (decisions/0005-legal-read-outcome.md).
v3 changelog (legal/reviews/2026-09-11-contract-review.md): §4.3 rewritten so captions-only is a Customer obligation, not a Provider warranty a customer can't breach (finding 2); §3.3/§4.1/§4.2 rewritten to remove the "or field" contradiction and state one unambiguous per-account- and-per-KB rule (finding 3); §4.4 rewritten so the Australia exclusion is absolute regardless of a creator licence (finding 4); new §2.3 (snippet cap) and §4.7 (anti-reassembly covenant) close the gap between "no bulk export" and "reconstruct the corpus by querying in a loop" (finding 7); §4.6/§6 takedown windows aligned so the acknowledgment window is never longer than the action window (finding 26); new §3.4 mirrors the MSA's access-authorization grant.
Purpose: this is the document that turns "nothing super risky in the scoped posture" (the legal read's finding) into something a customer is contractually bound by — the posture is only low-risk if customers actually stay inside it.
1. General restrictions (both products)
Customer will not, and will not permit anyone else to:
1.1. Reverse engineer, decompile, or attempt to discover the source code of the Product, except where Applicable Laws prohibit this restriction (and then only after advance notice to Provider);
1.2. Resell, sublicense, rent, or provide the Product to anyone outside Customer's own organization, or use it to offer a competing hosted or managed service to others;
1.3. Remove proprietary notices, or copy, modify, or create derivative works of the Product itself (as distinct from Customer's own Customer Content/Customer Data, which Customer may use freely);
1.4. Conduct security or penetration testing against, interfere with the operation of, or attempt to circumvent the tenant isolation or access controls of, the Product;
1.5. Access data, accounts, or portions of the Product Customer is not authorized to access, including attempting to query another tenant's knowledge base;
1.6. Use the Product to develop a directly competing product or service;
1.7. Use the Product for any High Risk Activity — a use where failure could reasonably lead to death, bodily injury, or environmental harm; or
1.8. Submit Prohibited Data — health information regulated by HIPAA, payment card or financial account numbers, government-issued identification numbers, or biometric identifiers, or special-category data under GDPR Art. 9 known to Customer to be present — to the Product, without Provider's prior written agreement to handle it under a Confidential Content Addendum.
2. Honest use of the retrieval results
2.1. Transcripts are machine-generated and may contain errors. Customer will not present retrieval results as an official, verbatim, or certified transcript of the source video, and will not remove or obscure the timestamp/deep-link attribution or the machine-generated-transcript disclaimer that accompanies each result.
2.2. Customer will not use the Product to systematically re-publish, redistribute, or re-host substantial portions of a source video's transcript outside the Product — the Product is a private index with citations back to the source, not a publishing platform.
2.3. Snippet cap. Retrieval results are snippet-length. Provider caps the length of any single passage returned and this cap is not configurable by Customer.
3. What Customer may submit — the content-rights rule (the one that matters most)
This section exists because it is what keeps the legal posture the engagement is built on (decisions/0005-legal-assessment.md) actually true in practice. Customer represents and warrants, for every channel, playlist, or video it submits to the Product, that one of the following is true:
3.1. Customer owns it. Customer (or Customer's organization) is the copyright owner of the video content and controls the YouTube channel or account it was published from; or
3.2. Customer has the rights. Customer holds a written license, employment relationship, or other legal right sufficient to authorize Provider to access, transcribe, index, and store the content, and to permit Customer's own Users to query it — for example, Customer is a firm submitting its own staff's recorded webinars, including any guest speakers, licensed music, or stock footage embedded in them, for which Customer confirms it holds the necessary rights; or
3.3. [O2 only] It is a single named creator's channel, submitted under the named-creator tier described in Section 4 below, subject to the additional restrictions there.
Customer is solely responsible for the accuracy of this representation. A false representation under this section is a material breach and grounds for immediate suspension and termination without a cure period, and triggers Customer's indemnification obligation under the Master Service Agreement / Terms of Service.
3.4. Access Authorization. Where Section 3.1 or 3.2 applies, Customer's warranty under this Section 3 also constitutes, and is confirmed by, the Access Authorization at MSA Section 1.8 / ToS Section 4.6 — Customer authorizes Provider to access the content on Customer's behalf as Customer's agent, by or with the authority of the copyright owner.
4. The named-creator tier (O2 only) — additional restrictions
Available only on O2. Not available on O1, which is scoped exclusively to content the customer owns or is licensed to use (Section 3.1–3.2).
4.1. Scope. A named-creator knowledge base may index one publicly available YouTube channel belonging to a specific, identifiable creator that Customer does not own or control, provided Customer can state who that creator is and why the knowledge base is being built (e.g., "grounding my coding assistant in Framework X's official channel"), unless Provider gives prior written approval under Section 4.2.
4.2. No bulk or arbitrary ingestion. Customer may maintain no more than one non-owned channel per knowledge base and no more than one named-creator knowledge base per account, in each case without Provider's prior written approval. Automated, programmatic, or bulk selection of channels is prohibited in all cases and approval will not be given for it.
4.3. Captions-only — a Customer obligation.
(a) Customer will not attempt to enable, request, or circumvent the audio-ingestion restriction for any channel submitted under this Section 4, and will not supply Provider with audio files, or transcripts derived from audio, for any such channel.
(b) Provider's ingestion pipeline is configured to process published caption tracks only for channels submitted under this Section 4. This describes Provider's current operational practice and is not a warranty; it is not part of the Performance Warranty and MSA Section 6.3 / ToS Section 7.2 does not apply to it.
4.4. Jurisdiction.
(a) This tier is available only to Customers domiciled in the United States.
(b) It is not available to Customers domiciled in Australia under any circumstances, including where Customer holds a licence from the creator.
(c) Provider may, in its discretion, permit a Customer domiciled outside the United States (other than Australia) to use this tier where Customer holds and produces on request an express written licence from the creator covering the uses described in this Policy.
(d) Customer declares its domicile at sign-up; a false declaration is a material breach under Section 3. "Domiciled" means, for an entity, its jurisdiction of formation and principal place of business.
4.5. No export of non-owned content. The full-transcript export feature is available only for content submitted under Section 3.1–3.2 (owned or licensed). Content submitted under this named-creator tier may be queried but not bulk-exported.
4.6. Takedown. Provider will remove content affected by a good-faith request from the creator or a rights holder promptly, and in any event within 5 business days of validating the request, whether or not the request follows a formal DMCA process. Provider targets removal within 48 hours and will act sooner where the request is clear on its face.
4.7. Anti-reassembly. Customer will not use the Product to reconstruct, and will not attempt to reconstruct, the whole or a substantial part of any transcript of content submitted under this Section 4 — including by issuing repeated, systematic, enumerative, or automated queries designed to retrieve successive passages, or by combining results across queries, sessions, knowledge bases, or accounts. Provider may rate-limit or suspend any account exhibiting a query pattern consistent with corpus reconstruction.
5. Enforcement
Provider may suspend or terminate access immediately, without prior notice, for a violation of Sections 3 or 4 above (the content-rights rules), and with notice when practicable for other violations of this AUP. Reinstatement is at Provider's discretion once the underlying issue is resolved.
6. Reporting a concern
A creator, rights holder, or any third party who believes content was submitted to the Product in violation of this policy may contact [takedown@yourdomain.com]. Provider will acknowledge within 2 business days and act within the window in Section 4.6. See also the Copyright Policy / DMCA notice-and-counter-notice procedure published at [public URL] (the DMCA designated agent registration under 17 U.S.C. §512 is done, confirmed 2026-09-18 — legal/00-company-facts.md — the agent's name/address and this section's public-posting URL are still placeholders pending the entity/ address facts).
7. Amendments
Provider may amend this Policy on 30 days' notice by email and by posting the updated version with a new effective date, per MSA Section 12.2 / ToS Section
- An amendment does not retroactively expand Customer's obligations for
content already submitted.
*Sections 1 and 2 adapt restriction language common to the Common Paper Cloud Service Agreement and Bonterms Cloud Terms (both CC BY 4.0). Sections 3–7 are original to this product and carry the actual legal-risk mitigation the engagement depends on — they are also the sections most recently revised (v3) after a dedicated contract-review pass, and deserve a careful second read from counsel rather than a light one.*