1. Who we are
This Privacy Policy explains how Sensorium Presents LLC ("Sensorium," "we," "us," or "our") handles personal information through Sensorium Events (sensorium.events) and at our events. We do not sell personal information, and we collect only what we need to run the site, sell tickets and hold the events.
Questions about this policy, or about your own information, go to knowledge@sensorium.events.
2. What we collect
- Your account — name, username, email address, password (stored only as a one-way hash), and whatever you add to your profile: a photo, a bio, links, and the practices or products you offer.
- Tickets and orders — the event, the tickets and quantities, the price and any discount, fees and tax, the name and email on the order, when you checked in, and, if you arrived through a member’s link, which member shared it.
- Payments — card payments are taken by Stripe. Your card number is entered into Stripe’s own secure field and never reaches our servers; we keep only Stripe’s reference for the payment, the amount, and whether it was refunded.
- Vendor and practitioner details — the answers you give when you apply (your business or practice, what you offer, contact details), the space you book on a floor plan, and the sessions, team roles and shifts you are given.
- Payout and tax information — if you are paid a share of an event, we record what you are owed and paid. If you choose to be paid to a bank account, you give your bank and identity details directly to Stripe, not to us. Tax forms such as a Form W-9 are stored encrypted and can be opened only by you and the people responsible for our taxes.
- What you post — posts, comments, messages to other members, files you upload, and forms you submit.
- Conversations with the assistant — described on the AI & Privacy page.
- Visit information — the pages you view, the site that referred you, your browser, device type and an approximate location. See section 7.
3. How we use it
- To run your account and show your profile, posts and messages to the people they are meant for.
- To sell and deliver tickets, check you in at the door, and refund a ticket when one is refunded.
- To confirm vendor spaces, organise practitioners and event teams, and calculate and pay out event shares and seller rewards.
- To tell you about the events you hold tickets for: confirmations, changes, reminders and anything you need to know on the day.
- With your permission, to tell you about upcoming gatherings and community news.
- To keep the site secure, prevent fraud and duplicate charges, and meet our tax and accounting obligations.
- To understand, in aggregate, which pages and events people are interested in, so we can improve them.
4. Emails, texts and how to stop them
Emails about something you bought or signed up for — your ticket, a change to an event, a space request, a team assignment, a password reset — are part of the service, and we send them while you hold the ticket or role.
Announcements and community news are sent only to people who have agreed to receive them. Every such email carries a link to unsubscribe, and you can also ask us to stop at any time. Our emails may contain a small image that tells us whether the email was opened; blocking images in your mail app prevents it.
Text messages. If you give us your mobile number and agree to receive texts, we may text you about events you are attending and, if you agreed to it, about upcoming events. Message frequency varies and message and data rates may apply. Reply STOP to stop at any time, or HELP for help. We never share your mobile number or your consent to receive texts with anyone for their own marketing.
Agreeing to marketing messages is never a condition of buying a ticket.
5. Who we share it with
We share personal information only as far as each purpose needs:
- The event’s organisers and door team see the names on tickets and check-in status for that event. Where another organiser hosts an event, they receive the orders for their event.
- Practitioners and vendors see what they need to take part — the schedule, the floor plan, and the team they work with — not attendees’ payment details. The event team page never shows anyone’s email address.
- A member whose link you used sees that a sale came through their link, so they can be credited for it; they do not see your payment details.
- Other members and the public see what you choose to make public: your profile, public posts and your membership of the community. Vendor and practitioner profiles show the details of their application that are marked public; contact details are private by default.
- Service providers who process information for us: Stripe (payments, refunds and bank payouts), Anthropic (the assistant; see AI & Privacy), Google Analytics (site statistics), ip-api.com (approximate location of a visit), Meta (only for the Facebook, Instagram and WhatsApp connections you choose to make; see below), and our hosting provider (servers and email delivery). Each handles information under its own privacy terms and only to provide its service to us.
- Where the law requires it, or to protect the safety of anyone at an event.
We do not sell personal information and do not share it with anyone for their own advertising.
Facebook, Instagram, Threads and WhatsApp
Linking an Instagram professional account or a Facebook Page is optional, and only happens when you press Connect. We then receive the account’s id, name or username and picture, so you can see which one is linked, and permission to publish to it only when you choose to share a post. We do not read your followers, comments or private messages through it.
Where a business on this site connects its Page, Instagram account or WhatsApp number to receive messages, the messages people send it, with their name and picture, are kept as that business’s conversations.
A link to a public Facebook, Instagram or Threads post may be shown as the post itself, in a frame that Meta serves; Meta may set its own cookies inside that frame under its privacy policy. In feeds the frame loads only when you press “Show post”.
The access Meta gives us is encrypted where we keep it and used only for these things — never sold, never used for advertising, never used to train an AI model. Disconnect any time in Account → Integrations. If you remove this site from your Facebook or Instagram settings, or ask Meta to have your data deleted, we delete every connection you made and give you a confirmation code and a page showing the request’s status.
6. Health and sensitive information
We do not ask for medical information to sell you a ticket. If you choose to tell us or a facilitator about a health condition so a practice can be adapted for you, it is used only for that. Please do not post health details in public areas of the site.
7. Cookies and analytics
- Session cookie — keeps you signed in. Required for the site to work.
- Our own visit counter — a random identifier that lets us count distinct visitors and returning visits. It is not linked to your name or email unless you are signed in, and it is never shared. To work out the country, region and city of a visit, the visit’s IP address is looked up at ip-api.com; we keep the place, not the IP address. Browsers that send a Do Not Track or Global Privacy Control signal are not counted.
- Seller link cookie — if you arrive through a member’s link to an event, we remember which member for 30 days so a ticket you buy is credited to them.
- Google Analytics — sets its own cookies to measure how the site is used. You can opt out with Google’s browser add-on or by blocking its cookies.
We do not run advertising networks on this site. Blocking cookies other than the session cookie does not stop you using it.
8. How long we keep it
- Your account and what you post are kept while your account is open, and deleted when you delete it.
- Tickets and payment records are kept after an account is deleted. A ticket is the event’s record of a sale as much as yours, and payment records are kept for as long as tax and accounting law requires.
- Payout records and tax forms are kept for as long as tax law requires.
- Security and audit logs — records of sign-ins and of who changed what — are kept so that problems can be investigated. They record actions, not the content of your messages.
9. Deleting your account
You can delete your account yourself from your account settings; we ask for your password to confirm it is you. Deletion removes your account and everything connected to it across the site — profile, posts, messages, files, preferences and sessions — except the records listed as kept in section 8. Content that belongs to someone else stays, without your name attached. If you cannot sign in, write to us and we will do it for you once we have confirmed who you are.
Where we issue a deletion certificate, it carries a fingerprint of what was destroyed and nothing personal, and anyone can check it on the verify a deletion certificate page.
10. Your rights
Wherever you live, you can ask us to:
- tell you what personal information we hold about you and give you a copy;
- correct anything that is wrong (most of it you can edit yourself in your account);
- delete your information, subject to the records we must keep;
- stop sending you marketing emails or texts.
Write to knowledge@sensorium.events. We will answer within 30 days, and we will not treat you differently for asking.
11. Security
The site is served only over encrypted connections, passwords are stored as one-way hashes, and card details never touch our servers. More detail is on our Security page.
12. Children
Sensorium Events is not directed at children. Accounts and ticket purchases are for adults aged 18 and over, and we do not knowingly collect personal information from children under 13. If you believe a child has given us information, tell us and we will delete it.
13. Changes to this policy
We may update this policy from time to time. The date at the top shows when it last changed, and we will tell account holders by email about any material change before it takes effect.
14. Contact
Sensorium Presents LLC
South Florida, United States
knowledge@sensorium.events
sensorium.events