Protect Camp Data.
Keep Access Simple.
Family, camper, medical, and payment information, protected by mechanisms you can check rather than adjectives: a dedicated identity provider, data isolated by organization on the server, role-based access, and AES-256 encryption at rest.
Built for the Questions Your IT Team Will Ask
Not adjectives. The actual mechanisms: who authenticates you, what keeps one tenant's data from another's, and what happens when something goes wrong.
Authentication via Clerk
Sign-in runs through Clerk, a dedicated identity provider, not a homegrown login system, with secure sessions and credential protection.
Multi-Tenant Data Isolation
Every data path, including AI-generated queries, is scoped to your tenant on the server. The AI never decides which tenant's data it can see; the platform does.
Role-Based Access Control
Custom roles with granular, category-organized permissions, including separate read/write access for reports and dashboards, and dedicated permissions for AI Builder, AI Placement, and Pulse IQ, so your seasonal counselor doesn't need to see the bank reconciliation.
Encrypted Everywhere
Customer data is encrypted at rest using AES-256, including database backups and uploaded files, and encrypted in transit using TLS.
Payment Protection
Payments run through your own connected Stripe account: PCI-compliant handling, no credit card data stored on CampPulse servers, and payouts follow your Stripe schedule directly to you.
Data Backup & Recovery
Continuous point-in-time recovery means your database can be restored to any moment within the past several days, not just the last nightly snapshot. Backups are independently retained for seven days.
Records That Can't Be Quietly Rewritten
Certifications can't be deleted, only superseded by a new record. System-generated communications can't be edited or deleted. Every placement override requires a typed reason, visible to anyone who asks.
Honest When Something's Wrong
A backend error never confirms or denies whether a camp exists to someone who isn't authorized to know. An unset timezone is labeled UTC, never guessed. A refund is announced as initiated, not returned, until the processor confirms it.
Your Data, Your Tenant
Every request resolves its tenant from your subdomain, and every data path, including AI-generated queries, is scoped to it on the server before it reaches the database. Your data doesn't stay separate because everyone remembered to filter by tenant. It stays separate because there's exactly one enforced place in the system where that filter happens.
camppulse360dbTenant 1
Isolated
Tenant 2
Isolated
Tenant 3
Isolated
Tenant 4
Isolated
Your Data Belongs to You
CampPulse is designed to protect personal information and ensure organizations retain full ownership of their data.
What to Expect When We Update the Platform
Most CampPulse 360 updates ship without any downtime, so you won't notice them. When maintenance does need to take the platform offline, we group it into one occurrence a month and pick the time we expect to affect the fewest organizations. We serve programs across many time zones, so there is no fixed window.
You'll get at least seven days' notice: it will be posted on our status page, and a banner inside CampPulse 360 will remind everyone who logs in. Occasionally something urgent, like a security patch, can't wait that long. When that happens we give as much notice as we can and tell you what happened afterwards.
Security Questions?
Organizations evaluating CampPulse often have questions about security practices, infrastructure, or compliance requirements. Our team is happy to provide additional information.
Security You Can Explain to Your Board
We're onboarding a limited number of founding partners personally, and we're happy to walk your IT team through any of this first.