UsageProof: Post-Expiry Ad Evidence for UGC Creators

UGC usage rights tracker opportunity snapshot

UsageProof is a proposed UGC usage rights tracker for creators who license their face, voice or video to brands for paid advertising. It records the agreed territory, platform and expiry date, guides the creator through a post-expiry check in official ad libraries, and turns confirmed matches into a timestamped evidence pack plus a calm renewal request.

Executive summary

A creator may finish a campaign while the brand continues paying to run their video. The creator then has three separate jobs: remember when the licence ends, find the live ad, and assemble enough neutral evidence to ask for a renewal. Today that work is split across contracts, spreadsheets, reminders, Meta’s Ad Library, TikTok Creative Center, screenshots and email.

The market is not empty. Kleym already offers daily visual matching, overrun alerts and proof PDFs for Meta ads delivered in the European Union and United Kingdom. UsageCue sells the operating workflow around usage terms and renewals for $7 per month, without automatic infringement detection. Those products validate the job and sharply constrain the wedge.

The surviving concept is not “AI catches every stolen ad.” It is a creator-controlled evidence workflow for places and platforms where comprehensive monitoring is unavailable. AI may extract proposed licence fields and draft a factual email, but the creator must confirm the contract terms, the asset match and the final request.

The problem

Paid usage rights are time-bound business terms, but many solo creators manage them in a spreadsheet or memory. When the end date passes, checking every advertiser and platform is repetitive. If a matching ad is found, a screenshot alone may omit the URL, ad identifier, observation time or the exact clause being relied on.

Fact: Meta maintains a public Ad Library. Kleym says it uses that public library to identify creator videos and build proof reports.

Fact: TikTok describes Top Ads as a collection of high-performing creatives, not a complete archive of every commercial ad. A product must not promise comprehensive TikTok coverage from this source.

Signal: Creator-community posts repeatedly ask how to discover ads that remain active after rights expire. These posts are self-selected anecdotes, and several recent threads were written by builders testing similar products, so they are not market-size evidence.

Assumption to test: creators outside Kleym’s automatic coverage will pay for a cleaner manual evidence workflow rather than use calendar reminders and screenshots.

Ideal customer profile

The first customer is a US-based or internationally active UGC creator managing at least ten paid-usage agreements at once. They work directly with brands or small agencies, invoice professionally, and already understand that organic posting, paid ads, whitelisting and raw-footage rights are different commercial terms.

Do not start with occasional creators who have one campaign every few months, talent agencies needing enterprise rights management, or people seeking legal enforcement. The product organises records and observations. It is not a law firm, a debt collector or a takedown service.

Current customer workflow

1. Save a contract or email thread and manually enter the usage end date.
2. Create a calendar reminder or spreadsheet row.
3. After expiry, search the advertiser in Meta Ad Library and other accessible public surfaces.
4. Compare the live creative with the delivered source files.
5. Capture screenshots and copy the ad URL or identifier.
6. Find the relevant licence clause and calculate a proposed extension fee.
7. Email the brand, then track whether it renews, pauses the ad or disputes the match.

The product earns its place only if it makes this workflow substantially safer and faster without pretending that public libraries are complete.

Discovery and screening

Twenty candidates were screened across consumer, travel, ecommerce, creator, education, browser-extension, marketplace and data-product categories. Scores are preliminary except for UsageProof.

Demand signals

• Existing spend: Kleym lists creator plans at €19.90 and €49.90 per month excluding VAT, while UsageCue lists $7 per month or a $69 launch lifetime plan.
• Economic trigger: a single paid-usage extension can be worth more than months of software. That is a plausible value argument, not a measured conversion rate.
• Repeated workflow: creators must track delivery, approval, payment, licence dates and renewals across many deals.
• Behavioural evidence: community discussions describe checking Meta after expiry and discovering continued use. The sample is anecdotal and cannot establish frequency.
• Data constraint: Kleym says Meta does not publish the delivery data it needs outside Europe, while TikTok’s public Top Ads surface is selective. The gap is real, but it also limits the proposed product.

Competitor landscape

What competitors do well

Kleym makes the monitoring job almost invisible where its data is available. UsageCue integrates licence tracking into the broader post-deal workflow at a low price. Both use cautious boundaries: neither claims to collect money automatically, and UsageCue explicitly says it does not detect unauthorised ads.

The gap and wedge

The viable wedge is creator-confirmed, platform-neutral evidence:

• focus on US and cross-border creators not fully covered by automated Meta delivery data;
• support user-initiated capture from Meta, TikTok, retailer pages and brand websites without claiming comprehensive monitoring;
• bind the observation to confirmed licence terms, source-asset fingerprints, time, URL and a cryptographic hash;
• produce a neutral renewal pack, not an accusation or legal conclusion;
• offer per-case pricing for creators who do not need another subscription.

This is weaker than true automatic detection. That weakness is also the honest product boundary.

Product concept

A web app plus a narrowly permissioned browser extension. The creator imports a contract or manually enters confirmed terms. At expiry, the app opens official public search surfaces with the correct advertiser and checklist. The creator confirms a matching creative. The extension captures visible metadata, URL, observation time and screenshot after an explicit click. The service hashes the evidence, records custody events and creates a PDF with the relevant confirmed terms and a draft renewal email.

MVP

Build

• Email or passkey authentication
• Deals, brands, assets and usage licences
• Manual fields for platform, territory, start, end and fee
• Optional contract upload with AI-proposed fields that require confirmation
• Expiry reminders
• Guided Meta Ad Library check
• User-triggered screenshot, URL, timestamp and visible ad-ID capture
• SHA-256 hashes for source assets and captured files
• Evidence timeline and PDF export
• Calm renewal-message draft based only on confirmed terms
• CSV export, deletion and retention controls

DON’T BUILD YET

• Unattended scraping or promises of 24/7 monitoring
• TikTok-wide detection from the selective Top Ads catalogue
• Legal conclusions, debt collection or automated takedowns
• Automatic invoices or claimed damages
• Computer-vision matching without a human confirmation step
• Agency CRM, social scheduling or a creator marketplace
• Native mobile apps

User journey

1. Create a deal and add the brand.
2. Upload the source asset or store a local fingerprint.
3. Enter usage terms manually or review AI-extracted suggestions.
4. Confirm the expiry date and reminder cadence.
5. At expiry, launch the guided official-library search.
6. Select a suspected match and compare it with the source asset.
7. Confirm or reject the match.
8. Capture the public evidence and add any brand correspondence.
9. Review the generated pack and renewal draft.
10. Send it personally and record the outcome.

Technical blueprint

• Web: TypeScript application with server-rendered account and evidence pages.
• Extension: Manifest V3 browser extension with the smallest possible host permissions and explicit capture actions.
• Database: PostgreSQL with tenant-scoped deals, licences, assets, observations and custody events.
• Files: encrypted object storage, signed short-lived URLs and immutable evidence versions.
• AI: structured contract-field proposals and renewal drafting. No autonomous legal interpretation.
• Matching: optional local perceptual fingerprints to assist comparison; never label a match confirmed until the creator does so.
• Integrity: SHA-256 hashes, append-only custody records and signed export manifests. Explain that these features organise provenance but do not guarantee legal admissibility.

Core schema

users, workspaces, memberships, brands, deals, assets, licenses, contract_documents, extraction_suggestions, reminders, search_sessions, observations, evidence_files, custody_events, evidence_packs, messages, outcomes, audit_log.

Unit economics and pricing

These are scenarios, not measured economics.

• Free: three active licences, reminders and manual records.
• Creator: $9/month or $79/year for unlimited licences, guided checks and evidence packs.
• One case: $12 for a single evidence pack, useful for intermittent creators.
• Pro: $19/month for a manager seat, shared workspace and brand history.

Storage and PDF generation should be inexpensive at creator scale. Support, privacy review and changing platform surfaces are likely to cost more than infrastructure. If the product requires frequent manual help, $9 per month is too low.

First 10 customers

1. Recruit 20 US-based creators with at least ten paid licences.
2. Collect anonymised examples of the spreadsheet, reminder and evidence workflow.
3. Offer a concierge post-expiry check for one licence.
4. Manually produce five evidence packs using only public pages and creator-supplied records.
5. Ask for payment before building: $12 per pack or a $79 annual pilot.
6. Measure whether the pack causes a renewal conversation, ad pause or useful clarification.
7. Partner with two UGC educators or contract-template sellers on an expiry checklist.

SEO and distribution

Keyword ideas are editorial hypotheses; no search-volume claims are made.

• how to check if a brand is still running my UGC ad
• UGC usage rights tracker
• paid usage rights expired
• Meta Ad Library UGC creator
• UGC renewal email template
• how to prove a brand used my video

The strongest acquisition assets are free and practical: a usage-expiry calculator, a licence tracker template, a renewal-email generator and a browser checklist for Meta Ad Library. Creator educators and UGC communities are more plausible than broad paid acquisition.

Seven-day validation

1. Day 1: interview five creators about the last expired paid-usage licence.
2. Day 2: build a clickable evidence-pack prototype with explicit data caveats.
3. Day 3: run three manual post-expiry checks using creator-provided advertiser names.
4. Day 4: deliver the packs and observe whether creators trust the format.
5. Day 5: test $12 per case, $9 monthly and $79 yearly.
6. Day 6: show the workflow to two creator managers and one lawyer for boundary feedback.
7. Day 7: decide using payment and real cases, not survey enthusiasm.

Pass: 15 interviews, eight creators with a real post-expiry checking habit, five supply a current case, three pay, and at least two evidence packs lead to a brand response.

Fail: fewer than five creators can name a recent case, most cases are resolved by a calendar reminder, creators will not upload terms, or platform pages do not expose durable evidence.

Risks and kill criteria

• Kleym expands to the US or adds the same assisted workflow.
• Meta, TikTok or other platforms alter public-library access or page structure.
• Creators interpret a neat PDF as legal proof when it is only an organised record.
• Contract extraction gets dates, territory or fee terms wrong.
• Creators avoid uploading contracts or source media for privacy reasons.
• Low campaign volume makes subscriptions feel wasteful.
• Manual confirmation removes too much of the promised convenience.

Kill the product if three paid concierge packs cannot be sold from 20 qualified interviews, or if fewer than half of real cases can produce a stable public URL plus useful visible metadata. Also kill automated detection positioning unless a documented, permitted data source supports it.

Moat and expansion

The initial software has little moat. A useful advantage could emerge from creator-owned brand histories, repeatable custody records, outcome data and trusted educator distribution. Never train on private contracts or media without explicit opt-in.

Only after retention is proven, expand to manager workspaces, renewal benchmarks based on voluntarily contributed anonymised outcomes, or direct brand renewal portals. Do not confuse a growing private evidence corpus with ownership of platform data.

Founder fit

This suits a founder comfortable with browser extensions, privacy-sensitive files, creator education and frequent platform changes. It is a poor fit for someone seeking a passive micro-SaaS or unwilling to support emotionally charged payment disputes. The best founder would be close enough to UGC creators to recruit cases without paid ads.

Final score

Total: 70/100. Research confidence: 78/100. Verdict: VALIDATE.

🛠 BUILD THIS WITH AI

COPY BUILD PROMPT

You are a senior product engineer, security engineer and UX designer. Design and implement a validation-first MVP called UsageProof. It helps professional UGC creators record paid-ad usage terms, perform user-initiated post-expiry checks on public ad surfaces, capture confirmed observations, and create a neutral evidence pack plus renewal-request draft.

PRODUCT OBJECTIVE
Reduce the time and mistakes between a usage-rights expiry date and a professional renewal conversation. This is an evidence-organisation product, not legal advice, debt collection, infringement detection or comprehensive ad monitoring.

TARGET USER
An independent US or international UGC creator managing 10 or more paid-usage licences. They work directly with brands or small agencies and currently use spreadsheets, calendar reminders, screenshots and email.

HARD PRODUCT BOUNDARIES
- Do not claim comprehensive monitoring of Meta, TikTok or any ad platform.
- Do not scrape behind authentication, evade rate limits or invent API access.
- Verify every current external capability against official documentation before implementation.
- TikTok Top Ads is a curated collection, not a complete ad archive. Label it accordingly.
- Any Meta workflow must be user-initiated against the public Ad Library and resilient to missing data.
- The product never decides infringement, calculates legal damages, sends accusations, issues takedowns or guarantees admissibility.
- The creator must confirm licence terms and creative matches.

USER STORIES
1. As a creator, I can record a brand deal and its paid-usage terms.
2. I can upload a contract and review structured suggestions before saving any extracted field.
3. I receive reminders before and after confirmed expiry.
4. I can launch a guided search in an official public ad surface.
5. I can explicitly capture a suspected ad's visible URL, identifier, timestamp and screenshot.
6. I can compare it with my source asset and confirm or reject the match.
7. I can generate a versioned evidence pack with hashes, terms and custody history.
8. I can edit a calm renewal email that cites only confirmed facts.
9. I can export or delete all my data.

MVP SCOPE
Build authentication, workspaces, brands, deals, assets, licences, reminders, manual and assisted contract entry, guided Meta Ad Library search, explicit browser capture, human match confirmation, evidence timeline, versioned PDF export, renewal draft, CSV export, account deletion and audit log.

DO NOT BUILD YET
Unattended scraping, background ad surveillance, TikTok-wide detection, automatic claims, legal advice, automatic invoices, takedowns, brand blacklists, a marketplace, native mobile apps, creator CRM features unrelated to rights, or autonomous computer-vision decisions.

SCREENS
1. Sign in and onboarding with product boundaries.
2. Dashboard: expiring, expired, checked and needs-action licences.
3. Add deal and brand.
4. Licence editor with platform, territory, start, end, fee, renewal terms and source.
5. Contract review: original document beside proposed fields, confidence and confirm/reject controls.
6. Asset detail with local fingerprint or encrypted upload.
7. Guided check with official-source link, advertiser name, checklist and coverage warning.
8. Capture review with screenshot, URL, visible metadata, source asset and confirm/reject.
9. Evidence timeline and custody log.
10. Evidence-pack preview and export.
11. Renewal-message editor.
12. Privacy, retention, export and deletion settings.

USER FLOWS
Happy path: create deal → add confirmed terms → add asset → schedule reminders → open guided check after expiry → explicitly capture candidate → compare and confirm → generate pack → edit message → record outcome.
Alternative flows: manual terms with no document; local-only asset hash with no media upload; no ad found; missing public URL; ambiguous creative; corrected licence term; deleted source page; disputed observation.

UI/UX
Use a calm evidence-workspace style. Clearly label CONFIRMED, CREATOR-ENTERED, AI-SUGGESTED, OBSERVED and UNKNOWN. Never use red to imply guilt. Show data-source and coverage caveats at the moment of search and export. Meet WCAG AA, provide keyboard navigation, visible focus, responsive layouts, useful empty states and recovery-oriented errors.

DATABASE
Create migrations for users, workspaces, memberships, brands, deals, assets, asset_fingerprints, licenses, contract_documents, extraction_suggestions, reminders, search_sessions, observations, evidence_files, custody_events, evidence_packs, pack_versions, messages, outcomes, audit_log and deletion_jobs. Every business record must be tenant-scoped. Use immutable identifiers for evidence artifacts and append-only custody events.

ARCHITECTURE
Use TypeScript. Separate the server-rendered web app, background worker and Manifest V3 browser extension. Use PostgreSQL, encrypted object storage, a durable queue and an email provider behind interfaces. Use UTC internally. Provide Docker-based local development and seed fixtures. Keep platform-search adapters separate from evidence storage so changing public surfaces does not corrupt old packs.

BROWSER EXTENSION
Request the minimum host permissions. Capture only after the user clicks a clear action. Display exactly what will be stored. Save page URL, title, observation time, visible advertiser/ad identifiers if present, and a user-approved screenshot. Do not collect cookies, hidden page data, unrelated browsing history or credentials. If a page structure changes, fail safely and permit manual metadata entry.

CONTRACT EXTRACTION
Use a provider-independent structured-output interface. Proposed fields: platform, usage_type, territory, start_date, end_date, renewal_clause, fee_reference, asset_reference and source_quote. Every suggestion stores model/provider version, confidence and document location. Nothing becomes a confirmed licence term until the user approves it. If the model is uncertain or terms conflict, show UNKNOWN and require manual entry. Never provide legal interpretation.

ASSET MATCHING
Start with side-by-side human comparison. Optionally compute local perceptual fingerprints or sampled-frame hashes to rank candidates, but never represent similarity as proof. The final match state requires explicit human confirmation with timestamp and user ID.

EVIDENCE INTEGRITY
Compute SHA-256 for each source and capture file. Store original bytes immutably, create derived preview files separately, and record every add, confirm, correct, export and delete event. Generate a signed manifest listing file hashes, URLs, observation times, confirmed terms and caveats. Explain in the product and PDF that provenance controls do not guarantee legal admissibility.

AUTHENTICATION AND PAYMENTS
Use a mature auth library with email magic link or passkey support. Roles: owner and manager. Prepare entitlements for Free, Creator and per-case pack purchase. Integrate Stripe only after paid concierge validation; keep billing behind an interface. Ensure users retain export access after cancellation.

ANALYTICS
Track privacy-safe events: deal_created, license_confirmed, reminder_sent, guided_check_opened, candidate_captured, match_confirmed, pack_generated, message_copied, outcome_recorded, export_completed and deletion_requested. Do not send contract text, asset URLs, screenshots, advertiser names or evidence contents to third-party analytics.

SECURITY AND PRIVACY
Encrypt contracts, media and sensitive fields at rest. Use short-lived signed URLs, malware scanning for uploads, strict MIME and size validation, CSRF protection, secure headers, rate limits, audit logging and tenant-isolation tests. Redact sensitive data from logs. Define retention per artifact, implement full export and deletion, and write a data-flow diagram plus threat model. Never train models on user documents or assets without separate explicit opt-in.

ERROR HANDLING
Handle expired links, changed platform markup, missing identifiers, deleted ads, unsupported pages, ambiguous matches, OCR/extraction failure, conflicting dates, failed reminders, PDF failure, duplicate captures, offline extension state, upload interruption, billing failure and deletion in progress. Never turn missing data into a positive match.

TESTS
Unit test date/expiry logic, term-confirmation state, hashes, manifest generation, custody immutability, permissions and prompt-output validation. Integration test uploads, explicit capture, duplicate observations, pack versioning, export and deletion. Add end-to-end tests for manual deal creation through evidence-pack export. Add tenant-boundary, authorization, upload, XSS and CSRF tests. Run accessibility checks on every core screen.

DEPLOYMENT
Provide separate web and worker services, managed PostgreSQL, encrypted object storage, queue, secret management, staging, health checks, structured logs, backups and restore testing. Package the extension for local developer loading first. Do not publish it to an extension store until permissions, privacy disclosures and platform terms have been reviewed.

ACCEPTANCE CRITERIA
- A user can create and confirm a licence without AI or document upload.
- AI-extracted terms remain suggestions until individually confirmed.
- An expiry reminder uses the confirmed date and user timezone.
- The extension captures nothing before explicit user action.
- A captured observation includes source URL, UTC time and artifact hash.
- A creative cannot become CONFIRMED without a human action.
- Every pack is versioned and includes hashes, terms, observations and caveats.
- No screen claims automatic or comprehensive platform coverage.
- A user can export and delete all records and files.
- Cross-tenant tests fail closed.
- Core flows pass automated, responsive and WCAG AA checks.

DELIVERY ORDER
First produce an architecture decision record, platform-capability audit, threat model, data-flow diagram, schema and clickable prototype. Then build the smallest vertical slice: one manual licence, one reminder, one explicit capture, one confirmed observation and one versioned evidence pack. Run five paid concierge cases before adding contract AI, similarity assistance or billing. If an official capability is unavailable, stop and redesign the workflow instead of inventing an API.

Continue the series

← Read Idea #002: UpdateTrace

Read Idea #004: DealProof Desk →

Sources

• Kleym: product, coverage and current pricing
• Kleym terms: service scope, limitations and prices
• UsageCue: UGC deal and usage-rights tracker
• Cliro usage-rights tracker
• Meta Ad Library
• TikTok: how to use the Top Ads Dashboard
• UGC creator discussion: checking ads after contract dates
• Influencer-marketing discussion: a competing builder tests the same problem

Research date: 29 September 2026. Prices and platform features can change. Community posts are treated as anecdotes. No market-size, incident-rate, search-volume or recovery-rate figures have been invented.