Security and privacy
Security is built into every layer of CHAMPREP: how you sign in, how each service decides what you can do, how your data travels, and how it is stored. Every statement on this page was checked against our source code and live infrastructure configuration before it was published. If we could not verify something, it is not here, and we do not claim a certification, audit or response target that we do not hold.
For a concise overview for security and procurement teams, visit the CHAMPREP Security & Trust page.
Security at a glance
Section titled “Security at a glance”- Encrypted at rest with AES-256: databases, file storage, the caches in use, queues, logs, secrets and backups.
- Encrypted in transit with TLS: every site, app and API is HTTPS only, with TLS 1.2 or newer, and our services reach their databases, caches and file storage over TLS.
- Chat messages are encrypted again by the chat service itself, with AES-256-GCM, before they are stored.
- One sign-in service issues every token. Tokens are signed with RS256, and every other service can only verify them, never create them.
- Strong sign-in options: two-factor authentication, recovery codes, passkeys, SAML single sign-on and SCIM 2.0 provisioning.
- Admin controls and audit logs let organizations decide who can use which service and review what changed.
- Card payments are handled by Stripe. Your full card number never reaches CHAMPREP.
- You stay in control of your data: export it, restore deleted items from Trash, and close your account when you choose.
- Hosted in the United States, on AWS and MongoDB Atlas regions.
Encryption
Section titled “Encryption”CHAMPREP encrypts customer data both when it is stored (at rest) and when it moves over a network (in transit). We checked every statement below against our live cloud configuration before publishing it.
Data at rest
Section titled “Data at rest”Customer data is stored encrypted with AES-256:
- Databases. Our MongoDB Atlas clusters and Amazon RDS PostgreSQL databases run on encrypted storage. Their automated backups and snapshots are encrypted too.
- Files. Drive files, chat and mail attachments, received email, meeting recordings, course media and other uploads are stored in Amazon S3 with server-side encryption.
- Caches and real-time data. The caches behind chat, Notes co-editing, mail and sign-in run on Amazon ElastiCache with encryption at rest. Our previous caches, which were not encrypted at rest, no longer receive or serve any data; they still hold old cache entries until they are deleted, by 19 November 2026.
- Queues and notifications. Message queues (Amazon SQS) and the notification topics our services publish to (Amazon SNS) are encrypted.
- Logs, secrets and backups. Service logs (Amazon CloudWatch Logs), application secrets (AWS Secrets Manager), backup vaults (AWS Backup), disk volumes (Amazon EBS) and container images (Amazon ECR) are encrypted.
- Stored credentials. Passwords you give Mail to import from another provider or to send through another mail server are stored encrypted. Your CHAMPREP password itself is never stored in readable form: we keep only a salted, one-way hash of it.
Encryption keys are managed by AWS Key Management Service and by MongoDB Atlas. CHAMPREP does not currently offer customer-managed encryption keys.
Chat message encryption
Section titled “Chat message encryption”Chat adds its own layer of encryption on top of encrypted storage:
- Message text is encrypted with AES-256-GCM before it is stored. The same applies to earlier versions of edited messages, drafts, scheduled messages, poll options and the text of safety reports.
- Chat inside a Meet meeting is stored by the same chat service, so it is encrypted the same way, guest messages included.
- Files you share in chat are stored with AES-256 server-side encryption.
To be precise about what this means: CHAMPREP manages the encryption key, and keeps it outside the database. Our servers decrypt messages to deliver, search and show them, so Chat is not end-to-end encrypted. Room names, member lists and timestamps are not encrypted by this layer, and short message previews in notifications and link previews are stored without it. They are still protected by the encrypted storage described above.
Data in transit
Section titled “Data in transit”Data moving over a network is protected with TLS:
- Between you and CHAMPREP. Every website, app and API on champrep.com is served over HTTPS only, including secure WebSockets for real-time features. Plain HTTP is redirected to HTTPS. Our domains accept TLS 1.2 or newer, with TLS 1.3 supported.
- From our services to our data stores. Connections to MongoDB Atlas, Amazon RDS and Amazon ElastiCache use TLS, and the databases and caches refuse unencrypted connections. Storage buckets that hold customer data refuse any request that does not use TLS.
- Inside our platform. Traffic between CHAMPREP services stays inside our private cloud network (Amazon VPC), which is not reachable from the internet.
- Meetings. Audio and video in meetings are encrypted in transit.
- Email. Incoming mail must arrive over TLS. Mail we send uses TLS whenever the receiving mail server supports it.
Sign-in and identity
Section titled “Sign-in and identity”Your account is protected by one dedicated sign-in service and a full set of modern sign-in options.
- One token issuer. Every sign-in token is signed with RS256 by the CHAMPREP sign-in service, which alone holds the signing key. Every other service holds only the public key, so it can check a token but can never create one.
- Email verification confirms a new account before it becomes fully active.
- Two-factor authentication (2FA) asks for a time-based code from a standard authenticator app. It still applies when you sign in with Google or Facebook, and after a password reset.
- Recovery codes give you single-use access when your authenticator is not available.
- Passkeys (WebAuthn) let you sign in with a credential stored on your device or in your password manager, with no password to type.
- SAML single sign-on lets an organization sign in through its own identity provider. An administrator can require single sign-on for everyone, the owner included, so passwords stop working for that organization.
- SCIM 2.0 provisioning lets your directory add, update and remove people automatically. See SCIM provisioning.
- Session controls let you review active sessions and sign out devices or browsers you do not recognize.
- Sign-in alerts and account activity make security-relevant events on your account visible to you.
- Confirmation for sensitive changes. Sensitive account actions ask you to confirm your identity again before they take effect.
Manage these controls from the Security, Active Sessions, and Account Activity areas of the personal dashboard.
Admin controls and audit logs
Section titled “Admin controls and audit logs”Organizations decide who can use what, and can see what changed.
- Members, seats and roles. Organization administrators manage members, seats and roles, and delegate administrative capabilities.
- Service and feature access. Administrators choose which services and features each member can use, within what the organization’s plan includes.
- Directory groups. Groups from your identity provider can be mapped to access in CHAMPREP.
- Sign-in policy. Administrators set up single sign-on, can require it, and can see which members have not turned on two-factor authentication.
- Verified domains. Organizations verify the email domains they own.
- Audit logs. Organization administrators can review the audit log of changes in their organization and export it.
- API key history. Every API key keeps its own audit log, so you can see how it has been used.
When CHAMPREP support views an account
Section titled “When CHAMPREP support views an account”If a CHAMPREP staff member needs to see an account the way its user does, to help with a support request, they must confirm their own password and give a reason before the session starts. Each session is logged, and sensitive account actions are blocked while it is active. Actions taken in CHAMPREP’s own administration tools are recorded in an audit log as well.
Access control and least privilege
Section titled “Access control and least privilege”Access is checked at every step, in the context of the profile you are using. Changing profiles changes the service, role, organization and plan context the platform applies.
- Every request is checked. Each service verifies the signed token on every signed-in request itself, then applies your role, your organization’s settings and your plan to what you ask it to do.
- Plans and policy decide access. Your plan determines which services and features are available; organization roles and member-level permissions narrow that further.
- Scoped API keys. Integrations use API keys rather than account passwords. Each key carries only the services, access levels and scopes you choose, can be limited to an IP allowlist, and can be revoked at any time. See Authentication and API keys.
- Signed webhooks. Webhook deliveries are signed with HMAC SHA-256 and carry a timestamp, so your receiver can reject forged or replayed events. See Webhooks.
- Separate identities for our services. Each CHAMPREP service runs under its own cloud identity rather than one shared platform credential, and requests between our services are authenticated.
- AI stays inside your permissions. CHAMPREP AI acts only with the access of the profile using it. See AI choice and control.
Isolated preview environments
Section titled “Isolated preview environments”When you start a preview or a cloud IDE session in CHAMPREP QA, it runs in its own short-lived container, created for that session alone. Each session has its own access token, and the container is shut down when you stop it or when it reaches its expiry time.
CI jobs on Runner Farm run in fresh environments created for each job. See CHAMPREP Code and Runner Farm.
Payments
Section titled “Payments”Card payments are processed by Stripe, a payment provider certified to the highest level of the Payment Card Industry Data Security Standard (PCI DSS).
- You enter card details into Stripe’s secure payment form, so your full card number and security code go directly to Stripe and never reach CHAMPREP’s servers.
- CHAMPREP keeps only what you need to recognize a card, such as its brand and last four digits.
- Card numbers that appear in billing activity text are masked to the last four digits.
Email security
Section titled “Email security”- Domain authentication. When you connect a domain to Mail, CHAMPREP gives you its DKIM signing records and a MAIL FROM domain with SPF, checks those records, and recommends a DMARC record.
- Required TLS for incoming mail. Mail sent to CHAMPREP without TLS is refused.
- Spam and virus scanning. Every incoming message is scanned, and a message flagged as a virus is not delivered.
- Remote image protection. In Mail on the web and desktop, remote images are blocked until you allow them. Allowed images load through CHAMPREP’s image proxy, so the sender’s server sees CHAMPREP, not your IP address or browser, and no cookies or referrer are sent.
Secure development and vulnerability scanning
Section titled “Secure development and vulnerability scanning”CHAMPREP continuous-integration pipelines run automated static security analysis with security and OWASP-oriented rules. Pipelines also run secret detection to identify credentials or sensitive values that should not enter source control. Findings are surfaced to engineering for review and remediation. Infrastructure changes are made through code and automated pipelines, not by hand.
These are the verified scan types represented publicly today. Dependency, container, infrastructure-as-code, dynamic application, and software-bill-of- materials coverage is being handled as a separate assurance expansion and is not implied by this statement.
Monitoring and service resilience
Section titled “Monitoring and service resilience”The platform uses centralized application and infrastructure logs, service health metrics, and alarms for operational conditions such as errors, latency, resource pressure, and unhealthy service targets. Production infrastructure uses availability-zone-aware networking and service placement where configured. Live service health and incident updates are published on the status page.
Monitoring data is access controlled. Public documentation does not disclose internal alarm thresholds, account identifiers, network topology, or other details that would make the platform easier to target.
Data location
Section titled “Data location”Core production application infrastructure and databases run in United States AWS and MongoDB Atlas regions. CHAMPREP does not use the word “onshore” as an absolute for every data flow: global content delivery, network protection, and approved service providers may process routing or service metadata under their applicable terms.
Customers with specific residency requirements should contact CHAMPREP so the exact services, data classes, and provider paths in scope can be reviewed.
AI choice and control
Section titled “AI choice and control”Using CHAMPREP AI is optional. AI operates within the permissions of the active profile and does not create broader service access for itself.
- Users can enable or disable AI access to connected services.
- Action-taking or agentic capabilities are disabled by default until a user explicitly enables them.
- Service and plan permissions continue to apply when AI assistance is used.
- Higher-impact actions can require user approval.
CHAMPREP is continuing to strengthen platform-wide consent defaults and organization-level AI policy controls. We do not describe every AI feature as opt-in by default until that work has been verified across the full platform.
Your data, your controls
Section titled “Your data, your controls”- Export your data. Your personal dashboard includes a data-export request flow for your account data.
- Restore deleted items. In Drive, Docs, Sheets, Notes, Forms, Work and meeting recordings, deleted items go to Trash first, so you can restore them. Deleting an item from Trash removes it permanently.
- Review sharing. The service that owns a file, recording, transcript, room, or other item shows who it is shared with and lets you change that.
- Close your account. When you close your account from the dashboard, sign-in is blocked and every session ends right away. Your data is not erased automatically; erasing it is a separate step. To ask for it, write to privacy@champrep.com.
- A failed payment never deletes your data. It pauses paid services until the open invoice is paid.
Read the Privacy Policy and Terms of Service for the governing privacy and service terms.
Report a vulnerability
Section titled “Report a vulnerability”Submit a report through champrep.com/contact-us and begin the subject with [Security] Vulnerability report.
Include:
- The affected CHAMPREP service or URL.
- A clear description of what you observed.
- The smallest safe set of steps needed to reproduce it.
- The potential impact, if known.
- Your preferred contact details for follow-up.
Do not include passwords, authentication tokens, payment data, customer content, or more personal data than is necessary to explain the issue. Do not disrupt service, access another person’s data, or retain data discovered during testing. A machine-readable disclosure pointer is also available at champrep.com/.well-known/security.txt.
Reports are triaged by severity and routed to the appropriate engineering owner. CHAMPREP does not publish a response-time promise on this page until a formal incident and vulnerability-response target has been approved and tested.
Enterprise security review
Section titled “Enterprise security review”Enterprise security, risk, and procurement teams may use the contact form to request a focused review. This page makes no certification or compliance claims. CHAMPREP will only provide a penetration-test summary, audit report, certification, or similar assurance artifact when that artifact exists, is current, and has been approved for release.