Security and GDPR in Rezu Office
One page: who is responsible for your employees' data, who processes it for us and where, how long we keep it and how to have it deleted. Everything comes from the Rezu Office terms and the privacy policy, and under each section we say where to check it. The terms exist in Polish only; the facts below are a plain-English summary of them.
As of 19 November 2026. Rezu Office terms, version 2026-11-18.
Who is responsible for what
- The company is the controller of the data of the people it adds to Rezu Office (employees, contractors, regular guests) and gives them the information the GDPR requires.
- Rezu is the processor of that data (“Office data”) and acts only on the company's documented instructions: the terms and the settings its admins choose in the panel.
- Rezu does not use Office data for its own purposes: it does not feed any parking index or demand signal, marketing, profiling or model training.
- Rezu is the controller of the company account and billing contacts, of Rezu accounts (sign-in, push notifications) and of billing with the company. The privacy policy describes this.
Rezu Office terms (Polish), part 10 items 1–4. The full processing agreement is on its own page, linked below.
What data we process for the company
Name, work e-mail, team and role, vehicle plate, bookings, draw entries, queue entries, fixed spaces, preferences (e.g. fixed arrival days), answers to the arrival question and when they were given, gate events, data sent to the company's systems through webhooks and the API, days off, settings, and the log of admin actions.
Arrival data is used to allocate spaces. It is not used to record working time or to check attendance at work. The panel shows the “I'm here” time only for the day of arrival, with no history and no export.
Rezu Office terms (Polish), part 10 item 4; privacy policy, paragraph on arrival data (Rezu Office).
Who else processes data, and where
The company gives a general authorisation for further processors. On the day the terms took effect they are:
| Processor | For what | Region |
|---|---|---|
| Neon Inc. | database | EU, Frankfurt |
| Vercel Inc. | hosting of the application and server | — |
| Resend Inc. | sending e-mails | — |
| 650 Industries Inc. (Expo), Apple and Google notification services | push notifications | — |
| Upstash Inc. | job scheduling | — |
| Functional Software Inc. (Sentry) | error monitoring | EU |
| PostHog Inc. | analytics of the browser app | EU |
| home.pl S.A. | the kontakt@getrezu.pl mailbox | Poland |
The regions of the other processors are not declared in the terms.
Transfers outside the European Economic Area rely on Chapter V of the GDPR, in particular an EU adequacy decision or standard contractual clauses. Rezu imposes data-protection duties on these processors that match the processing agreement and answers to the company for their actions.
We tell the company's admins by e-mail at least 14 days before adding or replacing a processor. The company may raise a reasoned objection; if we cannot agree, it may terminate the contract with immediate effect and we refund the unused part of the period it paid for.
Rezu Office is paid by invoice and bank transfer; payment cards are not accepted. The privacy policy lists all providers, including those behind the public part of the app.
Rezu Office terms (Polish), part 10 items 5–6 and part 5; privacy policy, §3 “Recipients of Data and Transfers Outside the EEA”.
How we protect data
- Encryption in transit: the app, the panel and the API talk to the server over HTTPS.
- Access control: the company's data is visible to its admins and to authorised Rezu staff bound by confidentiality. Authorised people see their own data, and other people's only when colleagues choose to share their plans. Billing data can be changed only by the company's Owner.
- Separation: each company's data is kept separate from every other company's.
- Gate secrets: the access key to the gate controller (e.g. Shelly) is stored in the database encrypted with AES-256-GCM.
- Breaches: we report a personal-data breach affecting Office data to the company without undue delay and within 48 hours of confirming it, by e-mail to the company's admins.
- Audit: once every 12 months, and also after a breach or at a supervisory authority's request, the company may check the processing: first by written questions and, if the answers are not enough, by an audit with at least 14 days' notice.
Rezu holds no information-security certificate today and does not claim one. Instead we describe the measures above and give an audit right in the processing agreement.
Rezu Office terms (Polish), parts 1 and 5 (roles and billing data), part 10 item 4 (b)–(c) and item 7. The encryption of the gate-controller key comes from Rezu's implementation, not from a commitment in the terms.
How long we keep data, and how to delete it
| Data | How long | Where it is written |
|---|---|---|
| Gate entry events (only for companies with a connected gate) | the plate is deleted after 90 days; entries opened from the app lose the link to the person, booking and space after 30 days; date, time, gate and decision stay | Rezu Office API documentation; privacy policy |
| Arrival answers (“I'm here”, “Not coming”, “Later”) | 30 days from the booking date | Privacy policy |
| Company data after the contract ends | 30 days to export as CSV, then deletion from production systems; from backups as they rotate, no later than a further 30 days | Terms, part 13 items 7–8 |
| IP addresses in security logs | up to 14 days | Privacy policy |
| Error reports (Sentry) | up to 90 days from the error | Privacy policy |
The company's admins can download an export of Office data as CSV (people, spaces, bookings) while the contract runs and for 30 days after it ends. On the company's request we confirm the deletion by e-mail.
We may keep data that we must or may keep by law (e.g. accounting records, defence of claims), as the controller of that data.
Data-subject rights (GDPR Articles 12–22): a request sent to Rezu is passed to the company without undue delay and we do not answer it on the merits without the company's instruction. We help the company to fulfil it where we can. Each person can delete their own Rezu account in the app.
Rezu Office terms (Polish), part 10 item 4 (d), (g) and part 13 items 7–8; privacy policy; API documentation.
Questions from IT or legal
Write to kontakt@getrezu.pl or call. I answer on working days. The operator is Karolina Tomaszyk, NIP (tax ID) 6653018221, REGON 381357920.