Terms and Conditions

In effect since 2026-08-30

GENERAL TERMS AND CONDITIONS OF MULTITICKETING

Courtesy translation. The authoritative text of these Terms is the Spanish one, published at the same address in Spanish. This English version is provided so that English-speaking readers can understand what they are accepting; in the event of any discrepancy between the two, the Spanish version prevails (section 37).

These Terms govern access to and use of Multiticketing. The organizer, and not Multiticketing except where it organizes an event of its own, offers and delivers the event to the attendee. Multiticketing retains responsibility for the technology, account, QR, collection, communication and support services, and for any other actions it effectively controls.

1. Identification of the operator

The platform known as "Multiticketing" is currently operated and administered by FUNDACIÓN REDPLANETTRIBE, an Ecuadorian private, social, non-profit organization, with taxpayer number (RUC) 1793228468001 (hereinafter, "Multiticketing", the "Foundation" or the "Operator").

Contractual address: Av. Portugal y Av. 6 de Diciembre, Plaza Arts, Quito, Ecuador, in accordance with the registered address on file.

Support and complaints: info@redplanettribe.org.

The Foundation operates Multiticketing within its institutional purposes and devotes its resources exclusively to fulfilling them. For as long as the Foundation is the Operator, the Platform may not be used for party-political or religious activities incompatible with its nature and bylaws.

Any change of operator will be communicated in advance, will identify the new provider, will preserve acquired rights, valid tickets, payments and outstanding obligations, and will collect fresh acceptance where the change is material or where the applicable relationship requires it.

2. Purpose, scope and contractual documents

These Terms set out the common rules and the specific rules that apply according to the way in which each person uses Multiticketing: visitor, attendee, buyer, organizer, representative of an organization, staff, sponsor or authorized user. The same person may take on several roles; in that case the rules of each role apply simultaneously in respect of the corresponding conduct.

Multiticketing may comprise, depending on the module enabled for each event: public discovery pages; registration and accounts; ticketing for free or paid events; ticket assignment; a dynamic personal QR; tools for organization, agenda, sessions, communications, chat and networking; technological tools for entry, exit and re-entry control managed by the organizer; management of staff and sponsors through the platform; metrics and reports; external links; and technological facilitation of payments through third parties.

The following form part of the relationship, as applicable: (i) these Terms; (ii) the offer and purchase summary shown before a transaction is confirmed; (iii) the event's particular conditions supplied by the organizer and expressly accepted by the user who buys tickets for that event; (iv) the conditions of the payment provider or of an external site, for its own service; and (v) the Privacy Policy in force, solely in respect of the processing of personal data. Acceptance of these Terms is contractual and is kept separate from the optional privacy consents.

These Terms do not retroactively modify prices, benefits or rights already acquired.

3. Acceptance and electronic contracting

Acceptance will be given by means of a mandatory, separate, un-preticked checkbox accompanied by a direct link to the full text in Spanish. Accessing or browsing the Platform, receiving an email, opening a link or continuing to use it evidences the express acceptance previously required.

The user accepts these Terms when creating or enabling their account and, where a materially modified version is introduced, in order to continue using the Platform. The organizer must accept them expressly in the capacity of organizer before publishing their first event, and each representative declares that they have sufficient authority to bind the person or entity they represent. Likewise, staff must accept them when enabling their account or permissions. If direct sponsor access is enabled in the future, the sponsor must accept before using it.

General acceptance will not be used as a substitute for the affirmative statement tied to the purchase of, or registration for, an event. Before completing a purchase or registration, the user must check the particular conditions supplied by the organizer and affirmatively declare that they accessed the applicable version. Multiticketing will retain the exact version tied to the event and to the transaction, and no dynamic link may alter what was accepted.

4. Definitions

  • Attendee: a person who registers for or intends to take part in an event, including a guest to whom a ticket is assigned.

  • Buyer: a person who starts or completes the acquisition of one or more tickets, for themselves or for guests.

  • Organizer: a natural or legal person who creates, publishes, offers, administers or delivers an event and defines its particular conditions. Where the Foundation publishes an event of its own, it will also act as organizer in respect of that event.

  • Staff: an individual person invited and authorized by the organizer to operate event functions. That fact alone does not make them part of Multiticketing's personnel.

  • Sponsor: a sponsor linked to the event by the organizer, whose brand, offer, content or participation may be displayed or managed through the Platform.

  • Account: an individual profile authenticated by email and a one-time code or another enabled mechanism.

  • Ticket: the right or authorization to register for and access an event, associated with an account and verifiable through the personal QR. The QR is not, by itself, the ticket.

  • Personal QR: a dynamic, individual and non-shareable identifier of the account, which allows the associated authorizations to be looked up when it is scanned by authorized personnel.

  • Particular conditions: the organizer's information and rules on price, date, venue, admission, benefits, restrictions, changes, cancellation, returns, refunds and other aspects of the event.

5. Description of the service and Multiticketing's role

Multiticketing supplies technological infrastructure to publish and discover events; create accounts; register, buy, assign and validate tickets; enable communications, networking, agenda and management features; display sponsors; produce metrics; and facilitate payments or transfers according to the enabled method. The modules may be used together or independently; for example, ticketing may operate without agenda, chat or networking.

Multiticketing does not ordinarily direct the logistics, venue, permits, capacity, security, content, agenda, benefits, admission or delivery of the event. Those matters fall to the organizer. Multiticketing will be responsible for its own conduct, including the reasonable operation of the account and QR, the information it publishes itself, the technological processing it controls, the collection or settlement it actually carries out, its charges, its receipts and its support.

Where payment is processed by PayPhone under the Foundation's merchant account and the funds initially enter the Foundation, Multiticketing takes part as a technology provider and as the operational recipient of the funds for reconciliation and subsequent settlement to the organizer, in addition to charging its service fee. This intervention is not described as mere brokerage and will be subject to the flow disclosed before the purchase.

6. Types of users, roles and representation

Visitors may consult public pages without creating an account, but may only carry out the actions that the interface permits without authentication. The assignment and use of a ticket by means of a QR requires an individual account. If the Platform enables a purchase before registration, the buyer must complete the creation or linking of an account and the applicable acceptance before using the ticket.

Anyone acting on behalf of a legal person or organization declares that they have sufficient authorization. Multiticketing may request reasonable information to verify the representation and may suspend organizing powers while an objective doubt exists. The organizer is responsible for the selection, invitation, permissions and acts carried out by their staff and other delegated users within the scope granted to them.

Consumer status will be determined by the specific purpose of the transaction. Consumer protection rules will apply to the attendee or final buyer where appropriate; relationships entered into by an organizer, sponsor or business client for their own activity will additionally be governed by commercial rules and by any B2B agreements that may be signed.

7. Capacity, access requirements and accounts

Only persons who have reached eighteen years of age may buy through Multiticketing. The user declares that they meet this requirement. Additional restrictions of age or capacity for an event, drink, prize draw, area or benefit are the organizer's responsibility and must be stated in the particular conditions and verified at the event.

The account is individual. The user must provide accurate and up-to-date information; safeguard access to their email, device and OTP codes; not share codes or sessions; close unrecognized sessions; and immediately notify support of any unauthorized access. Acts carried out from an authenticated account may be attributed to the account holder, save for timely notice and evidence to the contrary.

For as long as the email remains available, access can be recovered by OTP. If that email is lost, Multiticketing will provide best-efforts assistance to try to verify ownership through reasonable and secure information, but the current system does not guarantee recovery. This limitation does not by itself extinguish payment rights; that is, the user must immediately contact support and the organizer to seek an operational solution before the event.

8. Common obligations of users

Every user undertakes to: use the Platform in good faith and in accordance with the law; keep their information genuine; respect third-party rights; comply with the conditions applicable to their role and to the event; protect their account and QR; review operational notices; use support channels responsibly; and cooperate reasonably in preventing fraud, improper access and security incidents.

The user may not impersonate others, share the account or QR, alter receipts, interfere with validations, automate the extraction of information, evade access controls, introduce harmful code, overload the infrastructure, harass, discriminate, threaten, send spam, infringe rights, publish unlawful content or use the Platform for purposes incompatible with the Foundation — for as long as it is the Operator.

9. Rules applicable to organizers

The organizer is the offeror and the party principally responsible for the event towards attendees and buyers. On publishing, they declare that they can bind themselves or the identified entity, and they assume responsibility for: the offer, base price, capacity, categories, benefits, restrictions, particular conditions, invoicing of the event, permits, venue, accessibility, safety, emergencies, capacity limits, admission, agenda, guests, alcohol, promotions, prize draws, sponsors, staff, content, changes, cancellation, rescheduling, returns, refunds, and the event's other obligations.

Before publishing, the organizer will provide Multiticketing with their verifiable legal or trade name; a current direct channel for contact with attendees and buyers; a full description; date, time and venue; price and currency; capacity and categories; admission requirements; and any material restriction. The information will be clear, genuine and verifiable, and will be kept up to date.

The organizer must deal directly with enquiries and complaints relating to the event and issue the user the receipt corresponding to the event service. They may not use these Terms to reduce their own obligations, to shift to Multiticketing matters under their control, or to impose on the consumer waivers that are prohibited. They will be liable to Multiticketing for damage directly arising from their breach, to the extent permitted by law and without affecting third-party rights.

10. Publication and administration of events

The organizer may create, configure, edit and cancel events and, depending on the module, manage capacity, waiting lists, VIP access, areas, activities with limited places, re-entries, visibility, attendee approval, agenda, sessions, chat, sponsors, deliverables, team and reports. The existence of a tool does not mean that it is enabled for every event.

Multiticketing does not pre-approve every event. It may review, request corrections, decline to publish, deactivate or withdraw an event where there is a breach of these Terms, incomplete information, or where it identifies misleading information, risk to users or infrastructure, an order from an authority, infringement of rights, fraud, unlawful activity or objective incompatibility with the Foundation's purposes. Where possible, it will state the cause and allow correction before any definitive measure, save in cases of urgency or serious risk.

Technical deactivation does not by itself terminate contracts already entered into with attendees. The organizer must inform and fulfil their outstanding obligations, and Multiticketing will preserve the records and channels necessary within its control.

11. Organizer information and particular conditions

Each event page must identify the organizer and display, before purchase or registration, a direct channel supplied by them. The organizer warrants that this information is genuine and current. Multiticketing will apply reasonable controls, but does not warrant data it has been unable to verify; this does not remove its duty to correct or withdraw information when it becomes aware that it is inaccurate.

The attendee must contact the organizer to check all the particular conditions before making the affirmative statement; those conditions are distinct from these Terms and from PayPhone's conditions. The record of acceptance will link user or buyer, event, order, role, version, date and time.

The organizer may not retroactively modify the price, benefits or rights already acquired. If they modify the date, place, agenda, guests, benefits, requirements or any material condition, they must communicate this in good time and offer the remedies provided for in their conditions and by law. The user's mere duty to review information does not turn silence or continued use into acceptance of a material modification.

12. Rules applicable to attendees and buyers

Before registering or buying, the attendee must review the organizer's identity and contact details, the final price, date, venue, requirements, benefits, particular conditions and the change and refund policy. The affirmative statement confirms access to that information; it does not constitute a waiver of mandatory rights, nor does it cure information that is missing, false, illegible or altered.

The attendee will provide correct information for their account and for the assignment of tickets, will check that the ticket type and the guests are correct, and will attend to confirmation links in good time. Errors attributable to incorrect data may delay the assignment. Multiticketing may correct them on request where technically possible, without assuming the cost or responsibility for the event, which it did not cause.

Requests concerning logistics, admission, changes, cancellation, benefits, invoicing of the event and refunds after the period enabled in the payment method must be addressed to the organizer. Complaints about the account, QR, technological assignment, service fee, Multiticketing's own receipt, security or the functioning of Multiticketing will be addressed to its support channel.

13. Registration, purchase and assignment of tickets

Events may be free, paid, or may refer the user to an external site. Registration or payment does not guarantee the ticket until the published conditions are met, the applicable transaction is confirmed and the ticket appears associated with the account. In external purchases, the third party and the organizer govern the external transaction; Multiticketing is responsible only for the link or service it actually supplies.

A person may acquire several tickets. For guests, they must enter the required identifiers and emails. Each guest will receive a link and must sign in or create an account, accept the applicable documents and confirm the assignment. If they do not complete the process, the ticket will not be associated with their QR and cannot be validated at the event.

The current functionality allows the buyer to designate or replace guests. That power must be exercised in good faith, in accordance with the event's conditions, without resale or fraud and respecting rights already acquired by third parties. Reassignment does not make the personal QR transferable and may not be used to duplicate access or to disregard a validation already used.

14. The personal QR: nature, use and restrictions

Each account has a dynamic personal QR. The QR identifies the account and allows a check of whether a valid ticket or authorization exists for the event, session, area, deliverable or benefit. A separate QR is not necessarily generated for each event, and the QR, in isolation from the associated authorization, does not constitute a ticket.

The QR is personal and may not be shared, sold, reproduced for third parties or used from someone else's account. A screenshot may not work, because the identifier is dynamic. The person must display it from the application or enabled channel and must have internet access and a compatible device, unless the organizer announces an alternative.

Multiticketing and the organizer may block an account or authorization in cases of fraud, duplication, shared use, valid revocation, chargeback, breach or objective risk, each within their own remit. Suspending an account is not automatically equivalent to cancelling a paid ticket, and must be applied proportionately, with information and a route to review where possible.

15. Access, capacity, re-entry, areas and activities

Authorized staff scan the QR and validate the registered authorization. The organizer determines and enforces the rules on doors, identity, capacity, re-entry, areas, schedules, sessions, waiting lists, VIP access, deliverables and activities with limited places, in accordance with the offer and the particular conditions. Places may not be sold in excess of the applicable capacity.

Multiticketing's digital records are operational evidence, but they do not replace legitimate security or admission checks, nor do they authorize arbitrary decisions. A refusal attributable to the event's conditions is the organizer's; a refusal caused by an error of Multiticketing's own account, QR or records will be handled by Multiticketing.

Validation requires connectivity for the attendee and for staff under the current flow. The organizer must provide for a reasonable contingency procedure for a live event. The absence of an alternative does not authorize valid tickets to be disregarded, nor a failure controlled by the organizer to be shifted onto the user.

16. Prices, service fee, taxes and payment methods

Before a purchase is confirmed, the final amount will be shown in United States dollars, with the base price of the tickets, the service fee, the VAT applicable to that fee and any other permitted item. No cost that has not been disclosed and accepted will be added afterwards.

The organizer sets the base price. Multiticketing sets its service fee; under the arrangement currently disclosed, the standard fee is ten per cent (10%) of the base price, plus the VAT applicable to the fee, unless a different configuration or agreement is disclosed before the purchase. The organizer chooses whether the fee is added to the base price and borne by the buyer, or deducted from the amount the organizer receives. The screen shown before payment determines the binding amount for that transaction.

Where PayPhone is used, the payment form is hosted in PayPhone's environment and its own terms govern the financial processing. Multiticketing does not store or tokenize card data. The merchant account is in the Foundation's name and the current receipt identifies Multiticketing as the recipient of the payment.

The Platform may also enable a direct transfer to an account of the organizer. In that case, Multiticketing does not receive the funds, acts exclusively on the organizer's instruction to associate the ticket, and will not itself verify the proof of payment. If the organizer does not confirm, Multiticketing will report the lack of confirmation and direct the buyer to the organizer's channel, without prejudice to its support regarding the account.

17. Payment confirmation, reconciliation and settlement

For payments through PayPhone, the funds initially enter the Foundation. Payment confirmation and assignment may be automatic or may require human review. Multiticketing reconciles the transaction, withholds its fee and transfers to the organizer the balance due when the organizer requests a withdrawal or in accordance with the enabled frequency, once they have recorded valid bank details.

Multiticketing will inform the organizer of the available status of sales, withdrawals and transfers, and may request information to resolve payments that have failed or been duplicated, reversed, fraudulent or subject to chargeback. It may not appropriate the organizer's amounts beyond the fee and deductions previously disclosed or legally payable. The commercial settlement terms may additionally be documented in an order or B2B agreement.

Confirmation of receipt, an automatic email or the opening of a message do not by themselves substitute for acceptance or for the final confirmation of a purchase. The user must check the summary and the status of the ticket in their account.

18. Invoicing and financial responsibilities

The organizer will issue the buyer the invoice or receipt corresponding to the event service. The Foundation will issue the corresponding receipt solely for its service fee. If the Foundation organizes an event of its own, it will also assume the invoicing of the event in that capacity.

The organizer is responsible for the accuracy of their tax details, prices, taxes and obligations relating to the event. Multiticketing is responsible for its fee, its receipt, the reconciliation and the transfers it actually handles. Nothing in these Terms substitutes for the tax and accounting validation that falls to each party.

19. Cancellations, changes, returns and refunds

The organizer must have a cancellation and refund policy and must administer it directly. Cancellation, rescheduling, change of venue, substantial reduction of benefits, overselling, unjustified refusal of access or defective performance will be resolved in accordance with the offer, the particular conditions and the consumer's mandatory rights. No clause may exclude those rights in advance.

In the PayPhone flow, the user may request a voluntary reversal from the Platform until 20:00 on the same day as the transaction, subject to the payment provider's availability and rules. After that limit, the organizer directly handles and carries out any refund and its costs. For a mass cancellation, the organizer orders and carries out the return; Multiticketing will provide the relevant operational information about attendees and the communications within its control.

Responsibility for the service fee in a cancellation, mandatory return or failed performance will be resolved according to the cause, the offer, the law and the party that performed or breached the service. Multiticketing will not use this section to withhold a fee where it must legally be returned, nor may the organizer refuse a refund by referring the user to the Platform.

20. Sponsors, advertising, promotions and trademarks

The event functionality allows the incorporation of sponsors, featured profiles, logos, offers, deliverables, interactions and reports managed by the organizer. The sponsor currently contracts with the organizer and not, by that fact alone, with Multiticketing. The organizer uploads and approves their content, manages their communications and shares the relevant reports.

The organizer warrants that they have sufficient authorization and/or rights over the trademarks, images, advertisements, products, services, promotions, prize draws and materials they provide to Multiticketing. They must disclose conditions, availability and restrictions, and are liable for misleading advertising, infringements and delivery of benefits. Multiticketing may withdraw content where it becomes aware of an infringement, where there is an order from a competent authority or where these Terms are breached.

Multiticketing does not guarantee leads, sales, meetings, exposure or commercial results.

21. Staff and operational permissions

The organizer or their delegates invite individual staff accounts and configure their permissions. Depending on the configuration, staff may validate entries and sessions, record deliverables, moderate chat, view or manage questions, mark answers, update the status of sessions and consult operational data of speakers or authorized contacts. Shared credentials are not permitted.

Staff act on the organizer's behalf. The organizer must instruct them, limit their permissions to what is necessary, revoke access when their function ends, and be responsible for their door and management decisions. Multiticketing may technically suspend a staff account for misuse or risk, but this does not make staff its employees, nor does it assume the physical delivery of the event.

22. Profiles, networking, community and user content

The user may voluntarily activate, edit or hide a public profile with the information the interface permits, including job title, company, LinkedIn, website, interests, what they are looking for and what they offer. Visibility and messaging permissions may depend on the event and on the ticket type configured by the organizer. General event messages may be visible to everyone who is registered.

Harassment, threats, discrimination, spam, impersonation, scraping, misleading communications, unlawful content, unauthorized dissemination of information and any conduct that affects the security or experience of others are prohibited. Users may block or report where the feature exists and, in any case, may write to support. The organizer reviews the event's networking incidents, and Multiticketing handles those that affect the Platform or breach these Terms.

Multiticketing facilitates connections, but does not guarantee contacts, meetings, leads, sales, hires, partnerships or results. Closing an account does not extinguish outstanding obligations, nor does it authorize the deletion of evidence needed for purchases, complaints or legal compliance.

23. Multiticketing's intellectual property and licence of use

The Platform, its software, interfaces, documentation, structural databases, institutional content and distinctive signs are protected by the applicable rules and belong to Multiticketing or to their respective owners and licensors, as applicable. These Terms do not assert exclusive ownership that is not evidenced, nor do they transfer rights to the user.

While the account is in force, Multiticketing grants the user permission to access and use the enabled features in accordance with these Terms. It is not permitted to copy, exploit, decompile, circumvent controls, create derivative works or use Multiticketing's signs beyond what is permitted by law or by written authorization.

24. Content and rights of organizers, attendees and sponsors

Each user retains the rights over the content they upload. They grant Multiticketing, for as long as is necessary to provide the service and to fulfil outstanding obligations, a non-exclusive, territorially sufficient, royalty-free, limited licence, revocable so far as compatible with operations, to host, technically reproduce, adapt to formats, communicate and display that content at the event and in the configured channels.

The user warrants authorship, ownership or authorization, and that the content does not infringe rights, the law, public order or these Terms. The licence does not authorize Multiticketing to exploit the content for purposes unrelated to the service. Takedown requests for infringement must be sent to info@redplanettribe.org identifying the complainant, the work or sign, the location of the material, the grounds and a means of contact.

25. Prohibited conduct and acceptable use

In addition to the prohibitions above, it is prohibited to: create fictitious events; publish false prices, benefits or capacities; take payments without the ability to perform; evade disclosed fees; resell or duplicate tickets without authorization; manipulate metrics; obtain data through unauthorized automation; offer alcohol, prize draws or restricted benefits without conditions and controls; infringe licences; test vulnerabilities without permission; and use the Platform for party-political or religious activities incompatible with the Foundation for as long as it is the Operator.

Moderation measures will be based on seriousness, recurrence, risk and role. They may comprise a warning, withdrawal of content, functional limitation, temporary suspension, blocking of the QR, deactivation of an event or termination. Where there is no urgency, fraud, risk or legal impediment, the cause and a channel for review will be communicated.

26. Third-party services, links, components and licences

Multiticketing uses third-party services, currently including PayPhone for payments; Resend, AWS SES or other services for email; Google Cloud, Firebase and Google services for infrastructure or authentication; and software components subject to their own licences. Use of a specific third party's service may be subject to its terms, which must be presented separately where they impose obligations on the user.

Links to external registrations, purchases or sites will be identified as such. Multiticketing does not control their content or their transactions, and will be responsible for its own selection, integration or information only to the extent of its participation. Open-source and third-party licences will be respected in accordance with their texts; the inclusion of a component does not automatically make the whole Platform open-source software, nor does it authorize the use of third-party trademarks.

27. Metrics, reports and analytics

Depending on the module enabled and the event's configuration, Multiticketing may display metrics on visits, conversion, registrations, sales, affiliate links, entries, exits, re-entries, times, sessions, areas, deliverables, sponsors and interactions, and may allow exports in the available formats. Standalone ticketing is limited to metrics relating to tickets and digital channels; the management features widen the scope only when they are enabled.

The metrics are operational and of reasonable accuracy. They may be affected by connectivity, missed or duplicated scanning, configuration, devices, staff conduct, reversed payments or incomplete data. They therefore do not constitute a guarantee of attendance, revenue, compliance, leads or results. The organizer must check and retain the reports they need before their access is closed.

28. Availability, maintenance, support and contingencies

Multiticketing will seek to provide reasonable availability, without promising absolute continuity or a service level that has not been agreed. It may carry out maintenance, improvements, corrections and technical changes that do not alter essential rights. If scheduled maintenance may materially affect a live event, it will seek to give at least one week's notice; urgent incidents may be dealt with without prior notice.

The service depends on the internet, devices and external providers. Multiticketing will be responsible for the diligence required of it in its own systems and integrations; the organizer will be responsible for connectivity and contingency at the venue. In an outage, the organizer must verify tickets and restore the service, without imposing on the attendee the automatic loss of a valid ticket.

Support handles problems with OTP, accounts, the QR, technological assignment, checkout and the functioning of the Platform through info@redplanettribe.org. No specific response times are promised unless and until they are published or expressly agreed.

29. Suspension and termination of accounts, events or services

Multiticketing may suspend or terminate access for material breach, fraud, impersonation, a shared QR, abusive chargebacks, security risk, unlawful use, infringement of rights, failure to pay B2B obligations, an order from an authority, damage to the infrastructure or repeated offences. The measure must be proportionate and limited, where possible, to the account, feature or event affected.

The organizer may refuse or revoke an authorization for the causes provided for in their particular conditions and by law, but may not alter the account's general records nor use a revocation to avoid returns. Multiticketing will not reverse a valid operational decision of the organizer regarding a ticket, save to correct a technical error of its own, to comply with an order or to protect mandatory rights.

The user may request closure of their account. They are warned that without an account there will be no accessible QR, and that outstanding tickets, payments, receipts and complaints must be resolved first. Closure does not extinguish acquired rights or outstanding obligations, and Multiticketing will retain the records it is required to keep. If closure prevents access to a live event, the user must immediately contact support and the organizer.

30. Responsibility of the parties

Multiticketing's responsibility: it comprises the diligent provision of its technological services; the generation and functioning of the QR and the records under its control; reasonable account security; its own information and advertising; correction of its own errors; the service fee and the corresponding receipt; the receipt, reconciliation and settlement of funds it handles; support; and compliance with binding decisions within its sphere.

The organizer's responsibility: it comprises the whole event, such as the offer, conditions, base price, invoicing of the event, permits, venue, capacity, accessibility, safety, staff, sponsors, content, admission, changes, cancellation, rescheduling, returns, refunds and dealing directly with complaints about the event.

The user's responsibility: it comprises the accuracy of their data, safeguarding their account and QR, lawful use, compliance with access conditions and their own conduct.

Neither party will be liable for a breach caused exclusively by force majeure or an act of God for as long as it is unforeseeable and irresistible, provided they take reasonable mitigation measures and give notice where possible. Force majeure does not release a party from returning amounts where the law, the nature of the obligation or a service not provided so requires.

31. Warranties and permitted limits

Multiticketing does not warrant that all modules will always be enabled, that every account will be recoverable without sufficient evidence, that an event will take place, that the organizer will admit a person who fails valid requirements, or that networking, metrics or sponsors will produce results. These exclusions do not cover defects, wilful misconduct, negligence, its own breaches or the consumer's mandatory rights.

Any limitation of damages will apply solely in B2B relationships and to the extent permitted by law and by a negotiated agreement. Liability is not limited for personal injury, fraud, infringement of rights, improper handling of funds, obligations to make returns, its own defective performance or any case that cannot be excluded.

32. Support, complaints and content takedown

Complaints relating to Multiticketing may be submitted to info@redplanettribe.org. At least the complainant's identity and contact details, the date, the event or order, a description and the request will be recorded, and a record will be provided on request. Multiticketing may ask for information strictly necessary to verify the account or the incident.

Complaints about the event will be referred to the organizer's direct channel shown on the page, without preventing the user from informing Multiticketing of a lack of response, fraud, misleading information or risk. Multiticketing will not close a complaint of its own merely because an organizer is also involved.

33. Modification of the Terms and changes to the service

Multiticketing may update these Terms to reflect changes in law, operator, security, payments or features. Non-material changes may be communicated through the Platform or by email and will apply going forward. Material changes affecting obligations, liability, payments, dispute resolution, contractual privacy, access or rights will require prominent notice and fresh express acceptance before continuing to use the affected feature.

No update will retroactively alter a purchase, ticket, price, benefit or right that has been accepted. If the user does not accept a material version, they may stop using future features; Multiticketing will adopt a proportionate consequence and will allow prior tickets, payments, receipts and obligations to be resolved.

34. Versions, evidence and a true copy

Multiticketing will identify each version and will retain the exact text or a verifiable fingerprint, together with the evidence of acceptance. The record must include, depending on the act, the date and time, the user and email, the version, the role, and the technical data reasonably necessary for attribution, integrity and proof.

After accepting, the user will have access to a true and downloadable copy from their account; the text in force and the version history will also be available outside the account in the legal center. The version of the particular conditions accepted for a purchase will be retained statically and linked to the transaction.

Pre-existing accounts must accept this version prospectively in order to continue using the Platform. Organizers with events already published must accept before new publications or material management actions, without affecting prior contracts or retroactively shifting responsibilities.

35. Privacy Policy and communications

The processing of personal data is governed by the Privacy Policy in force, available in Multiticketing's legal center. These Terms do not replace that policy.

Messages that are indispensable for OTP, security, purchases, tickets, event changes, support and contractual performance are operational communications.

36. Governing law and dispute resolution

These Terms are governed by Ecuadorian law. Where a consumer is involved, the competent authorities and courts will be those corresponding to their domicile and to mandatory rules. No mediation or arbitration will be binding on the consumer without express, separate and unequivocal acceptance.

In B2B relationships, the parties will seek to resolve the dispute in good faith and may voluntarily resort to mediation. Failing a different written agreement, and without affecting mandatory jurisdiction, non-consumer disputes will be heard before the competent courts of Quito, Ecuador.

37. Final provisions

The nullity or unenforceability of a provision will not affect the remainder; the clause will be interpreted in the valid manner closest to its purpose, without reducing consumer rights. Failure to exercise a right does not constitute a waiver. The headings are for ease of reading and do not limit the scope of the text.

The Spanish version prevails over any translation. Contractual notices will be sent to the registered email or displayed in the account, without prejudice to any additional notices required. The user must keep their email up to date and Multiticketing must keep its support channel operational.

An assignment or change of operator may not be used to diminish acquired rights, release outstanding obligations or conceal the provider's identity. Where it is material, it will require prior notice and fresh acceptance.

Version 1
Fingerprint: 2b9bb4bc6b2c6e8ad4ddeb9737db2eba5b94ec4c66c84c1b239bfff9a1c9af24