StripPii's answer

StripPii is 100% offline. No cloud, no servers, no company ever sees your data. It detects PII (emails, credit cards, SSN, names) and EXIF metadata (location, device, timestamp) using Apple's native frameworks, then redacts everything locally on your device. Free for everyone. No subscriptions, no paywalls. Built by a solo indie developer who cares about privacy.

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.

StripPii's answer

Built entirely with native Apple frameworks. All processing happens on-device Mac, iPad, iPhone share the same codebase. No cloud servers, no third-party dependencies, no tracking.

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.

StripPii's answer

Most privacy tools process data in the cloud. StripPii doesn't. Your sensitive information never leaves your device. You see exactly what's being leaked before redacting. Plus it's free privacy shouldn't be expensive. One-time Pro purchase for batch processing if you need it. No monthly subscriptions draining your wallet.

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.

StripPii's answer

Privacy-conscious users who actually care about protecting their data. People sharing sensitive documents, screenshots, or images online. Professionals handling confidential information. Anyone tired of leaking location data, device fingerprints, and personal details without realizing it. Users on Mac, iPad, or iPhone who value offline-first design.

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.

StripPii's answer

Built it because I was tired of leaking my own data in every screenshot. Emails, credit card info, location metadata all exposed without realizing. Realized others faced the same problem. Decided to build something that detects and redacts everything automatically, offline, no cloud required. Free for everyone because privacy is a right, not a luxury.

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.

StripPii's answer

StripPii is free, so there aren't traditional "customers" yet. Users include:

Privacy-conscious professionals handling sensitive documents Remote workers sharing screenshots in secure environments Freelancers protecting client information Privacy advocates testing offline-first tools Mac/iPad/iPhone users concerned about data leaks Early adopters from Product Hunt, Reddit, Twitter communities

(Still in early adoption phase building community organically through word-of-mouth and privacy-focused communities.)