Documents
Privacy Policy
Version 1.18 · effective from 13 November 2026
This translation is provided for information only — only the Polish version is legally binding.
1. Data controller
The controller of the personal data of Customers (people who create an Account), people who send enquiries through the form on the website, people who place orders and visitors to the watchdog.com.pl website is SNAP2 Sp. z o.o., ul. Hoża 29, 00-521 Warszawa, entered in the register of entrepreneurs of the National Court Register kept by Sąd Rejonowy dla m.st. Warszawy w Warszawie, XII Wydział Gospodarczy Krajowego Rejestru Sądowego under KRS number 0001255063, NIP 7011323609, REGON 545301716, share capital 5000 PLN (the “Operator”, “we”).
For any matters concerning personal data, contact us: [email protected].
Capitalised terms (Customer, Account, Module, Premises, Premises User) have the meaning given to them in the Terms of Service.
2. Two roles: controller and processor
- Customer data — Account, login, enquiries, orders, correspondence: here we are the data controller.
- Data collected by the Module in the Premises — devices on the Premises Wi-Fi network (MAC and IP addresses, network names, manufacturer, times of presence), conditions in the Premises, Wi-Fi networks in the surroundings: the controller is the Customer (e.g. the landlord) who places the Module in the Premises and decides on the purposes of the monitoring. We process this data solely on the Customer’s behalf, as a processor (Article 28 GDPR, § 8 of the Terms of Service).
Tenants and guests should receive information about the monitoring from the Customer and exercise their GDPR rights primarily with the Customer. If a Premises User contacts us, we will forward the request to the relevant Customer and help them deal with it.
3. What data we process
| Category | Data | Source |
|---|---|---|
| Account | e-mail address, Account name, password (only as a scrypt hash — we do not know your password), date of acceptance of the Terms of Service and the Privacy Policy together with their versions, login dates, addresses of alarm recipients, phone numbers for SMS notifications (confirmed with a code sent by SMS) | Customer |
| Security | IP address and browser identifier at login and during the session, Dashboard event log (logins, settings changes, commands sent to Modules) | Customer’s browser |
| Enquiries | first name, e-mail, phone (optional), number of properties, what the enquiry is about (e.g. an apartment for rent, a house), message text, consent to be contacted with its date, website language, IP address | person sending the form |
| Orders and sale agreements | e-mail, full name or company name, phone (required for orders with payment — InPost sends the parcel notification to it; optional for reservations without payment), number of units, amount and delivery cost, code and address of the chosen InPost Paczkomat parcel locker, address (street, town, postcode — printed on the invoice), for company purchases the tax ID (NIP) and company name, comments, order number and status, date of acceptance of the Terms of Sale (for reservations — of consent to the pre-sale terms and to being contacted), website language (we send order e-mails in it), IP address and browser identifier when placing the order; once the order is paid (or the reservation accepted) we create a Watchdog account for the e-mail address you gave — the account name is the full name or company name from the order, and the account becomes active when you set a password using the link in the e-mail and accept the Terms; until then nobody can log in to it | person placing the order; company name and address — also the REGON register or the register of VAT taxpayers |
| Payments and parcels | payment status, PayU or Stripe payment identifier, payment method (e.g. BLIK, card), amount and time of payment (never the card number, the CVV code or online banking login details); InPost parcel number and status | PayU, Stripe, InPost |
| Form protection | IP address, the User-Agent header and other browser and connection characteristics needed to tell a human from a program (bot), and the result of that check — when the order, enquiry and add-on sign-up forms are sent | browser of the person filling in the form (Cloudflare Turnstile) |
| Data from Modules (entrusted by the Customer) | Module and connection status (Wi-Fi signal strength, memory, software version, IP address in the local network, name of the Premises Wi-Fi network), history of outages and restarts, Module event log, temperature and humidity, noise level from the noise sensor, if the Customer has connected and switched it on (only loudness indicators: how often and by how much sound exceeded the threshold set on the sensor — sound is not recorded or transmitted), devices on the Premises Wi-Fi network (MAC and IP addresses, names from DHCP/mDNS/NetBIOS, manufacturer based on the MAC address, times of presence on the network), scans of Wi-Fi networks in the surroundings (names and addresses of access points, channels, signal strength), backups of Module settings — the Wi-Fi password only in encrypted form | Module in the Premises |
| Supplier readings (when the Customer adds a supplier account) | login and password for the customer portal of an electricity or gas supplier (myORLEN, E.ON, TAURON) — the password and the portal session only in encrypted form; from the supplier’s portal: numbers and addresses of supply points, meter numbers, tariff, meter readings (date, value, type of reading); readings submitted to the supplier from the Module (if the Customer turns this on); requests for other suppliers | Customer, supplier’s portal |
| Notifications | content of the e-mails and text messages sent, recipients’ e-mail addresses and phone numbers, delivery status | Service |
| Statistics and advertising (only with consent) | identifiers from cookies (_ga, _fbp, _gcl_au), IP address (Google Analytics does not store it), type of device, operating system and browser, approximate location (country, city), pages visited and visit duration, traffic source (e.g. an ad, a search engine), events on the website (viewing the offer, clicking “Order” — adding to cart, starting an order, proceeding to payment with the chosen operator, sending and paying for an order — with its amount and number — or sending an enquiry, opening the demo, activity on the website: active browsing time, page scrolling, expanded questions, the meter model searched for, clicking an e-mail address or phone number) — without the data entered in forms (name, e-mail, phone) | visitor’s browser (Google Analytics, Google Ads, Meta Pixel) |
The Module does not record images or sound, does not measure internet speed and does not read the content transmitted over the Wi-Fi network. The noise sensor (off by default) only detects whether sound is louder than a threshold — it does not record sound, so its measurements cannot be used to reconstruct conversations or recognise voices.
4. Purposes and legal bases
- creating the Account and providing the Service (Dashboard, notifications, Module support) — Article 6(1)(b) GDPR (contract);
- fetching meter readings from the portals of electricity and gas suppliers for which the Customer has provided login details and, if the Customer turns this on, submitting the Module’s reading to the supplier and passing readings on to the Customer’s Home Assistant or SON — Article 6(1)(b) GDPR (contract, at the Customer’s request);
- security of the Website and prevention of abuse (limits on login attempts, event log) — Article 6(1)(f) GDPR (legitimate interest);
- answering an enquiry and presenting an offer — Article 6(1)(b) GDPR (steps taken before entering into a contract) and Article 6(1)(f) GDPR; consent to e-mail and telephone contact regarding the enquiry may be withdrawn at any time;
- accepting and fulfilling an order: concluding and performing the sale agreement (payment, delivery, return, complaint, Terms of Sale), as well as confirming the order and contacting you about it and — for a pre-sale reservation — notifying you of the start of sales — Article 6(1)(b) GDPR (steps taken at your request before entering into a contract and its performance); you can cancel a reservation before payment by replying to the confirmation e-mail;
- filling in the company name and address after you enter a tax ID (NIP) in the order (retrieving them from the REGON register kept by the President of Statistics Poland or from the register of VAT taxpayers kept by the Head of the National Revenue Administration) — Article 6(1)(b) GDPR (steps taken at your request before entering into a contract);
- protecting the order, enquiry and add-on sign-up forms against automated programs (bots) and spam (Cloudflare Turnstile) — Article 6(1)(f) GDPR (legitimate interest: security of the Website and prevention of abuse);
- compliance with legal obligations (e.g. handling complaints, issuing invoices, accounting) — Article 6(1)(c) GDPR;
- establishing, pursuing and defending claims — Article 6(1)(f) GDPR;
- website visit statistics (Google Analytics) and measuring the effectiveness of ads and showing ads to people who have visited the website (Meta Pixel; Google Ads — data from Google Analytics, only with consent to marketing cookies) — Article 6(1)(a) GDPR (consent given in the cookie banner; without consent these tools do not run); you can change or withdraw your consent at any time (the “Cookies” link in the website footer) without affecting the lawfulness of processing before its withdrawal;
- data from Modules — on behalf of and on the instructions of the Customer (the legal basis for the processing is provided by the Customer as the controller).
We do not make decisions based solely on automated processing, including profiling, that would produce legal effects concerning you. The automatic determination of the cause of an outage (e.g. “power cut”) is technical information for the Customer. With your consent to marketing cookies, Meta and Google may use information about your visit to tailor the ads shown to you (marketing profiling) — without legal effects concerning you.
5. How long we keep data
Default retention periods (data is deleted automatically once a day):
- presence of devices on the Premises network (scans and presence sessions): 90 days; devices inactive for more than 90 days are deleted together with their names;
- Wi-Fi network scans: 30 days; hourly Wi-Fi channel statistics: 365 days;
- Module telemetry (signal strength, memory): 90 days;
- temperature and humidity measurements: 90 days; hourly averages — for as long as the Module is used in the Service;
- noise level measurements (noise sensor): 90 days; hourly summaries — for as long as the Module is used in the Service;
- Module logs: 7 days; commands sent to the Module: 90 days;
- backups of Module settings: 60 days, except that the latest backup of each Module is kept for as long as the Module is used in the Service;
- readings of meters selected by the Customer: 5 years; meters detected in the surroundings that the Customer has not selected: 30 days from the last reception;
- supplier accounts (login, encrypted password and portal session) together with the downloaded readings and readings submitted to the supplier: until the Customer removes the supplier account in the Dashboard or deletes the Account; requests for other suppliers: 12 months;
- outage history of the Module: for as long as the Module is used in the Service (it documents the availability of the Premises); Module event log: 90 days;
- database backups: no longer than 4 weeks (daily and weekly backups), backups made before a Website update: 14 days;
- history of e-mails sent: 365 days; SMS log (with the phone number): 90 days; phone number not confirmed with a code: 7 days; login log (with the IP address): 180 days;
- login sessions: until logout, at most 30 days (7 days of inactivity);
- Account: until deleted by the Customer; unconfirmed Accounts: 7 days; activation links and password reset links are valid for 48 hours and 1 hour respectively;
- enquiries sent through the form: 12 months from the last status change, unless a contract is concluded;
- orders together with payment and parcel data: cancelled — 12 months from cancellation; others — for the time needed to fulfil and settle the order, and then for the period required by law (e.g. tax law) and until the limitation periods for claims expire;
- company name and address retrieved by tax ID (NIP): in the server cache for at most 24 hours (in the order — like the order data);
- Google Analytics (with consent): data about visits and events — 14 months;
_gacookies — 13 months from the last visit; - Meta Pixel (with consent): the
_fbpcookie — 90 days from the last visit; data transferred to Meta is kept by Meta under its own rules (section 6); - your choice in the cookie banner — 12 months, after which we will ask again;
- data needed to defend against claims or required by law — until the limitation periods or the periods specified by law expire.
Removing a Module from the Account immediately deletes the data about devices on the Premises network and the backups of settings containing Wi-Fi passwords. At the Customer’s request (e.g. when the tenant changes), we delete the data about devices on the Premises network before the retention period ends.
6. Recipients of data
- server infrastructure: the Control Centre runs on the Operator’s server in Poland;
- Cloudflare, Inc. — transmission and protection of network traffic to the Website and encryption of connections, as well as protection of the order, enquiry and add-on sign-up forms against automated programs (Cloudflare Turnstile: when telling humans from bots, Cloudflare is our processor, and it also uses the data as a separate controller to improve bot detection); as a result, data may be transferred outside the European Economic Area on the basis of a European Commission adequacy decision (EU–US Data Privacy Framework) or standard contractual clauses;
- PayU S.A., based in Poznań (ul. Grunwaldzka 186, 60-166 Poznań, Poland; KRS 0000274399, NIP 7792308495) — handling payments for orders: we pass on the e-mail address, full name or company name, phone number, order number, description and amount, and the IP address; you provide card details and other payment data directly to PayU, which is a separate controller with regard to payments (under its own privacy policy);
- Stripe Payments Europe, Limited, based in Dublin (1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland) — handling payments by card, Apple Pay and Google Pay when you choose this method in the order form (always for delivery abroad): we pass on the e-mail address, order number, description and amount; you provide card details and other payment data directly to Stripe, which is a separate controller with regard to payments (under its own privacy policy); data may be transferred to Stripe, Inc. in the USA (EU–US Data Privacy Framework, standard contractual clauses);
- InPost sp. z o.o., based in Krakow (ul. Pana Tadeusza 4, 30-727 Krakow, Poland; KRS 0000543759, NIP 6793108059) — delivery of the parcel to the Paczkomat parcel locker: full name or company name, phone number, e-mail address, Paczkomat code and order number; when you search for a Paczkomat, we pass the postcode or town you entered to InPost from our server (without your IP address);
- for delivery outside Poland — InPost S.A. as part of the InPost International service, also through delivery partners in the destination country (e.g. Mondial Relay, Austrian Post / Express One, Packeta): name, e-mail, phone, pick-up point and order number — to deliver the parcel (Article 6(1)(b) GDPR);
- Statistics Poland (REGON register) and the Polish Ministry of Finance (register of VAT taxpayers) — when you enter a tax ID (NIP) in the order, we send that number from our server to retrieve the company name and address;
- the e-mail service provider — sending notifications and messages from the Website;
- Vercom S.A., based in Poznań (ul. Wierzbięcice 1B, 61-569 Poznań, Poland; KRS 0000535618, NIP 7811765125, REGON 300061423), operator of the SerwerSMS.pl service (SMS gateway, processor) — sending SMS notifications and verification codes: the recipient’s phone number and the text of the message;
- Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) — Google Analytics, only with consent to statistics cookies; Google processes this data as our processor; with consent to marketing cookies, data from Google Analytics (events on the website, cookie identifiers, clicks on Google ads) is also sent to Google Ads — to measure the effectiveness of our ads and to show ads to people who have visited the website; to that extent Google acts as a separate controller (Google Ads terms); data may be transferred to Google LLC in the USA (EU–US Data Privacy Framework, standard contractual clauses); Google’s privacy policy;
- Meta Platforms Ireland Limited (Merrion Road, Dublin 4, D04 X2K5, Ireland) — Meta Pixel, only with consent to marketing cookies; we are jointly responsible with Meta for collecting data on our website and transmitting it to Meta (joint controllership, Article 26 GDPR — arrangement), while further processing (e.g. ad matching, linking with a Facebook or Instagram account) is carried out by Meta as a separate controller; data may be transferred to Meta Platforms, Inc. in the USA (EU–US Data Privacy Framework, standard contractual clauses); Meta’s privacy policy;
- electricity and gas suppliers indicated by the Customer (myORLEN, E.ON, TAURON) — we log in to their portals with the Customer’s details to fetch readings and, if the Customer turns this on, pass them the meter reading from the Module;
- entities providing us with IT, accounting or legal services — to the extent necessary and on the basis of agreements;
- public authorities — only where required by law.
We do not sell data. For advertising we use only data from the Meta Pixel and from Google Analytics (in Google Ads), only with your consent to marketing cookies — never data from the Account, forms or Modules.
7. Your rights
You have the right to: access your data, have it rectified or erased, restrict its processing, data portability, object to processing based on legitimate interest, and withdraw your consent at any time (without affecting the lawfulness of processing before its withdrawal).
You can exercise some of these rights yourself in the Dashboard: delete the Account, change notification recipients, delete the data about devices on the Premises network (“Remove from account”). You can change or withdraw your consent to statistics and marketing cookies in the cookie settings. For anything else, write to us: [email protected]. We will reply within one month. Regarding data collected by the Meta Pixel, you can also contact Meta.
You also have the right to lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warsaw, Poland, uodo.gov.pl).
Providing data when creating an Account is voluntary but necessary to use the Service; providing data in the enquiry form is voluntary, but without an e-mail address we cannot reply; providing data in an order is voluntary, but without an e-mail address and a full name (or company name) we cannot accept the order, without a phone number and a chosen Paczkomat we cannot deliver the parcel, and without an address we cannot issue the invoice.
8. Cookies and browser storage
We divide cookies into three types. Essential cookies are always on. Statistics and marketing cookies — only if you agree to them in the banner; before consent we do not load any statistics or advertising scripts.
Essential (no consent required — we inform you about them in the banner):
__Host-wd_sess— session after logging in (until logout, at most 30 days);__Host-wd_pre— protection of forms (login, registration, enquiry, order) against CSRF attacks (24 hours);__Host-wd_trust— trusted device: a browser you have already logged in from is not blocked during mass attempts to guess your password (12 months);wd_consent— your choice in the cookie banner (12 months);wd_cookies— confirmation of the cookie notice in the Dashboard, so the banner does not appear on every visit (12 months);wd_lang— remembers the website language chosen with the language switcher (12 months).
Statistics — Google Analytics (only with consent):
_ga,_ga_…— distinguishing visitors and visits for statistics (13 months).
Marketing — Meta Pixel (only with consent):
_fbp— recognition of the browser by Meta for measuring and targeting ads (90 days);_fbc— remembers a click on an ad on Facebook or Instagram (90 days, only after arriving from an ad).
If you have an open Facebook or Instagram session in the same browser, Meta may also read its own cookies from the facebook.com domain — under Meta’s privacy policy.
Marketing — Google Ads (only with consent; set by the Google Analytics script):
_gcl_au— measuring the effectiveness of Google ads (90 days);_gcl_aw— remembers a click on a Google ad (90 days, only after arriving from an ad).
Essential third-party services (no consent required — only on the pages that need them): on pages with the order, enquiry and add-on sign-up forms we load Cloudflare Turnstile, which checks that the form is being sent by a human. Payment takes place on the PayU or Stripe website. These services may store their own technical data in your browser — under Cloudflare’s, PayU’s and Stripe’s rules.
You can change or withdraw your consent at any time in the cookie settings (the “Cookies” link in the website footer). When consent is withdrawn, we delete the Google Analytics and Meta cookies from our domain.
In the browser’s storage (localStorage) we save only the chosen light or dark theme.
9. Security
- encrypted connections (TLS) between the browser and the Website and between the Module and the Control Centre;
- Account passwords stored only as a hash (scrypt); session tokens, e-mail link tokens and Module tokens stored as hashes; login details entered on the Module setup page sent to the Control Centre only in encrypted form;
- Wi-Fi passwords from settings backups stored only in encrypted form and never written to logs;
- passwords for suppliers’ portals and the sessions of those portals stored only in encrypted form, never shown in the Dashboard or written to logs; logging in to a portal that requires a browser takes place in an isolated environment of the Control Center that does not store anything;
- you provide payment card and online banking login details directly to the payment operator (PayU or Stripe) — they never reach us; we accept the payment status only from a signed notification from the operator or from its response to our query;
- data isolation between Accounts — every request in the Dashboard is limited to the data of the logged-in Customer’s Account;
- limits on login attempts and forms, protection against CSRF and automated programs (Cloudflare Turnstile), event log;
- regular database backups.
10. Information for tenants and guests
If a Watchdog Module operates in the apartment you use, its owner or manager (the Customer) may see:
- whether the apartment has power and internet, and when there were interruptions;
- the temperature and humidity in the apartment;
- whether it is loud in the apartment (how often sound exceeds the set threshold) — if the Customer has connected and switched on the noise sensor; the Customer may also receive notifications when it is loud for a longer time, e.g. during night-time quiet hours;
- the number and list of devices connected to the apartment’s Wi-Fi network (MAC and IP addresses, device names, manufacturer) and the times of their presence on the network — unless the Customer has switched this feature off.
The Module does not record images or sound (the noise sensor only measures how often it is loud) and cannot see the content transmitted over the network. The presence of a device on the network does not mean the presence of a person. The controller of this data is the landlord (the Customer) — it is the landlord who should inform you about the monitoring, and you should address any requests concerning your data to them. You can also write to us — we will forward the matter to the relevant Customer.
11. Changes to the Privacy Policy
We may change the Privacy Policy, e.g. due to changes in the law or in the features of the Service. Each version has a number and an effective date stated at the beginning of the document; we will inform Customers of material changes by e-mail.