Skip to content

GDPR Compliant

Privacy Policy

EPKO sp. z o.o.

Effective Date: 2026-11-19Version 2.6

Hosting
Finland (EU)
Dedicated server. Project data never leaves the EEA.
IP address
SHA-256 + salt
In the consent register we store only a salted hash, irreversibly.
Cookies
6 months
We re-ask every six months. By default everything is "denied".
Your rights
8 GDPR rights
We respond without undue delay, within 30 days at the latest.

Data Controller

The controller of your personal data is: EPKO Spółka z ograniczoną odpowiedzialnością (EPKO sp. z o.o.), a Polish limited liability company ul. Podleśna 2, 05-270 Marki, Poland KRS: 0000908693 (District Court for the Capital City of Warsaw in Warsaw, 14th Commercial Division of the National Court Register) Tax ID (NIP): 1251720637 Statistical number (REGON): 389307530 Share capital: PLN 6,300.00 (fully paid up) Contact regarding personal data: Email: biuro@epko.tech We have not appointed a Data Protection Officer (DPO) as we are not legally required to do so. Please direct all data protection inquiries to the email address above.

What Data We Collect

We only collect data that is necessary to provide our services and ensure the proper functioning of our website. Here is a complete list: 2.1. Data you provide voluntarily • First and last name • Email address • Phone number (optional) • Message subject • Message content in the contact form • Company name and position (if provided during collaboration) 2.2. Data collected automatically • IP address (anonymized in Google Analytics; held briefly in the contact form rate limiter; stored in the cookie consent log only as a SHA-256 hash with a server-side salt, with no way to recover the original IP) • Browser type and version • Operating system • Screen resolution • Language preferences • Pages you visit on our site • Time spent on pages • Referral source (how you found our site) • UTM campaign parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term): if you granted functional cookie consent, we store them in browser sessionStorage, where they are cleared when the tab closes. Without that consent we only keep them in the memory of the open page, until it is reloaded or closed. We save them together with the submission from the contact form, the free audit, and the CapTable report, and with a call booked through our calendar (Cal.com), so we know where inquiries come from. Along with them we save only the address of the page the submission was sent from, without any parameters in that address (e.g. an ad click identifier) • A/B test variant identifier (e.g., hero section version): stored in localStorage only after you grant functional cookie consent • Cookie consent identifier (consent_id): a random UUID generated in your browser when you first make a cookie decision. It lets us prove that we obtained your consent (GDPR Art. 7(1)). The identifier is not linked to any other data and does not identify you on its own. • Front-end failure report data (only when an error occurs in your browser): error message, stack trace, page address without query parameters, browser type and version, our application version, and a technical report identifier 2.3. Transaction data (during collaboration) • Order history and amounts • Payment dates • Invoice details (tax ID, company address) • Email correspondence history 2.4. Data from Sign in with Google in our apps If you sign in to Medova, HART or Bezpieczny Obywatel with your Google account, we receive basic account data from Google. We describe it in section 12. 2.5. Data from forms in Meta ads (Facebook, Instagram) If you send us a request through a form in an ad on Facebook or Instagram, Meta passes us (directly or through Zernio, section 5.2) the data you entered: your name, email address and phone number and, if the form asks for them, your company name, city and answers to the form questions. With them we receive data about the ad the request came from: the names or IDs of the campaign, ad set and ad, the form name and ID and, when Meta provides it, the platform (Facebook or Instagram). We save them in our CRM as a submission, just like a submission from a form on our website. Sections 3 and 6 explain why and for how long.

Why We Process Your Data and Legal Basis

Every data processing activity has a specific purpose and legal basis. Here is the full breakdown: 3.1. Contract performance or pre-contractual actions Legal basis: Art. 6(1)(b) GDPR • The call booked in the calendar on the contact page • Responding to a submission from a form in a Meta ad • Preparing and executing an offer or contract • Communication within an ongoing project • Payment processing and invoicing 3.2. Legal obligations Legal basis: Art. 6(1)(c) GDPR • Issuing and storing invoices (accounting regulations) • Tax settlements • Responding to requests from public authorities 3.3. Legitimate interests of the controller Legal basis: Art. 6(1)(f) GDPR Our legitimate interests are: • Establishing or defending against legal claims (e.g., project correspondence archive) • Ensuring website security, including limiting form abuse (IP-based rate limiting at 5 submissions per minute) • Internal lead-handling automation on our server in Finland (forwarding the contact form payload to our n8n instance for team notifications and classification) • Attributing submissions, that is knowing where inquiries come from: together with a submission from the contact form, the free audit, or the CapTable report we save the UTM parameters and the address of the page it was sent from (without the parameters in that address), so we can see which channels and pages bring inquiries; for a submission from a form in a Meta ad we save the form name and the names or IDs of the campaign and ad for this purpose • Cookieless visit analytics (self-hosted Umami): counting page views, traffic sources and basic Core Web Vitals metrics without identifying individuals, without cookies, and without sending data to the software vendor • Maintaining a consent register (GDPR Art. 7(1)) to demonstrate that we obtained consent • Detecting front-end failures in your browser: when a script on the page breaks, your browser sends us the error message, the stack trace, the page address without query parameters, and your browser type and version, so that we know what broke and can fix it. We do not store anything on your device and do not read anything from it, we do not send user identifiers or the contents of form fields, and we do not write your IP address to the log (it is used only to cap the number of reports). Reports go to our monitoring instance on our server in Finland and we delete them after 30 days. Before basing processing on Art. 6(1)(f) GDPR we carried out a legitimate-interest assessment (LIA) and concluded that our interest does not override your rights and freedoms. You can object at any time - see section 7.6. 3.4. Your consent Legal basis: Art. 6(1)(a) GDPR • Functional cookies (e.g., remembering A/B test variant) • Analytical cookies (Google Analytics) • Marketing cookies (Facebook Pixel, Google Ads, TikTok Pixel) • Sending hashed contact form data to the Meta Conversions API (only when you have granted marketing cookie consent) • Answering a submission from the contact form, the free audit, or the CapTable report. With the submission we record the date of your consent and the version of its wording, so we can demonstrate what you agreed to (Art. 7(1) GDPR) You may withdraw your consent at any time. Withdrawal does not affect the lawfulness of processing that occurred before withdrawal.

Cookies and Tracking Technologies

Our website uses cookies and similar technologies. We use four categories of cookies: • Necessary (always active) - required for the website to function • Functional - remember your preferences (e.g., dark/light theme, A/B test variant assignment) • Analytical - help us understand how you use the site (Google Analytics with IP anonymization) • Marketing - enable personalized advertising (Facebook Pixel, Google Ads, TikTok Pixel) Analytical and marketing cookies only load after your explicit consent. We implement Google Consent Mode v2, which means all consent signals are set to "denied" by default. In addition to cookies, we use a cookieless analytics tool (Umami) self-hosted on our server in Finland. Umami does not write cookies to your browser, does not create cross-site identifiers, and does not perform browser fingerprinting. The Umami script reads only a single value from your browser's localStorage: the key "umami.disabled" - an opt-out flag you can set with the "Cookieless analytics (Umami)" toggle in the cookie settings (the "Manage cookies" button in the footer) or manually. We write this key only when you disable Umami; it contains no identifier or other data - it is simply a flag of your preference. Server-side measurement relies on a short-lived anonymous hash of IP address, User-Agent and a daily salt; no persistent identifier is returned to your browser. Processing takes place on the basis of our legitimate interest (Art. 6(1)(f) GDPR). The mere read of the opt-out key from your terminal equipment is treated as strictly necessary to provide the service you explicitly requested (respecting your decision to disable Umami) - Art. 398(5)(2) of the Polish Electronic Communications Act of 12 July 2024 (formerly Art. 173(3)(2) of the Telecommunications Law, repealed in November 2024), implementing Art. 5(3) of the ePrivacy Directive. You can disable Umami at any time with the toggle in the cookie settings (effective immediately); you can also block the analytics.epko.tech domain in your browser or privacy extensions. You can change your preferences at any time using the "Manage cookies" button in the website footer.

For details, see our Cookie Policy.

Who We Share Your Data With

Your data may be processed by trusted third parties we work with. Here is the complete list: 5.1. Hosting and infrastructure • Dedicated server in Finland (EU) - hosts the website, the n8n instance, and the Umami analytics instance. Data on this layer never leaves the European Economic Area. • Self-hosted Umami analytics (software by Umami Software, Inc., USA) - runs under our own domain analytics.epko.tech on our server in Finland. Counts anonymous page views, conversion events (with no personal data), and Core Web Vitals metrics. Does not use cookies, does not build profiles, and does not transmit data to the software vendor. It operates independently of cookie consent - legal basis: Art. 6(1)(f) GDPR (legitimate interest, documented in our internal balancing test, LIA), with a visible opt-out in the cookie settings (see section 4). 5.2. Analytics and marketing (only with your consent) • Google LLC (Google Analytics 4, Google Ads) - with IP anonymization. Transfer to the USA based on the Data Privacy Framework (European Commission decision of 10 July 2023) and the EU Standard Contractual Clauses. • Meta Platforms Ireland Ltd (Facebook Pixel and Conversions API) - controller in the EU/EEA; Meta's infrastructure may involve transfer to the USA, safeguarded by the Data Privacy Framework and SCC. For Facebook Pixel and Conversions API we act as joint controllers with Meta under the Meta Business Tools Terms (Art. 26 GDPR). Essence of the arrangement: EPKO is responsible for the lawful basis of collecting the data (your marketing-cookie consent) and for informing you of the processing; Meta is responsible for the security of processing within its own systems and for fulfilling data subject rights regarding data already held on its platform (Meta data subject rights contact: https://www.facebook.com/help/contact/540977946302970). We use two parallel event transmission channels: - Facebook Pixel (browser): technical visit and click data - Conversions API (server-to-server): after a contact form submission we send hashed (SHA-256) data to Meta: email address, phone number, first and last name, along with IP address and session identifier. Hashed data is used exclusively for conversion deduplication and attribution; Meta does not have access to the original values. Both channels share a common event identifier, so each event is counted only once. • TikTok Technology Ltd (TikTok Pixel) - controller in Ireland (EU), global infrastructure. Transfer outside the EEA safeguarded by SCC. • LinkedIn Ireland Unlimited Company (LinkedIn Insight Tag) - data controller for EU users, based in Dublin. Script loaded from snap.licdn.com. LinkedIn is an independent controller of its own cookies (e.g., li_*, bcookie, lidc, UserMatchHistory); transfer to the USA is safeguarded by Standard Contractual Clauses. • Meta Platforms Ireland Ltd (forms in ads, Lead Ads) - a form in an ad on Facebook or Instagram runs on Meta's platform, which collects the data you enter under Meta's terms for forms in ads (Lead Ads Terms) and passes it to us. Data about how you use Facebook and Instagram is processed by Meta under its own privacy policy (https://www.facebook.com/privacy/policy). We receive the submitted request from Meta through its API, directly or through Zernio (below), and from then on we are responsible for that data (section 2.5). You fill in the form on your own initiative, so this part does not depend on your cookie consent. • Zernio Software SL (Palamós, Spain, EU) - processor: it retrieves submissions from forms in ads from our Meta account, stores them and passes them to us (name, email address, phone number, form answers, ad IDs). Zernio's database is in London (United Kingdom, covered by a European Commission adequacy decision), and its providers outside the EU operate under the Data Privacy Framework or Standard Contractual Clauses (list: https://zernio.com/subprocessors). 5.3. Business services • Supabase Inc. (incorporated in Delaware, USA) - database, authentication, storage of contact form messages, and the cookie consent register. Data is stored physically in the EU region (Frankfurt). Transfer outside the EEA is safeguarded by Standard Contractual Clauses (SCC) approved by the European Commission and by the Data Privacy Framework. • Sanity Inc. (USA / Norway) - headless CMS storing the content we publish on the site (blog articles, project descriptions, profiles of our team members). We do not store your data as a visitor in Sanity (it holds editorial content authored by our team, not data submitted by you). Transfer safeguarded by SCC and the Data Privacy Framework (for US operations). • Self-hosted n8n instance (software by n8n GmbH, Berlin, Germany) - automation platform running on our dedicated server in Finland (EU). After a contact form submission we forward a copy of the lead (full name, email, phone, company, subject, message content, source URL of the form, and the client IP address) to n8n for internal lead-handling automation (e.g., notifications, CRM integration, team tasks). The transmission is secured with an HMAC-SHA256 signature. Data does not leave the EEA and is not transferred to n8n GmbH as a processor; n8n GmbH is solely the software vendor. • Resend, Inc. (incorporated in Delaware, USA) - transactional email provider. We use Resend to send internal lead notifications (containing the data you submitted in the form) and replies to you from biuro@epko.tech. Transfer outside the EEA is safeguarded by Standard Contractual Clauses (SCC) approved by the European Commission. • Payment system providers (for invoicing, when you become our client) • Accounting firm (to the extent required by tax law; office in Poland) 5.4. Communication tools • The email providers mentioned above (Resend), plus the standard mail providers on both ends (yours and ours) as part of business correspondence. For entities outside the EU/EEA, we ensure an adequate level of data protection through: • European Commission adequacy decisions (e.g., the EU-U.S. Data Privacy Framework) • Standard Contractual Clauses (SCC) approved by the European Commission • Other legally permissible safeguards (Art. 46 GDPR) We never sell your data. We also do not share it with data brokers, third-party data marketplaces, or any other parties beyond those listed above.

At a glance

Who we trust with your data

Full list of processors that receive fragments of your data - with location and transfer safeguards.

  • Dedicated serverEEA

    Website, n8n and Umami hosting

    Finland (EU)

    Data never leaves the EEA

  • SupabaseOutside EEA

    Database, auth, consent register

    Frankfurt (EU) · US entity

    SCC + Data Privacy Framework

  • ResendOutside EEA

    Transactional email

    Delaware, USA

    European Commission SCC

  • TwilioOutside EEA

    SMS call notifications (when a number is provided)

    USA

    SCC + Data Privacy Framework

  • SanityOutside EEA

    Headless CMS (editorial content)

    USA / Norway

    SCC + Data Privacy Framework

  • n8n (self-hosted)Self-hosted

    Lead-handling automation

    Finland (EU)

    HMAC-SHA256, stays in the EEA

  • Umami (self-hosted)Self-hosted

    Cookieless analytics

    Finland (EU)

    No cookies, no persistent identifiers

  • Google (Analytics, Ads)Outside EEA

    Analytics and remarketing - only with consent

    USA

    Data Privacy Framework + SCC

  • Meta (Pixel, CAPI)Outside EEA

    Pixel and Conversions API - only with consent

    Ireland · USA

    SCC + Data Privacy Framework

  • ZernioOutside EEA

    Submissions from forms in Meta ads to our CRM

    Spain (EU) · database in London

    UK adequacy + DPF/SCC at subprocessors

  • LinkedIn (Insight Tag)Outside EEA

    LinkedIn conversion tag - only with consent

    Ireland · USA

    SCC + Data Privacy Framework

  • TikTokOutside EEA

    TikTok Pixel - only with consent

    Ireland, global infrastructure

    Standard Contractual Clauses

How Long We Keep Your Data

We do not store data longer than necessary. Here are the specific retention periods: • Message from the contact form, the free audit, or the CapTable report (contact_messages): 12 months after it was sent • The submission from these forms saved in our CRM (crm_leads), together with the UTM parameters and the address of the page it was sent from: for as long as we handle the matter, and after it is closed for up to 6 years from the last change to the submission. We keep a submission from a form in a Meta ad and a call booked through our calendar the same way • Contract and project data: duration of the contract + 6 years (statute of limitations for civil claims) • Accounting documents and invoices: 5 years from the end of the financial year (accounting regulations) • Email correspondence: duration of business relationship + 3 years • Cookie preferences (localStorage): 6 months from your last decision, after which we will ask for your consent again • Consent identifier (consent_id, localStorage): until you clear your browser storage or click "reset" in the cookie settings • Server-side consent register (consent_logs): 5 years on the basis of the accountability principle (Art. 5(2) and Art. 7(1) GDPR) - long enough to demonstrate that valid consent was obtained if it is ever challenged. We store a salted SHA-256 hash of the IP address instead of the IP itself. • UTM parameters (sessionStorage): until the browser tab is closed • A/B test variant (localStorage): for the duration of the test or until you withdraw functional cookie consent • Analytics data (Google Analytics): up to 26 months (with IP anonymization) • Anonymous Umami data (on our server in Finland): up to 24 months in aggregated form; contains no personal data that could identify you • Front-end failure reports (monitoring on our server in Finland): 30 days • Marketing data (Facebook Pixel, TikTok Pixel): up to 13 months After these periods, data is permanently deleted or effectively anonymized.

At a glance

How long we keep your data

Each data category has its own retention period. After that: permanent deletion or anonymization.

Form message
12 months
CRM submission, incl. UTM
case + up to 6 years
Submission from a form in a Meta ad
case + up to 6 years
Contract & project data
contract + 6 years
Invoices & accounting
5 years
Email correspondence
relationship + 3 years
Cookie preferences (localStorage)
6 months
Consent ID (localStorage)
until browser storage cleared
Server consent register (hashed IP)
5 years
UTM parameters (sessionStorage)
until tab closed
A/B test variant
duration of the test
Google Analytics
26 months
Umami (aggregated)
24 months
Front-end failure reports
30 days
Facebook / TikTok Pixel
13 months

Your Rights

Under the GDPR, you have a number of rights. We fulfill them without undue delay, within 30 days of receiving your request at the latest. 7.1. Right of access (Art. 15 GDPR) You can ask whether we process your data and request a copy of it. 7.2. Right to rectification (Art. 16 GDPR) If your data is inaccurate or incomplete, you have the right to correct it. 7.3. Right to erasure (Art. 17 GDPR) You can request the deletion of your data ("right to be forgotten"), unless we have a legal obligation to continue storing it. 7.4. Right to restriction of processing (Art. 18 GDPR) You can request restriction of data processing in certain situations. 7.5. Right to data portability (Art. 20 GDPR) You have the right to receive your data in a structured format (e.g., CSV, JSON) and transfer it to another controller. 7.6. Right to object (Art. 21 GDPR) You can object at any time to data processing based on legitimate interest (Art. 6(1)(f)). 7.7. Right to withdraw consent (Art. 7(3) GDPR) You can withdraw consent for cookies or other processing at any time. This does not affect the lawfulness of prior processing. 7.8. Right to lodge a complaint If you believe we process your data unlawfully, you have the right to lodge a complaint with: President of the Personal Data Protection Office (PUODO) ul. Stawki 2, 00-193 Warsaw, Poland Phone: +48 22 531 03 00 https://uodo.gov.pl To exercise any of the above rights, write to us at: biuro@epko.tech. We will respond as soon as possible.

At a glance

Your GDPR rights at a glance

Eight concrete rights. We fulfill them without undue delay, within 30 days at the latest.

  • 7.1Art. 15

    Right of access

    Ask whether we process your data and request a copy.

  • 7.2Art. 16

    Rectification

    Correct inaccurate or incomplete data.

  • 7.3Art. 17

    Erasure

    "Right to be forgotten" - unless we must retain by law.

  • 7.4Art. 18

    Restriction

    Pause processing in specific situations.

  • 7.5Art. 20

    Portability

    Receive your data in CSV / JSON and pass it to another controller.

  • 7.6Art. 21

    Object

    Object to processing based on legitimate interest.

  • 7.7Art. 7(3)

    Withdraw consent

    Withdraw at any time - no effect on prior processing.

  • 7.8Art. 77

    Lodge a complaint

    President of the PDPO, ul. Stawki 2, 00-193 Warsaw.

Automated Decision-Making and Profiling

We do not make decisions based solely on automated processing, including profiling, that produce legal effects or similarly significantly affect you (Art. 22 GDPR). The marketing and analytics tools we use (Google Analytics, Facebook Pixel, TikTok Pixel, Google Ads) may create behavioral profiles based on your activity on our site. This happens only after you have granted consent for the relevant cookie categories. These profiles are used to measure campaign effectiveness and tailor advertising; they are not used to make decisions that would have legal effects on you or would similarly significantly affect you within the meaning of Art. 22 GDPR.

Data Security

We take the security of your data seriously. We implement appropriate technical and organizational measures, including: • Data transmission encryption (SSL/TLS) • Dedicated server in Finland (EU) with controlled access • Regular software and dependency updates • Access control - personal data is processed only by authorized personnel • Encrypted backups • Security monitoring and event logging • Security headers (Content-Security-Policy, HSTS, X-Frame-Options) • IP anonymization in analytics tools If we become aware of a personal data breach likely to result in a risk to your rights and freedoms, we will notify the President of the Polish Personal Data Protection Office (UODO) without undue delay and, where feasible, not later than 72 hours after becoming aware of it (Art. 33 GDPR). If the breach is likely to result in a high risk to your rights and freedoms, we will also notify you without undue delay (Art. 34 GDPR).

Children's Data

Our website and services are not directed at individuals under the age of 16. We do not knowingly collect personal data from children. If you learn that a child has provided us with their data, please contact us and we will promptly delete it.

Whether You Have to Provide Your Data

Providing personal data is voluntary, but in some situations it is necessary for us to respond or to provide our services: • Contact form: full name, email address, and message content are required so that we can reply. Phone number and company name are optional. Without the required data we will not be able to contact you. • Service agreement: to enter into and perform a contract we need identification data (name or company name, tax ID, address) and contact data. Without this data we cannot conclude a contract or issue an invoice. • Analytical and marketing cookies: entirely optional. Lack of consent does not limit your access to the site and does not change its functionality. • Functional cookies (e.g., A/B test variant, theme): optional. Lack of consent means we will not remember your preferences between visits. Providing data for accounting purposes (invoicing) is required by law (the Polish Accounting Act, the VAT Act) and is mandatory once you become our client.

Sign in with Google in Our Apps

You can sign in to some of the apps we build and run with your Google account (the "Sign in with Google" button). This section explains what happens to your data when you do. It covers these apps: • Medova (medova.health, pro.medova.health) • HART (hart.bsagroup.pl) • Bezpieczny Obywatel (bezpiecznyobywatel.bsagroup.pl) The data controller for each of them is EPKO sp. z o.o. (details in section 1). Each app also has its own privacy policy that covers the rest of how it works. 12.1. What data we receive from Google We ask Google only for basic sign-in data (the openid, email and profile scopes): • your email address and whether Google has verified it • the first and last name on your Google account • the address of your Google profile picture • your Google account identifier, which lets us recognise you the next time you sign in We do not ask for access to Gmail, contacts, calendar, Google Drive or any other Google service. We do not store Google access tokens, so after you sign in we cannot read anything from your Google account or change anything in it. 12.2. What we use it for • To sign you in and recognise you on your next visit • To create and maintain your account in the app • Your email address: to send you account-related messages, such as confirmations, certificates and security notices Legal basis: Art. 6(1)(b) GDPR (providing the service you use after signing in). We do not display your Google profile picture in the apps. If you want a picture on your profile, you add it yourself. We do not use data from Google for advertising, we do not build marketing profiles from it, we do not sell it, and we do not pass it to analytics or advertising tools. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. 12.3. Where we store it and who can access it • Sign-in data is stored by the Supabase authentication service (Supabase Inc.), which we use as a data processor. The servers are in the EU: Stockholm (Sweden) for Medova, Frankfurt (Germany) for HART and Bezpieczny Obywatel. Transfer safeguards are described in section 5.3. • Your email address is also processed by Resend, Inc., which we use to send account-related messages (section 5.3). • Only authorised members of our team can access the data. We do not share this data with anyone else unless the law requires us to, for example on a court order. 12.4. How long we keep it For as long as your account exists. When you delete your account, the data we received from Google is deleted along with it. It may remain in our provider's backups for a short time, until they are overwritten. There is one exception for Medova: if your account is linked to medical records that the law requires us to keep, the app will not delete the account on its own. In that case, write to us and we will delete everything the law does not require us to keep. 12.5. How to delete your data or revoke access • In the app: in Medova, go to your account settings, in the data privacy section; in HART and Bezpieczny Obywatel, use the delete account button on your profile. Instructions for deleting an account without signing in are at bezpiecznyobywatel.bsagroup.pl/usuwanie-konta. • By email: write to biuro@epko.tech from the address you use to sign in to the app. We will delete the data without undue delay, within 30 days at the latest. • In Google: you can revoke the app's access to your Google account at any time at myaccount.google.com/permissions. Revoking access does not delete your account in the app. If you want to delete it, use one of the options above. Your other rights are described in section 7.

Changes to This Privacy Policy

We may update this Privacy Policy to reflect changes in legislation or our services. We will inform you of significant changes through: • A clear notice on the website • An information banner on your first visit after changes • An email message (if you are our client) The date of the last update is always visible at the top of this page. We encourage you to check the Privacy Policy regularly. Change history: • Version 2.2 (October 25, 2026) - new section 12 on data from Sign in with Google in Medova, HART and Bezpieczny Obywatel • Version 2.3 (November 3, 2026) - updated the UTM description in section 2.2: we save UTM parameters together with a submission from the contact form, the free audit, or the CapTable report, and added submission attribution to section 3.3 as a legitimate interest. The periods in section 6 and the retention table now describe the actual deletion (form message after 12 months, CRM submission for as long as the matter is handled and up to 6 years after it is closed), and we save the page address without its parameters. • Version 2.4 (November 18, 2026) - answering a submission from the contact form, the free audit, or the CapTable report is based on your consent (section 3.4, previously 3.1). With the submission we record the date of your consent and the version of its wording. New section 2.5 on submissions from forms in Meta ads (Facebook, Instagram), Meta and Zernio as recipients of the form data in section 5.2, and the retention period for such submissions in section 6. In section 2.2 we added that we also save UTM parameters when you book a call through our calendar. • Version 2.5 (November 19, 2026) - removed handling inquiries from section 3.3 as a legitimate interest: answering a submission from the contact form, the free audit, or the CapTable report is based on your consent (section 3.4). • Version 2.6 (November 19, 2026) - added detecting front-end failures in your browser to section 3.3 as a legitimate interest: when a script on the page breaks, your browser sends us an error report without user identifiers and without recording your IP address. Section 2.2 describes the scope of this data and section 6 the retention period (30 days).

Questions about your data?

Write to us. Requests to exercise GDPR rights, rectification, erasure or consent withdrawal are top priority.