Privacy Policy
1. Who is responsible for your data
Navpact is developed and operated by Oscar Fluur, a private individual based in Sweden (“Navpact”, “we”, “us”). For the purposes of the EU General Data Protection Regulation (GDPR) and Swedish data protection law, Oscar Fluur is the data controller for the personal data described in this policy.
You can reach us about anything in this policy at [email protected]. Because Navpact is a small service, we have not appointed a data protection officer; privacy questions are handled directly by the controller.
2. What this policy covers
This policy applies to the Navpact iPhone app, the website at navpact.com, and the servers that make them work (together, the “Service”). It explains what personal data we process when you use the Service, why, on what legal basis, who receives it, how long we keep it, and the rights you have.
It does not cover services run by others that you may use alongside Navpact — for example Apple’s App Store and TestFlight, or your Apple or Google account itself. Those companies process data under their own privacy policies.
3. What we collect
We only collect what the Service needs to work. Most of it you give us directly; some of it is created when you use the app.
3.1 Your account
- Email address and display name, when you create an account.
- Password, if you sign up with email. We never store the password itself — only a one-way, salted scrypt hash that cannot be turned back into your password.
- Sign in with Apple or Google. If you use one of these, Apple or Google tells us a unique account identifier for you and, if you allow it, your email address and name. We check the sign-in token directly against Apple’s or Google’s published keys; we never receive your Apple or Google password. If you choose Apple’s “Hide My Email”, we only ever see the private relay address Apple gives us.
- Your acceptance of our terms. Before you can use Navpact, you are asked to accept the Terms of Use, confirm you have read this Privacy Policy, and confirm you are 16 or older. We record which version of each document you accepted, when, and which version of the app you used — so we can show what you agreed to, and ask again if either document changes.
- Account status — when you signed up, when you last used the app, whether your email is confirmed, and security counters such as failed sign-in attempts (used to lock an account temporarily after too many wrong passwords).
3.2 Your profile and garage
- Profile photo, if you add one, and your chosen map colour and vehicle type.
- Bikes you add to your garage: their names, photos, and the distance and number of rides recorded on each.
- Your friend code, used to connect with other riders.
- Your settings, such as who can see you on the map and how your posts are shared.
3.3 Location and rides
Location is central to Navpact, so it has its own section — see section 4. In short:
- Live location — your precise position, direction and speed — is used while the app is open or while you are on a ride, to show you and the riders you have chosen on the map and to navigate.
- Recorded rides — the route you rode, its distance, duration and speeds — are saved when you record a ride.
- Destinations and stops you search for or add to a ride, and the search text you type into the address search.
3.4 Groups, messages and posts
- Groups you create or join, and your role in them.
- Messages you send in group chats and direct conversations, and ride alerts you send to your group.
- Posts you share to the feed — text, photos and ride summaries — and the kudos you give.
- Friend connections and friend requests.
3.5 Group voice
If you join group voice, your microphone audio is streamed live to the other riders in that voice room through our own voice server. We do not record voice. Audio is only transmitted while you are in a voice room, and never stored.
3.6 Notifications
If you allow notifications, your iPhone gives us a push token — an address Apple uses to deliver notifications to your device. We store it with your account so we can notify you about messages, invitations and group rides.
3.7 Feedback you send us
When you use Send feedback in the app, we receive your message, any screenshots you choose to attach, and basic information about your device and app to help us understand the problem: app version and build, iPhone model, iOS version, language and similar technical details. You can see what is included before you send it.
3.8 Technical and security records
When your app talks to our servers, we record limited technical information about each request: the time, the kind of action (for example “signed in” or “saved a ride”), whether it succeeded, how long it took, your IP address, and the app’s user-agent string. We use this to keep accounts secure, investigate problems and prevent abuse. We do not record the content of your messages or your location in these records, and we avoid logging passwords, sign-in links and access tokens.
3.9 What we do not collect
- We do not use advertising networks, analytics companies or tracking SDKs.
- We do not read your contacts, calendar or photo library — only the photos you pick.
- We do not track you across other apps or websites, and the app does not use Apple’s advertising identifier.
- We do not sell or rent personal data to anyone.
4. Your location, and who can see it
Your iPhone only shares your location with Navpact if you give the app location permission. You can change or withdraw that permission at any time in the iPhone’s Settings.
4.1 During a group ride
When you join a group ride, everyone in that group sees your live position, direction and speed on the map for as long as you are in the ride. That is what a group ride is. When you leave the ride, the group stops receiving your position. If “Always” location permission is granted, this continues while the phone is in your pocket, so the group can still see you with the screen off.
4.2 Outside a group ride
You choose who can see you with Map visibility:
- Friends — only riders you have both accepted as friends.
- Everyone — any signed-in Navpact rider nearby.
- Off — nobody. Your position is not shown to other riders and is not shown to Navpact’s operator either (see 4.4).
4.3 How live location is handled
Live positions pass through our real-time server so they can be delivered to the riders who are allowed to see them. Live positions are held in memory only and are never written to a database. A position disappears from the server within a few minutes of your phone stopping sending it. Your live location becomes a stored record only when you record a ride, and that recording belongs to your account.
4.4 The operator’s live map
During the beta, Navpact’s operator (Oscar Fluur) can see a map of riders who are currently using the app and whose map visibility is set to Friends or Everyone. It shows each rider’s current position, speed, display name and map colour, so that we can check the live service is working, understand how it is used, and help riders who report a problem.
- It only ever shows current positions; nothing is stored or kept as history.
- It never includes riders who have set map visibility to Off.
- It is reachable only from the operator’s private, encrypted network — not from the internet — and every time it is opened, that access is recorded in an audit log.
- It is used only for operating and supporting the Service, never for any other purpose.
If you do not want to appear on it, set your map visibility to Off. You can also object to this processing at any time (see section 10).
4.5 Maps, routes and address search
Map images, route calculation and address search all run on our own servers, using OpenStreetMap data. Your location and your searches are not sent to Google, Apple Maps or any other map provider.
5. Why we use your data, and our legal basis
The GDPR requires a legal basis for every use of personal data. These are ours:
| What we do | Data used | Legal basis |
|---|---|---|
| Create and run your account, and let you sign in | Account data, sign-in identifiers | Contract — necessary to provide the Service you signed up for (GDPR art. 6(1)(b)) |
| Show you and the riders you choose on the map; group rides; navigation | Live location, profile, group membership | Contract (art. 6(1)(b)) |
| Record and show your rides, bikes and stats | Recorded rides, garage | Contract (art. 6(1)(b)) |
| Chat, posts, friends, voice | Messages, posts, photos, friend connections, live audio | Contract (art. 6(1)(b)) |
| Send confirmation, password-reset and service emails | Email address | Contract (art. 6(1)(b)) |
| Send notifications you have allowed | Push token | Contract (art. 6(1)(b)); you control this with iPhone’s notification permission |
| Keep a record that you accepted the Terms and read this policy, and which versions | Account identifier, document versions, time, app version | Contract (art. 6(1)(b)) and our legitimate interest in being able to show what was agreed (art. 6(1)(f)) |
| Keep accounts secure, prevent abuse and fraud, investigate problems | Technical and security records, account status | Legitimate interest in a secure, working service (art. 6(1)(f)) |
| Handle reports about content or riders, and enforce our Terms | Reported content, account data, related records | Legitimate interest in keeping the community safe (art. 6(1)(f)) |
| Operator’s live map during the beta (see 4.4) | Current position, speed, name, map colour | Legitimate interest in operating and supporting the beta (art. 6(1)(f)) |
| Understand and fix problems you report | Feedback, screenshots, device details | Legitimate interest in improving the Service (art. 6(1)(f)) |
| Keep backups so data can be restored after a failure | All account data | Legitimate interest in not losing your data (art. 6(1)(f)) |
| Comply with legal requirements | Whatever the law requires | Legal obligation (art. 6(1)(c)) |
Where we rely on legitimate interest, we have weighed our interest against your rights and expectations, and chosen the least intrusive way to achieve it. You have the right to object to processing based on legitimate interest — see section 10.
We do not make decisions about you that are based solely on automated processing and that have legal or similarly significant effects.
7. Transfers outside the EU/EEA
Our own servers are in Sweden. Some of the providers listed in 6.2 are based in the United States, so limited data may be processed there. When that happens, the transfer is protected by the EU–US Data Privacy Framework where the provider is certified, and otherwise by the European Commission’s Standard Contractual Clauses. You can ask us for more information about these safeguards.
8. How long we keep data
We keep personal data only as long as we need it for the purposes above.
| Data | How long |
|---|---|
| Account, profile, garage, recorded rides, posts, messages, friends | Until you delete them or delete your account |
| Record of which Terms and Privacy Policy versions you accepted | For as long as you have an account; deleted with it |
| Live location | Held in memory only; gone within minutes of your phone stopping sending it |
| Voice | Not stored |
| Technical and security records | 60 days, then deleted automatically |
| Feedback, screenshots and device details you send us | Up to 12 months, then deleted automatically — or sooner if you delete your account |
| Reports about content or riders | Until reviewed, then up to 12 months to spot repeated abuse |
| Push token | Until it stops working, you sign out, or you delete your account |
| Password-reset and confirmation links | Until used or expired — 1 hour for password resets, 48 hours for email confirmation |
| Backups | Up to 35 days, then permanently deleted |
| Emails held by our email provider | Up to 30 days |
| Records of what the operator did in Control | Kept for accountability; your identity is removed from them when you delete your account |
9. Deleting your account
You can delete your account yourself in the app, under You → Profile → Delete account. For your protection you type DELETE to confirm, and password accounts also enter their current password.
When you confirm, we immediately and permanently delete from our live systems: your account and profile, photos, garage and bikes, recorded rides, posts and kudos, messages you sent (including in group chats), friend connections, push tokens, feedback and technical records, and the ride journal stored on that phone. Groups you created that other riders still belong to are handed over to one of them, so their shared history is not destroyed; groups with no one else in them are deleted.
Copies of deleted data can remain in our backups for up to 35 days, after which they are gone for good. We will not restore deleted data from a backup except to recover from a technical failure, and if that ever happened we would delete your data again.
If you cannot use the app, email [email protected] from the address on your account and we will delete it for you.
10. Your rights
Under the GDPR you have the right to:
- Access — get a copy of the personal data we hold about you.
- Rectification — have inaccurate data corrected. You can change most details yourself in the app.
- Erasure — have your data deleted. You can do this yourself (see section 9).
- Restriction — ask us to limit how we use your data while a question is being resolved.
- Data portability — receive the data you gave us in a structured, machine-readable format (for example your recorded rides), and have it sent to another service where technically possible.
- Object — object to processing based on our legitimate interests, including the operator’s live map. We will stop unless we have compelling grounds that override your interests, or need it for a legal claim.
- Withdraw consent — where anything relies on consent or a device permission, you can withdraw it at any time, without affecting what happened before.
To use any of these rights, email [email protected]. To protect your account, we may ask you to write from the email address on your account or to confirm your identity in the app. We will respond within one month; if a request is complex we may extend this by up to two further months and will tell you why. Using your rights is free of charge.
11. Other riders, reporting and blocking
Navpact is a place to ride with other people, so it includes content that riders create. If you see a post, message or profile that breaks our Terms, you can report it in the app, and you can block a rider so that you no longer see each other’s content or receive messages from them.
When you report something, we receive the reported content, who reported it and why, and we review it. Reports are kept for as long as needed to handle them and to prevent repeated abuse. The person you report is not told who reported them.
12. How we protect your data
We use measures appropriate to the risk, including:
- Encrypted connections (TLS) between the app and our servers.
- Passwords stored only as salted scrypt hashes; sign-in tokens verified against Apple’s and Google’s keys.
- Servers that are not directly reachable from the internet. The maps, routing and database services accept connections only from our own services.
- Administration only over a private, encrypted network, with separate credentials and audit logging of operator actions.
- Short-lived access tickets for the real-time service, so a copied link or old token stops working.
- Rate limiting and temporary lock-out after repeated failed sign-ins.
- Regular backups kept on a separate machine with restricted access.
No system is perfectly secure. If a personal data breach puts your rights at risk, we will notify you and the Swedish Authority for Privacy Protection as the law requires.
13. Age limit
Navpact is intended for riders aged 16 and over. We do not knowingly collect data from anyone younger. If you believe a child under 16 has created an account, contact us and we will delete it.
14. Taking part in the beta
Navpact is currently in beta. Features may change, and some may be added or removed while we test them. If we start processing personal data in a new way, we will update this policy before we do.
If you install the beta through Apple’s TestFlight, Apple may share certain information with us, such as crash reports, the feedback and screenshots you submit through TestFlight, your device model and iOS version, and — if you were invited by email — your name and email address. Apple processes this under its own privacy policy; we use it only to improve the app.
15. Changes to this policy
We may update this policy as the Service develops. The version and effective date at the top show when it last changed. If a change materially affects how we use your data, we will tell you in the app or by email before it takes effect, and the app will ask you to read and accept the new version before you continue.
16. Contact and complaints
Controller: Oscar Fluur, Sweden
Email: [email protected]
If you are unhappy with how we handle your personal data, please contact us first — we would like the chance to put it right. You also have the right to lodge a complaint with a supervisory authority. In Sweden that is Integritetsskyddsmyndigheten (IMY), the Swedish Authority for Privacy Protection, www.imy.se. If you live in another EU/EEA country, you can also complain to the authority there.