Legal FAQ

Jsonify collects data from public websites and mobile apps by automated means. That is web scraping in the ordinary sense of the term. What you buy is a pipeline built from your brief, checks on every row, a dataset published to your tools on schedule, and repair when a source changes. The legal questions are the same as for any automated collection: which sources, what access, what data, and what use. You confirm the sources and fields before anything is collected. By default, Jsonify does not access content behind a login or paywall; on self-serve you can connect your own account to some sources, as described below. The answers below cover the rest.

You do. Jason proposes sources, fields and a schedule; nothing runs until you confirm them. Jason may later suggest new sources or columns; those are applied only if you accept them. Your confirmed configuration is the instruction Jsonify works to.

Publicly available commercial information from websites and mobile apps: product listings, prices, availability, menus, catalogs, and similar data. Pipelines can also read files you upload as sources. Jsonify’s own pipelines are designed for products and services, not people. By default, Jsonify does not read content behind a login, paywall or subscription. On self-serve you can connect your own account to some sources. You sign in yourself; Jsonify does not store your password. Jsonify blocks this for many sources, including social networks and sources that are mainly about individuals, and stops on a site operator’s objection. See Terms Section 6.

For websites, robots.txt is read when a source is added. Jsonify honours rules addressed to its collector by name and builds no collection for paths they disallow; self-serve users cannot override this. Site owners can also ask us to stop directly, and we act on that for all customers. robots.txt does not apply to mobile apps, where Jsonify reads only what the app shows without signing in. By default, Jsonify does not read content behind a login, paywall or subscription. On self-serve you can connect your own account to some sources. You sign in yourself; Jsonify does not store your password. Jsonify blocks this for many sources, including social networks and sources that are mainly about individuals, and stops on a site operator’s objection. See Terms Section 6. Pipelines limit request rates and cache fetched content so sources are requested fewer times. Where a source is read through a third-party fetch provider, the same rules apply to that request.

Enterprise deployments can set stricter robots.txt handling, documented in the agreement, and access gated content only on sources named in the agreement, using the customer's own accounts within their permissions. The signed agreement governs over the self-serve Terms and can set different source rules than those described here. See Terms Section 1.

No. Self-serve collection does not tick boxes, register accounts or submit forms, so Jsonify does not accept any source's terms for you. Products that complete forms (Benchmark) are enterprise-only and governed by that agreement.

Jason proposes sources and schemas, but nothing runs until you confirm it, and you are responsible for what you confirm: whether you are authorized to access and use the data, and whether your use complies with applicable laws and any source terms that bind you. Jsonify is responsible for operating the Services as described in the Terms — honouring site-owner opt-outs which target our bots, accessing gated content only through an account you connect, and processing personal data only as your processor or as set out in a signed agreement.

On self-serve plans, you are the data controller for the pipelines you configure and Jsonify is your data processor under the Data Processing Addendum, which is incorporated into the Terms.

No. Jsonify does not use customer data to train models, and does not copy rows delivered to a customer into datasets offered to others. Jsonify may collect the same public data independently, for itself or for other customers; that collection is its own, not customer data. Pipelines are built and repaired using third-party large language models acting as subprocessors, under terms that do not permit them to train on the data. The current providers are listed on the subprocessors page. Jsonify may publish de-identified operational metrics about the platform, such as repair times, that do not reveal customer data.

Jason is an AI system, and Jsonify discloses that wherever you interact with it — in the product and in communications Jason sends — in line with the transparency obligations of Article 50.1 of the EU AI Act, which have applied since August 2026.

Pseudonymisation and filtering of personal-data fields can be configured into a pipeline under an enterprise agreement; where configured, it runs on every row. It is not enabled on self-serve pipelines. Note that techniques such as hashing or masking usernames are pseudonymisation rather than anonymisation in the GDPR sense; either way, personal data in your pipelines is handled under the Data Processing Addendum.

Datasets and run artifacts are stored on infrastructure in the European Union. Processing also happens in the United States through the fetch and model providers listed on the subprocessors page.

Jsonify may stop collecting from any source at any time, for all customers, including when the source's operator asks. Affected customers are notified where practicable and are not billed for rows not collected. Site and app owners: see For website and app owners.

A row is counted only when it has passed its checks and reached your dataset, or when Jason hands you collected records in a chat; every run counts. Each month up to 100 rows are free; above that, usage is billed at month end in arrears with a US$49 monthly minimum, at the rates on the pricing page. Builds, previews, retries, blocked pages and repairs are never charged. Billing starts only after you explicitly enable it and add a payment method. The full terms are in the Self-Serve Terms.

Not for decisions about an individual's eligibility for credit, employment, housing or insurance, or anything else regulated as a consumer report; the Services are not a consumer reporting agency. The Acceptable Use Policy also prohibits using datasets to locate or surveil individuals, to send unsolicited communications to contact details you collect, or for purposes the individual could not reasonably expect given where the data was published. Other business uses of personal data are yours to assess as the data controller.

Your schemas and source lists are yours. For the datasets Jsonify delivers to you, Jsonify grants a perpetual, transferable licence covering everything Jsonify holds in them, including the database right in their selection and arrangement: you can use them commercially, build on them, train models on them, and distribute or resell them, except for Provider-sourced Data, restricted-source content and connected-account content, which you may use in your own products but not redistribute as data. Jsonify holds no rights in the underlying data items themselves; those stay with the source owners and the individuals concerned. Jsonify owns the platform, its reusable extractors for public sources and its technical knowledge of how public pages are structured, and reuses those across customers. Raw fetched content may be cached and shared across pipelines to reduce load on sources; your rows, schemas and source lists are never shown to other customers. Read the ownership terms →

Yes. Unless a dataset's page says otherwise, the public datasets are licensed under CC BY 4.0: you can copy, share and adapt them, including commercially, if you credit Jsonify and link to the dataset's page. The licence covers the datasets as Jsonify compiled them; it grants no rights in the source websites' own content or trademarks, which stay with their owners. A dataset that includes content Jsonify may not redistribute carries its own terms on its page instead.