Privacy Policy
Before you start reading
We wrote this to be genuinely readable, not just to satisfy a legal checkbox. Kåduka is a trail running app, and your runs come to us from your watch or from a file you upload. That means we handle some of the most personal data that exists: where you went, when you went there, how fast, and how hard your heart worked. We take that seriously.
Our core promise: your location and health data are yours. You decide what is shared and with whom, and you can ask us for a full copy or ask us to delete everything at any time. We have also tried hard to describe only what Kåduka actually does today, and to say plainly when something is not built yet.
AI and your data
Kåduka does not use AI on your data today. We do plan to, for TrailIQ trail and route recommendations, and we will ask your permission first. Read Section 8: AI and TrailIQ for exactly what we plan and what we promise.
1. What Data We Collect
Kåduka handles your runs and the places you go, so we collect more data than a typical service. The tables below show what we collect, why, and whether it is required.
One thing worth knowing up front: Kåduka does not record your runs itself. There is no start or stop button here. Your runs arrive from a watch you connect, or from a GPX or FIT file you upload. See Section 9, Connected devices and services.
1.1 Information You Give Us Directly
| Data | What It Includes | Required? |
|---|---|---|
| Account details | Your email address, your name, and your @handle. We never set or store a password: you sign in with a code we email you | Yes, to create your account |
| Profile info | Your ZIP or postal code, home region, short bio, photo or avatar, and the running details you choose to add, such as your usual distance and pace | No, only if you volunteer it |
| Race registration details | If you sign up for a race through Kåduka: your legal name, date of birth, emergency contact name and phone, gender identity if you share it, and your answers to the organizer's questions and waiver | Yes, but only for the races you enter |
| Photos you upload | Photos you add to a run, a route, or an organization page | No, only what you add |
| Support and feedback messages | Anything you send us through the in-app feedback form or by email | No, only when you contact us |
1.2 Data That Arrives With Your Runs
When you connect a watch or upload a file, this is what comes with each workout:
| Data | What It Includes | Required? |
|---|---|---|
| Workout summary | The name, date and type of the activity, how far, how long, and how much climbing | Yes, it is the activity record |
| Your route | The GPS track of where you ran, including its start and end points, if your watch or file recorded one | No, only if the route is in the file |
| Health metrics | Heart rate and calories, when your watch sends them | No, only what your watch provides |
| Photo location | If a photo you upload carries GPS coordinates, we read them so the photo can sit on the map, then we remove them from the image file itself. See 3.6 | No, only if your photo carries them |
We never collect sleep, resting heart rate, daily step counts, stress, blood oxygen or body composition from a connected watch. We only ever see workouts, never your day to day health data, and we never see your watch account password.
1.3 Your Location in the Browser
Kåduka asks your browser for your location in two places only: when you tap 'Current location' while planning a route, and when you ask a map to show where you are. Your browser asks your permission first, and you can refuse and still use Kåduka. We use that position to answer the question in front of you. We do not store it as an activity, and we do not track you in the background.
1.4 Technical Data
Kåduka is a website, so our hosting provider receives the ordinary technical information every website receives with a request: your IP address, your browser and device type, and the page you asked for. We also keep error and performance logs so we can fix what breaks. If you turn on phone notifications, we store the push subscription your browser gives us, so we can send them.
1.5 Payment Information
All payments are processed by Stripe (stripe.com/privacy). We never see or store your card number. What we keep is a Stripe customer reference and the status of the payment, which is what lets us tell whether your Kåduka Plus subscription or your race entry is paid.
2. How We Use Your Data
We use your data only for the purposes below. We do not sell your personal information to advertisers, data brokers, or any third party; ever.
| Purpose | Description |
|---|---|
| Providing the service | Trail and route discovery, your activity log, race pages and registration, clubs and organization pages |
| Account and sign-in | Emailing you a sign-in code and keeping you signed in |
| Your personal analytics | Showing you your own progress, personal records, badges and training trends |
| Adding context to your runs | Looking up the weather where and when you ran, and giving the run a place name |
| App improvement | Understanding how features are used, and how people move through the app. See 6.1 for what our analytics provider receives |
| Communications | Responding to your requests and sending essential service notices |
| Marketing (opt-in only) | Updates about new trails or features, only if you subscribed; unsubscribe anytime |
| Legal compliance | Meeting obligations under applicable law |
3. Location Privacy: Threats, Research & Our Protections
Why location privacy deserves its own section:
Peer-reviewed security research (Mink et al., CHI 2022) studied how well 'privacy zones' actually protect fitness app users. Their finding was striking: even with a privacy zone enabled, 68% of guesses by ordinary, non-technical participants fell within 50 meters of a user's hidden home address, after viewing just three activities. In plain terms: the start/end point hiding that most fitness apps offer provides weaker protection than users assume. A motivated burglar, stalker, or other bad actor does not need technical skills to narrow down where you live: they just need to look at a few of your runs. We take those documented, real-world risks seriously, and the protection we lean on most is structural rather than a toggle you have to remember: your runs start Private and stay that way until you choose otherwise. The rest of this section is honest about what we have built and what we have not.
3.1 Your Activities Start Private
When you create an account, your activities are set to Private. That covers the whole run, including the GPS route and its start and end points. Nothing is visible to anyone else until you choose to share it, either by changing the default for future runs or by changing one run on its own.
Your profile is a separate setting, and it does not start private. See 4.3.
3.2 Protected Zone (Start/End Obfuscation): Not Built Yet
A Protected Zone would be a radius around a sensitive address, such as your home, your workplace or a regular trailhead, and routes would be trimmed inside it before anyone else could see them.
This does not exist yet. There are no controls for creating a zone, no zone exists on Kåduka today, and nothing is being trimmed. We are describing it here only so you know it is not protecting you right now, and we will update this section when it ships. Until then, treat any run you make Public as showing exactly where you started and finished.
Important limitation you should know
Privacy zones reduce, but cannot fully eliminate, the risk of location inference, and Kåduka does not have them yet at all. Researchers have demonstrated that an observer who can see multiple activities from the same user can sometimes estimate a sensitive location even with a zone active, by analyzing where routes consistently begin and end near the zone boundary. To protect your location today: keep your activities set to 'Private' or 'Friends Only' rather than 'Public'; vary your starting points when you can; and consider starting your watch a few blocks from home. This is an industry-wide limitation, not unique to Kåduka. We disclose it clearly because you deserve to understand the actual risk level.
3.3 We Do Not Mine Your Routes for Your Home Address
Kåduka does not analyze your routes to work out where you live, and we never send your stored GPS coordinates to anyone as data.
One honest exception, because it is easy to miss: our analytics provider records your screen (see 6.1), and a run's route line is drawn on the page, so looking at your own run puts that route line into the recording. What that provider receives is more than aggregate numbers, so please read 6.1 rather than assume.
3.4 There Is No Live Tracking
Kåduka has no live tracking and no way to broadcast where you are. Nobody can follow you in real time, and there is no link you could share that would let them. When you ask a map to show your position, that position is used to draw the map in your own browser and is not sent to other users.
3.5 You Control Deletion of Your Runs
You can delete any individual activity, including its complete GPS route, at any time from within the app. See Section 16 for a full copy of your data and for deleting your account.
3.6 Photo Location Is Removed From the Image File
Photos often carry the coordinates of where they were taken, buried in the image file. When you upload a photo to Kåduka, we strip that metadata out of the file before we store it, and if the strip fails we refuse the upload rather than store an image we have not cleaned. So a photo someone else views or downloads does not carry your location.
To be straight with you about the limit of this: we read those coordinates before we remove them, and we keep them on your photo's record so the photo can appear in the right place on your map. The image file is cleaned. Kåduka still knows where the photo was taken, and that location follows the same sharing setting as the run it belongs to.
4. Social Sharing: Opt-In, Always
Sharing a run is never automatic. Your activities start Private and stay that way until you choose otherwise. Your profile is the one thing that does not start private, and 4.3 says so plainly.
4.1 Activity Visibility Levels
| Level | Who Can See This Activity |
|---|---|
| 🔒 Private (the default) | Only you. No other runner can reach this activity through the app. |
| 🤝 Close Friends | Only the friends you have marked as close friends. |
| 👥 Friends Only | Runners you have accepted as friends. Friendship is mutual: both of you agreed. |
| 🌍 Public | Any signed-in Kåduka runner. On Kåduka, 'Public' means anyone signed in, not the open internet: signed-out visitors are not shown your runs, your name or your photo. A Public run shows your summary and your route, including its start and end points, so only use it when you are comfortable with that. |
You can also control the parts of a run separately, so your map, photos, stats or the date can each be narrower than the run itself. Kåduka staff can reach data in the database in order to run the service and to help you when you ask, which is covered by 10.
4.2 Friend Connections Are Always Opt-In
No one is added to your friends list without your explicit acceptance of a request. We do not auto-add friends, create social connections on your behalf, or suggest friends based on your physical proximity to another user during a run.
4.3 Your Profile Starts Visible to Other Runners
We want to be straight about this one, because it is the exception to everything above. When you create an account, your profile is set to Public, which on Kåduka means visible to any signed-in runner. Your name, your @handle, your photo and your bio can be seen by other runners, and you can be found when someone searches for people.
Signed-out visitors are a different matter: they are not shown your name, your @handle or your photo at all.
You can change this at any time in Privacy Settings. Narrowing it to Friends shows your profile only to runners you have accepted, and setting it to Anonymous means everyone except you sees the name 'Anonymous' with no photo, no bio, no location and no stats. Your activities are a separate setting and are Private either way.
4.4 Clubs and Organization Pages
If you join a club or appear on a race organization, coaching, trail work or shop page, your membership can be visible to other people who can see that page, and the page's managers can see you by name. Managers can hide a person's card, and you can hide your own.
Kåduka has no segment leaderboards and no group challenges. If we build them, we will say here what they would show before they ship.
4.5 There Is No Tagging
Other runners cannot tag you in activities or photos, because Kåduka has no tagging feature at all. Nobody can attach your name to someone else's run or photo. You can record who you ran with for your own log, and that is yours: it does not appear on their profile or notify them.
5. Legal Bases for Processing (Including GDPR)
European data protection law (GDPR) and many other privacy frameworks require us to identify a specific legal basis for each type of data processing. The table below explains this in plain language.
| What We Process | Legal Basis | What This Means for You |
|---|---|---|
| Account creation and sign-in | Contract | We need your email to deliver the service you signed up for. |
| Storing your runs and routes | Contract | Your activity log is the core product, and we cannot provide it without this. |
| Health data (heart rate, calories) | Explicit Consent (GDPR Art. 9) | You must actively connect a watch or upload a file. You can disconnect at any time. |
| Your location in the browser | Consent | Your browser asks you first, and you can refuse and still use Kåduka. |
| Race registration details | Contract | The organizer needs them to run the race you entered, including your emergency contact. |
| Marketing emails | Consent | You subscribe. You can unsubscribe instantly from any email. |
| Product analytics, including session replay | Legitimate Interests | Understanding how the app is used helps us improve it. See 6.1 for what this involves and 7 for how to switch it off. |
| Legal compliance and record-keeping | Legal Obligation | We must retain certain records as required by applicable law. |
Withdrawing consent: Where we rely on your consent, you may withdraw it at any time through Privacy Settings or by emailing [email protected]. Withdrawal will not affect the lawfulness of any processing that took place before you withdrew.
6. Who We Share Your Data With
We do not sell, rent, or trade your personal information. The only third parties who receive your data are service providers who help us operate Kåduka, and they are contractually prohibited from using it for any other purpose.
6.1 Service Providers
These are the outside companies that actually receive your data, what each one is for, and what each one gets. We have named them all rather than writing 'a hosting provider' or 'an analytics provider'.
| Provider | Purpose | Data Shared |
|---|---|---|
| Supabase | Our database, file storage and sign-in, in the United States | Everything you have in Kåduka: your account, your runs and their GPS routes, your photos, and the metrics from your watch |
| Vercel | Hosting and the server side of the app | Every request to Kåduka, which includes your IP address, your browser and device type, and the page you asked for |
| Stripe | Payments for Kåduka Plus, organization subscriptions and race entries | A customer reference and the payment status. Your card details go to Stripe directly and we never see or store them |
| Mapbox | Maps and drawing your route line | The map areas and tiles your browser requests, and your IP address |
| Esri (ArcGIS) | The topographic basemap under our maps | The map tiles your browser requests, and your IP address |
| Amplitude | Product analytics and session replay | Your account id and your profile details such as plan, home region, usual distance and pace; summary numbers when you do something, such as a run's distance, elevation and duration; and a recording of your screen as you use Kåduka (see the note below), which captures whatever is on the page at the time. That includes a run's route line on the map and its distance, duration, pace and elevation. Heart rate and calories are never shown on screen, so they are never recorded |
| Open-Meteo | The weather and air quality shown on a run or a route | Coordinates and a time, requested straight from your browser, so Open-Meteo also sees your IP address |
| Resend | Sending our emails, including your sign-in code | Your email address and the contents of that email |
| Stridee | The device connection behind Garmin and COROS sync | Your workouts from that watch, and the connection itself. See Section 9 |
| Suunto | Direct Suunto watch sync | Your workouts from that watch, and the connection itself. See Section 9 |
| Cloudflare | Checking that a sign-in is a person, not a bot | A browser signal and your IP address, at sign-in and when we send you a code |
| Discord | Where your in-app feedback reaches us | Your feedback message and your email address |
| Linear | Where feedback and organization claims become a task we track | Your name, your email address and your message |
| Apple, Google, Mozilla | Delivering phone notifications, if you turn them on | The push address your browser gives us and the contents of the notification. This is how web notifications work on every site |
About session replay
Our analytics provider records your session: the pages you open and the things you tap, played back as a recording so we can see where the app confuses people. It is on for every session. This is not aggregated and it is not anonymous, because it is tied to your account.
What it captures is what is on your screen. Anything you type into a form field is hidden before the recording leaves your browser. The rest of the page is not hidden, and that includes your own runs: when you look at one of your activities, its route line on the map, its distance, duration, pace and elevation are in the recording, even though that run is Private to other runners. Heart rate and calories are never shown anywhere in Kåduka, so they never reach a recording.
You can switch it off. In each browser you use, open these two addresses once: kaduka.app/?kdk_analytics=off and run.kaduka.app/?kdk_analytics=off. Both are needed, because each site address keeps its own setting. That switches off our analytics and session recording for that browser, and it stays off until you clear the browser's site data. To turn it back on, open the same two addresses with ?kdk_analytics=on. If you would like help doing this, email [email protected].
Each of these companies receives only what it needs for its job, is required to protect it, and may not use it for anything else. We do not sell your data and we never share it for advertising.
6.2 Legal Requirements
We may disclose your information when required by a valid court order, subpoena, or government investigation. Where permitted by law, we will notify you before complying with any such request.
6.3 Business Transfers
In the event of a merger, acquisition, or sale of substantially all assets, your information may be transferred as part of that transaction. You will be notified in advance and given the opportunity to delete your account before any transfer occurs.
6.4 Other Users (Only What You Choose to Share)
If you set an activity to Friends Only or Public, certain information becomes visible to the audience you selected. Choose your sharing level carefully, as we cannot control what users do with content they can legitimately view.
7. Cookies and Tracking Technologies
Kåduka sets very few cookies, and we have listed every one of them. We set no advertising cookies and no personalized-content cookies, and we do not let anyone else drop a cookie on our site to follow you elsewhere. That is also why you have never seen a cookie banner here.
| Cookie | Purpose | Can You Disable? |
|---|---|---|
| Sign-in session | Keeps you signed in as you move around the app | No, you cannot stay signed in without it |
| Accent color | Remembers the accent color you picked | Yes, clear your cookies; the app still works |
| Invite reference | Remembers who invited you, so they get the credit when you join | Yes, clear your cookies |
| Staff mode | Only ever set for Kåduka staff accounts | Not applicable to runners |
Our analytics provider also stores an identifier in your browser so it can tell one session from the next.
How to switch our analytics and session recording off. In each browser you use, open these two addresses once: kaduka.app/?kdk_analytics=off and run.kaduka.app/?kdk_analytics=off. Both are needed, because each site address keeps its own setting. Your browser remembers the choice until you clear its site data, so if you use another browser or another device, open the two addresses there too. To turn it back on, open them with ?kdk_analytics=on instead. If you would like help, email [email protected].
You can also block cookies and scripts in your browser's own settings. Note that our site does not act on your browser's Do-Not-Track setting, which Section 17 explains.
8. AI and TrailIQ
Kåduka does not use AI on your data today.
No AI and no machine learning looks at your runs, your routes, your photos or your profile. Nothing you put into Kåduka is sent to an AI service.
We plan to use AI to power TrailIQ, which recommends trails and routes for you. To do that, it may look at your profile, your preferences and your activities, including activities imported from a connected device such as a Garmin watch.
Here is what we promise about that, before any of it starts:
- The AI will only use your data to make recommendations for you.
- Your data will not be used to train AI models.
- We will update this policy first, to name the AI provider and explain exactly what data it uses and why. We have not chosen a provider yet, which is why none is named here.
- We will ask for your explicit permission. Nothing is processed without it.
- You can turn it off at any time in your settings.
EU and EEA users: you have the right under GDPR Article 22 not to be subject to solely automated decision-making that produces significant effects. Kåduka makes no automated decisions about you at all today.
9. Connected Devices and Services
Your runs reach Kåduka in one of two ways: you connect a watch and they arrive on their own, or you upload a file. You connect and disconnect yourself, and you can use Kåduka without connecting anything.
9.1 How Each Connection Works
| What You Connect | How It Reaches Us | What Happens |
|---|---|---|
| Garmin | Through Stridee, a device connection service | You sign in at Garmin and authorize Kåduka to read your workouts. We never see your Garmin password |
| COROS | Through Stridee, a device connection service | You sign in at COROS and authorize Kåduka to read your workouts. We never see your COROS password |
| Suunto | Directly with Suunto | You sign in at Suunto and authorize Kåduka to read your workouts. We never see your Suunto password |
| A GPX or FIT file | You upload it yourself | Nothing is connected and no account is linked. You can also bulk-import a data export you requested from Garmin, Strava or COROS |
We are also applying for direct access to Garmin's API. If that is granted, your Garmin data will come straight to Kåduka and Stridee will no longer handle it. We will update this section when that changes.
9.2 What We Take From a Connected Watch
| We Collect | We Never Collect |
|---|---|
| From each workout: its name, date and type. How far, how long, and how much climbing. Your route, if your watch recorded one. Heart rate and calories, when your watch sends them. | Sleep, resting heart rate, daily step counts, stress, blood oxygen, or body composition. We only ever see workouts, never your day to day health data. And we never see your password. |
Your history comes too. Connecting brings over your past workouts, not just the new ones. Depending on the watch and how long you have used it, that can be years of runs arriving at once. We say so here because it surprises people.
What we add. Once a workout arrives, we look up the weather where and when you ran and give it a place name, so your log reads like somewhere you went. That lookup sends the coordinates and the time to our weather provider (see 6.1).
9.3 Disconnecting, and What Happens to What Is Already Here
You can disconnect at any time from your device settings in Kåduka. When you do, we revoke the permission at the provider first, so the connection is genuinely withdrawn and not just hidden from you, and new workouts stop arriving.
Activities already imported stay in your account.Disconnecting does not delete your run history, because for most people that history is the reason they are here. If you want imported runs gone, delete them individually, or delete your whole account as described in Section 16. You can reconnect at any time.
9.4 We Never Sell This Data
Data from Garmin, COROS, Suunto or any other connected device is never sold, never rented, and never used for advertising or shared with advertisers. There is no advertising anywhere in Kåduka. It is used to show you your own runs, to show them to whoever you have chosen to share them with, and for the purposes in Section 2.
10. How Long We Keep Your Data
| Data Category | Retention Period | Reason |
|---|---|---|
| Account and profile data | While your account is active, then removed when you ask us to delete it | It is your account |
| Your runs and their GPS routes | Until you delete them, with no automatic expiry | It is your personal training record |
| Health metrics from your watch | Until you delete the run they belong to | Sensitive, so you remain in control |
| Race entries and registration details | Kept as a record of the race you entered, and for as long as tax and accounting law requires the order | The organizer and we both need the record of the entry |
| Payment records | 7 years from the transaction date | Tax and accounting law requirement |
| Marketing preferences | Until you unsubscribe | Respecting your communication choices |
| Error and performance logs | Kept only as long as they are useful for fixing problems | Operational reliability only |
| Support and feedback messages | Kept while we are working on what you raised, and as a record of it afterwards | So we can follow up and not lose your report |
You can ask us to delete any or all of your data at any time. See Section 16.
11. How We Keep Your Data Secure
Kåduka is a small team, so rather than list every measure a large company would claim, here is what is actually true:
- Everything travels over an encrypted connection (HTTPS, TLS 1.2 or higher). There is no way to reach Kåduka without it.
- Your data sits in our database behind per-row rules, so one runner's account cannot read another's. Every read that shows someone else's content goes through those rules rather than trusting the app.
- There is no password to steal: you sign in with a code we email you, so we never hold a password for your account.
- Location data is stripped out of the photo files you upload, as described in 3.6.
- Kåduka staff can reach data in the database in order to run the service and to help you when you ask. We keep that to the people who need it.
No system is completely secure
Despite our best efforts, no method of internet transmission or electronic storage is 100% secure. We cannot guarantee absolute security, but we will notify you without undue delay (and within 72 hours for EU users as required by GDPR Article 33) if a data breach occurs that is likely to affect your rights or freedoms.
12. Children's Privacy
Kåduka is for runners aged 16 and older. When you sign up you confirm that you are 16 or older, which is also what our Terms of Service require. We do not ask for your date of birth, so that confirmation is what we rely on. We do not knowingly collect personal data from children under 16, and if you believe we have, contact [email protected] and we will delete it promptly.
Runners aged 16 and 17: we recommend a parent or guardian read this policy with you. Your activities start Private, and the setting worth looking at is your profile, which starts visible to other runners (see 4.3).
Race registration is different and stricter. A runner under 18 cannot sign themselves up for a race through Kåduka today. An adult must enter them.
13. Your Rights at a Glance: All Regions
Regardless of where you live, the following rights apply to your data. How to exercise them is covered in Sections 14 to 16.
| Right | What It Means in Practice |
|---|---|
| Access | Request a copy of all personal data we hold about you. |
| Correction | Ask us to fix inaccurate or incomplete information. |
| Erasure / Deletion | Ask us to delete your data (subject to limited legal exceptions). You can also delete individual runs yourself, see Section 16. |
| Data portability | Ask us for your data in a machine-readable format. See Section 16. |
| Restrict processing | Ask us to pause how we use your data while a dispute is being resolved. |
| Object to processing | Object to processing based on legitimate interests (e.g., analytics). |
| Withdraw consent | Withdraw any consent at any time without penalty. This does not affect past processing. |
| Lodge a complaint | File a complaint with your national, regional, or state data protection authority. |
| Non-discrimination | We will never treat you differently for exercising any of these rights. |
14. European Residents: Full GDPR Rights
If you are located in the European Economic Area (EEA), the United Kingdom, or Switzerland, the General Data Protection Regulation (GDPR) and equivalent national laws apply to your data. This section supplements Sections 5 and 13.
14.1 Data Controller
Kåduka, LLC is the data controller for your personal data. Contact: [email protected] | 9611 SW Bank Rd, Vashon, WA 98070, United States.
14.2 Special Categories of Data (GDPR Article 9)
Health data is a 'special category' under GDPR and requires explicit consent. The only health data we hold is what your watch sends with a workout, so we hold it only because you connected that watch or uploaded that file, and you can disconnect at any time without penalty. We hold no biometric data: Kåduka has no fingerprint or face login.
14.3 International Data Transfers
Kåduka is based in the United States. When we transfer your data outside the EEA or UK, we rely on one or more of the following approved safeguards:
- Standard Contractual Clauses (SCCs) approved by the European Commission.
- Adequacy decisions where the destination country provides adequate protection.
- Binding Corporate Rules or other legally approved transfer mechanisms.
You may request a copy of the applicable safeguards by contacting [email protected].
14.4 Additional GDPR-Specific Rights
- Right to object to processing for direct marketing (Art. 21). We will honor this immediately, without exception.
- Right not to be subject to solely automated decision-making with significant effects (Art. 22).
- Right to lodge a complaint with your EU supervisory authority. A full list is available at edpb.europa.eu.
14.5 Response Timelines Under GDPR
We will respond to all GDPR rights requests within 30 days of receipt. For complex or numerous requests, we may extend this by up to two additional months, but we will inform you within the first 30 days if an extension is needed.
14.6 Our Legal Bases
Every kind of processing we do is listed in Section 5, and each one relies on one of: Art. 6(1)(a) consent; Art. 6(1)(b) contract; Art. 6(1)(c) legal obligation; Art. 6(1)(f) legitimate interests. For health data, which is a special category, we rely only on Art. 9(2)(a) explicit consent.
15. United States Residents: State Privacy Rights
Depending on your state of residence, you may have additional rights under state privacy laws including the California Consumer Privacy Act (CCPA/CPRA), Virginia CDPA, Colorado Privacy Act, Connecticut Data Privacy Act, and equivalent laws enacted in other states.
15.1 Categories of Personal Information Collected (CCPA Reference)
| Category | Collected? | Notes |
|---|---|---|
| Identifiers | Yes | Name, email, username, IP address |
| CA Customer Records info | Yes | Account details and contact information |
| Protected classifications | Yes (if voluntarily provided) | Gender identity and date of birth, only on a race entry, and only because the race needs them |
| Commercial information | Yes | Your Kåduka Plus subscription and race entries. Stripe handles the card; we receive no card data |
| Biometric information | No | Not collected. Kåduka has no fingerprint or face login |
| Internet/network activity | Yes | App interactions, feature usage, cookies, and session replay (see 6.1) |
| Geolocation data | Yes | The GPS routes in your runs and routes, and your browser location when you ask for it |
| Sensory/electronic data | Yes | The photos you choose to upload. We never access your camera or microphone |
| Professional/employment info | No | Not collected |
| Education information | No | Not collected |
| Inferences | No | We do not build a profile of inferred characteristics about you |
| Sensitive personal information | Yes | Health metrics from your watch, and precise location in your runs and routes |
15.2 Your California and State-Specific Rights
- Right to Know: what categories of personal information we collect, use, and disclose (we do not sell).
- Right to Delete: request deletion of your personal information (subject to limited legal exceptions).
- Right to Correct: request correction of inaccurate personal information we hold.
- Right to Opt Out: opt out of any 'sale' or 'sharing' of personal information. We do not sell data, but you may contact us to confirm your status.
- Right to Limit Use of Sensitive Information: restrict our use of sensitive personal information to only what is necessary to provide the service.
- Right to Non-Discrimination: we will never deny service, charge you more, or provide lower quality service because you exercised a privacy right.
To exercise these rights, email [email protected] from the address associated with your account. We will verify your identity and respond within 45 days, or the period required by your state's law.
16. Downloading and Deleting Your Data
Your data belongs to you
You have the right to take your data with you and the right to have it erased. Both are available to you at any time, with no questions asked and no penalty.
16.1 Getting a Copy of Your Data
You can ask us for a complete copy of your personal data at any time. There is no button for this in the app yet, so today it is an email and we handle it by hand. Your copy will include:
- Your full run and route history, including the GPS routes, in a machine-readable format.
- Your account profile, preferences, and privacy settings.
- Your health and activity metrics.
- Your friends, clubs, badges and race entries.
How to ask: email [email protected] with 'Data Export Request' as the subject, from the address on your account. We will send your copy within 30 days, in a format you can import into other services.
16.2 Deleting Individual Activities
You can delete any individual activity, including its full GPS route, directly from within the app at any time. This one you can do yourself, right now, with no need to ask us.
16.3 Deleting Your Entire Account
You can have your Kåduka account and the personal data in it permanently deleted at any time. There is no button for this in the app yet either, so today you ask us and we do it:
- Email [email protected] with the subject 'Account Deletion Request', from the address on your account.
- We confirm it is you, delete the account, and tell you when it is done.
Account deletion is permanent and cannot be undone. Upon deletion:
- Your profile, activities, GPS routes, health metrics, photos and friend connections are permanently removed within 30 days.
- Aggregate counts your runs contributed to, such as how many people have run a trail, may remain, because they cannot be linked back to you.
- Payment and race-entry records are kept for 7 years where tax law requires it, and are not reachable through the app.
- Copies in our providers’ backups age out according to their retention windows.
16.4 Verification
For security, we will verify your identity before processing any export or deletion request. This typically means confirming access to the email address associated with your account. We will respond within 45 days, or the period required by applicable law.
17. Do-Not-Track
Some browsers send a Do-Not-Track or Global Privacy Control signal. Kåduka does not detect either signal today, so we want to be clear that turning it on in your browser does not currently change what we collect.
What it would normally be asking us to stop, we do not do anyway: there is no advertising on Kåduka, no ad network, no targeted marketing and no data sold or shared with advertisers. The one thing a DNT signal would reasonably cover is our product analytics, including session replay, and you can switch that off yourself: open kaduka.app/?kdk_analytics=off and run.kaduka.app/?kdk_analytics=off once in each browser you use. Section 7 explains this in full.
18. Policy Updates
We may update this Privacy Policy as our practices, technology, or legal obligations evolve. When we do:
- The 'Effective Date' at the top of this document will change.
- For significant changes, we will provide at least 30 days' advance notice via the app and by email.
- Your continued use of Kåduka after the effective date constitutes acceptance of the updated policy.
- If you do not agree with a change, you may delete your account before the effective date at no penalty.
We will never reduce your privacy rights through a policy update without giving you the opportunity to opt out or delete your account first.
19. Contact Us
If you have any questions, concerns, or requests about this policy or your personal data, please reach out:
We aim to respond to all enquiries within 30 days, or as required by applicable law.
This Privacy Policy is effective as of October 27, 2026 and supersedes all previous versions.
Location privacy protections informed by peer-reviewed research: Mink et al., CHI 2022. DOI: 10.1145/3491102.3502136
