Privacy Policy

Effective date: 17 November 2026 · Last updated: 17 November 2026

Mastros ("we", "us", or "our") operates the mastros.online website and provides browser-based tools, including the Facebook Marketplace & Ad Library Exporter Chrome extension, which exports Marketplace listings and Meta Ad Library ads that your own browser session can already see.

This Privacy Policy explains what the extension reads, what stays on your device, and the small amount of information that reaches us. Contact: admin@mastros.online

1. The short version

  • The extension runs only on www.facebook.com, in the tab you have open. It reads what Facebook has already sent to that page. It does not log in for you and cannot see anything your session cannot see.
  • The data you extract never reaches our servers. Listings and ads are assembled in your browser, kept on your computer, and saved as a file you download. There is no endpoint on our side that would accept them.
  • What we do receive is limited to what is needed to run a licence and to keep the tool working: an account identifier, your plan, usage counts, and product analytics that carry no extracted content.
  • The extension never posts, comments, reacts, sends messages, follows or joins anything, and never reads Messenger.

2. What the extension reads

It works on four kinds of Facebook page:

  • Marketplace results and listings: title, price as shown, currency, location, posted date, the listing's link and image links, and on a listing page its description, category and condition. This includes the seller's name, and on a listing page a link to the seller's profile. Marketplace sellers are often private individuals, so section 7 applies to that column.
  • Meta Ad Library searches and advertiser pages: the ads Meta publishes there for transparency, with the advertiser's name, Page link and category, the Library ID, start date, platforms, format, headline, ad text, call to action, destination link and image link.

How it reads them. Facebook loads its pages through its own data requests. A small script in the page makes a copy of those responses as they arrive, without changing, delaying or adding to them, and the extension also reads the page as displayed. To reach more results it scrolls the page, as you would. It sends no requests to Facebook of its own, and it does not download photos or videos: images are exported as links.

If Facebook shows a security check, the run stops and tells you. If Facebook asks for less traffic, the run stops, keeps what it has, and waits. It never answers a check or retries into a limit for you.

3. What stays on your device

Everything you extract, and it is kept after the run. Each export is saved as a dataset in a browser database on your computer (IndexedDB, named fbexport_db) so that a long run can resume where it stopped and a finished one can be downloaded again without re-reading Facebook. That database never leaves your device. You can delete one dataset, or all of them, from the panel, and removing the extension removes the lot.

Settings, the state of an in-progress run, the pacing counters and your plan and usage figures are kept in Chrome's local extension storage. Chrome's synced storage holds one thing only: a random install ID, so a plan survives a reinstall.

The export file (CSV, XLSX, JSON or JSONL) is created in your browser and saved the way any download is. It does not pass through us.

4. What we receive

Licence and billing

Our licence service at fbexport-api.mastros.workers.dev (Cloudflare Workers) keeps one row per user containing:

  • An account identifier. If you are signed in to Chrome, this is the email address of your Chrome profile, read through Chrome's identity.email permission. If you are not, a randomly generated install ID is used instead and we never learn an email address.
  • A browser fingerprint: a short hash of your screen size, browser language, time zone and operating-system platform. It is used solely to stop one person claiming an unlimited number of free allowances, and never for analytics, profiling or advertising.
  • Your plan and subscription status, your billing cycle dates, and, if you subscribe, the Stripe customer and subscription identifiers.

Usage counters (how many records you have exported in the current cycle) are held separately in Cloudflare KV. They are counts, not content.

Moving a paid plan to a new device

If you restore a paid plan on another computer, you type your billing email into the extension and we email a six-digit code to that address to confirm it is yours. The code is stored only as a hash, for ten minutes, and works once. To stop the form being abused, the number of codes requested is counted for an hour against the email address and against the IP address the request came from. Those counters expire on their own and are used for nothing else.

Product analytics

We use PostHog, hosted in the EU (eu.i.posthog.com), to see whether the tool works. Each event carries a random ID created for this installation, never your name or email address. Events and their properties are restricted by allow-lists in the extension itself: anything not on the lists is dropped before the request is built, so a future change cannot leak content by accident.

What is sent: the event name, and only these kinds of properties:

  • product, plan, extension version;
  • which kind of page was used (for example "Marketplace search" or "Ad Library advertiser"), how many records were gathered, how long the run took, whether it was resumed, which export format you chose, and why a run stopped;
  • failure causes, including that a security check or a rate limit was detected (never its contents), which page element a run could not find, and the extension's own error message, cut to 120 characters.

What is never sent: listing titles, prices, descriptions, seller names or profiles, advertiser names, ad text, links, search terms, or page addresses. As with any web request, PostHog receives the IP address the event comes from and may derive an approximate location from it. We do not add one.

5. Permissions, and why each one exists

  • www.facebook.com: the only site the extension runs on, in the top frame of the page.
  • storage: settings and resumable run state, kept locally.
  • identity / identity.email: identifying your licence across devices. Optional in practice: without a Chrome sign-in you fall back to an anonymous install ID.
  • fbexport-api.mastros.workers.dev: the licence service.
  • eu.i.posthog.com: the analytics described above.

It does not ask for access to your tabs, cookies, downloads, or any other website.

6. Processors

  • Cloudflare: hosting for this site and the licence service (Workers, D1, KV).
  • Stripe: payments, once paid plans are offered. Card details go to Stripe directly; we never see or store them.
  • Resend: sends the six-digit restore code, only if you request one.
  • PostHog (EU region): product analytics, as scoped above.
  • SplitForms: the contact and uninstall-feedback forms on this website. It retains submissions in its own dashboard.
  • Google: distribution through the Chrome Web Store and the Chrome identity API.

When you uninstall, Chrome opens a feedback page on this site. Its address carries your plan, how many days the extension was installed, a rough band for how many records you exported, your interface language and the extension version, and nothing that identifies you. Anything you write on that page is sent only if you submit it.

7. Data you extract about other people

Most of what the extension exports describes items and ads, but a Marketplace seller's name and profile link are personal data about someone who is not party to this policy, and an advertiser may be an individual too. For that data you are the controller, not us. We never receive it and cannot act on it for you.

You are responsible for having a lawful basis to collect and use it, for honouring access and deletion requests from those people, and for complying with Meta's terms and the data-protection law that applies to you. If you do not need the seller column, delete it from your file.

8. Retention and your rights

The account record we hold is one row, and this is all of it: your email address or install ID, the browser fingerprint hash, your plan and subscription status, your billing cycle dates, and your Stripe customer and subscription identifiers if you have paid. Usage counters are held alongside it. A pending restore code and the request counters described in section 4 expire on their own within an hour.

The record is kept while your account exists. Usage counters are deleted with it. Billing records are kept for as long as tax and accounting law requires, which is the one thing a deletion request cannot reach. Analytics events are retained by PostHog under its own retention settings and cannot be tied back to you by name, because no name or email address is ever sent.

If the GDPR or a comparable law applies to you, you may request access to, correction of, or deletion of the data we hold about you, and you may object to processing or ask for a portable copy. Write to admin@mastros.online and we will show you the record or delete it within 30 days, keeping only what a payment record obliges us to keep.

9. Children

The Service is not directed at children under 16, and we do not knowingly create accounts for them.

10. Changes

If what the extension reads or collects changes, including when it starts working on a new kind of Facebook page, this page changes with it and the "last updated" date above moves. Material changes will be called out in the extension or on this site rather than made quietly.

Questions: admin@mastros.online