Short version: Doomly doesn't have a server that collects anything about you. There's no account, no analytics, no tracking pixel, nothing you view or type gets sent to us. Everything below explains exactly why, extension permission by permission, because "trust us" isn't good enough — you should be able to check.
What Doomly is
Doomly is a Chrome extension (and this companion website) that changes how X (twitter.com / x.com) displays photos and videos in your own browser — full-screen, mobile-style scrolling, played from your own logged-in session. It runs entirely on your device. There is no Doomly backend server that your browsing activity, your posts, your follows, or your media pass through.
What the extension can see, and why
Chrome extensions have to declare upfront what they're allowed to touch. Here's what Doomly asks for and what each one is actually used for:
- Access to twitter.com / x.com pages. This is how Doomly finds the photo or video you clicked and builds the full-screen view over it. It does not run on any other website.
- Access to pbs.twimg.com / video.twimg.com. These are X's own media servers — Doomly fetches the photo or video directly from there (the same place your browser already loads it from) so it can show it full-screen or let you download it. Nothing is proxied through a Doomly server, because there isn't one.
- Local storage (`chrome.storage`). Your settings — Shield on/off, which body-part categories to cover, button layout, color theme, word/account filters — are saved on your own device only. They're not synced anywhere, and Doomly can't read them either; they just sit in your browser's local extension storage.
- Offscreen document. Doomly Shield's detection model (an on-device object-detection model, not a cloud AI) runs in a hidden background page so it doesn't slow down the tab you're using. The image it checks is fetched from X's own CDN — the same URL your browser would load anyway — and the result never leaves your machine.
Doomly Shield specifically
Shield decides whether to cover part of an image or video using a model that runs locally in your browser (ONNX/WebAssembly). No image or video frame is ever uploaded to any server — not to X, not to Doomly, not to any third party — for this analysis. If detection fails, times out, or can't run for any reason, the content stays covered rather than being shown; it never fails open.
Downloads
When you download a photo or video through Doomly, the file is saved directly from X's own servers to your computer through your browser's normal download mechanism. Doomly doesn't keep a copy, a log, or a record of what you've downloaded.
Payments (Doomly Pro / Doomly Shield)
If you buy a paid plan, your payment is handled entirely by our payment processor, not by Doomly directly — Doomly never sees or stores your card number. We only receive confirmation that a purchase was made, which is what unlocks the paid features. Doomly's payment processor will be Lemon Squeezy once paid plans go live — this page will be updated with final billing details the moment that happens.
This website (doomly.vercel.app)
The Doomly marketing site doesn't run analytics, doesn't set tracking cookies, and doesn't have a newsletter or contact form that stores your data anywhere. It's static pages hosted on Vercel; Vercel's own infrastructure logs (standard web server access logs) are outside Doomly's control and covered by Vercel's privacy policy, not this one.
Third parties
Using Doomly still means you're using X — your activity on X (what you view, like, follow, or post) is governed by X's own privacy policy, exactly as if Doomly weren't installed. Doomly is not affiliated with, endorsed by, or officially connected to X Corp.
Children's privacy
Doomly is not directed at children and isn't intended for use by anyone under the minimum age required to use X itself.
Changes to this policy
If what Doomly collects ever changes — for example, once a real payment processor is wired in — this page will be updated and the "last updated" date above will change. We won't start collecting more without saying so here first.
Contact
Questions about this policy: support@doomly.app.