1. Who we are
ConferenceOS is built and operated by Peripety Labs LLC, a North Carolina limited liability company (“Peripety Labs,” “we,” “us”). This policy explains how we handle personal data in three places: this website, the ConferenceOS demonstration instance, and ConferenceOS deployments we operate for customers.
2. The conferenceos.io website
The website is a set of static pages. It has no sign-in, no forms, no advertising, and no analytics or tracking scripts, and it does not set cookies. Fonts and images are served from our own domain, so loading a page doesn’t contact any third party.
Our hosting provider, Vercel, records standard request logs (IP address, browser user agent, the page requested, and the time) to deliver the site and protect it from abuse. We don’t combine those logs with other data or use them to identify visitors.
If you email us, we receive whatever you include in your message and use it only to reply and to keep a record of the conversation.
We process this information on the basis of our legitimate interests in running and securing the website and in answering people who contact us.
3. The demonstration instance
demo.conferenceos.io is a demonstration of the product, not a place to run a real event. Peripety Labs is the controller for demo accounts. If you create one, our sign-in provider processes your name, email address, and authentication identifiers so you can log in, and sets the cookies sign-in needs. (Those cookies belong to the demo; the conferenceos.io website itself sets none.) The lawful basis is performance of a contract: providing the demo you signed up to use.
Anything you enter in the demo may be visible to other demo users. Demo accounts and content are kept only while the demo environment runs, and resetting the demo clears its content. You can ask us to delete your demo account at any time. Please don’t enter real attendee data or payment details in the demo.
4. ConferenceOS deployments: the organizer is in control
Each organization that runs events on ConferenceOS gets its own isolated deployment and database. For the attendee, speaker, sponsor, and registration data in that deployment, the organizer is the controller: it decides what to collect and why, and its own privacy notice governs that data. Where Peripety Labs operates a deployment on an organizer’s behalf, we act as its service provider (a “processor” under GDPR) and handle that data only to provide the service, under our agreement with the organizer.
If you registered for, spoke at, or sponsored an event that runs on ConferenceOS, contact that event’s organizer about your data. If you contact us instead, we’ll pass your request to the organizer and help them respond.
Ticket payments go through the organizer’s own Stripe account. Card details are entered on Stripe’s hosted checkout and never reach ConferenceOS servers.
5. Service providers
A deployment uses the providers below. Which ones are active depends on the capabilities an organizer turns on. Each is engaged to perform the function listed.
| Provider | Purpose | Data involved |
|---|---|---|
| Vercel | Hosting and delivery of the website and ConferenceOS deployments | Request logs, including IP address and user agent |
| Neon (PostgreSQL) | Database for ConferenceOS deployments | Event, registration, and account records |
| Clerk | Sign-in and account management in ConferenceOS | Name, email address, authentication identifiers |
| Resend | Transactional email sent by ConferenceOS | Recipient email address and message content |
| UploadThing | File uploads such as speaker photos and sponsor assets | Uploaded files |
| Anthropic or OpenAI | The AI assistant an organizer chooses to connect | Event data the assistant is permitted to read through its key |
An AI assistant sees only what the role on its key allows. The organizer chooses whether to connect one and which vendor to use.
6. We don't sell personal data
We don’t sell personal data, and we don’t share it for cross-context behavioral advertising. We don’t use data in customer deployments to train AI models.
7. How long we keep data
We keep email correspondence for as long as we need it to deal with your request and keep reasonable business records. Hosting request logs are kept for the provider’s standard retention period. Data in a customer deployment is kept and deleted according to the organizer’s instructions; when a customer relationship ends, the organizer can export its data first.
8. Your rights
Depending on where you live, you may have the right to access, correct, delete, or receive a copy of your personal data, and to object to or restrict certain processing. To make a request about data we hold as controller, email us at mrhinkle@peripety.com. We may need to confirm your identity first. For data in an event’s deployment, the organizer handles the request, as described in section 4.
If you’re in the EEA or UK, you can also complain to your local data-protection authority.
9. Where data is processed
Peripety Labs is based in the United States, and our service providers may process data in the United States and other countries. Where the law requires it, we rely on appropriate safeguards for international transfers, such as standard contractual clauses. You can ask us for details of the safeguards that apply to your data.
10. Children
ConferenceOS and this website are for professionals running and attending events. They aren’t directed at children under 16, and we don’t knowingly collect their personal data.
11. Changes to this policy
If we change this policy, we’ll update the effective date at the top of this page. For a material change affecting customer deployments, we’ll notify organizers directly.
Contact
Peripety Labs LLC
964 High House Rd #3074, Cary, NC 27513, United States
mrhinkle@peripety.com