Privacy policy

HiveConf is operated by Ozark Bee Barn, LLC(“we”, “us”). This policy covers hiveconf.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.
• 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. Turning notifications off in your browser ends it.

We don’t use advertising trackers, we don’t build attendee profiles, and we don’t sell or rent any of this. After a conference ends, the per-device rows above are collapsed into plain totals per talk and the underlying rows are deleted, so there’s no lasting trail of an individual device.

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.
• Purchase records if you buy an add-on. Payment is processed by Stripe and we never receive your card details — we keep the fact of the purchase and Stripe’s reference for it.
• 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.

HiveConf is built and paid for by Ozark Bee Barn, LLC, which sells beekeeping supplies. Being plain about what that means: business contact details that appear in vendor listings are also used by Ozark Bee Barn, LLC to make contact about wholesale supply — the same company, using information it holds, to talk to businesses in its industry.

• This applies to business contact details — a company’s address for enquiries, not a private individual’s personal details.
• We contact vendors who have claimed their listing and are marked as open to it. A listing an organizer typed in, that the business never engaged with, is not an outreach target.
• Any commercial email we send identifies itself as such, carries our postal address, and has a working unsubscribe that we act on promptly. Unsubscribing has no effect on your listing or the conference app.
• We don’t sell, rent, or pass these details to anyone else. Attendee data is not part of this and never has been.

If you’d rather not hear from us, say so and that’s the end of it — no account needed.

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), and your browser vendor’s push service if you enable reminders. Each acts on our instructions. We may also disclose information if the law requires it.

Site measurement is aggregate — page views and loading speed. There are no advertising cookies and nothing is shared with ad networks.

Per-device attendee data is reduced to anonymous totals once a conference ends. 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. 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.

HiveConf isn’t directed at children and we don’t knowingly collect their information. Young people do attend beekeeping conferences, 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 move the effective date 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.