Privacy Policy

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

Mastros ("we", "us", or "our") operates the mastros.online website and provides browser-based tools, including the Mastros X (Twitter) Data Exporter Chrome extension, which turns X pages you have open into CSV, Excel (XLSX), JSON or JSONL files on your computer.

This Privacy Policy explains what the extension reads, what stays on your device, and the small amount of information that reaches us. Mastros is independent and is not affiliated with, endorsed by or sponsored by X Corp. Contact: admin@mastros.online

1. The short version

  • The extension runs inside your browser on x.com (and twitter.com) and reads what the X page you have open has already loaded for you, in your own session.
  • What you export never reaches our servers. Posts, handles, names, bios, counts, links and image addresses are turned into the file you download, on your computer. There is no endpoint on our side that would accept them.
  • What we receive is limited to running your plan and keeping the tool working: an install ID, your Chrome profile email if you are signed in to Chrome, a short hash of basic browser settings, how many records you have exported, and product analytics without content.

2. What the extension reads, and how

The extension exports from these X pages:

  • an account's followers, following and verified followers;
  • a profile's posts, and your bookmarks;
  • a post and its replies, and the posts that quote it;
  • search results, for posts and for people;
  • a list's posts and its members;
  • the accounts that reposted a post, and the accounts that liked a post of your own (X shows likes only to a post's author).

On other X pages it says the page is not supported and exports nothing. It never reads direct messages. If more pages are supported later, this list changes before the extension ships them.

To read a page, a small script inside the X tab keeps a copy of the data responses X's own page fetches for itself. From each one it notes only the name of the request (for example "Followers"), its status, and the rate-limit figures X publishes with it; the extension then picks the fields it needs out of those copies, in your browser. Where X shows a page without such a response, for example a profile's posts when you are signed out, the extension reads the page as it is displayed.

It never sends a request to X of its own, and never changes, blocks or delays one X makes. It does not read your password, your cookies, X's security token or the headers your browser sends, and it cannot reach anything your own session cannot reach, such as a protected account you do not follow. It never clicks anything on X, and never posts, replies, likes, reposts, follows, bookmarks or sends a message. Images and videos are exported as links; the files themselves are never downloaded.

When you start an export of a list, the extension scrolls the page you have open, at a measured pace, so X loads more of it exactly as it would if you scrolled yourself. X publishes how many requests it allows and when that allowance resets; when the allowance runs low, the extension pauses until X's reset time and then carries on, with the rows so far saved. If the wait would be long, or it has already paused several times, it stops instead and keeps what it has. If X shows an account lock or a verification screen, the extension stops at once and tells you; it never tries to get past it. It opens another X page only when you click a link in its panel that says so.

3. What stays on your device

Everything you export. Files are built in your browser and saved through your browser's ordinary download.

Kept by the extension in your browser profile, and sent nowhere:

  • your saved exports ("datasets"), in the extension's own browser database (IndexedDB), until you delete them in the extension or remove it;
  • the rows of an export still in progress, saved after every batch (in the extension's local storage) so a reload or a pause never loses them;
  • your settings, your plan and usage meter, a record of your recent export activity that the extension uses to pace itself, and when you confirmed its one-time note on exporting lists of people.

Removing the extension removes all of it. The one exception is the install ID, which is also kept in Chrome's sync storage so that a reinstall keeps your plan; it syncs only to your own Chrome profile.

4. What we receive

Your plan and usage

To keep your plan and usage, the extension talks to our licence service at twexport-api.mastros.workers.dev (Cloudflare Workers), which keeps one record per installation. What it sends there:

  • A random install ID, created by the extension.
  • Your Chrome profile email, if you are signed in to Chrome. The extension reads it through Chrome's identity.email permission so your plan follows you to a reinstall or another computer. It is used for that and for billing, and for nothing else: no marketing, no profiling, no sharing.
  • A browser hash: a short code computed from your screen size, browser language, time zone and operating-system platform. It identifies no one on its own; it lets the service recognise a reinstall on the same browser so the free plan is not reset by reinstalling.
  • Your plan and how many records you have exported in the current cycle. These are counts, not content: the usage call carries a number, never the records themselves.

If the service cannot be reached, the extension keeps counting on your device and sends the count later; exporting does not depend on it.

Paid plans, when offered, are billed by Stripe. If you start a checkout, your install ID, your email if known, and the country Cloudflare derives from your connection are attached to the Stripe customer record, and we hold the Stripe customer and subscription identifiers and your billing cycle dates, never card details. During the beta every feature is free and has no record limit.

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. The extension gets the analytics key from our licence service; without it, nothing is sent to PostHog. Events are restricted by a strict allow-list in the extension itself: any event or property not on the list is dropped before the request is built, and text values are cut short, so a future change cannot leak content by accident.

What is sent: the event name, a random analytics ID, and only these kinds of properties:

  • product, plan and extension version;
  • which kind of X page an export ran on (for example "followers"), the file format, how many records, how long it took, and why a run stopped, including that it paused for X's rate limit or that X showed a lock or verification screen;
  • a short failure message when X's page changes and a read fails.

What is never sent: record content, post text, handles, names, URLs or page addresses, search terms, or your email address. Counts and causes only. As with any request, PostHog sees the IP address it comes from and may derive an approximate location from it under its own settings.

5. Permissions, and why each one exists

  • x.com and twitter.com: to read the pages you export, as described in section 2. They are the only sites the extension runs on.
  • storage: settings, the plan meter, the pacing record and the progress of an export, kept locally (section 3).
  • identity and identity.email: the Chrome profile email described in section 4.
  • twexport-api.mastros.workers.dev and eu.i.posthog.com: the licence service and analytics described in section 4.

There is no tabs, cookies, downloads, scripting, alarms, webRequest or history permission, and no access to any other site.

6. Processors

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

X Corp is not our processor: what you see on X is between you and X, under its terms and privacy policy. The extension sends X nothing beyond what its own pages already request.

7. Other people in your exports

Posts carry their authors' handles and names, and lists of people such as followers carry each account's handle, name, bio, the location and website it shows, and its public counts, so an export can contain personal data about people other than you. The extension exports only what X shows you: it adds no email address, phone number or other contact detail, and infers none. Before your first export of a list of people it asks you, once, to confirm that you will hold such data only for a lawful reason; each such run is capped in size and paced more slowly.

For the files you export, you are the controller, not us. We never receive them and cannot act on them for you. Use them only for a purpose you have a lawful basis for, and store and share them with care.

8. Retention and your rights

Your licence record is kept while you use the extension, and billing records, if any, for as long as tax and accounting rules require. A pending restore code and the request counters described in section 4 expire on their own within an hour. 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 is ever sent there.

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 from the email of your Chrome profile, or include your billing email, so we can find your licence.

When you uninstall, Chrome opens a short feedback page. Its address carries your plan, how many days you had the extension, a range for how many records you exported (for example "100 to 1,000"), your browser language and the extension version, so we can read the feedback in context. Nothing else.

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 collects changes, 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