NEXA co-host terms
TLDR
NEXA helps you review your Partiful event's guests using automated analysis. NEXA never automatically declines anyone; a decline is always your decision. Guest information is used to help with your event; other NEXA uses require the guest's separate permission. Public professional facts may be reused across co-hosted events. Event records and public professional facts have different retention periods, and both are deleted on 2026-12-01. You can remove NEXA from your event at any time. Questions and data requests go to zubin@nexa.community or jhalak@nexa.community. New terms require your fresh acceptance.
Visible co-host
NEXA appears as a co-host under its own Partiful account. These terms cover its co-host service for your events. Linking your NEXA Events account to your Partiful identity does not accept these terms for you. You can see event guest information only while you are an owner of that event in Partiful. Accepting these terms does not grant access to another host's event, and removal as an owner ends your access through NEXA.
Event and guest data
NEXA receives your event's roster, guest names, RSVP status and history, questionnaire answers, any public profile links supplied for the event, and relevant event details. We may use public data about guests on the web to find professional person and company facts and assess applicants against your published criteria. Service providers may process this information on our behalf. We require providers used for guest assessment not to retain the guest information we send them for that assessment. We do not obtain guests' email addresses or phone numbers from public-data services for this purpose.
For assessing applicants to your event, we process guest information on your behalf. RSVP details, questionnaire answers, scores and decisions remain specific to your event. Public professional facts may be retained separately and reused to help review applicants for other co-hosted events. Other hosts cannot browse those facts or see your guest list; each host sees only guests at events they currently own. An event RSVP does not enroll a guest in NEXA. NEXA's own matching, onboarding, marketing or other uses of event information require the guest's separate, recorded permission. We do not build a cross-event guest banlist or reputation score. NEXA does not message guests about their event application in this version; Partiful sends its own guest notifications.
Automated decisions
Automated scoring can be wrong. You review the criteria, the questions guests will answer and how their answers will be interpreted before publishing them. Reviewing all applicants yourself is the default. Where you enable it, NEXA may approve applicants above your chosen threshold or place them on a reversible waitlist for your review. Uncertain cases go to you.
NEXA never automatically declines anyone. Every decline requires a human host's explicit action. A reversible waitlist is the only unfavorable automated outcome. Missing or unavailable information is not treated as a negative score. Unsupported events do not receive guest processing; open events do not receive automated guest scoring or decisions.
Explicit analysis and history
Editing criteria does not automatically rescore existing guests. Each past assessment remains associated with the criteria used at the time. If you ask for a new assessment, it updates only the analysis you see. It never approves, waitlists or declines a guest, or changes a past decision or who made it. New assessments use only information we are still allowed to keep for the event; they do not collect fresh public facts. Missing information goes to your review. This history is retained only within the guest's applicable retention period.
Retention and sunset
For guests who have not separately opted in to NEXA, event-specific guest records, questionnaire answers and scoring history are deleted 30 days after the event date. Public professional facts about a person may be kept separately for approximately 90 days, and company facts for approximately 30 days. Those facts can outlive the event record and may be used for another co-hosted event during those periods.
On 2026-12-01 we delete both event guest data and the separately retained public professional facts, regardless of those periods. We may keep limited records of consent and decisions as evidence of what happened; that does not permit continued guest processing. A deletion request can cover both the event record and the separately retained facts. Deleting NEXA's copies does not delete the host's or Partiful's own copies.
Pauses
When NEXA pauses an event, automated actions stop until we resolve the issue. Removing NEXA or disabling the service does not suspend our deletion obligations. For a bad approval, criteria dispute or service issue, contact zubin@nexa.community or jhalak@nexa.community.
Shared account risk
NEXA uses its own Partiful account, never your credentials. An interruption to that account can pause NEXA's service across multiple events. You retain control of your event in Partiful.
Removing NEXA
You can remove NEXA as a co-host in Partiful at any time. Removal ends NEXA's permission immediately, and NEXA stops processing the event when it no longer has permission. Removal does not waive deletion obligations or grant access to your remaining Partiful data. NEXA otherwise stays visibly listed as co-host after your event.
Contact
Contact zubin@nexa.community or jhalak@nexa.community for access, correction, erasure, disputes or service questions, including requests covering both event records and separately retained public professional facts.
Changes and fresh acceptance
You accept the specific current version yourself using your NEXA Events account. Any change to these terms is a new version requiring fresh acceptance before host configuration or guest-data access can continue. Previous versions remain available at their dated links.
Criteria policy
The following is the NEXA Co-host Criteria Policy that applies to this version.
NEXA Co-host Criteria Policy
TLDR
NEXA supports affinity communities but does not help hosts exclude people based
on a protected characteristic. We review every set of criteria before it can be
used. Clear affinity may be approved; clear exclusion is refused; ambiguous
criteria are held for review. The host can revise and re-submit immediately, or
wait for NEXA review. Only approved criteria may be used to score applicants.
Questions or disputes go to zubin@nexa.community or
jhalak@nexa.community.
The line: affinity, not exclusion
A community gathering around a shared identity is different from excluding others because of theirs. Mentioning an identity is not itself a reason to refuse criteria. We consider the meaning and likely direction of a restriction, including coded or indirect wording.
| Allowed affinity | Refused exclusion |
|---|---|
| “women in AI”, “women founders” | “men only”, “no women” |
| “South Asian founders”, “German tech community” | “white founders only”, “no Indians” |
| “Black engineers”, “LGBTQ+ founders” | criteria whose effect is to exclude an under-represented group |
These examples explain the rule; they are not a complete list.
What happens to your criteria
- Approved: The host can review the resulting questions and use the criteria for applicant scoring.
- Refused: We do not publish criteria that clearly exclude people on a protected basis. The host can revise and re-submit immediately.
- Held for review: Ambiguous criteria are not published or used for scoring. The host can revise and re-submit immediately, or wait for NEXA review.
We review the exact wording each time a host publishes or republishes criteria. Editing an approved set creates a new draft; prior approval does not carry over to the changed wording. Refused, held, draft, pending and unknown criteria are not used to score applicants. Criteria without a usable question about overall fit may be published for display and manual review, but cannot enable automated decisions.
Questions and disputes
If we refuse or hold your criteria, we give you a short reason and a way to revise them or ask for review. A revised submission can proceed when approved; you do not have to wait for a response to an earlier review request.
Contact zubin@nexa.community or jhalak@nexa.community with a question or
dispute. Do not include guest personal information unless it is needed to
resolve your request.
Version 2026-09-29
Contact NEXA about these terms: zubin@nexa.community or jhalak@nexa.community.