Data should serve the verification—not become the product.

Depending on how a deployment is configured, Totem may process:

• Account identifiers such as name, email address, and organization membership.
• Waitlist consent, an encrypted email address, delivery timestamps, and pseudonymous abuse-control identifiers.
• Organization, contact, agent, credential, and delegated-authority metadata.
• Challenges, presentations, verification decisions, and audit event metadata.
• API and security telemetry needed to operate, diagnose, and protect the service.

Do not put passwords, raw API keys, confidential business content, or regulated personal data into descriptive fields or sandbox requests.

The application uses this data to authenticate users, maintain organization and contact relationships, register agents, issue or verify credentials, enforce action authority, deliver requested workflows, and preserve security evidence.

Deployment operators may also use limited operational data to investigate failures, prevent abuse, and maintain the service. Their own policies may add or narrow purposes.

Storage providers, geographic location, retention windows, backups, and authorized personnel depend on the deployment. Ask the organization that provided your account for those deployment-specific details.

The software is designed around organization-scoped access and server-side authorization. No technical control eliminates every risk, so operators should use production secrets, HTTPS, a supported database, monitoring, and regular security review.

Google Analytics is inactive unless the deployment operator configures a valid measurement ID. Even when configured, the public site asks for an explicit analytics choice and does not load Google’s script or send an analytics event before the visitor accepts. If accepted, Google may receive browser, device, page-view, and approximate-location information under the operator’s analytics configuration and Google’s terms.

Operators should provide any consent mechanism or additional notice required for their audience before enabling analytics. A visitor’s choice is stored in that browser’s local storage so the site can honor it on later visits.

For access, correction, deletion, retention, or privacy questions, contact the organization operating the Totem deployment where your account exists. It controls the relevant records and can confirm which rules apply.

Every waitlist confirmation includes a private leave-waitlist link. Using it suppresses future waitlist updates without revealing whether an address was stored.

For a suspected security vulnerability, contact the repository owner with only a request to establish a private reporting channel. Do not include exploit details, secrets, or personal data in a public message.

Project maintainers aim to acknowledge complete vulnerability reports within three business days and provide periodic updates while a validated issue is being fixed. This is a response target, not a contractual SLA or a promised remediation deadline.