Privacy policy
Last updated 22 October 2026
rheoshift.com is published by RHEOSHIFT Sp. z o.o. This policy explains what happens to your personal data when you visit the site or contact us through it: what we collect, why, on what legal basis, how long we keep it, who receives it, and what rights you have under the GDPR - Regulation (EU) 2016/679, known in Poland as RODO.
Controller
The controller of your personal data is RHEOSHIFT Sp. z o.o., Orchówek, ul. Brzozowa 11, 22-200 Włodawa, Poland. E-mail: [email protected]. The company's full registry data is on the legal notice page.
We have not appointed a data protection officer; the law does not require one for a company of our size and kind of work. In any matter concerning your data, write to the e-mail address above.
What we process, why and on what basis
We process only what each situation below needs. For each one we say which data it involves, what we use it for and which provision of the GDPR allows it - and, where information is stored on your device, which provision of the Polish Electronic Communications Law (ustawa z dnia 12 lipca 2024 r. - Prawo komunikacji elektronicznej, PKE). Cookies are described in full in the cookie policy.
- Visiting the site
- Every request to rheoshift.com passes through Cloudflare, the content delivery network in front of our server and the site's only public entry point, and reaches our server, which writes one line to its access log. This happens for every page you open; no account, form or consent is involved.
- Data
- Your IP address (as passed on to us by Cloudflare), the date and time, the address of the page requested, the response status, the page you came from (referrer) and your browser's identification string (User-Agent). Cloudflare additionally sees the request headers and any cookies in transit, as any network in front of a server does.
- Purpose
- Keeping the site secure and working: detecting attacks and abuse, diagnosing errors, checking that pages load.
- Legal basis
- Art. 6(1)(f) GDPR - our legitimate interest in the security of the site and of the systems behind it (recital 49 GDPR).
- Request limits
- To keep the forms from being abused, our server also counts requests from one IP address in its working memory. It accepts at most a few an hour, separately for the contact form and for booking a call. When a call is booked it also counts the invitations sent to one e-mail address, at most a few a day. The counters are not saved and disappear when the server restarts.
- Writing to us
- You can write to us through the contact form or directly to [email protected]. A form message is delivered to us as an e-mail, into the company's Microsoft 365 mailbox; nothing is stored in a database on the website.
- Data
- Your name, company, e-mail address and the content of your message - all four fields of the form are required. If you write by e-mail: whatever your message and signature contain. If you reached us from a tagged link - for example our LinkedIn post or advert - the message also carries that link's parameters (utm), the page you landed on and the site the visit came from; none of it is stored on your device or passed to LinkedIn - it only tells us which post or campaign produced the inquiry.
- Purpose
- Answering your inquiry and, if it leads to work, taking the steps that come before a contract: scoping, an offer, agreeing terms.
- Legal basis
- Art. 6(1)(f) GDPR - our legitimate interest in handling business correspondence; most people who write to us do so on behalf of a company they work for. Where you are yourself the prospective party (a sole trader or a private person), Art. 6(1)(b) GDPR - steps taken at your request before entering into a contract. There is no consent tick-box on the form: we do not need your consent to answer you.
- Booking a call
- The booking calendar is part of this site. You stay on rheoshift.com, and nothing is loaded from Microsoft's servers into your browser.
- Data
- Your name, company, e-mail address and the meeting topic - those are required - and the time slot you chose. The phone number is optional.
- What happens to it
- Our server asks Microsoft 365 which slots are free; that question carries none of your data. Once you pick a slot, our server passes the details above to Microsoft 365. A Teams meeting is created in our calendar and you become an attendee of it. That is why the invitation with the link reaches you from Microsoft 365. The booking is not written to any database - this site has none. It exists as an entry in our calendar.
- Purpose
- Holding the call you booked and preparing for it.
- Legal basis
- Art. 6(1)(b) GDPR - steps taken at your request before a contract - and, where you book on behalf of your employer, Art. 6(1)(f) GDPR, our legitimate interest in handling business contacts.
- Good to know
- No cookie is set in your browser for the booking. The connection to Microsoft is made by our server, not by your browser, so your IP address is not passed on with it. Microsoft Ireland Operations Limited processes the data for us under the Microsoft Products and Services Data Protection Addendum, with the data held in the EU.
- Site statistics
- We count visits with Plausible, running on our own server.
- Data
- the page you opened, where you came from, the country derived from your IP address, your device type, browser and operating system. The tool does not store your IP address; in place of an identifier it records, with every page view, the one-way daily hash described below. The request itself reaches our server like any other and leaves a trace in the server logs, which are deleted after 14 days; the retention section describes them.
- Nothing on your device
- the script sets no cookie and writes nothing to your browser. The one thing it checks is a “plausible_ignore” entry in your browser’s local storage. Only you store it - with the “Don’t count my visits” button - to switch counting off. Until then there is nothing there to read. Returning visits are told apart by a one-way hash of your IP address, your browser and a random value replaced once a day, the old one being deleted. After that the hash can neither be recomputed nor linked to a later visit.
- Purpose
- knowing which pages are read and where readers arrive from, so that we develop the ones people actually read.
- Legal basis
- Art. 6(1)(f) GDPR - our legitimate interest. No consent is required: with nothing stored on your device and nothing read back from it, Art. 399 PKE does not apply.
- Recipients
- no analytics vendor. The instance is ours, on our own server in Microsoft Azure’s Poland region; the backups stay there too. Requests to it pass through Cloudflare like all traffic to the site. Both are described under “Recipients” and “Transfers outside the EEA”.
- Objection
- you can object to this processing (Art. 21 GDPR) by e-mail to [email protected]. The only identifier stored with a page view is the daily hash, and once that day’s random value is deleted it can no longer be recomputed. So we cannot link a row to a named person (Art. 11 and Art. 12(2) GDPR), and therefore cannot find or delete that person’s rows. What does stop the counting is the “Don’t count my visits” button at the top of this page: it stores the “plausible_ignore” entry in your browser’s local storage. Blocking the script’s address, for example with a script blocker, has the same effect.
- Claims
- If a dispute arises from anything above - a contract, an inquiry, a request concerning your data - we may keep and use the data relevant to it for as long as claims can be established, pursued or defended.
- Data
- The correspondence, contract documents and records that concern the matter.
- Purpose
- Establishing, pursuing or defending legal claims.
- Legal basis
- Art. 6(1)(f) GDPR - our legitimate interest in protecting the company's legal position.
- Invoicing and accounting
- If work follows, we issue invoices and keep the accounts.
- Purpose
- Meeting our accounting and tax obligations.
- Legal basis
- Art. 6(1)(c) GDPR - a legal obligation under Art. 74(2) of the Polish Accounting Act (ustawa o rachunkowości) and Art. 86 § 1 of the Tax Ordinance (Ordynacja podatkowa).
Cookies
How the site uses cookies and similar storage is described in full in the cookie policy. In summary: the site sets the cookie rs_locale (“en” or “pl”, 1 year) only when you use the EN/PL language switch, and stores your light-or-dark choice under the key theme in your browser's localStorage only when you use the theme switch, and keeps one sessionStorage entry, rs-curtain, that remembers the welcome logo animation has already played in your tab. Cloudflare, the service every request to the site passes through, sets one cookie of its own, __cf_bm, for 30 minutes, to tell browsers from bots. None of them contains an identifier or is used to track you; the theme and the animation flag never leave your browser at all. rs_locale travels with your requests like any cookie, so it passes through Cloudflare - see “Transfers outside the EEA” below. All of them are necessary to provide what you asked for and need no consent (Art. 399(3) PKE).
Our fonts are served from our own server, so viewing the site sends no request to any external font service.
Recipients
We do not sell personal data. We share it only with companies that process it on our behalf and on our instructions, with the public authorities the law obliges us to, and - where a section above says so - with a joint controller. The recipients are:
- Microsoft Ireland Operations Limited (One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland) - hosting of the site on Microsoft Azure, and the Microsoft 365 mailbox the contact form and our correspondence go into.
- Cloudflare, Inc. (101 Townsend St, San Francisco, CA 94107, USA) - the network our site is served through: it passes every request on to our server and handles the encryption between your browser and Cloudflare.
- Our accounting office keeps the books and settles our invoices, under a data processing agreement (Art. 28 GDPR). It works on accounting software installed locally, and the data stays on the office's own disk - no cloud service, no further processor behind it. It goes nowhere except the national e-invoicing system (KSeF), which tax law requires (Art. 6(1)(c) GDPR); the tax authorities are separate controllers there, not processors. Nothing leaves the European Economic Area.
- IT providers, to the extent they process data on our instructions, also under a processing agreement. Legal advisers act as controllers in their own right, within their own professional duties and under professional secrecy.
- Microsoft also processes the details you enter when you book a call, as our processor: they go into our Microsoft 365 calendar, where the Teams meeting is created.
Public authorities - courts, the police, tax or supervisory authorities - receive data only where the law obliges us to hand it over.
Transfers outside the EEA
Some of these companies are based in the United States or have their parent company there. Cloudflare, Inc. sees every request to the site by the very nature of a proxy; Microsoft Corporation is the parent and a sub-processor of Microsoft Ireland Operations Limited.
Transfers to the USA rest on the EU-US Data Privacy Framework - Commission Implementing Decision (EU) 2023/1795 of 10 July 2023 - for organizations certified under it. Cloudflare, Inc. and Microsoft Corporation state that they are certified under the Framework; you can check the current status of each on dataprivacyframework.gov. As a fallback, should the Framework ever lapse, our contracts with them contain the European Commission's Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914). You can obtain a copy of these safeguards by writing to [email protected].
How long we keep data
- Server logs
- 14 days. A new log file starts every day and only the last fourteen are kept; the oldest is deleted automatically.
- Inquiries
- 12 months from our last exchange, if no contract follows - long enough to resume the matter if you contact us again.
- Contracts
- For the duration of the contract, then until claims from it are time-barred - 3 years for claims connected with running a business and 6 years for the rest (Art. 118 of the Polish Civil Code, Kodeks cywilny), a period that ends on 31 December unless it is shorter than two years - and, for invoiced work, the 5 years from the end of the tax year that accounting and tax law require of us (Art. 6(1)(c) GDPR - a legal obligation, which we cannot waive even if you ask us to delete the invoice).
- Business contact data
- Kept like the rest of our business correspondence: 12 months from our last exchange, or, where a contract follows, for the contract's duration and until claims from it are time-barred. We delete details that are out of date, and we delete them at once if you object and we have no overriding ground to keep them.
- Language choice
- The rs_locale cookie: 1 year from when it is set, on your device.
- Theme
- The theme entry in your browser's storage: until you clear it. It never leaves your device.
- Visit statistics
- records of individual page views - without the IP address and without an identifier for you, with the daily hash - kept indefinitely. The random value used for the hash is deleted after 24 hours; from then on the hash can neither be recomputed nor linked to a later visit.
- Booked calls
- Kept as part of our correspondence with you, on the same terms as an inquiry or, if work follows, a contract.
- Claims
- Until the limitation period for the claim in question has run out, or the dispute has ended.
Your rights
Under the GDPR you have the right to:
- Access
- Learn whether we process your data and, if so, receive a copy of it together with the information listed in Art. 15 GDPR.
- Rectification
- Have inaccurate data corrected and incomplete data completed (Art. 16 GDPR).
- Erasure
- Have your data deleted where there is no longer a reason to keep it (Art. 17 GDPR).
- Restriction
- Have processing limited to mere storage while, for example, a dispute about accuracy is being resolved (Art. 18 GDPR).
- Portability
- Receive the data you gave us in a common, machine-readable format - CSV or XLSX, for example - where the processing rests on your consent or a contract (Art. 20 GDPR).
- Objection
- Object to processing that rests on our legitimate interest, for reasons arising from your particular situation (Art. 21 GDPR) - see the note below.
- Withdrawal of consent
- Where processing rests on your consent, you can withdraw it at any time. Withdrawal does not affect what was lawfully done before it (Art. 7(3) GDPR).
- Complaint
- Lodge a complaint with a supervisory authority. In Poland this is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, PUODO) in Warsaw: uodo.gov.pl. You may also complain to the authority of the EU country where you live, where you work, or where the alleged infringement took place.
Several of the purposes above rest on our legitimate interest - each one says so in its “Legal basis” row. We point that out separately because you may object to any of them at any time, for reasons arising from your particular situation. We then stop, unless we can show compelling legitimate grounds that override your interests, rights and freedoms, or the data is needed to establish, pursue or defend legal claims.
To exercise any of these rights, write to [email protected] or by post to RHEOSHIFT Sp. z o.o., Orchówek, ul. Brzozowa 11, 22-200 Włodawa, Poland. We answer within one month (Art. 12(3) GDPR); if a request is unusually complex we may extend this by a further two months, and we tell you within the first month if so. Where we cannot otherwise be sure a request is yours, we may ask you to confirm your identity.
Is providing data obligatory?
Giving us your data is voluntary - no law obliges you to, and you can read the whole site without telling us anything; the server logs are a by-product of your browser requesting pages, not something you fill in. Some data is nevertheless necessary if you want something from us. To write to us, all four fields of the form are required: we need to know who you are, which company the matter concerns, where to reply, and what it is about. Without them we cannot answer, and without the data needed to prepare and sign a contract we cannot enter into one with you. There is no other consequence - we do not refuse anything else for want of data.
Booking a call requires your name, your company, an e-mail address and the meeting topic, so that we can hold the call and prepare for it; the phone number is optional.
Automated decisions
We make no decisions about you by automated means that would have legal or similarly significant effects on you (Art. 22 GDPR). There is no scoring, no automated acceptance or refusal, and no terms set by an algorithm.
Data we did not get from you
In business we sometimes hold contact details of people who did not give them to us themselves: a colleague of yours names you as the right person to contact, a client's contract lists you as its contact, or we find your professional details in a public source such as your LinkedIn profile or your company's website. In such cases we hold your name, role, employer and business contact details (Art. 14 GDPR).
We use them only for the business the contact concerns, on the basis of our legitimate interest in maintaining business relationships (Art. 6(1)(f) GDPR), and we tell you where we got them at the latest when we first contact you, and in any case within one month of obtaining them (Art. 14(3) GDPR). Everything else in this policy - recipients, retention, your rights, including the right to object - applies to this data too.
Our LinkedIn page
We run a company page at linkedin.com/company/rheoshift. When you visit or follow it, LinkedIn processes your data under its own privacy policy; we see your profile only as any LinkedIn member would.
LinkedIn also produces statistics about the page's visitors - “Page Insights”: aggregated counts and professional demographics. For these statistics, we and LinkedIn Ireland Unlimited Company are joint controllers under LinkedIn's Page Insights Joint Controller Addendum, which places most obligations, including answering requests about the underlying data, on LinkedIn. You can still address a request to us - Art. 26(3) GDPR - at [email protected], and we will pass on whatever we cannot handle ourselves. The Page Insights figures themselves are aggregated - we never receive data about an individual from them. Separately, as any page admin, we can see who follows the page and who reacts to or comments on our posts, exactly as LinkedIn shows it to every member.
Security
The site is served over HTTPS only; every connection is encrypted, both between your browser and Cloudflare and between Cloudflare and our server. The server runs in a professional Microsoft Azure data center in the European Union. Access to the server and the mailbox is limited to the team members who need it for their work. We keep as little data as possible and delete it on the schedule set out above.
No system is perfectly secure, and we do not claim that ours is. If we ever learn of a breach that puts your rights at risk, we will inform you and the supervisory authority as the GDPR requires (Art. 33-34 GDPR).
Changes
We may update this policy when the site, the law or the companies we work with change. It describes only what the site actually does: a section about a feature - site statistics, LinkedIn measurement, booking a call - is present only while that feature is switched on, and appears or disappears with it. The date at the top of the page shows the version you are reading.
Contact
Questions about this policy or about your data: [email protected], or by post to RHEOSHIFT Sp. z o.o., Orchówek, ul. Brzozowa 11, 22-200 Włodawa, Poland.