Privacy policy

1. Who is responsible for your data

The controller of your personal data is Multipolar Transport Kft. (registered office: 1151 Budapest, Kert köz 14., Hungary; company registration number: 01-09-394001; tax number: 27543430-2-42). You can reach us at hello@orbfill.com or by post at the address above.

Our company is not required to appoint a data protection officer under Article 37 of the GDPR. We process personal data lawfully, fairly and transparently, only for the purposes described here, limited to what is necessary, kept accurate, kept no longer than needed and protected by appropriate security.

2. What we process

Location data deserves care: activity routes can show where you live, work and spend your time. OrbFill keeps them private unless you decide otherwise (section 10).

3. Why we process it and on what legal basis

We do not sell personal data. We do not use it for advertising or to profile you, and we make no decisions about you by automated means that have legal or similarly significant effects.

If OrbFill is transferred to another company, for example in a merger or sale, your data may pass to that company, which must keep to this policy; we tell you beforehand. Data obtained from Strava passes only as far as Strava's API agreement allows, and is otherwise deleted.

4. Data from Strava

Connecting Strava is optional. If you connect it, you ask Strava to let OrbFill read your activities, including those only you can see and the parts of routes inside your privacy zones (Strava's activity:read_all permission). OrbFill writes to your Strava account only for the description line, and only while it is on. When you connect Strava, OrbFill also asks Strava for permission to edit your activities (activity:write). If you allow it on Strava's screen, the line is on from then; if you refuse it there, OrbFill connects without it and adds no line. You can turn the line on or off in Settings at any time. OrbFill uses the permission only to add one line with your coverage and new-road numbers to the description of activities you record after the line was turned on, right under your own text and above other apps' text, and to add it once more if another app's update removes it within ten minutes; it never changes anything else in the description.

• What we keep: OrbFill does not keep the GPS data it reads from Strava. The detailed GPS streams are deleted as soon as the activity is processed, at the latest within seven days, and the simplified route line after seven days. What stays are the results: the activity's type, date and distance, which road sections you covered, and the numbers OrbFill calculated (new roads, percentages, achievements).
• Who sees it: only you. Data obtained from Strava, and anything derived from it, never appears on your public profile, on share images, or to any other user.
• What we never do with it: sell it, use it for advertising, use it for analytics about our users or to improve our product, or give it to artificial-intelligence tools or to anyone other than the providers who run OrbFill for us (section 7).
• If the same activity also reaches OrbFill as a file you upload, from Ride with GPS or from your phone's health records, OrbFill keeps that copy instead and keeps only the Strava activity's ID with it, so that the description line can still be added on Strava.
• When you delete an activity on Strava, we remove it and everything derived from it from OrbFill within 48 hours.
• When you disconnect Strava in OrbFill's Settings, revoke OrbFill's access in your Strava settings (https://www.strava.com/settings/apps) or delete your Strava account, we delete all data obtained from Strava and derived from it, at the latest within 30 days. Activities you uploaded yourself stay.
• If you ask us, we confirm in writing that the deletion is complete.

Strava and OrbFill are separate controllers. Strava processes your data under its own privacy policy (https://www.strava.com/legal/privacy); please send requests about data held by Strava to Strava.

Strava may monitor and collect usage data about how OrbFill uses the Strava API, and may use that data for any business purpose, including improving the Strava API and the Strava platform, providing developer or user support, and making sure OrbFill complies with Strava's API agreement.

5. Data from Ride with GPS

Connecting Ride with GPS is optional. If you connect it, OrbFill reads the trips in your Ride with GPS account, including private ones, as GPS files (FIT or GPX), to find the roads you covered. It reads only your own trips, not routes or other people's trips you saved, and it never writes to your Ride with GPS account.

• What we keep: we handle a trip file like a file you upload (section 9): it is kept until the trip is processed, at most 90 days; the results stay as for your other activities.
• Who sees it: only you, unless you turn on a public profile when public profiles become available (section 10).
• If the same activity is also on Strava, OrbFill keeps the Ride with GPS copy and keeps only the Strava activity's ID with it, so that the description line (section 4) can still be added on Strava. That ID is deleted with your other Strava data.
• When you delete a trip on Ride with GPS, OrbFill removes it at its next sync, normally within minutes and at the latest within a day.
• When you disconnect Ride with GPS in OrbFill's Settings, we revoke OrbFill's access at Ride with GPS and delete every activity that came from it, with its coverage and achievements. If you revoke access on Ride with GPS instead, the same happens at the next sync. Activities you uploaded yourself stay.

Ride with GPS and OrbFill are separate controllers. Ride with GPS processes your data under its own privacy policy (https://ridewithgps.com/privacy).

6. Data from Apple Health and Health Connect

Reading your workouts is optional and only possible in the OrbFill app. You turn it on in the app, during setup or in Settings, and Apple Health or Health Connect then asks you which data OrbFill may read.

• What OrbFill reads: only workouts with a route, as described in section 2. The first time, up to one year back (on Android this uses Health Connect's permission to read past data); after that, workouts recorded since the last import. The app reads them while it is open, not in the background. OrbFill never writes anything to Apple Health or Health Connect.
• What we do with it: the same as with a file you upload. We match the route to roads, keep the results (the roads covered, the new road length and your progress) and a simplified route line, and delete the detailed points once the workout is processed (section 9).
• Who sees it: only you, unless you turn on a public profile when public profiles become available (section 10).
• What we never do with it: use it for advertising or marketing, sell it, share it with data brokers, use it to decide on credit, insurance or employment, or give it to anyone other than the providers who run OrbFill for us (section 7).
• Legal basis: a workout comes from your phone's health records and can say something about your health, so we treat it as health data and ask for your explicit consent (Article 9(2)(a) GDPR) when you turn the source on.
• Withdrawing consent: turn the source off in the app's Settings, or remove OrbFill's access on iPhone in Settings → Health → Data Access & Devices → OrbFill, or on Android in Health Connect → App permissions → OrbFill. OrbFill then reads nothing more. To delete the workouts already read, delete them in OrbFill or delete your account.
• If the same workout also reaches OrbFill from Strava, Ride with GPS or an upload, we keep it once.

7. Where your data is stored and who helps us

OrbFill's service, activity processing and road coverage database run with DigitalOcean in Frankfurt, Germany. Uploaded files are held in private storage at Supabase in Frankfurt. These providers process personal data on our behalf, under data processing terms:

Some services receive data directly, as independent controllers under their own terms: Strava, when you connect it; OpenFreeMap, which your browser asks for map images (it sees your IP address and the map area you view); and the OpenStreetMap Overpass service, to which our server sends the outline of an area when it loads that area's roads for the first time, without any account data. Map road files stored with Cloudflare contain OpenStreetMap data only, no personal data.

8. Transfers outside the European Economic Area

Some providers above are based in the United States. Where their processing involves a transfer outside the European Economic Area, it relies on the EU–US Data Privacy Framework where the provider is certified under it, or on the European Commission's Standard Contractual Clauses.

9. How long we keep data

10. Your public profile

Your account is private. Public profiles are switched off while OrbFill is being tested. When we switch them on, a public profile will be off until you turn it on in Settings; anyone with its address (orbfill.com/u/your-handle) will then see your display name, handle and the coverage from activity files you uploaded or from Ride with GPS. Coverage from Strava is never shown there. You will be able to turn it off at any time.

11. Cookies and browser storage

OrbFill uses no advertising or analytics cookies and does not track you across websites. Your browser stores only what the service needs to work, which does not require consent:

• Your sign-in session, in local storage, so that you stay signed in.
• A temporary sign-in verifier while you sign in, removed afterwards.
• The page to return to after signing in, in session storage.
• Your choice of kilometres or miles.
• Cloudflare, which protects our service, sets a strictly necessary security cookie (__cf_bm, 30 minutes).
• Our usage measurement (PostHog, section 12) keeps its identifier only in the open page's memory; it stores nothing in your browser.

The app keeps on your phone: your sign-in (in the phone's secure storage), a copy of your covered roads and of your last dashboard so that they appear at once and without a connection, and your settings. All of it is removed when you sign out.

12. Usage analytics

To see how OrbFill is used and to find errors, the website, the app and our service send usage data to PostHog, in its EU cloud in Frankfurt. This covers:

• the pages you open, what you click, and events such as creating an account, connecting Strava or processing an uploaded activity;
• errors, loading times, and your device type, browser, screen size and IP address.

In the app, the same rules apply with stricter limits: no recording of the screen, no record of what you tap, and nothing stored on your phone for analytics; only your account ID, the name of each screen you open and the same events.

The data is linked only to a random account ID, never to your name or email address. Nothing obtained from Strava, Ride with GPS, Apple Health or Health Connect is ever sent: no such activity, place, route or number, and no event about such an activity; events about activities concern only files you upload yourself. We use this data only ourselves, to improve OrbFill and fix faults, never for advertising.

Our legal basis is our legitimate interest (Article 6(1)(f) GDPR). You can object at any time, or ask us to delete your usage data, by writing to hello@orbfill.com from the address of your account.

13. Your rights

Under the GDPR you have the right to access your data and receive a copy (including the data we collected from Strava), to have it corrected, to have it erased, to restrict or object to its processing, and to receive it in a portable format. Where we rely on your consent, you can withdraw it at any time, for example by disconnecting Strava or turning off your public profile; this does not affect processing that took place before.

• In Settings you can change your profile, turn the public profile off, disconnect Strava and delete your account.
• For anything else, including deleting a single activity or getting a copy of your data, write to hello@orbfill.com from the address of your account.
• We answer within one month; for a complex request we can extend this by up to two more months, and we tell you why within the first month. It is free of charge.

If you live in a US state with a consumer privacy law, such as California, you have the right to know what personal information we collect and how we use it, to have it deleted or corrected, and not to be discriminated against for using these rights. We do not sell or share personal information for cross-context behavioural advertising. Use the same address to exercise these rights.

If you think we have not handled your data lawfully, please contact us first. You may also complain to the Hungarian supervisory authority, the Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH): 1055 Budapest, Falk Miksa utca 9-11.; postal address: 1363 Budapest, Pf. 9.; phone: +36 1 391 1400; email: ugyfelszolgalat@naih.hu; https://naih.hu. You may also complain to the authority of the EU country where you live, or go to court; in Hungary you can choose the court of your place of residence or stay.

14. Security

All traffic to OrbFill is encrypted (HTTPS). Strava access tokens are encrypted at rest, passwords are stored only in hashed form, and access to our systems is limited to the operator. No transmission over the internet is completely secure, but we take appropriate technical and organisational measures to protect your data. If a personal data breach affects you, we notify the supervisory authority and you as the law requires, and Strava without delay where the breach affects data from Strava.

15. Age

OrbFill is meant for people aged 18 or over, as our terms state. We do not knowingly collect data from children; if you believe a child has given us data, please tell us and we will delete it.

16. Changes to this policy

We publish every change on this page with a new effective date. If a change is significant, in particular if we start to collect a new kind of data from Strava or another source, we tell you in the app or by email beforehand, and ask for your consent again where the law or Strava's rules require it.

This policy follows the GDPR (Regulation (EU) 2016/679), the Hungarian Act CXII of 2011 on informational self-determination and freedom of information, and the Hungarian Act CVIII of 2001 on electronic commerce services.