Privacy Policy

Last updated: 15 October 2026

A Conference App (at aconference.app) is operated by Jonathan Cale ("we"). This policy explains what we store, who can see it, and what you can do about it.

The short version

  • No ads, no marketing, no data sales. What we send you is the notifications you turned on, plus the occasional message running your account requires (a sign-in link, a verification code).
  • No tracking cookies. We use cookies and browser storage to keep you signed in and remember your settings — no advertising or cross-site tracking, no behavioral-analytics scripts in the app.
  • Chat stays between the people in the chat. Message content is never sold, never sent to analytics or AI providers, and never shown to conference organizers.
  • You can delete your account from inside the app.

The rest of this page is the detail behind those four lines.

What we store

If you sign in: your email address, name, and profile picture from your sign-in provider, plus session data.

If an organizer imported you: the email address they uploaded, plus any name, headline, about text and tags in their attendee list — held before you ever sign in. Signing in with that email address attaches the record to your account, and you can edit or clear it from there.

If you fill it in: your per-conference profile (headline, about, tags, and any contact details you choose to publish), your meetings and RSVPs, chat messages, private meeting notes, meeting ratings, survey answers, job posts and job applications.

If you enable notifications: notification settings, push subscriptions for the devices you enabled, and your mobile phone number — only if you opt into text messages.

Whenever you use the app: ordinary server logs of requests to the app, which may include IP address, device and browser information, and which app functions ran. We use them for debugging, security and abuse handling. There is no deletion schedule for logs — we may keep ours indefinitely, and our hosting, sign-in and monitoring providers keep their own on their own terms.

We don't ask for special-category data (health, religion, political views, and so on). What you type into free-text fields is up to you.

Who can see what

Other attendees of the conference

Everything you post publicly to a conference: your name, photo, headline, about text, tags, contact details you added to your profile, the public sessions you create or RSVP to, and your messages in group chats you're in. Each conference also has a visibility setting, so depending on that setting this may be visible to any signed-in user rather than only to attendees.

When you're busy. Anyone who can schedule a 1-on-1 with you sees which slots you're already booked or tentative in, so they can pick a time that works. Private meetings count towards that. They see the times only — never the title, the location, the agenda, or who else is in it.

Private meetings are private

Everyone invited to a private meeting sees its title, agenda, time, location, and the other participants with their RSVP status. No other attendee or organizer sees any of it — though they can still see that you're busy then, as above.

Conference organizers (admins)

Organizers of a conference you joined see everything another attendee sees, plus:

  • Your account email address — the one you sign in with, even if you didn't publish it. It lets them match you to their registration list, and makes it harder for someone to impersonate you.
  • Whether you've signed in yet, and your check-in status.
  • Activity statistics with no names attached: how many 1-on-1s were created, accepted and declined, chat activity as counts only, notification enrollment. Exported as rows with no names, shuffled so the row order carries no signal. (At a very small conference a row can sometimes still be guessed at.)
  • Your meeting ratings, with your name, email and the day you gave the rating — but never which meeting it was about or who else was in it. The day hints at roughly when the meeting happened; organizers get no exact time.
  • Your survey answers, with your name, to whoever created that survey. Surveys are not anonymous.

Organizers cannot see your chat messages, your private meeting notes, or who you met privately.

Job posters

If you apply to a job on a conference job board, the owners of that posting (and the conference organizers) can see your name, profile, application note, and your account email address. The app tells you this before you apply.

Services you connect yourself

  • Calendar subscription: the calendar provider you gave the link to (Google, Apple, …) fetches your schedule on a repeating basis — meeting titles, times, locations, descriptions, and the names and RSVP status of the other participants. Anyone else who gets that secret link has the same access, so treat it like a password.
  • External AI connectors: an outside AI client you connect receives the conference's attendee list, sessions, jobs, info pages, and your own schedule. It never receives attendee-to-attendee chat. You can exclude your profile from these connectors in your settings.

The in-app AI assistant

If you use the assistant, your messages to it, public conference data (other attendees' public profiles, sessions, jobs, info pages) and your own schedule are sent to an AI provider to generate a reply, under terms that don't allow training on your data. The assistant has no access to attendee-to-attendee chat. The assistant may end a conversation; we may keep a record of when that happened, without its content.

Organizers may also use AI tools in the app, for example to turn a programme they paste into sessions. Those may send public conference data to an AI provider under the same terms, which may include the names of the hosts and speakers of public sessions. They have no access to attendee-to-attendee chat or to private meetings.

Us

We can technically reach the database — that's what running the service requires. We look at data when we have a reason to: investigating a bug or an abuse report, or a legal obligation. Chat content is not part of any routine process and is not in our logs.

Chat messages

Message content between attendees is never logged, never sent to analytics or AI providers, and never shown to conference organizers. The one exception is the push notification you asked for: its preview is encrypted before it leaves our servers (Web Push, RFC 8291), so the push service that delivers it can't read it. Email and text-message notifications never include message content.

Chat is not end-to-end encrypted. Messages are stored in our database — which runs on Convex, our hosting provider — so they're there on your next device, and so we can technically reach them. See the Terms on how much to rely on that.

Cookies and browser storage

  • Staying signed in: our authentication provider sets cookies for your session.
  • On your device: drafts, filters and display preferences live in your browser's local storage. You can inspect and clear them in the app's settings.
  • Error monitoring in the app itself doesn't track your behavior or build a profile of you.

Notifications

We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes.

You choose which notifications you get and can turn any of them off in the app.

  • Email — our email provider receives your address and the notification.
  • Push — delivered through your browser's push service, encrypted as described above.
  • Text messages (SMS) — only after you tick the separate SMS consent box and verify your mobile number. Message frequency varies; message and data rates may apply. Reply HELP for help or STOP to cancel. The full program terms are in the Terms.

We use your number to verify it when you add it, to send the notifications you asked for, and to honor a STOP — nothing else.

Service providers

Running the app means some of your data passes through other companies. They may use it only to provide their service to us.

In use today:

  • Clerk — sign-in and accounts.
  • Convex — database and backend.
  • Netlify — hosting.
  • Datadog — log analysis and monitoring, which our server logs are streamed to.
  • Resend — email delivery.
  • Twilio — text message delivery and phone number verification.
  • Browser push services (Apple, Google, Mozilla, …) — push delivery; content is encrypted.
  • Anthropic — the in-app AI assistant, and any other AI-generated suggestions we add.

We may add or swap providers in the categories above (a different AI, email, SMS or monitoring provider, for example) without rewriting this page each time.

Changing, exporting and deleting your data

You are providing your personal data of your own will and are under no obligation to do so. You may refuse to provide us with any personal data, but then we won't be able to provide you with the service.

  • Edit or clear your profile any time in the app.
  • Delete your account in the app. This deletes your profile, contact details, private notes, ratings, notification settings and profile picture, and detaches your name and email from what's left. Messages you already sent stay in their chats, no longer attached to your name — deleting them would tear holes in other people's conversations.
  • Ask us for a copy of your data, for deletion, or anything else about this policy: email the address below.

If you think your privacy was invaded

Email us and tell us — we'd rather hear it than not. We'll look into complaints and requests within a reasonable time and get back to you. If you're in the EU or another place with a data protection authority, you can also complain to that authority.

Changes to this policy

We'll update this page as the app changes, and announce significant changes in the app.

Contact

privacy@aconference.app