Longtrove (“we,” “us”) is a browser extension and web app that helps you save, organize, and track ads from the Meta Ad Library. This policy describes exactly what data Longtrove collects, why, and how you can get it deleted. We've tried to write it in plain language rather than boilerplate; if anything here is unclear, email us (see “Contact” below).
When you sign in, we collect your email address. We use it solely to authenticate you (via Google sign-in or a one-time email link) and to send you account-related email, such as daily tracking digests you've opted into. We don't use it for marketing and we don't sell it.
When you use the extension to save an ad, we store the public ad content shown on that Ad Library page (creative text, images/video references, advertiser name, and similar metadata) under your account, along with any boards or notes you create. This only happens when you take an explicit action to save an ad; we don't save ads you merely browse past.
When you track an advertiser, Longtrove operates a dedicated browser session against public Meta Ad Library views about once a day. They use a dedicated browser session, not your browser, the Longtrove extension, or your Facebook account.
Each check observes a recent window and an impression-ranked window for one country. The windows are capped and are not a complete catalog. To verify and reparse a capture, Longtrove may retain rendered document HTML, per-card evidence, matched structured response bodies, advertiser profile facts, archive IDs, dates, ranks, media descriptors, downloaded public ad media, timestamps, and integrity metadata.
Public-source evidence is deduplicated canonically for an advertiser and country, while your tracker, notes, boards, history view, and digest remain account-scoped. Absence from a capped window never proves or confirms removal.
Beta participants can send bug reports, confusing experiences, and ideas from signed-in app pages. We store the text you submit, optional steps to reproduce, your contact preference, your account and beta campaign references, a page-type template (without private IDs, query strings, or fragments), the app release, report status, and timestamps. We do not automatically capture screenshots, page contents, clipboard contents, or console logs.
Reports are visible only to their author and authorized Longtrove operators. Operator status changes are recorded without copying report text into the audit history. We use reports to improve and support Longtrove; we contact you about a report only if you allow it. Reports and their status history are deleted with your account. You can continue reporting after complimentary Pro ends while the beta feedback program is open.
The former shared feedback board is closed. Historical posts and comments are retained as previously shared feedback for internal reference, not presented as private reports. They are no longer visible through customer pages.
Subscriptions are processed by Stripe. We never see or store your card number, expiration date, or CVC; that information goes directly to Stripe and never touches Longtrove's servers. We store only what Stripe tells us is necessary to manage your subscription: your plan, subscription status, and Stripe customer ID.
The extension sends us lightweight, anonymous-to-content usage counts so we can tell whether the ad parser is broken (Meta changes its page markup periodically, which can silently stop Longtrove from reading ads correctly). Specifically, we collect:
That's it. Telemetry never includes page content, ad text, URLs beyond the fact that an Ad Library page was scanned, or your browsing history outside the Ad Library.
We use a session cookie to keep you signed in. We don't use advertising or tracking cookies, and we don't run third-party analytics on the web app.
Account-owned records are deletable on request: contact us through the Longtrove listing's Support tab on the Chrome Web Store, and we'll confirm once deletion is complete. Verified local staging is moved to recoverable Trash after seven full days. Private raw evidence, normalized history, and content-addressed media currently have no automatic TTL because accepted observations retain evidence provenance.
We do not sell your data, and we do not share it with third parties except the service providers required to run Longtrove (Stripe for billing, our email provider for sign-in links and digests, and our hosting/database providers).
Longtrove's use and transfer of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
Longtrove is an independent, third-party tool. It is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc. It reads publicly available pages from the Meta Ad Library the same way a browser normally would.
Questions about this policy or your data? Contact us through the Longtrove listing's Support tab on the Chrome Web Store.