Privacy Policy
Effective from: [Dátum účinnosti]
Symblu gives service companies (our Clients) an inquiry Calculator for their website and a dashboard for the inquiries (Leads) it collects. This policy explains what personal data Symblu processes, why, where it is kept and for how long, and what rights you have.
1. Who we are
[Obchodné meno][Sídlo]
Company ID (IČO): [IČO]
Registered in: [Zápis v obchodnom registri]
E-mail: [Kontaktný e-mail]
Symblu acts in two roles:
- Controller for the account data of the people who sign in to the dashboard (the Client's Team members and Symblu's own staff), and for the data needed to run and secure the service.
- Processor for the Leads that Customers send through a Client's Calculator. The Client is the controller of that data, and Symblu processes it only on the Client's instructions, under a data processing agreement.
If you sent an inquiry through a company's website, that company is responsible for your data. Please contact it first. If you write to us, we pass your request on to the company and help it answer.
2. Data we process as controller
- Account data: your e-mail address, display name, password (stored only as a hash by our sign-in service), and which Client you belong to and in which role.
- Activity: what you did on a Lead, such as changing its status or priority or scheduling a Visit, recorded with your name in the Lead's history; and each CSV export you make (who, when, how many Leads and with which filters), in an export log the Client's owners can see.
- Google Calendar connection: only if an owner connects Google Calendar. See Google user data below.
- Technical data: sign-in session cookies; error reports with personal data removed before they leave our server or your browser; and rate-limit counters, which store keyed one-way hashes, never the values themselves: of the sender's IP address for 10 minutes, to limit inquiries per Calculator, and of the Customer's e-mail address for 24 hours, to send at most 3 confirmation e-mails to one address a day.
We use this data:
- to provide the service to the Client you work for (performance of our contract with the Client, and our legitimate interest in providing it, Art. 6(1)(b) and (f) GDPR);
- to keep the service secure and prevent abuse (legitimate interest, Art. 6(1)(f) GDPR);
- to meet our legal obligations, such as accounting (Art. 6(1)(c) GDPR).
We do not sell personal data and do not use it for advertising.
3. Leads we process for our Clients
A Lead holds what the Customer entered in the Calculator: contact details (name, phone, e-mail), location (region, district and municipality), the selected services and answers, the language, where the inquiry came from, and when the Customer gave consent and to which wording. It also holds the Client's work on it: status, priority, an internal note, a Visit and its history.
On the Client's instructions, Symblu:
- stores Leads and shows them to the Client's Team members;
- sends the e-mails the Client has set up, such as the Lead notification to its team and the confirmation, Visit and reminder e-mails to the Customer;
- writes Visits to the Client's Google Calendar, if the Client connects it.
Symblu staff with admin access can see Leads only to run and support the service. The Client decides the legal basis for its Leads and informs its Customers.
4. Where the data is kept
The app, its database and its background jobs run on Railway in its EU West region, in Amsterdam, the Netherlands. The database is reachable only over Railway's private network, never from the internet.
Backups stay on Railway in two forms:
- snapshots of the database volume, made by Railway;
- a daily database dump, encrypted by us before upload, in a storage bucket in Amsterdam.
Once a month, the newest encrypted dump is also copied to restricted company storage outside Railway. The key that opens the dumps is never stored with them.
5. Sub-processors
| Provider | What for | Where |
|---|---|---|
| Railway | Hosting the app, database, background jobs and backups | EU West (Amsterdam) |
| Resend | Sending e-mails | EU region |
| Sentry | Error reports, with personal data removed first | EU data region |
| Calendar events, only when a Client connects Google Calendar | The Client's own Google account |
Some of these companies are based in the United States, and Railway says its own operational processing happens primarily there. Where personal data leaves the European Economic Area, we rely on the European Commission's standard contractual clauses or an adequacy decision.
6. Google user data
This applies only when a Client's owner connects Google Calendar to a Calculator on the Integrations page, so that Visits appear in the Client's calendar. Symblu requests these scopes, and uses each one only as described:
openidIdentifies the connected Google account by its account ID, so Symblu can tell whether another Calculator uses the same account.emailShows which Google account is connected, by its e-mail address, on the Integrations page.https://www.googleapis.com/auth/calendar.eventsCreates, updates and deletes the events for the Visits Symblu schedules, in the calendar the owner picks. Symblu reads back only those events, to check that one still exists. It never reads, changes or deletes any other event.https://www.googleapis.com/auth/calendar.calendarlist.readonlyLists the calendars the account can add events to, only so the owner can pick one. Symblu keeps only the chosen calendar's ID and name.
Symblu reads no other data from your Google account: no other events, contacts, e-mail or files.
What Symblu stores
- the OAuth access and refresh tokens, and the granted scopes;
- the connected account's ID and e-mail address;
- the chosen calendar's ID and name, and when it connected;
- for the connection, the last sync failure (when, and a reason code) until a later sync succeeds, and when sync found the access revoked at Google;
- for each Visit, the calendar and the ID of the event Symblu created there, and a version counter.
What Symblu writes to your calendar
One event per Visit, with its start and end, the title “Obhliadka: <Customer's name or phone>, <municipality>”, and a description with the Customer's phone, the selected services and a link to the Lead in the dashboard. Events have no attendees, so Google sends nobody an invitation. Edits you make to these events in Google are overwritten on the next change in Symblu.
How it is used and shared
Google user data is used only to provide this calendar sync to the Client who turned it on. It is not sold, not used for advertising, not used to train AI or machine-learning models, and not transferred to anyone except the hosting providers above, which store it for us. The Integrations page shows the connected account's e-mail address and calendar name to the Client's Team and to Symblu staff with admin access. Beyond that, no person at Symblu reads Google user data, unless you ask us to (for example for support), it is needed for security, or the law requires it.
How it is protected
The tokens are stored encrypted at rest with AES-256-GCM, in Symblu's database on Railway's servers in the EU (Amsterdam). Only Symblu's server can read and decrypt them, and the encryption key is kept apart from the database. No Team member can see them, owners included. They travel only over encrypted connections to Google, and are deleted on disconnect.
Disconnecting and deletion
- Disconnecting on the Integrations page deletes the tokens at once, and revokes Symblu's access at Google, unless another Calculator is still connected with the same Google account (Google revokes an account's access all at once). Events already in the calendar stay there.
- You can also remove Symblu's access at any time in your Google Account at myaccount.google.com/permissions. Sync then stops.
- Deleting a Lead deletes its event from the calendar while the connection works.
- Copies in our backups expire within about 3 months (see Retention).
Symblu's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
7. Retention
- Leads are kept until the Client deletes them or its Calculator, or until the contract with the Client ends.
- Accounts: removal from a team ends your access at once, and your name stays in that Client's Lead history. We delete the account on request or when the Client's contract ends.
- Google Calendar data is kept until the connection is disconnected.
- Rate-limit counters expire within 24 hours.
- Error reports are kept for Sentry's retention period.
- Backups: deleted data stays in backups for up to about 3 months (30 daily and 3 monthly copies) until the last backup holding it expires. Backups are restored only after a loss, and deletions made since then are repeated.
8. Security
- All traffic to the app is encrypted (HTTPS).
- Access rules in the database let each Client's Team members see only that Client's data.
- Secrets such as Google tokens are encrypted at rest (AES-256-GCM) and readable only by Symblu's server.
- Database dumps are encrypted before upload, and the key is kept apart from them.
- Our logs and error reports do not contain Customer data.
9. Cookies
The dashboard uses only cookies it needs: sign-in session cookies, and a cookie that lasts 10 minutes while an owner connects Google Calendar. The public Calculator sets no cookies. Symblu uses no analytics or advertising cookies.
10. Your rights
Under the GDPR you can ask for access to your data, its correction or deletion, restriction of processing, and a portable copy, and you can object to processing based on legitimate interest. Where processing is based on consent, you can withdraw it at any time. Write to [Kontaktný e-mail]. We answer within one month.
You can also complain to the Office for Personal Data Protection of the Slovak Republic (Úrad na ochranu osobných údajov Slovenskej republiky), Hraničná 12, 820 07 Bratislava 27, dataprotection.gov.sk, or to the authority where you live.
11. Changes
We update this policy when the service changes, and change the date at the top. We tell Clients' owners about material changes by e-mail before they take effect.