Privacy Policy
01Who we are
Izuke is an app that helps you find someone to run with nearby, and connect with other runners through group runs, other open activities and community events. This policy explains how we collect, use, disclose, and safeguard your personal data when you use our mobile application, what we collect, why, who sees it, and what control you have over it.
Where Izuke is available. Izuke is currently offered in Vietnam. If we open in other countries, we will update this policy to cover the data protection laws that apply there and tell you before the change takes effect.
The company responsible for your data (the "data controller") is:
Izuke Pte. Ltd. 160 Robinson Road, #14-04 Singapore Business Federation Center Singapore 068914 UEN: 202643606E
Contact: contact@izuke.app
In this policy, "we," "us," and "Izuke" mean Izuke Pte. Ltd. "You" means the person using the app.
02The short version
We know most people don't read these. Here's the summary: the detail follows, and the detail is what legally governs.
We run no analytics and no ad tracking
There is no Google Analytics, no Facebook Pixel, no advertising identifier, no data broker. We do not sell your data and never have. We do use a crash reporter to find and fix crashes. Section 10.
We check you're a real person with a selfie
A quick liveness check, handled by a specialist provider, which deletes the image after a month. Izuke never stores it. Section 6.
We collect your location, including during a run
For matching and for live tracking you switch on yourself. Other runners see only your general area. Section 5.
Your photos are served from public web addresses
Profile photos, moments and route posts sit at URLs anyone with the link can open. Chat images are private. Section 7.
We collect your running data
Distance, pace, duration, elevation. It goes to no insurer, employer or advertiser.
Your data is stored in Ireland, in the EU
Not in Vietnam. Section 11 explains what that means.
You can delete your account in the app
Settings → Account. Section 12 covers the few things that survive.
03What we collect
3.1 Data you give us
| Data | Why we need it | Required? |
|---|---|---|
| Name | So your running partner knows who they're meeting | Required |
| Email address | Account login, recovery, service notices | Required |
| Date of birth | To confirm you're 18 or over | Required |
| Gender | Matching preferences and safety filtering | Optional |
| Avatar / profile photo | So your partner can recognise you at the meeting point | Required |
| Selfie | Identity verification — see Section 6 | Required to become verified |
| Chat messages | So you can arrange a run with someone | As you use it |
| Route comments, replies, race-room posts | Community features | As you use it |
| Route posts and moment cards | Sharing your runs | As you use it |
| Emergency contacts — the name and phone number of up to three people you choose | So we can text them if you press SOS or don't check in after a meetup — see Section 5 | Required before your first meetup |
We do not collect your phone number. You sign in with Google, Apple, or Facebook or with an email address and a password you choose. If you use a password, it is stored only as a cryptographic hash - we never see it and cannot recover it, only reset it.
3.2 Data we collect automatically
| Data | Why |
|---|---|
| Precise location — GPS traces of runs, route geometry, open-run pins, live location shares | Recording your runs, placing open runs on the map, and live tracking when you turn it on |
| Coarse location — home city and approximate coordinates | Matching you with runners nearby |
| Health and fitness data — distance, pace, duration, elevation | Recording your runs and matching on pace |
| Device identifiers — your user ID and push notification token | Delivering notifications and linking your account to your device |
| Crash and error reports — what went wrong, the screen you were on, how long screens and requests took, your device model, operating system and app version, and your user ID | Finding and fixing crashes, errors and slow screens |
| Profile view records | Showing you who looked at your profile |
Location in the background. During an active run, Izuke continues to record your location while the app is in the background — otherwise the run would stop recording the moment you put your phone in your pocket. This happens only during a run you have started, and stops when the run ends.
3.3 Data from other sources
| Source | Data | When |
|---|---|---|
| Google, Apple, or Facebook | Your name, email address, and profile picture from the account you sign in with | When you create your account |
| Didit | The result of your identity verification | When you verify |
| Apple or Google, through RevenueCat | If you subscribe to Izuke Pro: your plan, whether it is a free trial, when it renews or ends, which store it was bought in, and whether a renewal payment failed. Never your card or payment details — purchases are handled entirely by Apple or Google | When you subscribe, renew, cancel, or a payment fails |
| Other Izuke users | Kudos and reports about you after a run | When another user submits them |
3.4 Sensitive personal data
Some of what we collect is treated as sensitive personal data under Vietnamese law and needs your separate, explicit permission. We ask for each of these individually — never bundled into a single "agree to everything" checkbox:
- Biometric data — the selfie used for verification. This is the most sensitive information Izuke handles. Section 6 sets out exactly what happens to it.
- Precise location, including while the app is in the background during a run.
- Health and fitness data — your distance, pace, duration and elevation.
We do not share health data with insurers, employers, or advertisers. We do not use it to infer anything about you beyond matching you on pace.
04Why we process your data, and on what legal basis
| Purpose | Legal basis |
|---|---|
| Creating and running your account | Performance of our contract with you |
| Matching you with running partners | Performance of our contract with you |
| Recording your runs and route data | Performance of our contract with you |
| Verifying you are a real person (selfie liveness check) | Your explicit consent |
| Processing location to find nearby runners | Your explicit consent |
| Live location sharing during a run | Your explicit consent, given each time you switch it on |
| Safe Meetup live link, and safety texts to your emergency contacts | Your explicit consent, asked the first time you share; in an emergency, protecting your vital interests |
| Chat, comments, and race rooms | Performance of our contract with you |
| Generating and sharing Moment cards | Performance of our contract, plus your consent for sharing |
| Investigating reports, ratings, and safety incidents | Our legitimate interest in user safety, and legal obligation |
| Preventing fraud and fake accounts | Our legitimate interest, and legal obligation |
| Service messages (run confirmations, safety notices) | Performance of our contract |
| Community event and marketing messages | Your consent — separate, and withdrawable |
| Izuke Pro: providing it, keeping it in step with your store subscription, and reminding you before a free trial or Pro ends | Performance of our contract |
You can withdraw any consent at any time. Withdrawing consent doesn't make anything we did beforehand unlawful, and we'll tell you plainly what stops working if you do.
05Location: how it actually works
This is the part most worth reading.
Five different things happen with your location, and they work differently.
1. Finding people nearby. For matching and discovery, other runners see only your general area — your home city and an approximate position. Never a street, never a pin on your home, never your live position. Zooming in on the map does not buy more precision; the coarsening happens on our servers before the data reaches anyone else's phone.
2. Recording your runs. When you start a run, Izuke records your GPS trace and route, including while the app is in the background. This is how the run gets recorded at all. It stops when the run ends. Your route data is yours — we don't show your route maps to other runners unless you choose to post a route.
3. Live location sharing. You can switch on live location during a run so a specific person can see where you are. This is off unless you turn it on, it's shared only with whoever you choose, and live location shares are deleted after one hour.
4. Activities on the map. An activity you post appears as a pin any Izuke user can see. The pin is placed within about a kilometre of where you actually are rather than on the spot, and an activity carries no exact meeting point — only the day, the time and roughly where.
5. A live link for someone you trust (Safe Meetup). Before you meet someone, you can send a link to a person you choose. Anyone with that link can see, on a web page and without an Izuke account, your live location, the meetup's time and place, and the first name, photo and verified badge of who you're meeting. It is off unless you start it, it runs only until an hour after the meetup ends or until you say you're safe (including while your phone is locked), and the person you're meeting isn't told. The page is hidden from search engines. Your location is deleted the moment sharing ends, and the record of the share 7 days later.
SOS and missed check-ins. At the end of a meetup the app asks whether you're all right. If you press SOS, or don't answer within 10 minutes, we send one text message to each of your emergency contacts with a link to your live location. Your emergency contacts are people you add yourself; we use their details for nothing else. Please let them know you've added them. Izuke doesn't monitor these alerts — your contacts do — and we can't guarantee a text arrives.
What we never do:
- Track your location when you are not on a run or sharing a live link
- Show another runner your live position unless you have deliberately shared it with them
- Display your home or workplace address
- Sell or share location data with advertisers or data brokers
An honest limit. Coarse-area matching protects you well in a dense neighbourhood where your area holds hundreds of runners. It protects you less in a quiet district, at an unusual hour, or if your combination of goal, pace, and schedule is distinctive. Someone paying close attention may still be able to infer roughly where you run. We can't engineer this away without making the app unable to do the one thing it exists to do. You should know it, and factor it in.
Controlling your visibility. You are not stuck being visible:
- Hide my distance — stay matchable without showing how far away you are.
- Pause mode (part of Izuke Pro) — disappear from other runners' results entirely, without deleting your account or losing your history.
- Turn off location permission — in your device settings, at any time. Matching stops working; nothing else about your account is affected.
Meeting points. When you agree to a run, you and your partner agree on a meeting location. That location is shared between the two of you. We recommend a public, well-lit place. Never share your home address through Izuke.
06Identity verification
To become a verified runner, you take a quick selfie. We don't ask for an ID document. This is the most sensitive data Izuke touches, so here is exactly what happens to it.
Who processes it. Verification is carried out by Didit, a specialist identity verification provider, acting on our instructions. Didit checks that the selfie is of a live person rather than a photograph, a screen or a mask. That is the whole check: it confirms you are a real person, not who you are.
What is kept. Didit stores the selfie for a month after which the data is automatically deleted. Izuke receives and stores only the result — whether you passed — and never holds your selfie.
What it is never used for. Your verification images are not used for advertising, not used to train artificial intelligence models, and not sold, traded, or shared with anyone. We have explicitly opted out of model training.
Your choice. Verification is required to become a verified runner. You can ask us to delete your verification record at any time by emailing contact@izuke.app.
07What other people can see
Your profile
| Visible to other runners | Never visible to anyone |
|---|---|
| Name | Your email address |
| Profile photo | Your date of birth |
| Gender, if you shared it | Your verification selfie |
| General area | Your precise location |
| Pace and running history | Your GPS route traces, unless you post a route |
| Verified badge, if you have it | Reports you have filed |
| Kudos from past runs (only a count not comment) | Runners you have blocked |
| Route posts, comments, and race-room posts you make | Your private chat messages |
When someone you meet shares a live link
If a runner you're meeting sends a Safe Meetup link to someone they trust, that person can see your first name, profile photo and verified badge, and the meetup's time and place — the same things you'd see of each other in person. Never your full name, contact details or location. The link stops working when their meetup ends.
Photos and media are served from public web addresses
This matters and we would rather be plain about it than reassuring.
Your avatar, profile photo, moment cards, route posts, club media, and feedback media are stored at web addresses that anyone holding the link can open, without an Izuke account. Chat images are the exception — those are private.
What this means in practice:
- Someone with the link to your profile photo can open it whether or not they use Izuke.
- A link, once shared or saved by someone else, keeps working. Blocking that person does not revoke it.
- Search engines and image-search tools may be able to index publicly linked images.
What you can do: treat your profile photo as a public photograph. Use one you would be comfortable seeing elsewhere on the internet. You can change or remove it at any time in Settings.
08Moment cards and sharing
After a run or an activity, you can make a Moment card: a photo you choose, with the title you give it, the run's distance, pace and time when there is a recorded run, and the Izuke logo.
- No names on the card. The card shows nobody's name, yours or anyone else's.
- Each person makes their own. A Moment is saved to your history only. The people you ran with make their own if they want one. Your saved Moment notes who you ran with, which only you see in your own Moments.
- Sharing is never automatic. A card leaves Izuke only when you tap to share it.
- The photo is yours to choose. If it shows other people, sharing the card shares their image too, so ask them first.
- Once you export a card to Instagram, WhatsApp, TikTok, or anywhere else, it's governed by that platform's rules, not ours. We can't retrieve or delete it.
- Moment cards are stored at public web addresses, as described in Section 7.
09Safety: kudos, reports, and blocks
After a run or an activity you can give the other person kudos, and you can report a problem. These work differently from the rest of your data.
- Kudos are a count, not a score. There is no rating out of five. You either give kudos or you don't, and a profile shows the total received. There is nothing to average, and no way to give a bad one.
- We record who gave which kudos, so that one can only be given once per run and can be taken back. The app never displays it.
- Reports are confidential. If you report someone, we do not tell them who reported them. This is deliberate and non-negotiable — a reporting system that exposes reporters is a system nobody uses.
- Blocking is silent. The blocked user isn't notified.
- We review reports and may warn, suspend, or permanently remove accounts. We keep a record of a removed account to stop that person re-registering.
- Where a report involves a credible risk of harm, we may share information with law enforcement.
- If you say a run wasn't good, we record that and anything you write with it. The other runner is never shown it and it does not affect their kudos. We use it only when reviewing a report.
On your right of access: you can ask what data we hold about you, including kudos and the substance of reports. We will provide it — but we will redact anything that would identify who reported or rated you, and anything that would compromise an ongoing safety investigation or put another person at risk.
10Who we share your data with
What we don't do
Izuke runs no analytics SDK and no advertising or tracking technology of any kind. There is no Google Analytics, no Facebook Pixel, no advertising identifier, no attribution tracker, no data broker. We do not sell your personal data, we do not share it for advertising, and we never have.
Very few apps can say this. We can, and we intend to keep it that way.
We do run one crash reporter. When the app crashes or hits an error, or something fails on our servers, a report goes to Sentry, hosted in the EU, so we can find and fix the problem. A report says what went wrong and where, and for the app also your device model, operating system and app version, and your user ID, a random identifier rather than your name. It never includes your name, email address, messages, photos or location, and we don't use it to follow what you do in the app.
Service providers who work on our behalf
| Provider | What they do | Where |
|---|---|---|
| Supabase | Database, storage, authentication, hosting | Ireland (EU) |
| Didit | Selfie liveness check for verification | EU |
| Sign-In, Maps, and Places — Maps and Places receive location data to show you the map; Google Play, if you subscribe to Izuke Pro on Android | Global | |
| Firebase Cloud Messaging (Google) | Push notifications | Global |
| Apple | Sign in with Apple; the App Store, if you subscribe to Izuke Pro on an iPhone | Global |
| RevenueCat | Manages Izuke Pro subscriptions across the App Store and Google Play. Receives your user ID (a random identifier, not your name or email) and your purchase and subscription details — never your card details | United States |
| Facebook (Meta) | Sign in with Facebook, if you choose it | Global |
| Resend | Sending service emails | Global |
| Twilio | Sending safety text messages to your emergency contacts (SOS and missed check-ins) | Global |
| Sentry | Crash and error reporting | EU (Germany) |
| Netlify and GitHub Pages | Hosting our website and app redirect links | Global |
These providers may only use your data to provide their service to us. They may not use it for their own purposes.
Google Fonts. Our app loads typefaces from Google's font service when it starts, which sends your IP address to Google. We are working to bundle these fonts into the app so this no longer happens.
Address lookup. When the app turns a place name into coordinates - search a city, or naming a meeting point - it uses your phone’s own geocoder. On an iPhone that sends the text to Apple; on an Android phone, to Google.
Others
Law enforcement and authorities — where we're legally required to, or where there's a credible risk to someone's life or safety.
A future acquirer — if Izuke is acquired or merges, your data may transfer. We'll tell you before it happens, and this policy continues to apply until you're given a new one.
11Storing your data outside Vietnam
Your data is stored and processed in Ireland, not in Vietnam. Our database, file storage and authentication run on Supabase infrastructure in Ireland. Our other service providers may access it from other countries.
We do this because it lets us run a faster, more reliable and better-secured service than we otherwise could. We protect it by:
- Contractually binding every overseas provider to protect your data to the standard Vietnamese law requires
- Encrypting data in transit and at rest
- Restricting access to the minimum number of people who need it
12How long we keep your data
| Data | Deleted after |
|---|---|
| Live location shares | 1 hour |
| Safe Meetup live links — your location | When sharing ends |
| Safe Meetup live links — the record, and any safety texts sent | 7 days after sharing ends |
| Emergency contacts | When you remove them, or delete your account |
| Match request log | 7 days |
| Profile view records | 30 days |
| Email media | 90 days |
| Feedback media | 6 months |
| Your runs, planned runs, moments, in-app feedback, profile and gallery photos | When you delete your account |
| Chat messages, routes you created, route posts, and comments, race entries, kudos you gave | Kept — see below |
| Account data | When you delete your account |
| Reports and safety records | [3 years] after the report, or longer where there's an ongoing investigation |
| Records of banned accounts | Kept, limited to the minimum needed to prevent re-registration |
| Consent records | For as long as required by law |
| Your Izuke Pro subscription status | When you delete your account (RevenueCat and the store keep their own purchase records under their policies) |
| Transaction records | As required by tax and accounting law |
| Notifications | 30 days once read, 90 days if unread |
| Crash and error reports | Up to 90 days |
| Records of account and moderation changes (for example a change of plan, a verification result, a report's outcome or a deleted account) | 3 years |
| Activities nobody joined | 7 days after they were due to start |
| Expired safety pins | 7 days after they expire |
| "Not good" answers and their comments | 12 months |
What survives deleting your account. Deleting your account removes your login, your profile details, your photo, your tracked and planned runs, your moments, your notifications and any feedback you send. Your name is removed from moments other runners saved.
What stays: your chat messages in other people's threads, routes you created and posts or comments you made on them, race entries, and kudos you have given. Removing those would delete other people's history along with yours. We also keep safety and report records, and the minimum record needed to enforce a ban.
If you told us a run wasn't good, that note stays too, for the same reason: it is about the other runner, not about you. Notes about you are deleted with your account.
Moment cards another runner saved, and anything either of you shared to another platform, are outside our control.
13Your rights
You have the right to:
- Know what data we hold about you and how we use it
- Access a copy of it
- Correct anything inaccurate
- Delete your data and your account
- Withdraw consent at any time
- Object to or restrict certain processing
- Take your data with you in a portable format
- Complain to us or to the authorities
Deleting your account: in the app, under Settings → Account. You do not need to email us or ask permission.
Everything else: in the app under Settings, or by emailing contact@izuke.app. We will acknowledge your request within 2 working days and give you a substantive response within 7 to 10 working days.
We may need to verify your identity first — this protects you from someone else requesting your data.
Withdrawing location consent. You can turn off location permission in your device settings at any time. Matching, run recording, and the map stop working, because they can't function without it. Your account, history and messages are unaffected.
Automated matching. Izuke's matching engine uses automated processing to suggest running partners based on your goal, schedule, location, and pace. It suggests — it never makes a decision with a legal or similarly significant effect on you, and you're always free to decline. You can ask us how the matching works and ask a human to review a decision you think is wrong.
Complaints. If you're unhappy with how we've handled your data, contact us first at contact@izuke.app. You can also complain to the Department of Cybersecurity and Hi-tech Crime Prevention (A05) under Vietnam's Ministry of Public Security.
14Security
We protect your data with encryption in transit and at rest, access controls limiting who on our team can see what, identity verification to keep out fake accounts, and monitoring for unusual access.
No system is perfectly secure, and we won't claim otherwise. If a breach occurs that affects your data, we'll notify you and the relevant authorities within the time limits the law requires.
What you can do: keep the account you sign in with secure, keep the app updated, and report anything that feels wrong.
15Age requirement
Izuke is for people aged 18 and over. We don't knowingly collect data from anyone under 18. If you're under 18, don't create an account.
If we learn that someone under 18 has created an account, we'll remove it and delete their data. If you believe a minor is using Izuke, contact us at contact@izuke.app.
Izuke has zero tolerance for child sexual abuse and exploitation. Our full commitments, and how to report a concern, are set out in our Child Safety Standards Policy.
16Changes to this policy
We'll update this policy as Izuke evolves. If a change materially affects how we use your data, we'll notify you in the app or by email before it takes effect, and where the law requires it, ask for your consent again. The "last updated" date at the top always reflects the current version.
17Contact
Izuke Pte. Ltd. 160 Robinson Road, #14-04 Singapore Business Federation Center Singapore 068914
All privacy questions and requests: contact@izuke.app Data Protection Officer: [DPO NAME AND CONTACT — appointment required, see Section 11 note]
Izuke — the strength you find when you show up together.