Privacy & data sourcing

1. How we collect data for our datasets

Dataset collection is carried out from publicly accessible pages. Specifically:

• We do not use another person's account, login, or authentication to reach non-public data.
• We do not circumvent access controls, paywalls, or subscription barriers.
• We do not obtain data from breaches, leaked sources, or private systems.
• We do not assemble customer datasets from feeds purchased from third-party data aggregators.

Collection runs on infrastructure we operate. Customer datasets are built in-house rather than assembled from other vendors' feeds. Project scope is reviewed before collection, including the source, fields, intended use, and any privacy concerns that the data may raise.

2. What our datasets contain

Our datasets are designed to describe commercial activity, not people. Typical records cover marketplace listings, events, venues, products, menus, part numbers, stock levels, and prices. We do not build profiles of individuals.

Incidental personal data and redaction

One dataset includes a free-text field in which a seller may type anything they choose. A small number of sellers enter an email address or telephone number in that field. Automated pattern matching detects those values and replaces them with a redaction marker before delivery.

In one audited 205-day series, this affected approximately 32,700 of 588 million rows, or about 0.006%. Every detected match was redacted from the delivered dataset. If a comparable field is identified in a future project, we apply the same safeguard before the first delivery.

Business contact details

Some restaurant datasets contain the street address and telephone number of commercial premises, as publicly listed by the source platform. These fields identify business locations and are retained because they are used to identify and match stores. If a field identifies a person rather than a business location, we assess and handle it as personal data.

Our approach to data protection law

Public availability does not by itself place personal data outside data protection law. If information capable of identifying a person appears during collection, we treat its collection, filtering, and removal as processing. Our controls are designed to minimise that processing and prevent identifiable personal data from entering customer deliveries.

We do not sell or share personal information as those terms are used by the California Consumer Privacy Act. If you believe a dataset we license contains personal data relating to you, contact us. We will investigate and, where appropriate, remove or correct the information and address the source of the issue.

3. Data we hold about you

Separately from customer datasets, Pyronets holds limited personal information about people who contact us and technical information generated when this website is requested.

When you contact us

If you complete a form or email us, we receive the name, email address, company, project details, and message you provide. Website forms send those details to our business inbox through our mail infrastructure. We use them to respond, prepare a proposal or take steps you request before a contract, manage any resulting business relationship, prevent misuse of the form, and keep an appropriate business record.

Where UK or EU data protection law applies, the relevant legal bases may include taking steps at your request before entering a contract, performing a contract, complying with legal obligations, and our legitimate interests in responding to enquiries, securing the site, and maintaining business records.

When you visit this site

Our hosting provider processes standard request and security information, which may include an IP address, browser and device details, requested pages, timestamps, and diagnostic data. This is used to deliver the site, maintain reliability, detect abuse, and troubleshoot faults. Pyronets does not use this information to build visitor profiles.

Cookies and analytics

At the date of this policy, this site does not use advertising cookies, cross-site tracking pixels, or third-party analytics cookies. If that changes, we will update this notice and, where required, ask for consent before non-essential cookies are used.

How long we keep information

Enquiries are kept while the conversation is active and for up to two years afterwards so that a prior discussion can be resumed. Records connected with a customer relationship are kept as long as needed to perform the contract, maintain security and delivery records, meet accounting or legal obligations, and establish or defend legal claims. Hosting and security logs follow the retention periods set by the relevant provider and our account configuration.

Who receives it and where it is processed

We do not sell, rent, or trade your personal information. It is available only to people at Pyronets who need it and to providers that support our hosting and business email, acting for those limited purposes. We may also disclose information to professional advisers or authorities where reasonably necessary or required by law.

Pyronets is based in Pakistan and its service providers may process information in other countries. Where a data protection law requires safeguards for an international transfer, we use the safeguards available through the relevant provider or agreement.

Your rights

Depending on the law that applies, you may have rights to ask whether we hold personal data about you, obtain a copy, correct or delete it, restrict or object to processing, or receive certain information in a portable format. You may also complain to the data protection authority that applies where you live or work.

Email us to make a request. We may ask for enough information to verify that the request concerns you, and we will respond within the period required by applicable law. You will not be treated differently for exercising a privacy right.

4. Security

Data is held on access-controlled infrastructure. Customer deliveries are made over authenticated channels, such as SFTP or customer-controlled cloud storage. Credentials are not shared between customers. We use technical and organisational safeguards appropriate to the nature of the information, while recognising that no internet transmission or storage system can be guaranteed completely secure.

5. Client confidentiality

We do not publicly disclose customer identities, commissioned sources, or customer specifications without permission. Requirements, target lists, credentials, and feedback supplied by one customer are not reused for another customer.

6. Changes to this page

If our practices change, we will update this page and revise the date at the top. Material changes will be explained here before or when they take effect where required.

7. Contact

Pyronets is responsible for the website enquiry information described in this notice. Questions about the policy, or requests relating to personal data, can be sent to: