Privacy Notice

Version 10, effective Thu, 29 Oct 2026

RunLokal is a product of Vanguard AI Analytics, Inc., a corporation organized under the laws of the Republic of the Philippines, which owns and operates the RunLokal website at runlokal.com and its related services ("RunLokal", "we", "us", "our"). We are the personal information controller for the personal information described in this notice. We process it in accordance with the Data Privacy Act of 2012 (Republic Act No. 10173), its Implementing Rules and Regulations, and the issuances of the National Privacy Commission.

This notice explains what we collect, why, who we share it with, how long we keep it, how we protect it and what your rights are. Read it together with our Terms of Use.

1. Information we collect

Your account

Your first and last name, your email address and your password. We store your password only as a one-way hash, so it cannot be read back.
Whether you have confirmed your email address, and when you created your account.
If you sign in with Google: the name, email address and profile picture that Google shares with us, an identifier for your Google account, and the tokens Google gives us to sign you in.

Your profile, which your public page shows

Your handle: the address of your page, which we usually make from your name. We also keep the handles you used before.
Your display name, which is your first and last name unless you choose another.
Your photo, if you add one. Before we store it, we remove its location and other hidden details.
Your home city, if you choose one.

Your private runner details, if you add them

Your birthday, gender and mobile number.
The name and mobile number of your emergency contact. You must have their permission to give us their details.
A shipping address, if you save one: the name of the person who receives the kit, a mobile number, the street address, the barangay, the city or municipality, the province and the postal code. You can replace it at your next registration, or delete it from your account page at any time.

Your birthday shows your age, which the Data Privacy Act treats as sensitive personal information. We collect it only if you choose to give it.

Your walks and runs, if you use the RunLokal app

The workouts that the app reads from Health Connect (on Android) or Apple Health (on iPhone): for each, its type of activity (such as a run or a walk), its start and end, its distance, its steps and the elevation gained, the app that recorded it, how it was recorded (automatically or entered by hand), the model of the device that recorded it (such as a Samsung S24 or an iPhone, never the name you gave the device), and its route (the GPS points of the run) when the source gives one. This is health and fitness data, and a route is location data. When you record a walk or run in the app, it reads your location while it records, and your steps.
The app uploads the walks and runs it reads, from about 30 days before it first reads them (or from the start of a virtual event you joined, if that is earlier), and those you record in the app. It does not upload other activities, such as cycling.
The route of a workout is visible only to you. It is never shown on a leaderboard and never given to an organizer.
Your push token: a code that identifies your phone to a push service, so that we can send it notifications. You can turn the notifications off (section 2).
What we work out from a workout: whether it counts toward a registration, and the distance and finish recorded for the registration.

Registrations, if you register for an event

What you enter about each participant, yourself included: first and last name, birthday, gender, the category chosen, and an email address and a mobile number (both optional for a participant who is a minor), and the emergency contact's name and mobile number. You must have each person's permission, or for a child their parent's or guardian's, to give us these details.
Your own name and email address as the person who pays, the order (its time, status and amount) and, for each participant, the registration (a reference, the price and fee, and its status).
That the waiver and release was accepted, when, and for which participants, and which version of the event's waiver it was.
If you choose shipping for a kit: the shipping address you enter for the participant (the name of the person who receives it, a mobile number, the street address, the barangay, the city or municipality, the province and the postal code), the shipping fee, and the kit and size chosen. We keep a copy of the address with the registration.
For a paid order, the payment's reference and status that the payment gateway gives us. Your card or wallet details are handled by the payment gateway, and RunLokal never receives or stores them.
If you ask to join a private event: your name, your email address and the message you write.

Organizers and events, if you create an organizer

The organizer's name, its address on RunLokal (and the ones it used before), its kind, its description, its logo, its header photo, its contact email and the addresses of its Facebook and Instagram pages.
Its events: what you write about each one, its photos, and the YouTube videos you add to it. Before we store a logo, a header photo or a photo, we remove its location and other hidden details.
That your account owns the organizer.
For payouts, the bank account of the organizer: the name of the bank, the account number, the name of the account holder, whether the holder is a person or an organization, and the holder's address and city. We also keep what the organizer earns, its payouts and any amounts withheld or adjusted.
If the owner of an organizer asks to be verified, the document they send: a business registration, or a government ID, with the name, photo, birth date and number on it.
Which versions of the Organizer Agreement you accepted, for which organizer and when, with the network address and browser you used.
Important changes to the organizer and its events, such as creating, publishing, closing or deleting them, in our audit log.

Records of your account

Your sign-in sessions, each with the network address (IP address) and browser it came from, and your two-factor authentication settings if you turn it on.
Which versions of the Terms of Use and this notice you accepted and when, with the network address and browser you used.
Important changes to your account, such as a new handle or the deletion of your account, with the network address they came from, in our audit log.

Emails

Copies of the emails we send you, such as the confirmation of a registration. The confirmation we send to each participant who has an email address also invites that person to create an account with that email address, when no confirmed account has it yet.
The emails you send to [email protected].

Technical data

Our servers log each request to RunLokal, with the network address, the browser and the page requested.
Our own cookies keep you signed in and protect your session and the site.
Where an event page shows a map background, your browser loads map images from our map provider, which receives your IP address, browser details and the part of the map shown, to draw the map.

Google Analytics, on our public pages

We use Google Analytics on the pages anyone can open: the home page, event pages, organizer pages, runners' public pages, and the Terms of Use, this notice and the Organizer Agreement. It is not used on sign-in or sign-up pages, in your account, in the organizer dashboard or anywhere else. When you open one of these pages, Google Analytics collects:

the page you visited and the page you came from, without the part of the address after a question mark; if you came from another website, only that website's address. The address of a runner's public page includes the runner's handle, so when someone else opens your page, its address, with your handle, is sent to Google Analytics. While you are signed in, your visits to your own page are not measured, and its address is not passed on when you go from it to another page;
your device, browser and screen size, and your approximate location, such as your city and country, which it works out from your network address;
a random identifier for your browser, kept in cookies named _ga and _ga_ followed by an identifier of our Google Analytics property.

It does not collect your name, your email address or anything else from your account. We do not use advertising cookies.

2. Why we use it, and our legal basis

The Data Privacy Act of 2012 allows us to process personal information only on a lawful basis. We use yours for these purposes, on these bases:

To create and run your account: confirming your email address, signing you in, keeping your account secure and sending you emails about it, such as a link to reset your password or a notice that your password was changed. Basis: our contract with you (Sec. 12(b)).
To show your public page, while it is public. Basis: our contract with you (Sec. 12(b)).
To run your organizers: showing their pages and their events' pages, listing their events on the home page and in search, and sending you emails about them, such as a notice that one of their events was put on hold. Basis: our contract with you (Sec. 12(b)). For an organizer whose owner has deleted their account, we keep its published pages on our legitimate interests in keeping the events that runners have seen, and their history, available (Sec. 12(f)).
To take your registration and payment: holding a slot, confirming it, taking the payment through the payment gateway, emailing the confirmations, showing you your registrations, and giving the participants' details to the organizer of the event. Basis: our contract with you (Sec. 12(b)) and, for the details of the people you register, your confirmation that you may give them.
To deliver a kit: when you choose shipping, asking you for a shipping address, keeping a copy of it with the registration, and showing it to the event's organizer so that it can deliver the kit; and, if you choose to save an address to your profile, filling it in for your next order. Basis: our contract with you (Sec. 12(b)) and, for the address of another participant, your confirmation that you may give it.
To show you your walks and runs, and count them toward virtual events you joined: reading your workouts in the app, uploading your walks and runs, showing them to you in Activity, adding up your distance for an event from those inside its dates, and showing your progress to you. Basis: our contract with you (Sec. 12(b)) and, for health and fitness data, your consent (Sec. 13(a)), which you give by connecting the app to Health Connect or Apple Health and which you can withdraw by disconnecting it and deleting your workouts. We use steps only to check that a distance is plausible. We use a route only to show it to you.
To show the leaderboard of a virtual event: your distance and finish appear on it. Your name and handle appear only if your public page is on and set to show your events; otherwise it shows "Runner". Basis: our contract with you (Sec. 12(b)).
To let an organizer decide a flagged run: when a workout looks wrong, for example too fast, or too few steps for its distance, the organizer of the event sees its start, distance, duration, pace and steps, and why it was flagged, including whether it was entered by hand or recorded automatically. The organizer decides whether it counts. Basis: our contract with you (Sec. 12(b)).
To send you notifications from the app: that a run was counted, and reminders about events you joined, through your phone's push service. Basis: our contract with you (Sec. 12(b)). You can turn each of the two kinds off in the app.
To link a registration to an account: when a participant's email address is the confirmed email address of a RunLokal account, the registration shows in that person's list of registrations. Linking does not change the person's profile and does not put the registration on their runner page. Basis: our legitimate interests (Sec. 12(f)).
To keep your private runner details in your account and show them to you. When your registration of yourself is confirmed, the details you entered for yourself (your birthday, gender, mobile number and emergency contact) fill any of these details that are empty in your account; they never replace details you have already saved. Registering someone else, or being registered by someone else, never changes them. The details in a registration are shared with the event's organizer (section 3). Basis: your consent (Sec. 12(a)) and, for your birthday, your consent to the processing of sensitive personal information (Sec. 13(a)). You can remove these details at any time.
To pay organizers: keeping the bank account of an organizer, working out what it is owed, sending its payouts to that bank account through the payment gateway, checking our payouts against the payment gateway's records, and sending the owner emails about them. Basis: our contract with you (Sec. 12(b)) and our legal obligations (Sec. 12(c)), for example for tax.
To verify an organizer and review reports: We use a verification document only to check that an organizer's bank account belongs to the person or business named on it, and to show the Verified organizer badge. Our basis is our legitimate interest in preventing fraud on RunLokal. We use a report only to review the event reported.
To record what you accepted: which versions of the Terms of Use, this notice and the Organizer Agreement you accepted, as evidence of what we agreed. Basis: our legitimate interests (Sec. 12(f)).
To protect RunLokal and its users: limiting repeated attempts to sign in, sign up or reset a password, keeping records of sessions and of important account changes, finding and stopping misuse, and dealing with reports about content: putting events on hold, and suspending, clearing or removing organizers. Basis: our legitimate interests in a safe and secure service (Sec. 12(f)).
To understand how RunLokal is used: counting visits to our public pages, which of them people open and where they arrive from, with Google Analytics, so that we can improve RunLokal. Basis: our legitimate interests in understanding and improving our service (Sec. 12(f)). You can opt out at any time, as section 8 explains.
To answer your messages and requests, including requests about your personal information. Basis: our legitimate interests (Sec. 12(f)) and our obligations under the Data Privacy Act (Sec. 12(c)).
To comply with the law and with lawful requests from courts and government agencies, and to establish, exercise or defend legal claims. Basis: our legal obligations (Sec. 12(c)), our legitimate interests (Sec. 12(f)) and, for sensitive personal information, Sec. 13(f).

We never sell your personal information, and that includes your workouts, your routes and your push token. We do not use it for advertising, and we share your workouts with no one beyond what section 3 says. We do not send you marketing emails, and we do not make decisions about you by automated means alone that have legal or similarly significant effects on you.

3. Who we share it with

Everyone, through your public page: while your page is public, anyone, including search engines, can see your handle, display name, photo and home city.
Everyone, through organizer and event pages: what an organizer publishes, as section 4 explains.
The leaderboard of a virtual event, which anyone who can open the event's page can see: your rank, distance and finish, the number of milestones you unlocked, and your name and handle only if your public page is on and set to show your events. Otherwise it shows "Runner". Your routes and your other workout details are never on it.
The organizer of a virtual event, for a flagged run only: when a workout is flagged for review, the organizer sees its start, distance, duration, pace and steps, with your registration, and why it was flagged, including whether it was entered by hand or recorded automatically. It uses them to decide whether the run counts. The organizer never sees a route. Your other workouts are not shown to it, and it also sees the distance and finish recorded for your registration, like the rest of the registration.
The organizer of an event you register for, which receives the details of every participant it has registered, your name and email address as the person who paid, and the waiver acceptance. For a kit that you choose to have shipped, it also receives the shipping address, which it sees to deliver the kit. It uses them to run the event. It is a separate controller of the information it receives, and its use of it is governed by the Organizer Agreement and the law. For a private event you ask to join, the organizer also receives your name, email address and message.
RunLokal's admins, for verification documents and reports: A verification document is seen only by the organizer's owner or admin who sent it and RunLokal's admins. A report is seen only by RunLokal's admins; we do not tell the organizer who reported its event.
Our service providers, which handle personal information for us under terms that require them to protect it:
- The payment gateway takes and processes your payment, so it receives your name, your email address and the amount, and your card or wallet details, which RunLokal never receives or stores.
- The payment gateway also makes the payouts to organizers, so it receives the bank, the account number, the holder's name, whether the holder is a person or an organization, and the holder's address of an organizer's bank account, and the amount, to make the transfer.
- DigitalOcean hosts our server, our database and the storage for photos, in Singapore. Its content delivery network delivers photos to browsers, so it receives your network address and browser details when a photo loads.
- Cloudflare carries and protects the traffic between your browser and runlokal.com, so what you send to runlokal.com and the pages it sends back pass through Cloudflare.
- Resend sends our emails, so it handles your email address and what our emails to you say.
- Expo, and Apple's or Google's push services, deliver the notifications that the app shows. We send the notification to Expo's push service with your push token, and Expo passes it to Apple's or Google's push service, which delivers it to your phone. A notification says that a run was counted or reminds you of an event, so the text of it passes through them.
- Our map provider draws the maps behind some event pages. Where an event page shows a map background, your browser loads map images from it, so it receives your IP address, browser details and the part of the map shown, to draw the map.
- Google runs our [email protected] mailbox (Google Workspace), so it holds the emails you send us and our replies.
- Google also provides Google Analytics, so it receives the information about visits to our public pages that section 1 describes. We have turned off Google signals and ad personalisation for it, so it is not used to show you ads.
Google, when you choose to sign in with Google: Google confirms who you are to us, and so learns that you use RunLokal. Google handles that under its own privacy policy.
YouTube, when an event page shows a video: the page loads the video from YouTube's privacy-enhanced service (youtube-nocookie.com), so YouTube, which is part of Google, receives your network address and browser details when you open the page, and learns what you do with the video if you play it. YouTube handles that under Google's own privacy policy.
Government and law enforcement: the National Privacy Commission, courts and law enforcement agencies, when the law requires or allows it.
Professional advisers, such as lawyers and auditors, who must keep it confidential.
A successor business, if Vanguard AI Analytics, Inc. is involved in a merger, acquisition or sale of assets. It must handle your personal information as this notice describes.

4. Organizer pages and what organizers publish

What is public. An organizer's page shows its name, its kind, its description, its logo, its header photo, its contact email, links to its Facebook and Instagram pages, and its events, from the time the organizer publishes its first event. Each published event's page shows what the organizer wrote about it, with its photos and videos. Anyone can see these pages, and search engines may list them. Anything on them can be seen, copied or saved by others, and later changes do not remove the copies they made.
What is never shown. Organizer and event pages never show the name, email address or runner profile of the account that owns the organizer. What an organizer publishes is its owner's choice: if you use your own name or photo for an organizer, it is public.
Registrants. An organizer sees the details of the people registered for its events, to run them, and may keep them for its own records. When an account is deleted, the registrations it made, and the details in them, stay with the organizer and in our records of the order, as section 6 explains.
Closed organizers. An organizer that has published an event cannot be deleted, only closed, by its owner or when its owner deletes their account. A closed organizer's pages, and its events' pages, upcoming events included, stay public. When its owner deletes their account, the organizer is kept without an owner.
Handing over. RunLokal may hand an organizer that has no owner to another account, which then becomes its owner and can change what it publishes.
Erasing an organizer. To ask us to erase an organizer, for example one that shows your name or photo, write to [email protected]. Once we have checked the request, an admin removes the organizer: its page and every one of its events' pages are no longer shown, and its name, description, logo, header photo, links, and its events' descriptions and photos, are deleted. Its address on RunLokal stays reserved.
Never published. An organizer that has never published an event is deleted, with its drafts and their photos, when its owner deletes it or deletes their account.

5. Transfers outside the Philippines

Our service providers store and process personal information outside the Philippines. DigitalOcean keeps our server, our database and the storage for photos in Singapore, and its content delivery network keeps copies of public photos in other countries so that they load quickly. Cloudflare, Resend and Google may process personal information in other countries where they operate, and Google processes and stores Google Analytics information outside the Philippines. We remain responsible for your personal information when it is transferred, and we use contractual and other reasonable means to protect it, as the Data Privacy Act requires.

6. How long we keep it

We keep personal information only for as long as we need it:

Your account, profile and private runner details: while your account exists. You can change your profile, and remove your photo, home city, private runner details and saved shipping address, at any time. The saved shipping address is deleted with your account.
When you delete your account, we immediately erase your account, your sessions, your profile, your private runner details and your saved shipping address, and we delete your photo from storage straight after. Copies of your photo held by DigitalOcean's content delivery network expire shortly after that. Organizers you own are kept or deleted as section 4 explains. You can delete your account once what you still run is finished: while an organizer you own has an upcoming published event, or a partner you own has a coupon that is still live, first cancel or wait out your upcoming events, and close your partners. A partner is an account for a brand that sponsors runs with coupons; when a runner redeems one of its coupons, the brand is shown the time and the code of the redemption, never the runner's name, handle, email or photo.
Your workouts, routes and push token: until you delete them. In the app you can delete a workout, or all of them, at any time; deleting a workout deletes its route. Your push token is deleted when you sign out of the app, and when the push service reports it dead. When you delete your account, we delete all your workouts, with their routes, and your push tokens at once.
The results of a virtual event: a result is the distance and finish recorded for a registration, and it stays with the registration as the organizer's record of who took part, like the rest of the registration (the next item). When you delete a workout or your account, the results it counted toward are worked out again from your remaining workouts, so the distance can fall. A result becomes final about 9 days after the event's dates end: 2 days after, the worker freezes it, and 7 days after that it is final. Once it is final, it stays as it is, with its distance and finish time, even if you delete a workout or your account. After your account is deleted, every one of your results shows as "Runner", with no name or handle.
Registrations and orders: the details of a registration, the order and the payment reference are kept after you delete your account, with the event's organizer and in our records, as the organizer's record of who took part and for as long as we may need them to show what was paid and agreed. Deleting your account does not remove them. The copy of a shipping address on a registration is part of the registration record, so it stays too, with the organizer who delivers the kit. The address you saved to your profile is not: it is deleted with your account.
An organizer's bank account and payout records: the bank account details are kept while the organizer exists, including after it is closed or removed and after its owner deletes their account. When the owner saves another account, the earlier one is kept too, marked as replaced, because the payouts sent to it refer to it. An organizer that is deleted (section 4) is deleted with its bank accounts. The payout records (what an organizer earned, what was paid or withheld, adjustments, and the bank account each payout went to) are kept after the organizer is closed or removed, and after its owner deletes their account, at least for as long as the law requires us to keep financial and tax records and as we may need them to establish or defend legal claims. The owner's emails about payouts name a bank account only by its bank and its last four digits.
Organizers and their events: while the organizer exists, including after it is closed and after its owner deletes their account. When an admin removes an organizer (section 4), we delete its name, description, logo, header photo and links, and its events' descriptions and photos, with their files; the rest of its events' details, such as their titles, dates, venues, prices and waivers, are kept with the removed organizer, and are no longer shown. A logo, header photo or photo is deleted from storage shortly after it is replaced, removed or cleared, or after its event or organizer is deleted or removed.
Verification documents and reports: We delete a verification document 30 days after it is rejected or withdrawn or stops being current, and when the organizer is removed or deleted. We keep the record that a document was approved or rejected. We keep a report with the event it is about.
Records of what you accepted, and our audit log: kept after you delete your account, as evidence of what was agreed and done, for as long as we may need them to show that we met our obligations or to establish or defend legal claims. They refer to your account only by its internal identifier, not by your name or email address.
An organizer's decisions and manual distances: an organizer's decision to approve or reject a flagged run is kept with the run for as long as the workout exists, and is deleted with the workout, and it is also in our audit log. A manual distance an organizer adds, with the reason the organizer wrote, is kept with the registration. These records name the registration, whose record holds the participant's name, and hold no route.
Your handles: every handle your page has used stays reserved permanently, with your account's internal identifier, so that no one else can take an address that was yours.
Copies of the emails we send you: at most 30 days. When you delete your account, we remove the copies sent to its current email address at once, apart from the email that confirms the deletion.
Sign-in sessions: until you sign out or the session expires, at most 30 days after you last used it.
Emails you send us: for as long as we need them to answer you and to keep a record of what you asked.
Server logs: until newer entries replace them.
Google Analytics: Google keeps the information about your visits, linked to the cookie identifier, for 2 months, and then deletes it. Reports that only count visits, and identify no one, may be kept longer. The _ga cookies expire 2 years after your last visit to a public page, unless you delete them sooner.

Our backups hold copies of this information, so a copy of something deleted can remain in a backup until that backup is itself deleted. We use backups only to restore RunLokal after a failure.

7. How we protect it

We use organizational, physical and technical measures suited to the risk, including:

encryption of every connection to RunLokal (HTTPS), and of the connection between our server and our database;
encryption at rest of our database and photo storage, by our hosting provider;
passwords stored only as one-way hashes;
access to personal information only for authorized staff who need it, with two-factor authentication required for administrators;
records of acceptances and an audit log that RunLokal can add to but cannot change or delete;
limits on repeated attempts to sign in, sign up or reset a password.

No system is perfectly secure. If a personal data breach puts you at real risk of serious harm, we will notify you and the National Privacy Commission as the law requires.

8. Your rights

Under the Data Privacy Act, you have the right to:

be informed about how we process your personal information, which is what this notice does;
access it: you can see your profile and private runner details in your account at any time, and ask us by email for a copy of the rest;
correct it: you can change your profile and private runner details yourself, and ask us by email to correct anything else;
erasure or blocking: you can delete your account yourself in your account settings, and ask us to block or remove personal information that is incomplete, outdated, false, unlawfully obtained or no longer needed, including an organizer that shows it (section 4);
object to processing, and withdraw your consent where we rely on it, for example by removing your private runner details or deleting your account;
remove a registration from your account: a registration that is linked to your account by your email address can be removed from your list in your account at any time, and is not linked again; the organizer keeps its record of it;
data portability: ask us by email, and we will send you a copy of your personal information in a common electronic format;
damages, if you suffer harm because personal information about you was inaccurate, incomplete, outdated, false, unlawfully obtained or used without authority; and
file a complaint with the National Privacy Commission (privacy.gov.ph).

To stop Google Analytics from measuring your visits, you do not need to ask us: install Google's Google Analytics opt-out browser add-on, which stops it altogether. You can also block or delete the _ga cookies in your browser: Google Analytics then no longer links your later visits to your earlier ones, although it still counts the pages you open. RunLokal needs its own sign-in cookies, so do not block all cookies from runlokal.com, or you will not be able to sign in.

To use any of these rights, email our Data Protection Officer at [email protected]. We may first need to confirm that the request comes from you, and we will answer within a reasonable time. Some information is kept even after you ask us to erase it, such as the records of what you accepted, as section 6 explains. Withdrawing your consent does not affect what we did before you withdrew it.

9. Children

RunLokal does not set a minimum age for an account. A parent, guardian or other adult can register a child for an event. For a participant under 18 on the day of the event, we hold the name, birthday, gender, the emergency contact and, if given, the email address and mobile number. The waiver is accepted for the child by the person registering, as their parent or guardian. The details are shared with the event's organizer like any participant's.

When a person saves a birthday that makes them under 18 for the first time, or registers themselves with such a birthday, their public runner page and its list of events are hidden by default. They can turn either back on in their privacy settings. If you want us to delete the details of a child, or the account of someone under 18, write to [email protected].

10. Changes to this notice

We may update this notice. We will post the new version on this page with its effective date and, if a change is material, ask you to accept the new version before you continue to use your account.

11. Contact

For questions about this notice or your personal information, or to use your rights, write to our Data Protection Officer.

Data Protection Officer, Vanguard AI Analytics, Inc., operator of RunLokal

Email: [email protected]