Curator data stays curator data
Registration data collected through a curator's form is never exposed to another curator.
Trust Center
Your data belongs to you.
Always.
HereNow helps curators build an audience. We are not here to take the relationship after the curator earned the trust.
Our position, in one sentence
If you brought the audience, the audience is yours.
We provide the room.
Many event platforms treat attendee data as platform property. HereNow takes the opposite stance: the curator earns the trust, so the curator controls the outcome.
The matrix
Who owns what.
Three parties, three roles. This is the practical data ownership model we build against.
Data type
Curator
Attendee
HereNow
Attendee name and email
RSVP form data collected for an event
Owns
Owns
Custodian
Custom registration answers
Questions configured by the curator
Owns
Owns
Custodian
Event content
Description, images, agenda, recap, and reviews
Owns
-
Hosts
Curator brand assets
Slug, profile, colors, logo, and public identity
Owns
-
Hosts
Guest browsing behavior
Unauthenticated browsing and RSVP behavior
Aggregated only
Owns
Aggregates
AI prompts and event drafts
Conversation used to create or edit an event
Owns
-
Processes
Platform-level analytics
Total events, categories, and anonymized product usage
-
-
Owns
The promise
Trust is not a banner. It is product behavior.
These commitments are deliberately concrete so they can be checked in code and product decisions.
Guest emails are not marketing inventory
Guest RSVP emails are used for event operations, not platform growth campaigns.
Export and deletion are product requirements
Curators need CSV export and deletion paths because the audience relationship belongs to them.
No private cross-curator profiling
We do not privately stitch guest identities across unrelated curators' attendee lists.
Red lines
Four things we do not cross.
The easiest way to understand our model is to know what we refuse to do.
Never expose Curator A's attendee list to Curator B.
Never send platform marketing to guest RSVP emails.
Never force an attendee to create an account before RSVPing.
Never hide export or deletion behind a paid plan.
Security practices
Built with privacy boundaries from the start.
The product is still early, but the data model is not an afterthought. Access control, export, deletion, and guest privacy are core platform requirements.
Encrypted in transit
All app traffic runs over HTTPS/TLS.
Modern authentication
OAuth and magic-link flows reduce password friction and risk.
Hosted on Vercel
The public web app is built for managed deployments and observability.
Input validation
Forms and APIs are designed around validation, authorization, and scoped access.
Build the audience. Keep the relationship.
Create a first event page and keep your attendee data under your control from day one.