Barecopy's answer

Privacy-conscious professionals who share documents and photos: lawyers, journalists, HR and recruiters, real-estate and finance staff, consultants, and anyone in a corporate environment who needs to strip author names, company info, edit history, or GPS location before sending a file out. The corporate-network-friendly, no-upload design specifically targets people whose employers block cloud tools.

TranscriptFetch's answer:

Developers and technical teams building on video and web content. The common cases are RAG and retrieval pipelines that need video as text, AI agents that need to read a link mid-conversation, content teams repurposing short-form video at scale, and media monitoring and research tools. It is an API first, so the buyer is usually the person writing the integration rather than an end user. The free browser tools exist for one-off transcripts and for evaluating output quality before writing any code.

Barecopy's answer

Barecopy grew out of a real, recurring problem: hidden metadata leaking sensitive information — an author's name, a company, revision history, or the GPS coordinates baked into a photo. Existing online cleaners solved this by uploading your file to their servers, which defeats the purpose. Barecopy was built on the opposite principle — your files never leave your machine — after CDN-blocking corporate networks repeatedly broke server-dependent tools. It's a deliberately simple, self-hosted, single-page app so that the privacy guarantee is provable, not just marketing.

TranscriptFetch's answer:

It started with discovering there is no good way to get the text of a video. YouTube’s official Data API will confirm a caption track exists and then refuse to hand it over, because captions.download requires the video owner’s OAuth token. The popular open-source libraries work until you deploy them, at which point platforms start refusing datacenter IPs. And YouTube is the easy case: TikTok and Instagram publish no caption file at all. Every workaround solved one platform, worked locally, and broke in production. TranscriptFetch is the version that handles the failure cases as first-class behaviour rather than edge cases.

Barecopy's answer

Barecopy does 100% of its work in your browser. Files are read, analyzed, and cleaned locally — nothing is ever uploaded to a server. Most "metadata remover" tools online quietly upload your document to their backend to process it, which is exactly the wrong trust model for a privacy tool handling sensitive files. Barecopy's entire app is a single static page with self-hosted libraries and zero external requests, so even on locked-down corporate networks (which block CDNs) it works — and there's no server that could leak your data.

TranscriptFetch's answer:

Most short-form video has no caption track to download. TikTok’s auto-captions are opt-in per upload, Instagram never publishes a downloadable track, and many captions on both are burned into the video frames where no parser can read them. TranscriptFetch transcribes the audio when no caption track exists, on the same endpoint, with the same response shape. Your code never branches on which method produced the text. It also covers YouTube, TikTok, Instagram, X and Facebook plus any web page as clean Markdown, so a pipeline spanning several sources is one integration rather than five.

Barecopy's answer

Barecopy is used by privacy-conscious individuals and professionals across legal, journalism, HR, and corporate roles. By design it processes files entirely on the user's device and collects no data, so it keeps no customer list.

Barecopy's answer

• Truly private by design — not a promise, an architecture. There's no upload endpoint.
• Broad format coverage — Word/Excel/PowerPoint (DOCX/XLSX/PPTX), PDF, and JPG/PNG/WebP photos, all in one tool.
• Lossless photo cleaning — strips EXIF/GPS while copying pixels untouched (no re-compression).
• Deep cleaning, not just the obvious fields — clears document core/app/custom properties, thumbnails, PDF info dict + XMP metadata.
• Verifiable results — an optional on-brand PDF report records what was found and removed per file, including the SHA-256 of the clean copy.
• Honest, fair pricing — free for up to 3 files at a time; Pro is €4/mo.

TranscriptFetch's answer:

Three reasons. Coverage: one API key and one response shape across five video platforms and the open web, instead of stitching together a library per platform. Reliability: requests run through rotating infrastructure, so code that works locally keeps working from a server, which is where most open-source approaches break. Billing that matches reality: one credit per successful response, with failed, blocked and empty results never charged. That last point matters on short-form video, where a meaningful share of any batch is music with no speech in it. There is also an MCP server, so AI agents can fetch transcripts as a tool without a custom integration.

Barecopy's answer

• Plain HTML/CSS/JavaScript — no framework, no bundler, no build step; one static page.
• Client-side libraries, self-hosted: JSZip (OOXML unzip/rezip), pdf-lib (PDF metadata), exif-js (EXIF).
• Browser-native APIs for byte-level image metadata stripping.
• Hosting: Vercel (static), with a single serverless function only for the contact form (SMTP via nodemailer).
• Payments: Polar for the Pro subscription.

TranscriptFetch's answer:

Next.js with TypeScript and Tailwind on the front end and API layer, Clerk for auth with SHA-256 hashed API keys, Neon Postgres with Drizzle ORM, Redis for caching, and Stripe for billing. The extraction layer is a Python and FastAPI service. Speech-to-text uses Whisper-class models. The MCP server is published in the official Model Context Protocol registry with a DNS-verified namespace.