Organizer Agreement
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"). In this agreement, "we", "us" and "our" mean Vanguard AI Analytics, Inc.
This Organizer Agreement covers the organizers you own on RunLokal and the events they publish. It adds to our Terms of Use and our Privacy Notice. If this agreement and the Terms of Use differ on anything about an organizer or its events, this agreement applies.
1. Who this agreement is between
1.1. This agreement is between you and Vanguard AI Analytics, Inc. "You" means the person whose RunLokal account owns an organizer. An organizer is a page on RunLokal for a person, a club or group, or a registered business that holds running events, together with the events it publishes.
1.2. You accept this agreement for each organizer: when you create it, when we hand it to you (section 8), and again when we publish a new version that is a material change (section 10). Until you have accepted, for an organizer, the last version of this agreement that was a material change, or a later one, you cannot use its dashboard.
1.3. If you create or own an organizer for a club, a group or a business, you confirm that you are authorized to act for it, and you accept this agreement on its behalf as well as your own.
1.4. When you tick the box or press "I agree" to accept this agreement, that is your electronic signature under the Electronic Commerce Act (Republic Act No. 8792). We may give you notices about your organizer by email or on RunLokal.
2. Your organizer and who may use it
2.1. Each organizer has one owner: the account that created it, or the account we handed it to. Only its owner can use its dashboard. Do not let anyone else use your account to manage it.
2.2. Choose your organizer's name, its address on RunLokal and its kind (Individual, Club or group, or Registered business) truthfully. Do not use a name, logo or address that belongs to someone else, or that suggests that you are someone you are not.
2.3. You are responsible for everything done through your organizer and for everything it publishes.
2.4. Your organizer's page is public from the time it publishes its first event. It shows its name, kind, description, logo, header photo, contact email, links to its Facebook and Instagram pages, and its events. It never shows your name, email address or runner profile as its owner, unless you put them in what the organizer publishes.
2.5. Until your organizer has published an event, you can delete it, with its drafts, and its address on RunLokal is then free for others to use. After that, you can close it but not delete it (section 8).
2.6. An admin. Despite 2.1, you may appoint one admin for your organizer, by an invitation to an email address. An admin acts for your organizer and can use its dashboard, except for what is the owner's alone: its bank account, its team, and closing, deleting or reopening it. An admin accepts this agreement for the organizer when they join, and again when we publish a new version that is a material change. You remain responsible for everything an admin does for your organizer, as for what you do yourself (2.3). You can remove the admin at any time, and the admin can leave.
3. Your events: accuracy, safety, permits and insurance
3.1. You are the organizer of every event your organizer publishes. RunLokal does not organize, run, supervise or insure it, and does not check what you publish.
3.2. Accuracy. Keep each event's page accurate and up to date: its date and time, venue, route and distances, prices, slots, inclusions, waiver and anything else that a runner relies on. If something changes, change the page. If the event will not take place, cancel it on RunLokal, unless your organizer is suspended (section 7.3).
3.3. Safety. You are responsible for the safety of everyone who takes part in your event, including a safe route, enough marshals, water and medical support, and the management of traffic, as the event calls for and the law requires.
3.4. Permits. Get every permit, clearance and permission that your event needs, from the local government, the owners of its roads and venues and anyone else, before the event takes place.
3.5. Insurance. Have the insurance that the law requires for your event, and any other insurance that it calls for.
3.6. The waiver. Each event has a waiver for its runners. When you create an event, RunLokal fills its waiver in with a default text, which you can change. That text is a starting point, not legal advice. You are responsible for the waiver your event publishes, and for making it right for your event.
3.7. Follow the law in everything about your events, including the laws on consumer protection and data privacy.
3.8. Registrant data. RunLokal gives you the details of the people registered for your events, such as their names, birthdays, contact details and emergency contacts, and the waiver acceptance, so that you can run the event. Use them only to run that event and to keep your own records of it. Keep them safe. Do not sell them, share them with a sponsor or use them to advertise. Some registrants are children: take extra care with their details.
3.9. Private events. If you make an event private, only the people you approve, and people already registered, can see its page and register. A person who asks to join gives you their name, email address and a message. Use them only to decide on that request. You are responsible for who you approve.
3.10. Kits and shipping. If you sell kits with your event, you deliver them. Your event says whether a kit is for pickup, at the place and time you give, or for shipping to the participant. RunLokal does not ship anything and is not a courier: it does not pack, send, track or insure a kit, and a kit that is late, lost or damaged is a matter between you and the participant. When a participant chooses shipping, RunLokal gives you the shipping address they entered, with the registration. Use it only to deliver that kit, keep it safe, and treat it as registrant data under 3.8.
3.11. Virtual events: the review queue and manual distance. For a virtual event, RunLokal counts the workouts that runners upload, and sends a workout to your review queue when it looks wrong. You decide whether it counts; you may also add or take away a manual distance for a participant. Use the review queue and manual distance only to decide results fairly. Every manual distance must carry a reason that is true; do not give a reason that is false or invented. Your review shows you a flagged run's start, distance, duration, pace and steps, and never a route. Use those workout details for nothing else: do not keep, share, publish or sell them, or use them to advertise, and treat them as registrant data under 3.8.
4. Your content and our licence to display it
4.1. You keep ownership of what your organizer publishes: its name, description, logo and header photo, and its events' texts and photos ("your content").
4.2. You give Vanguard AI Analytics, Inc. a non-exclusive, worldwide, royalty-free licence to host, store, copy, adapt (for example, resize, crop or convert) and display your content, and to let our service providers do so for us, as needed to run RunLokal: to show it on your organizer's page and its events' pages, to list your events on RunLokal's home page and in its search, and to show it in the preview that appears when someone shares a link to one of those pages and in the information about those pages that search engines read.
4.3. The licence lasts while your content is on RunLokal, including after you close your organizer, after you delete your account and after we hand your organizer to another account (section 8), and for a reasonable time afterwards for copies in backups and in previews already shared.
4.4. You confirm that you have the rights needed to publish your content and to give us this licence: to its photos, logos and texts, including any sponsor's logo, and the permission of anyone shown in your photos. A YouTube video that you add to an event's page stays on YouTube, under YouTube's own terms.
4.5. Do not publish anyone's personal information without their permission.
5. RunLokal's fee
5.1. Creating an organizer and publishing events on RunLokal is free.
5.2. RunLokal charges a fee on each paid registration. The fee is set for each market and shown to runners with each price. In the Philippines it is 10% of your price for each participant, or ₱50, whichever is higher. A paid price is at least ₱100. Free registrations carry no fee.
5.3. For each event, you choose who pays the fee: the runner, on top of your price, or you, out of your price. Whoever pays it, each paid price must be at least ₱100, the minimum charge, so a price you pay the fee out of always leaves you something. A paid category priced under ₱100 cannot be registered for until you raise its price to at least ₱100.
5.4. The fee includes the costs of the payment gateway, which you do not pay separately.
5.5. RunLokal's fee is not returned to you or to the runner, whether or not a registration is refunded and including when an event is cancelled.
5.6. A change to the fee is a change to this agreement (section 10).
5.7. Shipping fees. Your organizer keeps shipping fees in full. If you charge a shipping fee for a kit, RunLokal charges no fee on it. It is part of your share, subject to the reserve and the rest of section 9.
5.8. Sponsorship fees. You may ask a brand a sponsorship fee when you invite it to sponsor your event. RunLokal collects it for you and charges 10% of it, paid by the brand or taken from your fee, as you choose in the invitation. The rest is yours and is paid out with your other earnings, under the same reserve. If you cancel the event or remove a brand's coupon, any refund of the fee is between you and the brand; RunLokal does not refund it.
6. All sales are final, and refunds are up to you
6.1. Every registration sold for your events through RunLokal is final: a runner cannot cancel it for a refund on RunLokal. Runners are told so before they pay: "All sales are final. Any refund is up to the organizer."
6.2. Refunds are your responsibility. If you refund a registration, you do it yourself, outside RunLokal. RunLokal does not decide on your refunds and does not make them for you.
6.3. Contact email. Each event has a contact email for refunds and questions. You must give one, keep it working and answer it. RunLokal shows it on your organizer's page, and to runners with the line "For a refund, contact" your organizer at that email.
6.4. Cancelled events. If you cancel an event, or it does not take place, you must honour each registration or refund it. RunLokal then cancels the registrations, emails each registrant, and lists the paid orders in your event's Refunds tab, with a CSV export, to help you. The refunds are up to you.
6.5. RunLokal's fee is not returned, including when an event is cancelled and when you refund a registration (section 5.5).
6.6. Late and double payments. If a payment arrives after its order ended, or a second payment arrives for an order that is already confirmed, RunLokal does not confirm it and refunds it to the payer itself. RunLokal makes no other refund unless the payment gateway, a bank or the law requires it.
6.7. Shipping fees. A refund of a shipping fee is up to you, like a refund of a price, under 6.2 and 6.4. If you cancel an event, or a kit is not delivered, you must deliver the kit or refund the shipping fee. RunLokal does not refund a shipping fee for you.
7. Holds, suspension, clearing and removal
7.1. We may take the steps below if we believe that your organizer or one of its events is false, unsafe or offensive, breaks this agreement, the Terms of Use or the law, or infringes someone's rights, and on a lawful request to erase personal information that it shows. We may take them without telling you first.
7.2. Hold. We may put an event on hold. While it is on hold, its page is not shown and it cannot be published, but you can still edit it, to fix what we raised. It keeps its status: when we release the hold, the event is back as it was.
7.3. Suspension. We may suspend your organizer. While it is suspended, you can open its dashboard and preview its events, but nothing else: you cannot create, edit, publish, unpublish or cancel its events, change its profile, or close it. Its page and its past events stay public, and we may put its upcoming events on hold. When we reinstate it, you can use it again, and we may release those holds.
7.4. Clearing. We may clear your organizer's logo, header photo, description or name. A cleared name is shown as "Organizer" until you change it.
7.5. Removal. We may remove your organizer. Its page and every one of its events' pages are then no longer shown; its name becomes "Removed organizer"; its description, logo, header photo, links, and its events' descriptions and photos, are deleted; and it no longer has an owner. Its address on RunLokal stays reserved.
7.6. Cancelling an event. If we believe that an event is fraudulent or seriously misleading, we may cancel it. Its registrations are cancelled and its registrants are told that it was cancelled. Your payouts may pause (9.9), and we may refund its runners (9.11).
7.7. We email you when we take one of these steps, and when we release a hold or reinstate your organizer, with our reason for a hold, a suspension or a clearing. To ask about a step we took, write to [email protected].
8. Closing your organizer, and ownerless organizers
8.1. You can close your organizer from its profile while it is active. While it is closed, you cannot create, edit or publish its events, but you can still cancel an upcoming event and open its dashboard. Its page and its events' pages, upcoming events included, stay public as they are, and its drafts are kept. RunLokal's team is told that it is closed, and may put any of its events on hold.
8.2. You can reopen your closed organizer from its profile, once you have accepted for it the last version of this agreement that was a material change, or a later one.
8.3. If you delete your account, each organizer you own that has published an event is kept without an owner: it is closed, or stays suspended if we have suspended it, and its pages, upcoming events included, stay public. An organizer you own that has never published an event is deleted with its drafts.
8.4. RunLokal may hand an organizer that has no owner to another account. That account becomes its owner, accepts this agreement for it, and can then change what it publishes, or close it, unless it is suspended (section 7.3). A closed organizer that we hand over is open again; a suspended one stays suspended.
9. Payouts and the reserve
9.1. RunLokal collects what runners pay for your events through the payment gateway, keeps its fee (section 5) and pays your share to your bank account. This section sets out how. It applies once RunLokal takes payments and sends payouts, which we will tell you before it happens.
9.2. Your bank account. Before RunLokal can pay you, the owner of your organizer must save a bank account for it, with the name of the account holder and the holder's address. The account name must match the bank's records for that account, and the account must be one that you are allowed to receive money in. If the name does not match, the bank may return the payout, and we may pause your payouts until you save a correct account. An event with a paid price can be published only once your organizer has a bank account. Saving a bank account, and publishing an event with a paid price, need you to have accepted this agreement. You are responsible for the bank details you save being correct. RunLokal sends each payout to the account saved for your organizer, and is not responsible for a payout that reaches a wrong account because of the details you gave. RunLokal does not recover money sent to such an account.
9.3. When we pay. RunLokal pays once a day, at 10:00 Manila time. It pays your share of the registrations whose payments the payment gateway has cleared and which are not held back for another reason in this section. A payout is sent to the bank account saved for your organizer on the day of the run.
9.4. The minimum. RunLokal makes a payout when the amount due is at least ₱1,500. A smaller amount waits for the next days' sales. Once every event of your organizer with paid registrations ended more than 7 days ago, RunLokal pays whatever is due, however small.
9.5. The reserve. RunLokal holds back 10% of your share of each paid registration as a reserve, until 7 days after the event ends. The rest of your share is paid as in 9.3. Once the event is over and the 7 days have passed, the reserve becomes part of what is due, and is paid as in 9.3 and 9.4. If the event is cancelled, its reserve is frozen: RunLokal does not pay it until it has reviewed the event with you.
9.6. Changing the bank account. Your organizer's first bank account can be paid at once. When the bank account is changed, RunLokal does not pay your organizer for 48 hours. Each time a bank account is saved or changed, we email the owner of the organizer. If you did not make the change, write to us at [email protected] at once.
9.7. Costs. RunLokal pays every payment gateway cost, transfer fees included. A payout is never reduced by the cost of sending it. Your share is the price of each registration, or the price less the fee if you chose to pay the fee out of your price (section 5.3).
9.8. Taxes. Where the law requires RunLokal to withhold tax on a payout, RunLokal withholds it, pays it to the tax authority, and shows you the amount withheld on the payout. Amounts that are withheld are part of your share for the purposes of this agreement, and you remain responsible for your own taxes.
9.9. When payouts pause. RunLokal may pause the payouts of your organizer, and email the owner that they are paused, when: one of its events with paid registrations is cancelled; a payout to your bank account fails; we are reviewing reports or unusual sales; or we have a reason under section 7. While your organizer is suspended or removed (section 7), the daily payouts of 9.3 are not made either. A pause delays payouts and does not cancel them. RunLokal resumes the payouts once the reason is settled, and what you are owed stays owed.
9.10. Adjustments. If money that RunLokal has paid you, or owes you, turns out to be wrong, because a payment is disputed or reversed by the payer's bank or wallet, because RunLokal had to return a confirmed payment to the payer or refunded a runner under 9.11, or because of an error, RunLokal records an adjustment. An adjustment is netted against what you are owed in your next payouts. If an amount is still owed to RunLokal after that, for example when your organizer has no more payouts coming, you must repay it when we ask.
9.11. All sales are final. All sales are final, and refunds are up to you (section 6). RunLokal does not refund a registration for you, except that when RunLokal cancels an event under 7.6 it may refund the event's runners out of the money it holds for your organizer, and records each refund as an adjustment (9.10). RunLokal does not return its fee (section 5.5). If you refund a runner yourself, that is between you and the runner.
9.12. Documents. We may ask you for documents that the law, the payment gateway or the bank requires, such as proof of the account holder's identity. We may pause your payouts until you give them.
9.13. Your records. Your organizer's Payouts page shows its earnings, the reserve, each payout and what was withheld or adjusted. Write to us at [email protected] if something there looks wrong.
9.14. A payout of money RunLokal already owes you is not stopped because a new version of this agreement is waiting for you to accept it.
9.15. Verification. Verification is optional. The owner of your organizer may send a business registration (from the SEC, the DTI or the CDA) or a government ID whose name matches the holder of your organizer's bank account. RunLokal checks only that the name on the document matches the account holder's name and, if it does, shows "Verified organizer" on your organizer's pages and at checkout. The badge is removed when the bank account changes or your organizer gets a new owner, until a new document is approved. It is not an endorsement of your organizer or its events. An organizer that is not verified can still publish events and be paid.
10. Changes to this agreement
10.1. We may update this agreement. We will post the new version at runlokal.com/legal/organizer-agreement with its effective date.
10.2. If a change is material, you must accept the new version for each organizer you own before you use its dashboard again. Other changes, such as corrections, apply from the date we post them.
10.3. Until you accept a new version that is a material change, your organizer and its pages stay as they are, but you cannot use its dashboard. If you do not agree to the change, write to us at [email protected], and we can put your upcoming events on hold or remove your organizer.
11. Governing law and disputes
11.1. This agreement is governed by the laws of the Republic of the Philippines.
11.2. If you have a complaint or a dispute with us, please write to us first at [email protected], so that we can try to resolve it informally.
11.3. Any suit arising from this agreement shall be filed exclusively in the proper courts of the city where Vanguard AI Analytics, Inc. has its principal office, to the exclusion of all other venues, without prejudice to any right you have to bring a complaint before the National Privacy Commission or another government agency.
11.4. If a court finds any part of this agreement invalid, the rest remains in effect. If we do not enforce a part of this agreement, we have not waived it.
12. Contact
Vanguard AI Analytics, Inc., operator of RunLokal
Email: [email protected]