# videocompressor.online — Compliance / Privacy / Copyright Boundary v0

Date: 2026-06-03
Task: t_069ada5b
Tenant: site-videocompressor-20260603
Domain: videocompressor.online
Company: Nextfield Labs LLC [confirm exact legal display name]
Jurisdiction baseline: Wyoming, USA
Contact email: support@videocompressor.online [required before launch]
Input sources:
- /root/.hermes/reports/site-videocompressor-20260603/research-v0.md
- /root/.hermes/reports/site-videocompressor-20260603/prd-v1.md
- /root/.hermes/reports/site-videocompressor-20260603/input-brief.md

Not legal advice. This is product compliance guidance and launch copy for a small web utility; high-stakes changes should be reviewed by counsel.

## 0. Verdict

COMPLIANCE_GO_WITH_CONSTRAINTS.

The site can proceed if v0 stays client-side-first and no-upload by default. The compliance advantage is real: local browser processing materially lowers privacy, storage, content moderation, and deletion burden.

Hard constraints:
1. Default mode must not upload the selected video, thumbnail, filename, local path, or media content to any server.
2. Analytics must only collect non-sensitive, bucketed product events.
3. Discord, WhatsApp, Instagram, and Email presets must be described as sharing scenarios / target-size presets, not as official integrations or endorsed tools.
4. Copy must not promise unlimited, lossless, no quality loss, all formats/codecs, exact target-size success, or desktop-equivalent mobile performance.
5. If server-side upload/queue is added later, this v0 verdict no longer covers it; a new privacy, retention, abuse, and deletion design is required.

P0 risks: none if the above constraints are enforced.
Conditional risks: see sections 2–8.

## 1. Product risk classification

Risk level: LOW-to-MEDIUM for v0.

Why not pure low risk:
- Users select local video files. Even without upload, the product handles potentially sensitive personal media in the browser.
- Compression failure and quality loss can create user expectation disputes if copy overpromises.
- Platform names appear in URLs and presets, so nominative-use discipline is required.
- Analytics must avoid accidentally logging filenames, file paths, thumbnails, raw metadata, or media-derived identifiers.

Why not high risk:
- v0 has no account system.
- v0 has no payment.
- v0 has no server-side video storage or processing.
- v0 does not generate synthetic media, deepfakes, biometric analysis, health/financial/legal decisions, or child-directed services.

## 2. Privacy boundary: local processing / no upload

### 2.1 Required product behavior

The default compression workflow must run in the user’s browser. The selected video must remain on the user’s device unless the user explicitly chooses a future server-side mode.

Implementation requirements for frontend/QA:
- No upload request containing the video file, blob, thumbnail, frame capture, local path, filename, or raw media metadata.
- No background upload to R2/S3/Cloudflare storage, analytics providers, error monitoring providers, or “diagnostic” endpoints.
- Downloaded compressed result should be created locally and offered via browser download/blob URL.
- Browser memory cleanup should happen after cancel/success where feasible.
- If the app detects an unsupported browser or file, show a failure/fallback state instead of sending the file elsewhere.

Allowed network activity in v0:
- Loading static app assets from videocompressor.online / Cloudflare Pages.
- Loading analytics scripts if configured and legally disclosed.
- Sending non-sensitive analytics events listed in section 3.
- Loading legal/content pages.

Disallowed network activity in v0:
- Media upload.
- Thumbnail upload.
- File-name or file-path telemetry.
- Raw codec/duration/resolution metadata if granular enough to identify a specific file; use buckets only.
- Error logs containing the original filename, local path, media bytes, stack payloads with blob URLs, or screenshots of user video.

### 2.2 Required on-page copy

Use consistent wording in Hero/tool empty state, `/privacy-video-compressor`, `/privacy`, FAQ, and footer trust strip.

Approved copy:

- “Private by default: videos are processed locally in your browser in supported browsers.”
- “No upload by default. Your selected video is not sent to our servers for compression in the standard workflow.”
- “We do not collect your video content, thumbnails, local file path, or filename for analytics.”
- “Large files depend on your device, browser, codec, duration, and available memory.”
- “For best results, use desktop Chrome or Edge and try 720p or a higher target size if compression fails.”

Do not write:

- “We never process any data.” Static assets, security logs, and analytics may still process limited data.
- “100% private” or “zero data collection.” Too absolute if analytics/security logs exist.
- “No upload ever.” Only safe if there is no future server mode and no import/export feature. Prefer “no upload by default” / “standard local workflow.”
- “Works on every browser/device.”

## 3. Analytics boundary

### 3.1 Allowed analytics events

Analytics may collect product usage only in safe buckets:

- `page_view`: route, referrer/domain if analytics tool supports privacy-safe mode.
- `file_selected`: size_bucket, mime_category, browser_family, device_class.
- `preset_selected`: `discord_10mb`, `whatsapp_16mb`, `email_25mb`, `instagram`, `custom`.
- `compression_started`: resolution_option, quality_option, target_size_bucket.
- `compression_completed`: input_size_bucket, output_size_bucket, duration_bucket, success_target_met boolean.
- `compression_failed_reason`: unsupported_browser, unsupported_codec, memory, timeout, mux_error, user_cancelled, unknown.
- `download_clicked`.
- `cta_click` / `faq_open` / `privacy_link_click` if needed.

### 3.2 Disallowed analytics fields

Never send:

- Filename.
- Local file path.
- Video content, frames, thumbnails, or waveform.
- Blob URLs or object URLs.
- Raw file hash or media fingerprint.
- Exact duration, exact resolution, exact bitrate, exact codec profile, exact file size if not bucketed.
- User-entered notes, if any are added later.
- IP address as a custom event property.

Recommended buckets:

- input_size_bucket: `<10MB`, `10-25MB`, `25-100MB`, `100-500MB`, `500MB-1GB`, `>1GB`.
- output_size_bucket: same or coarser.
- duration_bucket: `<30s`, `30s-2m`, `2-10m`, `>10m`.
- target_size_bucket: `<=10MB`, `11-16MB`, `17-25MB`, `26-50MB`, `>50MB`.
- device_class: `desktop`, `tablet`, `mobile`.

### 3.3 Cookie / consent position

If using Plausible without cookies and without cross-site tracking:
- Privacy Policy must disclose analytics.
- Cookie banner may not be required solely for Plausible, depending on configuration and target market.

If using GA4, Clarity, advertising pixels, remarketing, heatmaps, or non-essential cookies:
- Add Cookie Policy or cookie section in Privacy Policy.
- For EU/UK users, load non-essential analytics/marketing cookies only after consent unless a privacy-safe cookieless configuration is confirmed.
- Do not run Clarity session replay on pages where file selection or video preview could reveal user content unless it is configured to mask/suppress media and sensitive UI. Safer v0 position: avoid session replay on the tool area.

## 4. Privacy Policy required content

Minimum Privacy Policy sections:

1. Operator
   - “videocompressor.online is operated by Nextfield Labs LLC [confirm].”
   - Contact: support@videocompressor.online [required before launch].

2. Local processing
   - “The default video compression workflow runs locally in your browser. Your selected video is not uploaded to our servers for compression.”
   - “Your browser may temporarily hold the input and output video in local memory while processing.”

3. Data we do not collect in v0
   - Video content.
   - Thumbnails/frames.
   - Filenames/local paths.
   - Raw media metadata as analytics.
   - Account or payment data, because v0 has no account/payment.

4. Data we may collect
   - Usage analytics: route, event type, preset selected, bucketed file size/duration, browser/device class.
   - Technical/security data: IP address, user agent, request logs handled by Cloudflare or hosting providers.
   - Voluntary contact data if user emails support.

5. Purposes and lawful bases

| Data type | Purpose | Lawful basis for EU/UK | Third parties | Retention |
|---|---|---|---|---|
| Static request/security logs | Deliver site, prevent abuse, debug errors | Legitimate interests | Cloudflare / hosting | As configured by provider; keep minimal |
| Privacy-safe analytics events | Improve UX, measure feature usage | Legitimate interests or consent depending on tool/config | Plausible/GA4/other analytics [confirm] | Provider-configured retention |
| Cookie-based analytics/marketing, if any | Analytics/attribution | Consent for EU/UK | GA4/Clarity/ad platforms [confirm] | Provider-configured retention |
| Support emails | Respond to user requests | Contract / legitimate interests | Email provider [confirm] | As needed for support and records |
| Selected video files | Local compression only | Contract | No server recipient in v0 | Not stored by site server |

6. Third-party services
   - Cloudflare Pages/CDN/DNS/security.
   - Analytics provider [confirm before launch].
   - Email provider [if support form/email handling exists].
   - No Stripe/payment provider in v0 unless added later.

7. User rights
   - Access, deletion, correction, opt-out/withdraw consent where applicable.
   - Contact email for privacy requests.
   - Explain that local files are not held by the site server, so there is no server-side media file to delete in v0.

8. Children
   - Not directed to children under 13 / under applicable age threshold.

9. International transfers
   - Site/operator/providers may process data in the United States and other countries.

10. Updates
   - Last updated date.
   - Policy changes when product adds accounts, payments, server upload, storage, or AI features.

## 5. Terms of Service required content

Minimum Terms sections:

1. Service description
   - “A browser-based video compression tool that helps users reduce video file size and prepare files for common sharing scenarios.”
   - “The default workflow is local browser processing; server-side upload/transcoding is not part of v0 unless separately disclosed.”

2. User responsibility
   - Users must have rights to the videos they compress.
   - Users are responsible for the content they process and share.
   - The service does not grant rights to copyrighted material.

3. Acceptable use
   - No illegal content or activity.
   - No infringement, harassment, malware, abuse, or attempts to overload the service.
   - No use to process or distribute content that violates applicable law or platform rules.

4. Output and quality disclaimer
   - Compression can reduce quality.
   - Target file size is an aim, not a guaranteed result.
   - Browser/device support varies.
   - Some formats/codecs are unsupported.

5. No affiliation
   - “Discord, WhatsApp, Instagram, and other platform names are used only to describe common sharing scenarios and target-size presets. videocompressor.online is not affiliated with, endorsed by, sponsored by, or officially connected to those platforms.”

6. IP
   - Users retain rights to their own videos.
   - Site UI, copy, code, logo, and documentation are owned/licensed by the operator.

7. Availability and changes
   - Service may change or be unavailable.
   - Features may be modified as browser support and technical constraints change.

8. Limitation of liability
   - No guarantee of uninterrupted service, exact output size, quality preservation, compatibility, or platform acceptance.
   - Liability limited to the maximum extent allowed by law.

9. Governing law
   - Wyoming / United States baseline [confirm final dispute venue].

10. Future paid features
   - If payments/subscriptions are added, Terms must be updated before launch of paid plan.

## 6. Cookie Policy required content

If v0 uses only strictly necessary cookies or no cookies:
- Say the site may use necessary technologies for security, delivery, and basic operation.
- Say analytics may be cookieless if configured that way.
- Explain that browser local processing may use temporary in-memory objects; these are not tracking cookies.

If v0 uses GA4, Clarity, ad pixels, or other non-essential cookies:
- List cookie categories: necessary, analytics, marketing.
- Explain purpose, provider, approximate retention, and opt-out/consent controls.
- Add consent banner for EU/UK visitors if non-essential cookies load.

Required cookie copy:

“Do not place analytics or session-replay scripts in a way that records filenames, local paths, video previews, frames, thumbnails, or the contents of files selected in the tool.”

## 7. Copyright / content boundary

### 7.1 User content

Recommended Terms copy:

“You are responsible for the videos you choose to compress and share. You must have the necessary rights and permissions to process and distribute your content. Using this tool does not give you any rights to third-party copyrighted material.”

### 7.2 No server custody in v0

Because v0 does not upload media by default, takedown exposure is lower than a hosting/transcoding site. Still, the site should publish a contact email for rights complaints.

Recommended copy:

“If you believe content made available through our website infringes your rights, contact us at support@videocompressor.online with enough information to identify the issue. In the default local compression workflow, user-selected videos are not uploaded to or stored on our servers.”

### 7.3 Prohibited content / use

Terms should prohibit using the service to process, prepare, or distribute:
- Illegal content.
- Copyright-infringing content without authorization.
- Malware or harmful files.
- Harassment, hate, sexual exploitation, child sexual abuse material, or other illegal material.
- Content intended to violate platform rules or applicable laws.

## 8. Platform-name nominative use boundary

Platform names in route names and presets are acceptable only as descriptive / nominative use, not branding.

Allowed:
- “Compress video for Discord 10MB.”
- “Prepare smaller MP4 files for WhatsApp sharing.”
- “Instagram preset: 1080p and balanced quality guidance.”
- “Target-size presets for Discord, WhatsApp, Email, Instagram, or custom MB.”

Required placement:
- Footer or relevant page note: “Not affiliated with Discord, WhatsApp, Instagram, Meta, or any other platform. Platform names are used for descriptive purposes only.”
- Terms no-affiliation clause.
- Avoid using platform logos unless a separate trademark review confirms logo-use permission. Text names are safer.

Forbidden:
- “Official Discord video compressor.”
- “Instagram-approved compressor.”
- “WhatsApp partner tool.”
- “Certified by Meta.”
- Platform logos as primary branding.
- Any badge implying endorsement, sponsorship, partnership, certification, or compatibility guarantee.

Route/copy notes:
- `/compress-video-for-discord` is acceptable as descriptive use.
- `/compress-video-for-whatsapp` is acceptable as descriptive use.
- `/compress-video-for-instagram` is acceptable as descriptive use.
- Do not buy ads or write title tags that imply official affiliation.

## 9. Forbidden / high-risk marketing claims

Never use these claims unless separately verified and legally reviewed:

- “unlimited video compression”
- “no limits”
- “lossless video compressor”
- “no quality loss”
- “supports all formats”
- “compress any video size”
- “5GB local compression”
- “fastest video compressor”
- “perfectly compress to target size”
- “guaranteed under 10MB/16MB/25MB”
- “official / approved / certified / endorsed / sponsored / partner” for platform pages
- “100% private” / “zero data collection” if analytics/security logs exist

Safer alternatives:

- “Aim for a target size.”
- “If the result is still too large, lower the resolution, choose a higher target size, or try a shorter clip.”
- “Best on desktop Chrome or Edge.”
- “MP4/H.264 first; some formats/codecs may not be supported in the first version.”
- “No upload by default.”
- “Analytics events do not include filenames or media content.”

## 10. Required page-level compliance copy

### `/` homepage / tool

Short trust strip:

“Private by default. Your video is processed locally in supported browsers — no upload in the standard workflow, and no filename or media-content tracking.”

Tool caveat:

“Compression may reduce visual quality. Results depend on your browser, device, codec, duration, and selected target size. If the target is missed, try 720p, a higher target MB, or a shorter clip.”

Browser support:

“Best on desktop Chrome or Edge. Safari, iPhone, and older devices may be slower or unsupported for full local compression.”

### `/mp4-compressor`

“Built for MP4/H.264 sharing tasks first. Some formats and codecs may not be supported in v0.”

### `/compress-video-for-discord`

“Use the 10MB preset to aim for a smaller file for Discord sharing. This tool is not affiliated with or endorsed by Discord. Target-size results are not guaranteed; if the output is still too large, lower the resolution or choose a smaller/shorter clip.”

### `/compress-video-for-whatsapp`

“Use the 16MB preset to aim for a smaller file for WhatsApp sharing. This tool is not affiliated with or endorsed by WhatsApp or Meta. Limits and behavior may vary by app version, region, and account type.”

### `/compress-video-for-instagram`

“Instagram sharing is usually about format, resolution, and quality tradeoffs, not one universal file-size limit. Use 1080p/balanced guidance and MP4/H.264 output where supported. This tool is not affiliated with or endorsed by Instagram or Meta.”

### `/privacy-video-compressor`

“The standard workflow is local: your selected video stays in your browser for compression. We do not receive, store, or analyze your video content, thumbnails, local file path, or filename in v0. If we add an optional cloud mode later, it will be clearly labeled and covered by a separate retention/deletion policy.”

### Footer

Required footer links:
- Privacy Policy: `/privacy`
- Terms of Service: `/terms`
- Cookie Policy or cookie section: `/cookie-policy` if non-essential cookies exist, otherwise Privacy section is acceptable
- Contact: `support@videocompressor.online`
- No-affiliation note: “Not affiliated with Discord, WhatsApp, Instagram, Meta, or any other platform named on this site.”

## 11. Server-side mode future gate

If a later version adds upload/cloud compression, this v0 compliance report is insufficient. Before release, create a new compliance review covering:

- Explicit opt-in upload consent.
- File retention window, e.g. deletion within X minutes/hours after processing.
- User deletion request process.
- Storage provider and region.
- R2/S3 object lifecycle rules.
- Signed URL expiry.
- Abuse and illegal-content reporting.
- DMCA/contact handling.
- Whether staff/admins can access uploaded files.
- Whether files are scanned, transformed, logged, or used for model training.
- Paid plan limits, taxes, refund policy, subscription cancellation, and Stripe disclosures.

Server-side copy must not appear on v0 pages unless the feature exists.

## 12. Launch gate checklist for downstream agents

Compliance P0 must be green before final QA:

- [ ] `/privacy` exists and includes no-upload/local-processing boundary.
- [ ] `/terms` exists and includes user-content responsibility, no-affiliation, output quality disclaimer, acceptable use, and limitation of liability.
- [ ] Footer links to Privacy and Terms from every indexable page.
- [ ] Contact email uses site domain; no Gmail placeholder in production.
- [ ] Hero/tool/privacy copy consistently says “no upload by default” and does not overpromise.
- [ ] Analytics implementation sends only allowed event fields; no filename/media content/local path/raw metadata.
- [ ] Platform pages include no-affiliation language.
- [ ] No forbidden claims appear in title, meta, H1, FAQ, CTA, schema, sitemap pages, or social preview copy.
- [ ] If Cookie Banner is needed, non-essential scripts do not load before consent.
- [ ] DNS/Cloudflare pending state is tracked as production activation, not compliance P0.

## 13. Required policy copy package

Use these as source blocks for copy/implementation.

### Privacy Policy — short draft

“videocompressor.online is operated by Nextfield Labs LLC [confirm]. The default video compression workflow runs locally in your browser. Your selected video is not uploaded to our servers for compression, and we do not collect your video content, thumbnails, local file path, or filename for analytics.

We may process limited technical data to deliver and secure the site, such as request logs handled by our hosting/CDN provider. We may also collect privacy-safe analytics events, such as page views, selected preset, browser/device class, and bucketed file-size or duration ranges. These events must not include filenames, paths, raw media content, thumbnails, or exact media fingerprints.

If you contact us, we process the information you send so we can respond. If we add accounts, payments, cloud upload, server-side compression, or storage features in the future, we will update this policy before those features are launched.

Contact: support@videocompressor.online [required before launch]. Last updated: 2026-06-03.”

### Terms — short draft

“videocompressor.online helps users reduce video file size and prepare videos for common sharing scenarios. Compression quality, speed, browser support, and target-size results vary by device, browser, codec, duration, resolution, and selected settings. We do not guarantee that a file will reach a specific target size or preserve original quality.

You are responsible for the videos you choose to compress and share. You must have the rights and permissions needed to process and distribute your content. You may not use the service for illegal, infringing, harmful, abusive, or platform-violating activity.

Discord, WhatsApp, Instagram, Meta, and other platform names are used only to describe common sharing scenarios and target-size presets. videocompressor.online is not affiliated with, endorsed by, sponsored by, certified by, or officially connected to those platforms.

The service is provided as-is to the maximum extent permitted by law. We may change or discontinue features as browser support and technical constraints change.”

### Cookie / analytics disclosure — short draft

“We use necessary technologies to deliver and secure the site. If analytics are enabled, they are used to understand feature usage and improve the product. Analytics must not collect filenames, local paths, video content, thumbnails, or raw media metadata. If we use non-essential cookies, session replay, advertising pixels, or similar tracking, we will disclose them and, where required, ask for consent before loading them.”

### Copyright / takedown contact — short draft

“Users are responsible for the content they process and share. If you believe material made available through this website infringes your rights, contact support@videocompressor.online with enough information to identify the issue. In the default local compression workflow, selected videos are not uploaded to or stored on our servers.”

## 14. Metadata

```json
{
  "compliance_verdict": "COMPLIANCE_GO_WITH_CONSTRAINTS",
  "p0_risks": [],
  "required_policy_copy": {
    "privacy": "Default local browser processing; no video upload in standard workflow; no filename/local path/media content/thumbnail analytics; disclose Cloudflare/security logs and privacy-safe analytics; update before accounts/payments/cloud upload/server-side compression.",
    "terms": "User owns/responsible for content; compression may reduce quality; target size/browser support not guaranteed; acceptable use; no affiliation with Discord/WhatsApp/Instagram/Meta; limitation of liability; Wyoming/operator details confirmed before launch.",
    "cookie": "Disclose necessary technologies and analytics; do not load non-essential cookies/session replay/ad pixels before consent where required; never capture file names, local paths, video previews, thumbnails, or media content.",
    "copyright": "Users must have rights to videos; local v0 has no server custody; provide support@videocompressor.online for rights complaints."
  },
  "next_inputs": [
    "Confirm production contact email support@videocompressor.online or alternative site-domain address",
    "Confirm final analytics provider and whether it is cookieless Plausible, GA4, Clarity, or other",
    "Frontend must provide analytics event schema proof showing no filename/media content/local path/raw metadata",
    "QA must verify no media upload in default compression flow via network inspection",
    "If any server-side/cloud mode is added, trigger new compliance review before launch"
  ],
  "artifact_paths": [
    "/root/.hermes/reports/site-videocompressor-20260603/compliance-v0.md"
  ]
}
```