Skip to content
Trust and security

Your participants' data, handled like it's ours.

Every organization on Karsenics runs on its own isolated service. Nobody sees another organization's people, money, or plans, and card numbers never touch us. This page says exactly what we do, what we've had checked, and what's still in progress. Where a document backs a claim, you can ask for it.

Last reviewed October 2026 · reviewed quarterly
What's true today

Four things you can count on before you read anything else.

These aren't goals. They're how the platform is built and run right now.

Your organization is on its own island.

Each organization gets its own service, its own storage, and its own database, hosted in the United States and encrypted at rest and in transit. There's no shared database and no switch that could show one organization another's data, because the data isn't in the same place.

Your organizationown service · own database
Another orgown service · own database
Another orgown service · own database

Named people, no passwords to leak.

Your team signs in with a one-time link to their email. There's no password to reuse or steal. Your Primary Administrator decides who can see money, send messages, or change registrations, and can switch anyone off in one click.

Payments go to Stripe, never through us.

When a participant pays, they're handed to Stripe's own checkout page. Stripe is certified at the highest level of the card industry's security standard. Card numbers never reach Karsenics; we receive a payment confirmation. We're completing the card industry's self-assessment for this kind of setup, and we'll sign it every year.

Backed up every day. Restored on purpose, not just hoped for.

Every day, and every hour around your event, a full copy of your service goes to separate, encrypted storage in the United States, locked so nobody who gets into your service can change or delete it early. On October 22, 2026 we restored one onto a fresh server and checked the data, and it was running in under two minutes, because a backup nobody has tested is a hope. We repeat that test every quarter and record each result.

Independent assurance

Where we stand, without the badge wall.

Some of these we do ourselves and document. Some need an outside auditor. Most are in progress today, and each one says so with a date.

PCI DSSCard payment security
In progress: Target Q2 2027
Card details are typed only on Stripe's own payment page, so card numbers never reach Karsenics. Because we run the pages that send payers to Stripe, we assess ourselves as a service provider using the card industry's SAQ D for Service Providers, and we will sign it each year. Each organization files its own short merchant form, and we give it a sheet showing which requirements are ours, which are theirs, and which are shared.
Attestation, when signed
Accessibility, WCAG 2.2 AAVPAT / Accessibility Conformance Report
Self-assessed: Published, October 2026
We tested registration, volunteer signup, the document portal, the public map and pages, check-in, and the admin console against every WCAG 2.2 Level A and AA criterion, with a keyboard, the VoiceOver screen reader, and automated checks. The report gives every result. Four criteria are partly met, all in the map editors organizers use, with a fix date of Q2 2027.
CSA STAR Level 1Cloud Security Alliance registry
Listed publicly: Listed, October 2026
Our full security questionnaire, all 283 answers, is published in the Cloud Security Alliance's public registry where anyone can read every answer. Level 1 is a self-assessment: we answer Yes only where the control is fully in place today with evidence on file, and we update the entry every year.
SOC 2 Type IIIndependent audit of security controls
In progress: Target 2028
Our controls run on a documented schedule and we keep the evidence. The audit comes once that record is long enough to be worth auditing. Until the report exists, we won't say we have it.
Report, when issued
GDPREuropean privacy law
Not pursued: Not claimed
KarsenicsOS isn't set up for data covered by the EU or UK GDPR, and we don't claim GDPR compliance. If an organization ever needs that, our Data Processing Agreement requires a separate Standard Contractual Clauses addendum to be signed first, and until then that data stays out of the platform.
ISO/IEC 27001International security certification
Not pursued
Our SOC 2 controls are mapped to ISO 27001. We'll pursue certification when a client or partner needs it by name.
Our rule for this page: nothing here says “certified” or “compliant” unless a signed document exists and you can have a copy. When something is still a plan, it says so and carries a date.
Milton, Milton AI, and your data

Two names, one clear line: only Milton AI uses AI.

Milton sends your emails, with no AI involved

Confirmations, receipts, payment reminders, document requests, and deposit summaries go out from Milton, the automated assistant built into Karsenics. They are standard messages filled in from your records. They do not use AI, and nothing in them is sent to Anthropic.

Milton AI is the part that uses AI

Milton AI is an AI assistant built on a large language model: Claude, from Anthropic. It answers questions, builds lists, drafts memos, and explains parade lineup placements. It sees only what your organization has loaded: your event setup, the screen you are on, the agreements you upload, and registrations and money for team members who have access to them. Anthropic does not use what Milton AI is asked, or what it answers, to train its models.

Check before you rely on it

Milton AI can make mistakes. When an answer comes from the Karsenics guide or a document your organization uploaded, it links straight to that source. For money or deadlines, confirm the figure on its screen before you act. A memo Milton AI helps draft is sent by a person, under that person's name.

Turn Milton AI off, and it is off for everyone

Your Primary Administrator can turn off Milton AI in Event Setup. From then on nobody can use it for your organization, including Karsenics staff helping your account, and nothing from your organization is sent to Anthropic. Milton keeps sending your automated emails.

The full rules are in our AI Governance and Acceptable Use Policy.

Privacy, in plain terms

Participants choose how they appear publicly: full listing, name only, or hidden. We collect what your event setup asks for and nothing more, we never sell data, and we never combine one organization's data with another's. Our Data Processing Agreement follows California and Texas privacy law and names every company that touches participant data.

Accessibility, honestly

We build to WCAG 2.2 Level AA. In October 2026 we tested the platform against every Level A and AA criterion and published the results, gaps and fix dates included. It's our own testing, not an outside audit, and the report says so. If you hit a barrier, tell us and we'll fix it.

Who touches the data

Every company involved, named.

We publish this list and give 30 days' notice before adding to it.

ProviderWhat they do for youWhereWhat they see
RenderHosts your isolated service and database, and keeps a daily snapshot of its disk for 7 daysUnited StatesAll platform data, encrypted at rest
StripeProcesses card payments on your organization's own accountUnited States, and worldwide under Stripe's own termsPayer name, email, amount, last four digits
ResendSends confirmations, receipts, and sign-in linksUnited StatesRecipient name, email, message content
BoldSignElectronic signatures, only if your organization uses themUnited States for storage; may be accessed from other countriesSigner name, email, signature record
AnthropicPowers Milton AI's answers and drafts. Not used to train their models. Receives nothing from an organization that has turned Milton AI offUnited States for stored data; the model may run in other countriesWhat Milton AI is asked and the records it reads to answer, which can include names and contact details
NeonHolds the copy of each site's security and access log kept outside the platform, for 12 months. Nothing in the platform can change itUnited StatesSecurity log entries: mostly staff names, emails and sign-in addresses, and which records were changed. Some entries name a participant's organization or a staff correction to an answer. Never uploaded documents
CloudflareStores your service's off-site backups, each copy locked against deletion for 30 days (2 for hourly copies)United StatesAll platform data, inside the encrypted backups

Running Karsenics itself

These support Karsenics as a company and never receive participant data from the platform.

ProviderWhat they doWhat they see
VercelHosts the karsenics.com website you are readingSite visitor technical data
ResendDelivers messages sent through our contact pageWhat you type into the contact form
Google AnalyticsCounts visits to karsenics.com, with analytics storage denied by defaultSite visitor technical data
Google Maps PlatformAddress search on the platform's map screens, used by organization staff in Event Setup. The maps themselves are drawn without GoogleThe staff member's browser address and the addresses they type into the search. No participant data
Cloudflare (street-map file)Hosts the public street-map file the platform's maps are drawn from. Each site downloads it and serves it to its own map screensNothing
UptimeRobotChecks each site's public health page every 5 minutes and tells us when one stops answeringNothing
PasswdPassword manager for our own keys and passwordsKarsenics staff sign-in details
Documents on request

Need this for a board, a grant, or your city's IT team?

Ask and we'll send what we have: the Data Processing Agreement, our security policies (written, with formal adoption scheduled for Q4 2026), and each attestation as it's signed. Some documents go out under a simple confidentiality agreement.

Information Security PolicyIncident Response PlanBusiness Continuity PlanData Processing AgreementSubprocessor RegisterEach attestation, as it is signed

Found a security problem?

Tell us through the contact page and start your message with the word “security.” We read those first and reply within one business day, the same promise as every message through that page. We won't take action against anyone who reports in good faith. Our machine-readable contact details are published at the standard address security researchers check.

Report a security issue

# https://karsenics.com/.well-known/security.txt
Contact: https://karsenics.com/contact
Preferred-Languages: en
Canonical: https://karsenics.com/.well-known/security.txt
Policy: https://karsenics.com/trust