Frequently Asked Questions

Quick answers about what FTVDB is, how it works, and how to take part. Still stuck? The Contact page is open.

What is FTVDB?

FTVDB is a community-driven reference library that indexes public update URLs for Amazon devices — Fire TV, Fire Tablet, Echo, and Kindle — along with the metadata needed to understand each record later, such as device model, software version, build, checksum, and capture date.

Does FTVDB host firmware or app files?

No. FTVDB stores links and metadata only. It does not host firmware images, app packages, copyrighted update files, device backups, or account data. When you follow a record, you are reaching a public location, not a copy kept by FTVDB.

Is this legal? Is it piracy?

FTVDB documents where public update files have been published. It does not distribute paid content, crack software, or bypass protections. The project does not promote piracy, downgrading, rooting, or getting around device security. If a rights holder believes a specific linked location infringes their rights, they can request review at support@ftvdb.com.

Why can't I find an old link that used to be here?

FTVDB favors live links over a catalog of dead ones. Amazon's update infrastructure changes over time, and links that stop working are removed so the database stays accurate. A smaller set of working records is more useful than a large set full of broken ones. A missing link can also mean the original capturer asked for it to be excluded.

Why does the firmware version matter more than the device name?

Two devices that share a marketing name can run very different software. A current Fire TV Stick may run Vega OS while a Fire TV smart TV runs an Android-based Fire OS, and older hardware spans several Fire OS generations. The model, build, and version are what actually tell you how a device behaves — which is why every record keeps that context.

How do I find my device's model and software version?

It is in each device's settings. On Fire TV, open Settings → My Fire TV → About. On a Fire Tablet, open Settings → Device Options. On a Kindle, open Settings → Device Options → Device Info. The manual walks through each one step by step.

How do I contribute a URL?

Capture a public update URL from a device you own, then send it through the submission page, or use the API if you collect links regularly. Helpful submissions include the device family, model, current version, and target version. The manual explains how to recognize a good URL.

Do I get credit for links I capture?

If you want it. Contributors who would like recognition can be listed on the Credits page. Crediting is optional and never required to contribute.

Can I contribute anonymously?

Yes. Many contributors prefer to stay anonymous, and that is fully respected. The project does not log who submits a link.

I captured a URL and I want it removed. What now?

Send an opt-out request to support@ftvdb.com. You may be asked for proof that you were the original capturer, so that someone cannot remove records they did not collect. If you were the first to capture it, the matching records will be removed.

I'm a rights holder. How do I request removal?

Email support@ftvdb.com with the details of the linked location you believe infringes your rights. Requests are reviewed and answered promptly. See the Terms & Disclaimer page for the full process.

Does FTVDB help me downgrade or root my device?

No. FTVDB is a documentation project. It does not provide downgrade paths, rooting instructions, or ways to bypass update systems or device security. It records public update history so it can be searched and preserved.

Can I use the data in my own project?

Yes. Full database snapshots are published to the FTVDB GitHub repository in a simple, scriptable structure. You are welcome to read, analyze, and build tools on top of it.

How is my privacy handled, and what about ads?

Site analytics use a cookieless, privacy-respecting tool, and submissions are processed only to validate and index the URL. The site may show ads via Google AdSense, which can use cookies as described on the Privacy Policy page.