How ChapterIQ protects your data

ChapterIQ holds membership rosters, contact details, and attendance history for the organizations that use it. This page describes, in plain terms, how that data is protected. It is written for the person at a member organization who has to answer the question "what does this vendor do with our data?" before a purchase is approved. If it does not answer your question, write to info@chapteriqevents.com and we will.

ChapterIQ is a new product from a small company. We do not yet hold a SOC 2 report or an ISO 27001 certification, and we would rather say so here than let you find out later. What follows is what we actually do.

Where it runs

ChapterIQ runs entirely on Microsoft Azure, in data centers in the United States. The database is Azure SQL, files are in Azure Storage, and the application runs on Azure App Service. Microsoft's own physical and infrastructure security controls, which are independently audited, apply underneath everything we build.

Encryption

Every connection to ChapterIQ uses TLS 1.2 or later, and plain HTTP is redirected to HTTPS. Data at rest is encrypted by Azure SQL and Azure Storage using their built-in encryption. Backups are encrypted the same way. Secrets such as database credentials and API keys live in Azure Key Vault and are read by the application through managed identities, so they are never stored in code or configuration files.

Keeping customers apart

Every customer's data carries the customer's identifier, and the database enforces row-level security keyed to it. That means a query from one customer's session cannot return another customer's rows even if the application code makes a mistake. Our automated tests exercise every endpoint with a second customer's credentials to confirm that nothing leaks across the boundary, and a change that fails that test cannot be deployed.

Who can sign in

Staff sign in with the Microsoft 365 or Google work account they already have. ChapterIQ never sees or stores a password, and it inherits whatever multifactor and conditional access policies your IT department has already applied to those accounts. Enterprise single sign-on through your own identity provider is available on the Scale and Enterprise plans. Members and invitees never need an account at all. They respond and check in through a personal link that is signed and expires.

Inside the service, access is scoped by chapter. A chapter manager sees only the chapters they are assigned to, and headquarters roles see the whole network. Every action that changes data is written to an audit log that the customer's administrators can read.

Connecting to your CRM

ChapterIQ reads organizations and people from Salesforce, HubSpot, or Dynamics 365 through a dedicated integration user whose permissions you control. You choose which fields are mapped, and ChapterIQ asks for read access to those fields and nothing else. Writing participation back to the CRM is off by default, and when it is on it is limited to attendance and engagement fields. Dietary and accommodation details are never written to a CRM. A page inside ChapterIQ shows exactly which objects, fields, and records the connection can see, and it can be exported for a security review.

Sharing with sponsors and venues

Venues and caterers receive counts and dietary totals, never names. Sponsors receive an attendee roster only if the customer turns that on, and attendees can decline to be included. Roster download links are signed and expire.

Backups and recovery

The database is backed up automatically by Azure SQL with point-in-time restore, and backups are stored in a separate region from the live service. We test restoring from backup as part of our release process.

Your data is yours

A customer can export every organization, person, event, RSVP, and attendance record it holds, as CSV or Excel or through the API, at any time. When a contract ends we keep the data for 90 days so it can be exported, and then we delete it. Our Privacy Policy lists the providers that process data on our behalf.

Reporting a vulnerability

If you believe you have found a security problem in ChapterIQ, please tell us at info@chapteriqevents.com. We will acknowledge your report within three business days, keep you informed while we work on it, and credit you if you would like. We ask that you give us a reasonable time to fix the problem before making it public, and that you not access or alter data that is not yours while testing.

Questions for a security review

If your organization has a vendor questionnaire, send it to the address above. We answer them ourselves, in writing, and we would rather answer a hard question honestly than sell you something that does not fit.