what you agree to, and what we owe you.

The short version

nCommunity is a place to find things happening near you, say you are coming, and turn up. We are not the organiser of the events on it. Hosts and venues run those; we run the platform that helps you find each other, hold a place, pay, and prove you were there.

That distinction runs through everything below. It is why section 15 asks you to think about your own safety, why section 10 puts real obligations on hosts, and why we can suspend an account but cannot promise that every event will be good.

This summary is not part of the agreement. The sections are.

The agreement

These terms are between you and [LEGAL ENTITY NAME] of [REGISTERED ADDRESS] (“nCommunity”, “we”). They cover the nCommunity app, this website, and nCommunity Studio.

By creating an account you accept them. Our privacy policy explains what we do with your information and forms part of this agreement.

Who can use nCommunity

You must be 18 or over. Individual events may set a higher minimum age, and where alcohol is served or the venue requires it, that limit is not the host’s choice. You may be asked for identification at the door.

You may not use nCommunity if we have previously removed you, or if the law where you are prohibits it. One account per person.

Your account

You sign in with a one-time code sent to your email or phone, so keep control of that address or number. Anybody who has it can sign in as you. You can see every device signed in as you and end any of them from your settings.

Give us accurate information. Your date of birth in particular cannot be changed by you once set, because an age gate you can edit is not an age gate; a genuine mistake is a support request.

How to behave

You agree not to:

• harass, threaten, stalk, impersonate or discriminate against anybody, on or off the platform;
• use nCommunity to arrange anything illegal, or to sell anything that requires a licence you do not hold;
• misrepresent an event: what it is, where it is, who is running it, what it costs, or what is included;
• interfere with verified attendance: no sharing check-in codes, no checking in people who are not there, no minting redemptions for offers nobody earned;
• scrape, resell or republish other members’ information, or attempt to work out where a member lives;
• probe, overload or reverse-engineer our systems, other than to report a vulnerability responsibly;
• create a second account to get around an enforcement action, or hold an account on behalf of somebody who has one.

Contacting somebody requires a mutual connection made after an event you both attended. There is no way to message a stranger, and that is a design decision rather than a feature we have not got to yet.

Attending events

An RSVP is a commitment to a host who is counting on you and often paying for a room based on that count.

• Full means full. Capacity is enforced on our server under a lock, so two people cannot be given the last place.
• Waitlists have a total order and drain in that order. Nobody can move you up it and nobody can move anybody past you. Not us, and not the host. The host’s only lever is to raise capacity, which drains the queue for everybody at once.
• Cancel as early as you can. Cancelling early counts exactly the same as attending in your reliability record. Cancelling late, or not showing up without cancelling, does not.
• Lateness is recorded and never punished. A door closes only when a person closes it, or when the host’s stated grace period runs out.
• You will be told if the deal changes. If the start time, the end time, the place, the price, the minimum age or the capacity of an event you are going to changes materially, that is recorded and you are notified. Typos and photographs are not material. A notification for every small edit teaches people to ignore the one that says the address moved.

Paying for a ticket

nCommunity is the merchant of record. When you buy a ticket, we take the payment and pay the host afterwards out of what we hold. Your card statement will show nCommunity, not the host, and we pay the card-processing fees rather than passing them to you as a separate line.

The price you see is the price charged. The amount is read from the event on our server; there is no field anywhere in the app or its interfaces where an amount could be supplied by a client. Any fee is shown before you pay.

Refunds

• If the host cancels, you get all of it back. Always, in full. The refund windows a host sets govern you changing your mind; they have nothing to say about an event that is not happening.
• If you cancel, the host’s stated refund window applies. It is shown on the event before you pay.
• Refunds go back to the card you paid with. We owe it the moment it is due and we record it as paid only once the processor confirms it.
• A host cannot reprice an event somebody has already paid for. That would leave two people holding the same thing at different prices with no way to say which was right.

If an event was materially not what was advertised, tell us. We investigate and can refund; we would rather do that than have you argue with a stranger about it.

Waitlists and saved cards

You can save a card to make checking out faster. That, on its own, does not let anybody charge it while you are away.

Being charged for a waitlist place is a separate permission, given per card, in words. If a host has enabled it and you opt in, the exact sentence you agreed to is stored, not a tick in a box, because a tick records that something was agreed and cannot later say what it said. If you are promoted from the waitlist, that card is charged for the place at the price you agreed to.

• If the price changed, you are skipped and keep your place rather than being charged the new amount. A host who repriced has changed the deal.
• A declined charge is not retried. The permission is withdrawn, you keep your place in the queue, and you are told. Six declined attempts on somebody’s statement is its own harm.
• You can withdraw the permission, or remove the card, at any time.

Supporting a host

You can send a host money after an event you attended. Call it what it is: support, or a tip. It is not a donation. nCommunity is not a charity and nothing you send is tax-deductible.

• We take no cut. There is no platform fee on support, and no code anywhere that could apply one.
• It buys nothing. Not a place, not a better place in a queue, not priority at a door, not visibility, not reputation. It is structurally incapable of doing so: the record of a tip has no link to the record of your place at an event.
• The host is shown a total and a count, never who. A host who knew would know it at the door of the next one.
• Support is not refundable, because it was not a purchase.

Hosting an event

If you put an event on, you are the organiser of it. You are responsible for it actually happening as described, and for complying with the law where it happens.

• You need the permissions the event needs: the venue’s agreement, any permit for a public space, any licence for alcohol, food or amplified sound, and any insurance the venue or the law requires. We do not check these and do not represent that you hold them.
• Describe it accurately, including price, age limit, accessibility and anything a person would want to know before committing an evening to it.
• Changing the deal notifies everybody. Moving the time or the place, changing the price, raising the age limit or lowering capacity is recorded and announced. That is not a second, optional step you decide to take. Changing the start time is the announcement.
• Cancelling needs a reason, and refunds everybody in full. A cancellation is a request that our server applies, so that everybody holding a place is told and everybody who paid is refunded, rather than an event quietly disappearing.
• Lowering capacity ejects nobody. It closes the door to new arrivals. If more people are coming than now fit, your dashboard says so loudly, and sorting that out is yours to do.
• Check people in honestly. Verified attendance is the spine of this platform; marking somebody present who was not there is fraud against every other host whose reputation is measured the same way.
• You may admit somebody without an RSVP at a free event, if there is capacity and they meet the age limit. Not at a paid one.
• Attendee information is for running the event and nothing else. Do not export it, add it to a mailing list, or contact people about anything other than the event they came to.

Getting paid

Payouts run through Stripe and require you to complete their onboarding, including the identity checks anti-money-laundering rules impose. We pay out what you are owed less any platform fee disclosed to you at the time, after refunds and adjustments. You are responsible for your own taxes.

Venues, businesses and Studio

Studio is the portal for venues, local businesses, creators and brands. A business account is separate from a member account and is held by a person acting for the business, who confirms they are authorised to do so.

Asking to manage a listing grants you nothing. Claims are reviewed by a person at nCommunity, who verifies control of the business out of band before granting it. A contested claim is recorded and never auto-granted.

An offer you publish is redeemed at your door and only for somebody with a verified attendance record for that event. Neither you nor the attendee can mint a redemption from a laptop. Anything looser is a discount code, and a code that leaks makes the footfall number a lie.

Everything Studio shows you about the people near you is an aggregate with a floor of five distinct people. You will never be given a list of individuals, and you agree not to attempt to re-identify anybody from what you are shown.

Turning up

We keep a record of the places you held and the places you kept, because hosts commit rooms and money on the strength of an RSVP. It is deliberately blunt in your favour: cancelling early scores exactly the same as attending, everybody starts with the benefit of the doubt, an open dispute is excluded rather than counted against you, and it decays over time so that turning up again fixes it.

A poor record can add friction: a reminder, a confirmation step. It is never the sole automated basis for a sanction, and no automated system suspends anybody.

What you post

You keep ownership of everything you post: photographs, descriptions, reviews, messages. You give us a non-exclusive, worldwide, royalty-free licence to host, store, resize and display it for the purpose of running nCommunity, and to show event photographs and listings in places where we promote that event. That licence ends when you delete the content, except where it has already been shared with somebody else or is retained under our retention rules.

Only post what you have the right to post. If you upload a photograph of identifiable people, that is your responsibility, not theirs and not ours.

Reviews require verified attendance. You cannot review an event you did not go to. That is enforced rather than requested.

If you believe something on nCommunity infringes your copyright, write to [LEGAL EMAIL] with enough detail to find it and we will act on it.

Reports, enforcement and appeals

You can report an event, a host, a venue, a profile, a message or a review. Reporting is one report per person per thing, and if you report the same thing twice the first reason stands. Tapping twice while upset is not two complaints.

You can also simply hide a host, venue, community or interest from your recommendations. That is not a report. Nothing is sent to a moderator, nobody is told, and it never removes an event you already hold a place at.

If we act on your account, this is what you are owed:

• A reason, written for you and shown to you in full. Not a code, not a category.
• An end date. Suspensions are always for a stated period. We do not model permanent removal, because that is a heavier decision that deserves its own policy rather than being inherited from a list of options.
• One appeal, decided by a person, with a reason you will read. If we agree we got it wrong, the action is lifted at the same moment. Agreeing somebody was wrongly restricted and leaving them restricted is the worst available outcome.
• A person’s name on it. Every action records who took it. Automated systems may flag; they never decide.

We may remove content, restrict what you can do, or suspend an account where we reasonably believe these terms have been broken or somebody is at risk. Where somebody is in immediate danger we will act first and explain afterwards.

Events happen in the real world

This is the section to read properly.

nCommunity does not organise, run, supervise, inspect or insure the events listed on it. We do not vet hosts or attendees beyond what is described in these terms, we do not run background checks, and a rating is other people’s opinion rather than our endorsement.

Meeting people you do not know is the point of this platform, and it carries risk. Physical activity carries risk. Venues carry risk. You attend at your own risk and you are responsible for your own safety and your own decisions, including whether to go somewhere, whether to go alone, and whether to leave.

Use what we have built for this: the Safety Card on each event, the attendee visibility controls, blocking, and the option to share where you are going with somebody you trust. Tell somebody where you are going. If somebody makes you uncomfortable, report them. You do not need proof and you do not need to justify it.

To the fullest extent the law allows, you release nCommunity from claims arising out of what happens at an event, including the conduct of hosts, attendees, venues and anybody else present. Nothing in this section limits liability that cannot lawfully be limited.

If somebody is in danger, call emergency services first. We are not an emergency service and cannot respond at that speed.

The service itself

We will try to keep nCommunity available and working, and we will not promise uninterrupted service. We may change features, and we will not remove something you are relying on (a place you hold, money you are owed) without telling you.

Some features depend on third parties: payments on Stripe, maps on a tile provider, notifications on Apple and Google. When they are down, so is that part of nCommunity.

Disclaimers and liability

nCommunity is provided as-is. To the fullest extent permitted by law we disclaim implied warranties of merchantability, fitness for a particular purpose and non-infringement, and we do not warrant that any event will take place, will be as described, or will be enjoyable.

To the fullest extent permitted by law, nCommunity is not liable for indirect, incidental, special or consequential losses, or for lost profits or lost opportunity. Our total liability to you in any twelve-month period is limited to the greater of [CAP AMOUNT] and the total amount you paid us through the platform in that period.

None of this applies to things that cannot be excluded: death or personal injury caused by our negligence, fraud, or any liability the law does not permit us to limit. If you are a consumer, you keep every right your local law gives you, and nothing here takes it away.

If you are hosting, running a venue, or using Studio for a business, you agree to indemnify us against claims arising from your event, your premises or your breach of these terms. That does not apply to members attending events.

Governing law and disputes

These terms are governed by the laws of the State of New York, without regard to its conflict-of-laws rules. Disputes go to the state and federal courts sitting in New York County, New York, and we each consent to that jurisdiction.

If you are a consumer resident elsewhere, this does not deprive you of the protection of mandatory law where you live, or of the right to bring proceedings in your local courts where the law gives you that right.

Before either of us goes to court, please write to [LEGAL EMAIL]. Most things are faster to fix than to argue about.

Changes and ending this

We may update these terms. Material changes will be notified in the app or by email at least 30 days before they take effect, and continuing to use nCommunity afterwards means you accept them. If you do not, you can close your account, and any refund you were already owed is still owed.

You can stop using nCommunity at any time. To close your account, write to [PRIVACY EMAIL]. There is no self-serve control for this yet, and we would rather say so than pretend otherwise.

We may suspend or close an account under section 14. Sections that by their nature should survive (content licences already granted, liability, indemnity, governing law) survive the end of this agreement.

If a court finds any part of these terms unenforceable, the rest stays in force. Our not enforcing something once does not waive it.

Contact

Legal notices: [LEGAL EMAIL]
Account and privacy requests: [PRIVACY EMAIL]
Post: [LEGAL ENTITY NAME], [REGISTERED ADDRESS]

How we handle your information is in our privacy policy.