Privacy policy

2.1 When you send a request

The grid check is free and needs no details about you. If you request a demo or an analysis, the form asks for:

• your name, your work email and your company
• your role
• a message, if you write one
• for an analysis, the figures you entered in the grid check and the result shown to you

We add to the email the language of the page you sent the form from (English or Polish). If you came through a campaign link, the campaign values in the address (utm_source, utm_medium, utm_campaign, utm_term, utm_content) are added too. Nothing else about your visit is added.

We send these details as one email to our team's mailbox, and one automatic confirmation to the address you gave, unless a daily limit is reached or the confirmation cannot be sent. The confirmation repeats only your name, your company and the kind of request. Its header shows our logo, which your email program may load from this website, like any page file (see Server logs). There is no database behind the form. We use them only to answer your request. You do not have to send a form. Without the details, we cannot answer you.

2.2 The free grid check

The figures you enter are sent to our server only to compute the estimate. The answer comes straight back to your screen.

The figures are not stored and not written to a log. The server writes one line for each request with the date and time, the method, the page path, the result and the time taken. That line has no figures, no internet address and no query. Those lines are kept on our server in rotating files of limited size, which are overwritten as new entries arrive.

2.3 Protection against abuse

The forms have a hidden field that a person leaves empty. A request that fills it is dropped. When a form loads, it gets a signed time stamp from our server. A form sent within 10 seconds of loading is refused, and you are asked to wait. Each time stamp works for one form only. The server also limits how many requests one internet address can make per minute, and counts how many forms one internet address sends in 24 hours (at most 10). For an IPv6 address, both limits count the network block it belongs to as one address. It keeps both counts in memory only, never on disk or in a log. It forgets the count of requests after a minute without requests, and the count of forms after 24 hours without forms. It forgets both sooner when the service restarts or when many newer addresses push them out.

The demo and analysis forms also use Google reCAPTCHA v3, which tells people from automated senders. It loads only on the pages with these forms, when you first use a form. It loads before any cookie choice, because the form cannot be protected without it. Nothing else from Google loads before you agree. Google receives your internet address, data from your browser and how you use the page. When you send the form, our server sends Google the token your browser received, with your internet address, and Google returns a score for the request to our server. If the check fails, or Google cannot be reached, the form is not sent and you are asked to try again or to write to us by email. Google may set or read its own cookies for this check. Google describes its handling in Google's privacy policy (opens in a new tab).

The automatic confirmation goes only to the address entered in the form. To limit how often the form can send mail to an address someone typed in, the server sends at most 3 confirmations to one email address (spellings of one mailbox, such as different capitals or a +tag, count together) in 24 hours. Past that, the request still reaches us. Only the confirmation is not sent. The server keeps this count, with the address it belongs to, in memory only, never on disk or in a log. It forgets it 24 hours after the last confirmation sent or tried for that address, and sooner when the service restarts or when many newer addresses push it out.

2.4 Measurement and advertising

Nothing is measured until you agree. Before that, all Google consent signals are set to denied and no Google script is loaded, apart from reCAPTCHA when you use a form (see Protection against abuse).

If you choose "Accept all", or allow analytics or advertising in the settings, we load Google Tag Manager. Through it we use Google Analytics 4 to count visits and Google Ads to see which adverts bring visitors. Google receives data from your browser, such as your internet address and the pages you view. If you reject, Google Tag Manager is not loaded.

With analytics allowed, we also send Google these events. Each one names the language of the page (English or Polish):

• a click on a "Book a demo" link (with the role of the card, or the film the link sits under, if any)
• the grid check started
• the grid check done, with whether you run a grid today and the queue-risk band of the result
• a demo or analysis form sent, with the role you chose
• a film opened in the viewer, with the film's name, and the film you came from when you choose "See the full story"
• a part of a film chosen in the viewer (problem, GridFit or result), with the film's name
• a click on the language switch, with the language you left and the one you chose

We never send your figures, your name or your email.

Google describes its handling in Google's privacy policy (opens in a new tab). You can change or withdraw your choice at any time with "Cookie settings" in the footer.

2.5 Campaign values

The campaign values in the address you arrived with (utm_* and the Google Ads click ids gclid, gbraid and wbraid) are held in the page's memory and added to the links between our home, grid check and demo pages so they are not lost. They stay in the page address, so, like any address, they can appear in your browser history. We do not write them to storage on your device. Only the five utm_* values are sent, and only with a form you submit. The click ids are never sent with a form.

2.6 Storage on your device

The site keeps two entries in your browser's local storage, described on the Cookie policy page: your cookie choice and your colour theme. It sets no cookies of its own. When you use a demo or analysis form, Google's reCAPTCHA script may add an entry of its own (see the same page).

2.7 Server logs

Our web server keeps no access log of the pages and files that your browser or email program requests from it. If an error happens on our side, the server's error log may record the request, including your internet address and the path. We use it to keep the service secure and to find faults.

These logs are kept on our server in rotating files of limited size, which are overwritten as new entries arrive. They may hold technical data, such as your internet address.