01Who this covers
This notice explains what RunAsOne does with personal data collected through this website, and applies to runners who register for events, people registered as part of someone else's group, and organizers who hold accounts here.
It is written to meet the Data Privacy Act of 2012 (Republic Act No. 10173) and its implementing rules.
02What we collect
Only what a race actually needs. Nothing on this list is optional decoration — each field ends up on a bib, in a kit order, in a results table, or in the hands of a marshal if something goes wrong on the course.
- For the person paying: name, email address, and mobile number, plus a delivery address and province when a race kit is being shipped.
- For each runner entered: first and last name, email address, mobile number, gender, date of birth, shirt size, running community, and any medical condition you choose to disclose.
- Emergency contact: the name and mobile number of the person to call if a runner needs help during the event.
- Payment records: the amount, the method, the order reference, and — for bank transfers — the reference number and the receipt image you upload. Card and e-wallet details are entered on the payment provider’s own page and never reach our servers.
- Consent record: whether the event waiver was accepted and the timestamp at which it was.
- Race results: bib number, name, gender, category and finishing times, once the organizer uploads them.
03Why we collect it
Each purpose below is the reason a specific field exists.
- To process your registration and payment, and to send you confirmation of both.
- To give the organizer the list they need to print bibs, order shirts in the right sizes, pack kits, and manage the start line.
- To reach a runner’s emergency contact if there is an incident during the event.
- To publish official results and generate e-certificates after the race.
- To answer support requests, verify a payment, and investigate disputed or fraudulent registrations.
04Health information
The medical conditions field is optional and is treated as sensitive personal information. It exists so that event medical staff can respond appropriately to a runner they are treating. It is visible only to the organizer of the event you entered, and is never used for marketing, profiling, or shared with anyone else.
05Who sees your data
- The organizer of the event you registered for. They receive the details of every runner in your registration, because they are the ones running the race.
- Our payment provider, which processes card and e-wallet payments and receives only what it needs to charge and confirm the transaction.
- Our hosting, database and file-storage providers, which hold the data on our behalf and are not permitted to use it for anything else.
- Anyone at all, but only for what a race is expected to publish: your name, bib number, category, gender and finishing time appear in public results. Your contact details, birthdate, address, emergency contact and medical notes never do.
06What we never do
We do not sell your personal data. We do not rent or trade contact lists. We do not pass your details to advertisers, and we do not use the medical field for anything other than the safety purpose it was collected for.
07How long we keep it
Registration and payment records are kept for as long as the organizer may need them to settle the event and for as long as tax and dispute-resolution obligations require.
Race results and e-certificates are kept indefinitely, because a finishing time is a public record a runner expects to be able to look up years later. Only the fields listed above as public are held that way.
Payment receipt images are kept only as long as they are needed to verify and settle the transaction they belong to.
08How it is protected
Data is held on managed infrastructure and transmitted over encrypted connections. Organizer passwords are stored hashed, never in readable form. Access to the admin areas is restricted to authenticated organizer accounts, and an organizer can only see registrations for their own events.
No system is perfect. If a breach occurs that puts your data at serious risk, we will notify you and the National Privacy Commission as the law requires.
09Registering someone else
When you enter another person into a race, you are giving us their personal data. You must have their permission to do so, and you must have shown them the event waiver before you accept it on their behalf. They hold the same rights over their data as you do over yours, and can exercise them directly with us.
10Your rights
Under the Data Privacy Act you may ask to see the personal data we hold about you, have it corrected if it is wrong, object to how it is being processed, ask for it to be erased or blocked where the law allows, receive a copy in a portable form, and complain to the National Privacy Commission.
To exercise any of these, email info@cresendorunningcommunity.com from the address on your registration and tell us what you need. We will respond within a reasonable period.
Two limits worth stating plainly: we cannot erase data an organizer is legally required to keep for tax or dispute purposes, and a published finishing time is a public race record.
12Changes and contact
We will update this notice as the platform changes, and the date at the top always tells you when it was last rewritten.
For anything on this page — a question, a request, or a complaint — write to info@cresendorunningcommunity.com.
Data Privacy Act of 2012
Privacy Policy
What we collect when you register for a race, why each field exists, who gets to see it, and how to get it corrected or removed.
Last updated September 5, 2026