Companion
Privacy
Draft, not yet legal advice. This text describes what the software actually does today, verified against the running code. It has not yet been reviewed by a lawyer for your specific legal position, and the operator's own identity and country of establishment are still being confirmed. Before this page goes live, both gaps must be closed.
This notice covers the Companion for Drivers application, its public website, and its Telegram bot. It is written to be read: every statement here corresponds to something in the running system.
1. Who is responsible for your data
Companion for Drivers is an independent product operated by an individual developer. The exact legal identity, business form, and country of establishment have not yet been finalised and must be filled in here before publication.
Until that is settled, questions about your data can be raised through the contact details at the end of this page and are answered by a person.
2. What we collect
Your account
A username, a role, an account status, the date the account was created, and a bcrypt hash of your password if you have one. If you signed in through Telegram, your Telegram numeric ID, chat ID, and Telegram handle are also stored, because that is how your sign-in code reaches you and how your account is matched to your application.
Your application
If you applied to the beta, the answers you gave, the language you chose, and the outcome of the review. If your answers were translated for the reviewer, the translation is stored alongside the original.
How you use the app
Which screen you opened, when, and how long you stayed. This is used to understand which features matter and to find faults. It is capped at the 1,000 most recent events and is only visible to the operator.
Sign-in records
The time, the IP address, and the browser string of each sign-in, kept for the last 50 sign-ins, so that a new device can be recognised and an unfamiliar one can be investigated.
What you send us directly
Feedback messages, and any notification permission you grant for push messages. Push subscriptions are stored only for as long as you keep them enabled.
3. Data inventory
Every category of personal data the system stores, what it is used for, and how long it is kept. This table is derived from the running code, not from a template.
| Data | Purpose | Kept for | Visible to |
|---|---|---|---|
| Username, password hash, role, status, creation date | Signing in and controlling access | Until you delete your account | Operator |
| Telegram ID, chat ID, handle | Delivering your sign-in code, matching your application | Until you delete your account | Operator, Telegram |
| Application answers and their translation | Deciding who joins the beta | Until you delete your account | Operator |
| Screen and feature events | Finding faults, understanding which features are used | Last 1,000 events | Operator |
| Sign-in time, IP address, browser string | Recognising a new device, investigating a stolen session | Last 50 sign-ins | Operator |
| Feedback you send | Answering you and fixing what you report | Last 1,000 messages | Operator |
| Push subscription | Sending you the alerts you asked for | Until you switch it off or delete your account | Operator, browser push service |
| Coordinates you send for a lookup | Answering that one request | Not stored | Nobody, after the response |
| Operational log of operator actions | Accountability for who changed what | Last 500 entries | Operator |
Two further files exist and are deliberately not personal: the recorded surge history for the city, and the recorded weather. They describe Wrocław, not you.
4. Why we are allowed to use your data
Under the EU General Data Protection Regulation, each use needs a basis. The bases relied on here are:
- Performing our contract with you. Signing you in, showing you the app, and sending you your daily summary are the service you asked for.
- Our legitimate interest in keeping the service secure and working. This covers sign-in records, fault reports, and the operational log. It is a real interest, it does not override your rights, and you can object.
- Your consent. Push notifications and optional application answers are only used because you chose to provide them. You can withdraw this at any time.
- Steps taken before entering a contract. Your beta application is processed so we can decide whether to offer you the service.
5. Who else sees your data
We do not sell your data and we do not share it for advertising. These services receive data because the product cannot work without them.
| Service | What it receives | Why |
|---|---|---|
| Telegram | Telegram ID, chat ID, handle, and the content of messages you send the bot | Your sign-in codes, applications, and daily summaries travel through Telegram |
| Anthropic | Your application answers, for translation. City event searches, with no personal data | Translating applications so they can be reviewed; finding public events |
| OpenStreetMap Nominatim | Place names you search for, and coordinates you ask to be reversed | Turning a typed place into a point on the map |
| CARTO and Stadia Maps | Tile coordinates your browser requests | Drawing the basemap |
| Open-Meteo | Fixed Wrocław coordinates | Weather and rainfall, which affect demand |
| Polish rail, and flight data providers | Station and airport identifiers, no personal data | Arrival boards for the airport and main station |
| Google Drive | Generated video files, no personal data | Backing up the daily summary videos |
| Our hosting provider | Everything above, as it sits on the server | Running the service |
Where a service is outside the European Economic Area, the transfer relies on the European Commission's standard contractual clauses. The specific countries must be listed here once the provider list is finalised.
6. Your location
The app has no background location feature and keeps no history of where you have been.
When you look up weather, reverse-geocode an address, or price a route between two points, the coordinates involved are used to answer that single request and then discarded. They are not written to any file, and they are not associated with your account afterwards.
The surge map shows the city, not you. The number of other drivers visible near a point is city data collected by a server-side process that never involves your device.
7. Artificial intelligence
Two features use Claude, made by Anthropic.
Translating applications. If you apply in Polish or Ukrainian, your answer text is sent for translation. Only the answer text is sent: your Telegram identity, your handle, and any location stay on our server and are not included in the request.
Finding events. A scheduled job searches for public concerts and matches in Wrocław. This request contains no personal data at all.
No AI model decides where you should drive, writes your work plan, or shows a number to you that has not first been checked against recorded data. If you turn on a planning feature later, this notice will say exactly what is sent, and that is a change that needs your consent.
8. Cookies and analytics
There are no advertising cookies, and no third-party analytics service. Google Analytics, Plausible, and similar tools are not present in this application.
One cookie is set, and it is strictly necessary:
-
cfd_sessionkeeps you signed in. It is HttpOnly, so no script on your device can read it, and SameSite=Strict, so it is never sent from another site.
Because this is the only cookie and it is necessary for the service to work, no cookie banner is shown. That is the reason for its absence, not an oversight.
The website sets no cookies at all. It loads one font from Google Fonts, which means your browser contacts Google when you open the page; no identifier is stored by us from that.
9. How long we keep your data
Your account and application are kept until you ask us to delete them. Everything else is capped so it cannot grow without limit:
- Screen and feature events: the most recent 1,000.
- Sign-in records: the most recent 50.
- Feedback: the most recent 1,000 messages.
- Operator action log: the most recent 500 entries.
10. How it is protected
- Passwords are stored as bcrypt hashes, never as readable text.
- Sessions are held in an HttpOnly cookie, not in browser storage.
- State-changing requests require a matching origin, so another site cannot submit forms as you.
- A strict content security policy limits which scripts, styles, and connections the page may load.
- Each completed day of city data is hashed and sealed, so silent later edits are detectable.
- Access to the server is limited to the operator, and the database is encrypted in nightly backups.
No system is perfectly secure. If a breach affects your data, we will tell you and the relevant supervisory authority without undue delay.
11. Your rights
Where the GDPR applies, you have the right to:
- Access what we hold about you, and get a copy.
- Correct anything inaccurate.
- Delete your account and its data.
- Restrict or object to processing you have not consented to.
- Port your data in a readable format.
- Withdraw consent for anything you agreed to, such as push notifications.
- Complain to your country's data protection authority.
Self-service is not built yet. Export and deletion from inside the app are on the roadmap. Until they exist, these requests are handled by a person through the contact details below, and are answered within 30 days.
12. Deleting your account
Ask us and your account is deleted along with your application, screen events, sign-in records, feedback, and push subscription.
Where a figure must still appear in an aggregate count, your name is replaced with an irreversible anonymous identifier rather than being removed, because deleting it would corrupt that count for everyone else.
Some records must be kept for a short period after deletion, for example the operator action log where your username appears, so that the deletion itself remains auditable. These entries are anonymised at deletion.
13. Children
This service is for adults who work as drivers. We do not knowingly collect data from anyone under 18. If you believe a minor has an account, contact us and it will be removed.
14. Changes to this notice
When this notice changes materially, the change is dated at the top of this page and announced in the app before it takes effect. Continuing to use the service after a change means you accept it. If a change affects a use of your data that rests on consent, we will ask again rather than assume.
15. Contact
Data requests, corrections, and deletions: message us on Telegram.
A postal address for formal correspondence must be added here once the operator's registered address is confirmed.