# Security and accessibility

> How Highbar protects your event and attendee data, what the AI Concierge can see, who processes data for us, and how the event app supports attendees with disabilities.

Source: https://help.highbar.ai/docs/reference/security-and-accessibility
Audience: event organizers, working in the Highbar dashboard

Use this page to answer your security, IT or accessibility team's questions about Highbar. For a DPA, an NDA or anything not covered here, email [hello@highbar.ai](mailto:hello@highbar.ai).

## Security at a glance

- **Hosted on Google Cloud and Vercel,** with data encrypted in transit and at rest.
- **Each event is isolated.** Every event has its own address and its own login, and every database query is limited to one event. Attendees of one event can't see anything from another.
- **No passwords.** Attendees log in with a one-time code sent by email. Organizers use an email code or Google.
- **Minimal personal data.** Highbar stores what it needs to run your event, and nothing it doesn't.
- **Your data isn't for sale.** Highbar never sells, enriches or profiles attendee data, or uses it for advertising.

## Attendee data

### What Highbar stores

- Email addresses, to log in
- Attendee profiles: the details you import or register (name, company, job title, bio) and what attendees add themselves
- What attendees do in the app: bookmarks, session registrations, meetings, posts, messages and contacts they exchange
- Push notification tokens, for devices where attendees turn on notifications

Highbar doesn't collect government IDs or sensitive categories of personal data. For paid registration, card details go straight to Stripe and never reach Highbar's servers.

### Who can see what

- **Organizers** see the attendee list, analytics, and what attendees post in public places such as the activity stream. You can't read private messages between attendees.
- **Other attendees** see each other's profiles in **Community**, when you've turned it on. Attendees can hide their own profile and turn off direct messages if you allow it. See [Community and networking](https://help.highbar.ai/docs/attendees/community-and-networking#control-who-can-find-you).
- **Sponsors** see the leads their staff scan at the booth, and the analytics you share with them.

### Removing someone

Deleting a person from the [attendee list](https://help.highbar.ai/docs/event-app/access) also signs them out of the app on every device and cuts off their access to messages and the activity stream. With **Attendee list** access, they can't log back in.

## Logging in

- **One-time codes.** Attendees enter their email and get a 6-digit code. Codes are stored hashed, expire after 20 minutes, and are rate limited: after several wrong tries, the app refuses every code for a while.
- **Who can log in** is your choice: only people on your attendee list, or anyone with a valid email. See [Access](https://help.highbar.ai/docs/event-app/access).
- **Sessions** use secure, HTTP-only cookies.
- **Your team.** Organizers log in to the dashboard with an email code or with Google. Collaborators you invite can work only on the events they're invited to.

## The AI Concierge

The [AI Concierge](https://help.highbar.ai/docs/event-app/ai/ai-concierge) runs on Google Cloud's Vertex AI. To answer a question, it receives:

- The question and the conversation so far
- Your event's content: sessions, speakers, sponsors, FAQs, resources and event details
- The asking attendee's own details, so it can answer "What's my next session?": their profile, saved sessions, session registrations and their own meetings

It never sees other attendees' private messages, meeting invitations or feedback. When [AI Curation](https://help.highbar.ai/docs/event-app/ai/ai-curation) is on, it can suggest people to meet using the profile details attendees can already see in **Community**. Questions are checked for unsafe requests before they reach the model.

## Infrastructure

| Provider | What it runs | Certifications |
| --- | --- | --- |
| **Google Cloud Platform** | Databases (Cloud SQL), file storage, AI (Vertex AI) | SOC 2 Type II, ISO 27001, GDPR compliant |
| **Vercel** | The apps themselves, logins, caching, usage analytics | SOC 2 |

- **Separate databases.** Logins, attendee data, event content and settings live in separate databases with their own credentials.
- **Encrypted connections.** Every database connection uses TLS, with certificates rotated automatically.
- **No stored passwords for production systems.** Highbar connects to Google Cloud with Workload Identity Federation, so there are no long-lived keys to leak.
- **Backups** are managed by Google Cloud and Vercel.

Highbar itself doesn't hold an independent SOC 2 or ISO 27001 certification yet. It's on the roadmap.

## Subprocessors

| Subprocessor | Purpose | Data processed |
| --- | --- | --- |
| **Google Cloud Platform** | Databases, file storage and AI | Attendee profiles, event content, uploaded files, AI Concierge questions |
| **Vercel** | App hosting, logins, analytics | Login sessions, email addresses, usage analytics |
| **GetStream.io** | Activity stream, chat and messaging | Posts, comments, messages, attendee display names |
| **Stripe** | Payments for paid registration | Payment details for ticket purchases |
| **Postmark** | Email | Email addresses, login codes, transactional emails |
| **Crisp** | Highbar's support chat | Chat messages and contact details people share in it |
| **Sentry** | Error reporting | Technical error logs |

[Integrations](https://help.highbar.ai/docs/event-app/integrations) you connect, such as your registration platform, aren't on this list: you turn them on, and they bring your event data into Highbar.

## If something goes wrong

Highbar follows standard incident response practice. If there's a data breach, affected organizers and attendees are told within the time the law requires.

## Accessibility

The event app runs in the phone's browser, so it works with the accessibility features attendees already use, such as VoiceOver on iPhone and TalkBack on Android. Nothing needs to be downloaded from an app store.

- **Screen readers.** The app uses standard web controls, and its icon buttons, such as bookmarks, star ratings and the round quick-action button, have labels a screen reader reads out.
- **Reduced motion.** When a phone is set to reduce motion, the app turns off its animations.
- **Voice questions.** Attendees can speak their questions to the AI Concierge instead of typing.
- **No passwords to type.** The login code is at the start of the email's subject line and can be pasted in one go.
- **Accessible sessions.** Mark sessions with [session attributes](https://help.highbar.ai/docs/event-app/content/schedule#tracks-types-attributes-and-levels) such as Closed Captioning or ASL, so attendees can filter the schedule for them. Add a livestream to sessions people can follow remotely.
- **Your own words.** You can rename menu items and the word for sessions to whatever your attendees know. The app's built-in buttons and messages are in English.

<Callout type="warn">
Pinch-to-zoom is turned off in the event app. Attendees who need larger text can use their phone's own zoom: on iPhone, **Settings** > **Accessibility** > **Zoom**; on Android, **Settings** > **Accessibility** > **Magnification**.
</Callout>

If your organization needs an accessibility conformance report, or an attendee has an accessibility problem with the app, email [hello@highbar.ai](mailto:hello@highbar.ai).

