Privacy policy
In force since 1 September 2026. Covers the Keyup mobile app, the web console at admin.keyupgo.com and the tracking page at track.keyupgo.com.
This is a translation provided for convenience. The legally binding version of this policy is the Czech one; in case of any discrepancy, the Czech text prevails.
1. Who processes the data
The controller is Keyup s.r.o., Reg. No. 23933381, VAT No. CZ23933381, registered office at Na Folimance 2155/15, Vinohrady, 120 00 Prague 2, Czech Republic, entered in the Commercial Register kept by the Municipal Court in Prague (“we” or “Keyup”). Czech data box: 2vfwjuf. For data protection matters contact info@keyupgo.com.
We hold two different roles under data protection law, and it matters not to confuse them:
- We are the controller for user account data — that is, for the people who sign in to Keyup (technicians, dispatchers, company owners).
- We are the processor for job and end-customer data that a service company enters into Keyup. The controller of that data is the company, not us. If you want to exercise rights over data about your own job, contact the company that attended to you; we will assist them.
2. What data we process
| Data | Purpose | Legal basis |
|---|---|---|
| User e-mail, name, phone number | Signing in, identification within the team, password recovery. | Performance of a contract |
| Technician location (including in the background) | Working out the drive to a job, showing it on the dispatch map, estimating arrival for the customer. | Employer's legitimate interest in managing call-outs |
| Job address, phone number and notes | Handing the job to a technician, navigation, contacting the customer. | On the company's instructions (we are the processor) |
| Job financials (revenue, VAT, commission) | Settling the technician's work and the company's overviews. | On the company's instructions (we are the processor) |
| Device push token | Delivering notifications about a new or changed job. | Performance of a contract |
| Technical diagnostics (device model, OS version, app version, permission status) | Fixing bugs and verifying the technician runs a current version. | Legitimate interest in a working service |
| Error reports and app crashes | Finding and fixing bugs. | Legitimate interest in a working service |
What we don't collect: the app doesn't use the microphone or camera for recording, doesn't read contacts, doesn't track you in other apps or across the web, and passes nothing to advertising networks. We use no advertising identifiers and carry out no profiling with legal effects.
3. Location, including background location
Keyup is a field tool, so location sits at its core. We want to be specific, because this is sensitive data.
- What it's for. Working out the drive to a job, ordering jobs along a route, and letting the dispatcher see who is closest.
- When we read it. While the technician is signed in to the app and has granted location permission. We send location at most once a minute, and only if the technician has moved at least 100 metres.
- Why in the background too. Without background location the arrival estimate would stop updating the moment the technician locks their phone and drives — exactly when it's needed. That's why the app asks for the “Always” permission.
- What gets stored. Only ever the last known position, which is overwritten. We don't store a movement history and no route can be reconstructed from it afterwards.
- What the customer sees. Only the arrival estimate, and only until the technician arrives — after that the live location stops being shown to them.
- Who sees it. The dispatcher and management of their own company. Never another company — the data is separated at database level.
- How to switch it off. In your phone's settings for the Keyup app. The app keeps working, just without the drive-time calculation.
4. The tracking SMS to the customer
When a technician sets off to a job, the company can send the customer an SMS with a link for tracking the arrival. The link is single-use and expires when the job is completed, and after 12 hours at the latest. The customer is shown only the arrival estimate, not the technician's movement history. At most one SMS goes out per job, and only when the job has a phone number on it.
5. Who we pass data to
We don't sell data. We pass it only to providers without whom the service wouldn't run, and always under data processing agreements:
| Provider | Purpose | Where |
|---|---|---|
| Supabase | Database and authentication | EU (Ireland) |
| Expo | Delivering push notifications | USA (SCCs) |
| Sentry | Error and crash reporting | EU |
| Google Maps | Geocoding addresses and calculating drive times | EU / USA (SCCs) |
| SMS and phone system provider | Sending the tracking SMS, matching a call to a job | EU |
| Hostinger | Running the website | EU |
Outside the EU we transfer data only under the standard contractual clauses approved by the European Commission.
6. How long we keep data
- Account data — for as long as the account exists, and 12 months after.
- Jobs and their financials — for as long as the company, as controller, decides; accounting records follow the statutory period (usually 10 years).
- Technician location — only the last known position is kept, and every newer one overwrites it. No history is stored.
- Error reports — 90 days at most.
7. Your rights
Under the GDPR you have the right to access your data, to have it corrected, to have it erased, to restrict processing, to data portability, and to object to processing based on legitimate interest.
Write to us at info@keyupgo.com and we'll come back to you within one month at the latest. If the request concerns job data, we'll pass it to the company that controls it.
Closing an account. Keyup accounts are created and closed by your company's administrator in the web console — the app has no self-service sign-up. To close an account, ask your company's administrator, or write to us and we'll arrange it.
You also have the right to lodge a complaint with the Czech Data Protection Authority, or with the supervisory authority in your own country.
8. Security
Data is encrypted in transit and at rest. Access is enforced at database level — every user sees only their own company's data, and a technician only the jobs assigned to them. Credentials are kept in the operating system's secure storage, and passwords only as a one-way hash.
9. Children
Keyup is a work tool and is not intended for anyone under 16. We do not knowingly process their data.
10. Changes to this policy
We may amend this policy. We'll announce any material change in the app or by e-mail at least 14 days in advance. The date of the last change is always shown at the top.
Keyup s.r.o., Reg. No. 23933381, Na Folimance 2155/15, 120 00 Prague 2, Czech Republic · info@keyupgo.com · keyupgo.com