Privacy

What the extension sends

When you extract data locally, the pages you visit, the selectors you build and the rows you capture stay inside your browser profile. They are written to IndexedDB on your own machine. We do not receive them, we cannot see them, and there is no telemetry that reports which sites you use Fyre on.

The extension contacts our servers in exactly two situations: to validate a licence key, and to check for an update. Licence validation sends the key and a hashed machine identifier. It does not send URLs, page content, extracted rows, or anything about what you were doing at the time.

What cloud runs send

A scheduled cloud run executes on our infrastructure, so by definition the target URLs, the recipe and the resulting rows pass through our systems. Results are retained for 30 days so you can re-download them, then deleted automatically. You can shorten that window, or set a run to delete its results as soon as delivery succeeds.

We do not read the contents of your runs, sell them, or use them to train anything. Engineers can access run data only when you ask for help with a specific run, and that access is logged.

Account and payment data

If you buy a licence we store your email address, your licence key and its activation records, and the payment reference returned by our payment processor. We never see or store your card details — those go directly to the processor, who is the party actually handling them.

If you never buy anything, we hold nothing about you at all, because the free tier does not require an account.

Website analytics

This website uses privacy-respecting, cookie-free analytics that record page views and referrers in aggregate. There is no cross-site tracking, no advertising pixel, and no consent banner, because there is nothing to consent to.

Your rights

You can ask for a copy of everything we hold about you, ask us to correct it, or ask us to delete it, and we will do so within 30 days. Deleting your account removes the licence record, which deactivates the licence — so do it deliberately.

• Access — a copy of your account data, by email.
• Correction — fix anything inaccurate.
• Deletion — remove your account and licence record.
• Export — your cloud run results as CSV or JSON.
• Objection — stop any processing you disagree with, where the law gives you that right.

Data you collect with Fyre

This matters and it is easy to skip: when you scrape personal data, you become the controller of it. Your obligations under GDPR or equivalent laws attach to you, not to us. Fyre is the tool; the lawful basis, the retention period and the notice obligations for whatever you collect are yours to work out.

Contact

Questions about any of this go to the support address below and are answered by a person, not a form.