getregdata
Home / Data API / API terms
Terms · Data API

GetRegData API terms

Version 1.0, effective 2026-11-02. The Polish version (Regulamin usługi API GetRegData) prevails if the two differ.

1. Provider

  1. The service is provided by DESTINA SŁAWIŃSKA GROWIFY, a business registered in the Polish Central Register of Business Activity (CEIDG), NIP (tax ID) 9291789361, REGON 384770507, trading as GetRegData (the Provider). The business address is public in the CEIDG entry.
  2. Contact: contact@getregdata.com.

2. Definitions

  1. Customer - a business or organisation using the API for its business or professional activity. The service is not for consumers.
  2. API - the interface at https://api.getregdata.com, as described in the documentation given to the Customer.
  3. Key - an individual access key (test grd_test_ or production grd_live_).
  4. Check - one completed API request that is charged under the price list, for example a full company check by tax ID or company number (/v1/checks) or a request to one data line (/v1/lookups).
  5. Order - the production key order form on getregdata.com, or an order sent by e-mail and confirmed by the Provider.

3. Scope

  1. The API returns data from official public registers, as listed in the documentation and at /v1/lines, and - where an Order includes them - daily change files (feeds).
  2. Data is read from the register at request time or from a change file updated daily. Every response states the date and time the data is current as of.
  3. The Provider does not change or correct register data. A response reflects the register at the time it was read.
  4. The API does not return national identification numbers (PESEL).

4. Contract and keys

  1. The contract starts when a production Key is issued after an Order and acceptance of these terms.
  2. A test Key is free and limited to the number of Checks stated when it is issued.
  3. The Customer keeps the Key confidential and is responsible for requests made with it, and tells the Provider at once if a Key is lost or exposed; the Provider issues a new Key.
  4. The Customer does not share the Key. A partner that builds the API into its own software may use one Key on behalf of its clients only if agreed in writing or by e-mail.

5. Prices and billing

  1. Prices are those in the Order or in the price list sent to the Customer, net of VAT.
  2. Only completed Checks are charged. A request the API did not complete is free. A “no match” result is a completed Check unless the price list says otherwise.
  3. Billing is monthly in arrears: by the 7th of each month the Provider invoices the previous month’s Checks, payable within 14 days.
  4. The Customer can see usage at any time at /v1/usage.
  5. The Provider gives at least 30 days’ notice of a price change by e-mail. A Customer who does not accept the new prices may end the contract before that date.
  6. If payment is more than 14 days late, the Provider may suspend the Key after notice by e-mail.

6. Availability

  1. The Provider aims for uninterrupted service but does not guarantee it. Public registers can be unavailable or slow, which can delay or prevent a response.
  2. A service level (SLA) applies only if the Order includes one.
  3. The Provider may limit concurrent requests per Key, as stated in the documentation or when the Key is issued.
  4. The Provider gives at least 30 days’ notice by e-mail of planned downtime and of changes that break backward compatibility. Adding fields to a response is not such a change.

7. Customer obligations

  1. Use the API and the data lawfully, including data-protection law.
  2. Do not resell the data as a database or offer it as your own API service without the Provider’s written or e-mail consent.
  3. Do not disrupt the API, exceed limits or try to bypass its safeguards.

8. Personal data

  1. Responses can contain personal data from public registers: names of board members, commercial proxies, partners and beneficial owners, and for sole traders their register and notice data.
  2. The Provider processes this data as a controller to the extent needed to provide the service, as described in the privacy notice at getregdata.com/privacy/.
  3. A Customer that receives data in a response becomes a separate controller and needs its own legal basis (for example anti-money-laundering obligations or a legitimate interest in verifying a counterparty).
  4. If the Customer gives the Provider personal data to process on its behalf (for example a list of sole traders’ tax IDs for ongoing monitoring), the parties sign a data processing agreement before that processing starts.

9. Liability

  1. The Provider is not liable for the content of register data, its errors, gaps or late publication by the register.
  2. The Provider’s total liability to the Customer, on any basis, is limited to the fees the Customer paid in the three months before the event giving rise to the claim, and excludes lost profits.
  3. These limits do not apply to wilful misconduct.

10. Complaints

  1. Send complaints to contact@getregdata.com with the Key ID (not the secret), the request ID and a description.
  2. The Provider answers within 14 days. A Check that returned a wrong result because of the Provider is not charged, or is credited.

11. Term and termination

  1. The contract runs for an indefinite period.
  2. The Customer may end it at any time by e-mail; Checks made until then are payable.
  3. The Provider may end it with 30 days’ notice, or immediately for a material breach not cured within 7 days of notice by e-mail.
  4. The Key is switched off when the contract ends.

12. Changes and final provisions

  1. The Provider gives at least 30 days’ notice by e-mail of changes to these terms. A Customer who does not accept a change may end the contract before it takes effect.
  2. Terms agreed individually in an Order or a separate contract prevail over these terms.
  3. Polish law applies. Disputes go to the court competent for the Provider’s place of business.
  4. The parties communicate by e-mail, using the addresses in the Order and contact@getregdata.com.

Polish version: Regulamin usługi API GetRegData. Order a production key: API key order form. Website terms: Terms of use.