Terms of service

Last updated: [[NEEDS LEGAL REVIEW: effective date of this document]]

The service

Evento lets organisations keep a member roster, publish events, take attendance, and collect fees for memberships and real-world events. Members and guests use the mobile app; organisations manage members, events, approvals, and billing features through the same product.

[[NEEDS LEGAL REVIEW: contracting entity, who the customer is (individual member vs organisation), and whether these terms bind both]]

Accounts

You must keep your sign-in details safe. You may sign in with email and password, phone OTP (SMS delivery is currently a development mock in server code until a production SMS provider is wired), or Google Sign-In.

Organisation owners can grant roles to other members. If your account is suspended, you cannot authenticate until the suspension is lifted.

If you own any organisations, you must transfer or delete them before you can delete your account.

[[NEEDS LEGAL REVIEW: age minimum, acceptable-use rules, and account suspension policy]]

Payments

Organisations can charge membership joining fees and event registration fees. Checkout is created as a Razorpay order on a single Evento Razorpay account (orders.create). The product does not currently create Razorpay Route transfers or automatic payouts to organisation bank accounts; payout runs exist in the database as a future / manual workflow.

Order notes sent to Razorpay include organisation id, membership or registration id, your user id, and the fee purpose. Default currency is INR unless configured otherwise. Organisations may choose whether they or the member absorb gateway transaction fees (feeAbsorbedBy).

Refunds, when issued by an organisation manager or by event-cancel flows, call Razorpay payments.refund against the stored payment id and return money through Razorpay to the original payment method. Evento does not hold a separate wallet balance for members.

Honest summary of the counterparty today: money is collected into Evento’s Razorpay merchant account on behalf of organisations. Remittance from that account to each organisation is not automated in code. For a refund, the technical counterparty that returns funds is Razorpay acting on that merchant account — not a separate organisation-linked Razorpay Route account.

[[NEEDS LEGAL REVIEW: RBI Payment Aggregator / Payment Gateway implications of collecting on behalf of organisations into one Razorpay account without Route splits; merchant-of-record; platform take-rate disclosure; chargeback handling; and written refund / remittance policy]]

Third parties

Evento currently sends data to the services below. Each row is taken from the product code; a lawyer must still confirm purposes, contracts, and where processing happens.

[[NEEDS LEGAL REVIEW: confirm each processor and DPA; add hosting (MongoDB Atlas, Redis, Render) and any production SMS provider; confirm Nominatim/OpenStreetMap fallback for geocoding]]

Liability

[[NEEDS LEGAL REVIEW: limitation of liability, warranty disclaimer, and indemnity — do not invent caps or exclusions here]]

Contact

[[NEEDS LEGAL REVIEW: legal contact email and postal address for notices under these terms]]

Jurisdiction

These draft terms assume India as the primary place of use.

[[NEEDS LEGAL REVIEW: governing law and courts or arbitration venue once the contracting entity is named]]