Privacy and cookies

Privacy and cookies policy

A short, practical note about what data may appear when you contact Web Rescue and which technical mechanisms are active on this website.

Controller and contact

The controller of data provided in correspondence is Web Rescue, Tax ID (NIP): 5391400805. Contact for website and data matters: kontakt@webrescue.pl.

What data we may receive

If you send an email or use the contact form, we may receive your name, email address, website URL, problem description, indicative budget and technical context needed to answer the enquiry.

The form sends data to Web Rescue and may store a technical copy of the enquiry for contact handling and lead loss prevention.

The technical copy may also include operational lead metadata: enquiry ID, form type, source URL, landing page, referrer and UTM parameters if they were present in the URL. This does not mean that Google Analytics, ads or external trackers are active.

Technical copies of enquiries are stored for up to 12 months, unless the contact becomes a client relationship or requires a longer correspondence history.

Cookies and localStorage

At this stage the website does not load Google Analytics, Google Ads, remarketing or external trackers. The cookie notice stores only the information that the notice has been accepted. This is saved in browser localStorage.

If analytics, advertising tools, CRM tools or webhooks are added later, this policy and the consent mechanism should be updated before those integrations go live.

Purpose of contact

Data from your message is used to answer the enquiry, assess the audit or repair sprint scope and continue correspondence about the website you submitted.

Your rights

You can ask for access, correction, deletion, restriction of processing or object to further contact. The simplest path is an email to kontakt@webrescue.pl.

Integrations that require a decision

Google Analytics 4, Google Ads, advertising pixels, Formspree and Make/Zapier webhooks are not currently active on the website. A first-party form endpoint is active for enquiry handling. If they are added, the proper consent setup should be implemented, including Consent Mode v2 where required.

Last updated: April 25, 2026.