Updated September 29, 2026
You are responsible for the data you put into the Service: those are your clients and your records. We process it on your instructions and for the purposes described here.
For your own account data we are responsible: Myroslav Podryhulia, NIF Y9837838Q, calle La Laja, 7, Adeje, 38678, Santa Cruz de Tenerife, España. Contact: info@gethourgrid.com.
Account: name, email address, password hash (the password itself cannot be recovered from it), role in the workspace.
Working data: bookings, clients and their contacts, amounts, payments, tasks, shifts, enquiries.
Technical: sign-in times, the IP address a request came from, error reports.
What you upload to Inbox: photos, documents, voice recordings, text.
Messages from connected enquiry channels: if you have connected a channel, we process what guests write to your bot, and with bot replies enabled we also parse those messages to draft a booking request.
Where you came from: if you opened our site through a link with advertising campaign labels (utm parameters in the address), we store those labels and the page you started from together with your workspace. They are taken from the link only — without cookies or third-party scripts — and are not passed to advertising networks.
Visits to our public pages: we count, per day, which page was opened from outside the site and where the visit came from — the advertising labels in the link, or the domain of the site or app that linked to us. Only these daily totals are stored, for 13 months: no cookies, no IP address, no device identifier. Anything in the link labels that looks like an email address or a phone number is removed. People signed in to Hourgrid are not counted.
The main database and files are on Supabase, Ireland region (European Union).
Backups are on Scaleway, Paris region (France, European Union). A copy is taken once a day, encrypted with our key before it is sent, and kept for 30 days.
Data leaves the EU only in the cases listed below.
Supabase — database and file storage, EU.
Vercel — application hosting, EU (Frankfurt); keeps technical request logs.
Brevo — email delivery: confirmations, reminders and, if the venue has enabled the after-visit email, thank-you messages to your guests; service messages to you. It receives the recipient's address and the contents of the message.
Stripe — subscription payments. If you have enabled guest payments, Stripe also processes those on your own account, and when you connect that account it asks you for identity verification details. Payment details go to Stripe directly; we neither see nor store them.
Anthropic (United States) — recognition of photos and documents sent to Inbox. If Groq is unavailable, text goes to Anthropic as well.
Along with what you send to Inbox, the model receives the venue's reference lists: room and expense-category names, the price list of extras, and up to sixty client names. Without them it could not recognise an existing client or room in a note and would suggest creating them again. Client phone numbers and addresses are not sent.
Groq (United States) — recognition of text and transcription of speech sent to Inbox. It also answers guests if you have enabled bot replies in an enquiry channel: it processes your guests' messages and extracts the requested time and phone number.
Under both providers' terms, what is sent through their API is not used to train models.
Telegram — only if you have connected a bot as an enquiry source: we then receive the messages sent to your bot.
Sentry — collection of application crash reports (Germany region, EU). It receives the error description and the place in the code where it happened. Client data is not sent there: collection of IP addresses, cookies, headers, request bodies, database query values and variable values is switched off item by item.
Zoho — email on our own domain: your enquiries to us and our replies pass through it.
Scaleway — backup storage, France (EU). The copies are encrypted; Scaleway is not given the decryption key.
GitHub (USA) — the environment where the copy is taken: the data passes through it unencrypted, is encrypted there, and only then goes to storage.
We do not sell data and do not share it for advertising.
To provide the Service and perform the contract — the software working, payment, support.
To comply with the law — accounting and tax duties.
Our legitimate interest — security, abuse prevention, keeping the Service running, and understanding which of our advertising brings customers.
As long as your workspace exists. After it is closed, working data and uploaded files are deleted within 30 days.
For up to 31 days more, deleted data remains in backups: that is how long the oldest copy lives — 30 days of retention plus one day to erase the superseded version for good — and it disappears together with that copy.
Payment records are kept for as long as tax law requires.
You may obtain a copy of your data, correct it, delete it, restrict or object to processing, and lodge a complaint with a data protection authority.
A separate right is portability: to receive your data in a machine-readable form and pass it to another provider. Export is available in the Account section in JSON and CSV.
Deletion is in the same place. We answer written requests within 30 days.
We use only those without which signing in does not work: they hold your session and chosen language. There are no advertising or tracking cookies, which is why we do not ask for consent to them.
We will announce material changes to this policy by email at least 30 days in advance.