Privacy Policy
Last updated: 2026-10-24
Privacy Policy — Knowledge Broker Labs (YT-KB O1 / O2)
Status: Approved 2026-09-19 — Amit confirmed the content is reviewed and cleared for publication at a public URL. This is the document every other asset in this venture references as {privacy URL} / "privacy policy — to be published" (marketing/site/managed.html, endpoint.html, assets/sequence.md, assets/landing.md ×2, and both LAUNCH-AUTH.md checklists all point here). It is the public-facing notice required by GDPR Art. 13/14 and similar laws (CCPA/CPRA, UK GDPR) — distinct from, and simpler than, 04-dpa.md, which is the contractual processing terms signed with a paying customer. Where the two overlap, the DPA controls for customers who have signed it; this document is what everyone else (a site visitor, a prospect who hasn't signed anything yet, a free-tier signup) sees. Built original, structured around the actual data this venture actually collects — not a generic template — because a mismatch between a boilerplate privacy policy and what the product really does is itself a compliance risk (and the fastest way to make a lawyer's review slower and more expensive, not less).
Purpose: turns "we only ingest what you own, we export/delete on request" — the operating posture already committed to across every other asset (legal/00-company-facts.md, both LAUNCH-AUTH.md files, marketing/*/assets/claims.md) — into the actual public disclosure that posture depends on being honoured.
Effective date: [DATE — set on publication] Last updated: 2026-10-24
Knowledge Broker Labs ("we," "us," "Provider" in the Managed Knowledge Base MSA and MCP Endpoint ToS) operates YT-KB: a Managed Knowledge Base service (O1) and a self-serve MCP Endpoint service (O2) that turn YouTube video archives into queryable knowledge bases. This policy explains what personal data we collect, why, and what rights you have over it — whether you're browsing the website, signing up for the free tier, or a customer of either paid product.
1. Who this covers
This policy applies to:
- Visitors to
taxatlas.ai/kbland its subpages (the marketing site). - O2 self-serve signups — anyone who creates a free or paid knowledge
base via the signup/portal flow.
- O1 customers and prospects — anyone we correspond with about the
Managed Knowledge Base service, from the first outreach email through an active subscription.
It does not cover the content of the YouTube videos we index on a customer's behalf — that's Customer Content/Customer Data under the MSA or ToS, governed by the DPA where applicable, not personal data we collect *about* the customer.
2. What we collect, and why
| Category | What, specifically | Why (legal basis, where GDPR applies) |
|---|---|---|
| Site visit | Nothing beyond what your browser sends to load the page. No analytics, no tracking pixels, no third-party cookies are set by this site today — the only thing written to your browser is a localStorage entry remembering your light/dark theme choice, which never leaves your device. If that changes (e.g. adding analytics later), this policy is updated first. | N/A — no personal data processed |
| O2 signup | Email address; the YouTube channel URL(s) you submit; your query token and portal token (random secrets, not personal data themselves, but they identify your account) | Performance of a contract (Art. 6(1)(b)) — we need your email to send you the endpoint URL and account notifications, and the channel URL to build what you asked for |
| O2 usage | Query volume and timing (for rate-limit/plan-cap enforcement, query_log/caller_log in tenants.py); a salted hash of the source IP for a distinct-caller signal (never the raw IP, never linkable back to it) | Legitimate interest (Art. 6(1)(f)) — abuse prevention on a shared, per-token endpoint (see docs/OPERATING.md's Anti-abuse section). We do not log or retain the text of your queries beyond what's needed for the current day's budget count — see the note in assets/claims.md C-13: there is no query-content logging for reporting purposes |
| O2 product usage (not yet active — see note) | Which /app/* pages your account opens, and five account-management actions you take (adding or removing a channel, rotating your API token, changing plan, starting an export) — product_events in tenants.py. Not collected today: this category is built but switched off (YT_KB_TRACK_PRODUCT_EVENTS=false in production) pending this policy update going live; this row will be revised to drop "not yet active" the day it's turned on. | Legitimate interest (Art. 6(1)(f)) — understanding product usage and account health, operator-side only; never shown to any other customer, never sold, never used for third-party advertising |
| O1 prospecting (before you're a customer) | Your name, work email, and business contact details, sourced from your organisation's own public website or a business registry — recorded with the exact source, per row, in pipeline.csv | Legitimate interest (Art. 6(1)(f)) for the initial outreach (B2B, one relevant email, an unsubscribe on every message — see assets/sequence.md); consent/contract thereafter if you reply |
| O1 customer | Name, work email, billing contact, the channels you authorise us to ingest, correspondence, and the monthly report data described in the MSA | Performance of a contract (Art. 6(1)(b)) |
| Billing | Handled by our payment processors directly — PayPal (O1) and Lemon Squeezy (O2, merchant of record). We receive confirmation that a payment succeeded/failed and, for the O2 webhook, the subscription status and a reference id — we do not receive or store your card number, PayPal login, or bank details; those live with the processor | Performance of a contract |
3. Who we share it with
We do not sell personal data, and we do not share it for third parties' marketing. The sub-processors below are the only parties involved, each for the function stated — full detail and their locations are in 04-dpa.md Schedule 2, kept current as the authoritative list:
[VPS/hosting provider — TBD]— hosts the application, the tenant
database, and the vector store.
- PayPal — processes O1 payments.
- Lemon Squeezy, Inc. — processes O2 payments and, as merchant of
record, handles O2's tax/compliance.
[email delivery provider — TBD, once real SMTP is configured]—
sends account/notification emails (not yet live; see docs/OPERATING.md — every notification today is logged, not sent).
We may also disclose personal data if legally required to (e.g. a valid court order), or to protect against fraud, abuse, or a security incident — never as a routine practice.
4. International transfers
No personal data subject to the EU GDPR, UK GDPR, or Swiss FADP is transferred outside the EEA/UK/Switzerland under this policy until 04-dpa.md Schedule 3 is completed — that schedule fails closed by design (see legal/reviews/2026-09-16-infrastructure-jurisdiction-review.md), and this policy inherits the same restriction rather than silently allowing what the DPA blocks.
5. How long we keep it
- O2 free-tier / paid accounts: kept for the life of the account, then
60 days after termination (matches the MSA/ToS retention term in legal/00-company-facts.md), after which the account row, its channel tags, and the indexed content are deleted. A tenant can request earlier deletion at any time via the portal or by contacting us.
- O1 prospecting records (
pipeline.csv): removed on an unsubscribe/
objection request, immediately and permanently — per the suppression-list commitment in assets/sequence.md and the LAUNCH-AUTH prerequisites.
- O1 customer records: for the life of the contract, then per the same
60-day post-termination window.
- Billing records: kept only as long as the payment processor and
applicable tax law require — we don't hold card/bank data ourselves (see §2 above).
6. Your rights
Wherever GDPR, UK GDPR, CCPA/CPRA, or a similar law applies to you, you can ask us to:
- Access the personal data we hold about you.
- Correct it, if it's wrong.
- Delete it (subject to the retention needs in §5 — e.g. we can't
delete an active paid subscription's billing reference until the subscription ends).
- Export it — for O1/O2 knowledge-base data specifically, this is
already a standing product commitment (full Markdown export, no charge, any time — see assets/claims.md C-12).
- Object to processing based on legitimate interest (e.g. the O1
prospecting outreach) — we stop contact immediately and permanently.
- Withdraw consent, where processing is consent-based.
To exercise any of these: [notice email — set once the domain/entity is finalised, per legal/00-company-facts.md], or for O2 accounts, directly from your subscription portal where the action exists (rotate token, remove a channel, cancel).
7. Cookies and tracking
None beyond a strictly necessary one. The marketing site sets exactly one thing in your browser — a localStorage entry for your light/dark theme preference (ytkb-theme), which never leaves your device and is not a cookie sent to a server. No analytics, no ad pixels, no third-party trackers, no cross-site tracking of any kind, on the site as it exists today. If this changes, this section is updated and, where required, a consent mechanism is added *before* the change ships — not after.
8. Children
This service is not directed at children, and we do not knowingly collect personal data from anyone under 16 (or the applicable age in your jurisdiction).
9. Copyright / DMCA
Copyright complaints about content we index are handled under the Copyright Policy in 02-tos-o2.md and the designated-agent registration referenced in legal/00-company-facts.md — this Privacy Policy governs personal data, not copyright claims.
10. Changes to this policy
We'll post the effective date at the top when this changes, and for a material change (what we collect, who we share it with, why) we'll say so directly to active accounts, not just update the page silently.
11. Contact
[operating entity name — set once chosen, legal/00-company-facts.md], [registered address — TBD]. [notice email — TBD].
Open items before this can be published (tracked, not oversights)
Same posture as the other four documents in legal/ — this is a complete draft, not a placeholder skeleton, but it is genuinely blocked on:
- Entity name, address, notice email — same three tokens every other
contract in this directory is blocked on (legal/00-company-facts.md).
- VPS/hosting provider — once chosen, fills the Schedule 2 row this
policy points to.
- Lawyer review — same as
01-msa-o1.md/02-tos-o2.md/03-aup.md/
04-dpa.md; this should go to the same redline pass, not a separate one.
- DPA Schedule 3 (cross-border transfers) — §4 above inherits whatever
that schedule resolves to; nothing to do here once it's filled in.
- Once published at a real URL, replace every
{privacy URL}/
"privacy policy — to be published" placeholder across marketing/ and both site pages with the live link (tracked in backlog.md).