Privacy policy

Event Easel is operated by Nectarmark, LLC (nectarmark.com) (“we”, “us”). This policy covers eventeasel.com, the conference apps hosted on it, and the interfaces organizers use to build events.

You don’t sign in, and there’s no account to create. The app is built so that we do not know who you are, which is why the list below is short.

• Talks you star. Stored on your phone, and sent to us attached to a random identifier generated by your browser. It lets organizers see that forty people plan to attend a session in a room that seats thirty. It is not linked to a name, an email address, or an account, because we don’t have those.
• Ratings and comments you leave on a talk. Stored with a hashed device identifier, purely so the same phone can revise its own rating instead of voting twice. Organizers see ratings and comments, and cannot see which device left which.
• Your answers to the attendee survey. A short survey about how the app worked for you, stored with a hashed device identifier so the same phone can change its answer and isn’t asked again. It also records whether your phone scanned the event’s printed QR code, so results from people who were there can be told apart. Leaving a name and email is optional. At events with a prize drawing, an email is needed to enter, and whoever runs the drawing (Event Easel or the event organizers, as the survey says) sees the winners’ names and emails to get the prizes to them. Organizers see anyone else’s email only if you tick the box letting them contact you. A written comment may be used in Event Easel marketing materials; the survey says so where you write it, and nothing more than your first name, last initial, and the event it came from is ever shown with it. The name, email, and device identifier are deleted 90 days after the event; the anonymous answers are kept.
• That the app was opened. Counted once per device per day using an identifier that is re-salted daily, so the counts cannot be joined together into a record of one person’s movements across days.
• A push subscription, if you turn on reminders. This is an opaque address issued by your browser vendor, with no identity attached. We store it with a hashed device identifier, so the survey notification skips phones that already answered. It lasts until you turn notifications off in your browser, which ends it.

There are no advertising trackers anywhere in the conference app or on event pages, we don’t build attendee profiles, and we don’t sell or rent any of this. After a conference ends, starred talks and app opens are collapsed into plain totals and the per-device rows are deleted. Talk ratings and survey answers are kept, so organizers can see how their events change from year to year; the survey’s device identifier, name, and email are deleted 90 days after the event.

These hold at every event, whatever features its organizer uses.

• There are no advertising trackers in the conference app or on event pages.
• We don’t sell or rent information about attendees. We don’t use it for our own marketing or advertising, or to train AI models. The one exception is a comment you tick a box to let us quote, and then only as described above.
• Nothing about attendees is ever passed to the venue hosting the event.
• The schedule and the venue map work without signing in.
• Nothing that needs to know who you are is switched on at an event unless its organizer turns it on. If a feature like that is ever added, this policy will describe it before it is available, and the event will tell you before you are asked for anything.

We store your email address, the events you may edit, and everything you enter about your conference. There are no passwords: you sign in with a link sent to your email.

• Your event’s content — schedule, speakers, vendors, rooms, venue and registration details. Most of it is intended to be public, and is.
• A history of changes. We keep snapshots of your event document so a bad edit can be undone. These contain your event’s content, not your conversations.
• What the venue hosting your event sees. Your event is part of a booking with that venue, and the venue sees the booking: the event’s name and dates, the rooms it uses, the contracted headcount, and what has been billed and paid for it. It never sees attendee data.
• Assistant connections, if you connect an AI assistant to your event. We store a hashed access credential, which events it covers, and when it was last used. Disconnecting deletes it.

Organizers build listings for the people and businesses at their conference, usually from a spreadsheet or their own website, and usually before speaking to us or to you. A listing can include your name, business name, description, website, logo or photo, social links, booth number, and contact details the organizer holds.

Vendor listings are published with contact information, because a directory of vendors nobody can reach is of no use to attendees. You can claim your listing and maintain it yourself, and you can ask us to correct or remove it at any time — you do not need an account, a reason, or the organizer’s permission. Write to our legal address or use the support page, and we’ll confirm when it’s done.

Contact details in speaker and vendor listings are used to run those listings: to publish what the organizer chose to publish, to invite the person listed to manage their own listing, and to answer them when they write to us. We don’t use them for sales outreach, and we don’t sell, rent, or pass them to anyone else. Attendee data is not part of this, because we don’t collect it.

The home page lets someone planning an event tell us which venue it’s booked at, so we can offer Event Easel to that venue. We receive what you type: your name and email, the venue and its city, and a contact there if you give one. It reaches us as an email; we use it to get in touch with that venue and, if needed, to reply to you. We give the venue your name and email only if you tick the box that allows it; otherwise we tell them only that a client asked. We don’t add you to a mailing list, and we don’t pass what you sent to anyone else.

We advertise Event Easel to venues, and to see which ads work, our home page and these legal and support pages load Meta’s advertising pixel. It never loads in the venue dashboard or the admin, on an event page or in the conference apps, in an embedded schedule, or on a printed sheet.

• What the pixel sees. Meta sets cookies that identify your browser, and receives the pages you view here, your IP address and browser details, and the ad you arrived from, if any, including the campaign labels on its link. Meta handles that under its own privacy policy.
• When it loads. In the European Economic Area, the United Kingdom, and Switzerland we ask first, and nothing loads until you allow it. Elsewhere it loads unless you turn it off. “Ad settings” at the bottom of these pages changes your choice at any time, and a browser that sends Global Privacy Control never loads it.
• If you get in touch. When the pixel was allowed in your browser, tapping our email address, or suggesting your venue to us, is reported to Meta as a contact or a lead. A venue suggestion is also reported from our server, with the pixel’s identifiers, the campaign labels, your browser’s description and a one-way hash of the email you entered rather than the address itself, so an ad blocker doesn’t lose it; Meta counts the two as one. We keep none of it.
• What we don’t do. We don’t use any of this to build a profile of you, we don’t sell it, and nothing about attendees is ever part of it.

To see where organizers stop on the way from signing up to a live event, we record, on our own server, the first time each organizer reaches each step: asking for a sign-in link, using it, accepting the organizer agreement, creating an event, adding a schedule, and going live. Each record is the step, your email address, the event, and the time. Only the people who run Event Easel see it, it is not shared, and it doesn’t depend on the ad tags or your choice about them. The records are kept for a year; after that only monthly totals remain.

We use Anthropic’s Claude models in a few defined places. Text sent to them is used to produce the result and is not used to train models.

• Tidying what people write. Speaker bios, vendor descriptions, and session descriptions get a light spelling and punctuation pass when saved. It adds no facts, claims, or links. The original is kept and the change can be undone.
• Writing vendor descriptions. Where a vendor listing has no usable description, we may write one from the business’s own public website and publish it. It is checked against the business name first, and if the site doesn’t clearly belong to that business we stop rather than guess. Every listing carries a note that this happens, the original text is kept, and we will change or remove the wording on request — this is the most common thing people write to us about, and it is not a difficult conversation.
• Building a theme from a logo. An uploaded logo is sent to the model to generate color palettes.
• Assistants connected by an organizer. If an organizer connects Claude or ChatGPT to their event, that assistant reads and changes event content with their approval. We record what changed and when. We do not receive or store the organizer’s conversation with their assistant.

We keep the list short and use each for one job: Vercel (hosting and basic traffic measurement), Neon and Cloudflare R2 (database and file storage), Stripe (payments), Resend (email delivery), Anthropic (the AI features above), your browser vendor’s push service if you enable reminders, and Meta for advertising measurement, as described under Advertising on our website. Each acts on our instructions. We may also disclose information if the law requires it.

Site measurement is aggregate — page views and loading speed. The attendee app sets one cookie: the random device identifier described above, so that a copy of the app added to a phone’s Home Screen can find the talks that were starred in the browser. It names a device, never a person, and expires after a year. The attendee app sets no advertising cookies and shares nothing with ad networks.

Starred talks and app-open counts are reduced to anonymous totals once a conference ends. Talk ratings and survey answers are kept without an end date; names, emails, and the device identifier on survey answers are deleted 90 days after the event. Event content, listings, and change history are kept while the event exists, because links to talks and speakers are shared publicly and are expected to keep working. The record of which steps an organizer reached is kept a year, then reduced to monthly totals. Purchase records are kept as long as tax and accounting rules require. Ask us to delete something and we’ll tell you plainly what we can remove and what we’re obliged to keep.

Ask us what we hold about you, ask for it corrected, ask for it deleted, or ask us to stop contacting you. Depending on where you live you may have these as legal rights; we try to honor them for everyone regardless. We don’t charge for this and we won’t make you create an account to do it. Reach us through the support page.

Event Easel isn’t directed at children and we don’t knowingly collect their information. Young people do attend conferences and fairs, and the attendee app is built to need nothing from them — no account, no name, no email.

When we change how any of this works, we update this page and give it a new version number and effective date, shown at the top. If a change is significant — a new use of information, or a new company handling it — we’ll say so where organizers will see it rather than relying on you to re-read the page.

Earlier versions: version 5 (October 26, 2026 to October 29, 2026), version 4 (October 25, 2026 to October 26, 2026).