getregdata
Home / Privacy
Privacy

Privacy

Last updated: 24 October 2026

getregdata provides software - agent skills, an MCP server, and scraper actors on the Apify platform - for accessing official, publicly available business-registry data, and for some registers a managed feed that we run and deliver ourselves. This notice covers the getregdata.com website and those managed feeds. It is short on purpose, because we collect very little.

Who we are

getregdata is operated by DESTINA SŁAWIŃSKA GROWIFY, a business registered in Poland, tax identification number (NIP) PL9291789361. For this website, for enquiries sent to us, and for the managed feeds described below, this business is the data controller. For anything about personal data, write to contact@getregdata.com.

What we collect on this website

  • Website analytics. We use Cloudflare Web Analytics, which is cookieless. It does not set cookies, does not track you across other sites, and does not store information that identifies you. There is no advertising or profiling.
  • If you contact us. If you e-mail us or use a form on this site, we receive what you enter - your e-mail address, and your name, company and message if you give them - together with the page you wrote from. We use it only to reply, to prepare a sample or quote you asked for, and to keep a record of the request. We do not sell or share it, and we do not add you to any mailing list. The form is delivered to our mailbox by service providers acting for us (website hosting, e-mail delivery and mailbox hosting).

Self-serve actors: we do not see your data

When you run the actors yourself, we do not receive, store, or process the data you extract. The actors run on the Apify platform under your own Apify account, and the results go to your Apify storage - not to us. Your use of Apify, including how your runs and results are handled, is governed by Apify's privacy policy and terms.

The registries return information about companies and, in some cases, individuals (such as directors or beneficial owners) from official public sources. When you run an actor, you decide what to query and how to use the results - so for that activity you act as the data controller. Please use the tools and any data you obtain lawfully and in line with applicable data-protection law.

Managed feeds: what we collect and deliver

A managed feed is different: we run the extraction and send the results to the client, so for that activity we are the controller of the data we handle.

  • Company-level data only. Managed feeds deliver information about companies and other legal entities as published by official registers and gazettes - for example name, registered address, legal form, corporate purpose, share capital, registry reference, and publication or filing dates. Standard feeds do not include the names of directors, shareholders or beneficial owners, and do not cover proceedings concerning private individuals.
  • Where a person can still appear. Official records sometimes contain a person's name inside company data - a company named after its founder, or a small company registered at a private address. We pass such records on exactly as the register publishes them and do not add, combine or infer anything about individuals.
  • Court-appointed professionals. Where an insolvency notice names the trustee or another professional appointed by the court (in practice a lawyer or licensed practitioner acting in that office), the feed may carry their name and role as published, only where a client's use requires it (for example filing and following claims). They are not part of the standard feed. Supervising judges, company directors and liquidators who are not court-appointed professionals are not included.
  • Sources. Only official, publicly accessible registers and gazettes. Every record carries its source and the date it was read.
  • Why we may do this. Our legal basis is legitimate interest: making company information that the law requires to be published usable in practice, for the client's business purposes. We do not enrich records with contact details, and we do not build profiles of people.
  • How long we keep it. Run data is held on our processing platform for up to 31 days. A copy of each delivered file is kept with our delivery records for up to 12 months, for support and billing, and then deleted.
  • Who receives it. The client who ordered the feed, and the service providers that process it for us (run platform, e-mail delivery, mailbox hosting, payment processing for invoices). Clients are responsible for their own use of the data, including the marketing and data-protection rules that apply to them.

The getregdata API and monitoring

Clients with an API key can query official registers through api.getregdata.com, receive register feeds, and monitor a list of companies they choose. Two roles apply, depending on who decides what is processed:

  • Lookups, checks and feeds. The client decides which company to check and how to use the answer, so for the results the client is the controller. We read the official register at the time of the request and keep the result for 30 to 90 days so the client can read it again, plus a short record of the request (identifier, date, outcome) for billing. Results come only from official, publicly accessible registers. National identification numbers of private individuals (such as PESEL) are never returned.
  • Monitoring lists. When a client gives us a list of companies to monitor, the client is the controller of that list and we process it on the client's behalf, under a written data processing agreement. A list can include sole traders, who are natural persons, only when such an agreement has been signed. We use the list only to check the registers for that client, keep it separate from every other client's data, and never use it for anyone else.
  • How long we keep it. For monitoring: raw run data up to 31 days, the events we found up to 12 months, and an entry removed from a list stops being checked from the next business day and is deleted within 30 days. At the end of a contract the list is returned or deleted within 30 days.
  • Who processes it for us. Service providers in these categories: run platform, network and hosting infrastructure, e-mail delivery and mailbox hosting. The data processing agreement names each of them for the client.

Weekly digest e-mail

If you subscribe to the weekly digest, we process your e-mail address to send it to you. The legal basis is your consent, confirmed by clicking the link in the confirmation e-mail - until you click it, your address is not added to any list. The list is held by our e-mail delivery provider. Every issue has a one-click unsubscribe link, which removes you from future issues immediately; you can also write to contact@getregdata.com. The digest itself contains company-level register data only, never information about private individuals.

Your rights and contact

If you believe a managed feed contains information about you, or you want to know what we hold, to object, or to have something corrected or removed, write to contact@getregdata.com. We will check, exclude the record from future deliveries where you are entitled to that, and tell you which official register it came from - only that register can change the underlying public record. The same address works for any correspondence you have sent us. You also have the right to complain to your data-protection authority.

Changes

We may update this notice from time to time. The date above reflects the latest version.