Security

How Badge 6 protects your agency’s records.

Policies and proofs are agency records, and many contain other people’s personal information. Here’s what Badge 6 does with them, in plain language, so your IT and purchasing teams can check it.

  • Sign-in

    A password is never enough on its own.

    • Every login needs your password plus a 6-digit code sent by email.
    • The code expires in 5 minutes and works only once.
    • One active session per user.
    • Passwords must be at least 10 characters and are stored as bcrypt hashes, never as plain text.
    • Password reset links expire after 1 hour.
  • Roles and sharing

    People see what their role needs, and assessors read only what’s on a manual connected to their accrediting body.

    • Role, module and permission rules are enforced on the server, not just hidden in the screen.
    • Assessors see your evidence only on manuals connected to their accrediting body, only when assigned to your agency, and they can’t change it.
    • Each standard has an Internal chat that only your agency can see.
  • Redaction

    Other people’s personal details are removed before anyone reviews the file.

    • Every upload is checked for names, addresses, plates, case and badge numbers, faces, text in images and spoken details.
    • Word gets stand-ins like “[Person 1]”, PDFs get black boxes, images are blurred, audio and video are beeped.
    • You review the list before publishing. Redaction is final once published.
    • Your agency’s own details are never redacted.
  • Storage and links

    Your files stay in the United States, and no link stays open.

    • Files are stored in Amazon S3 in the United States.
    • Every document link is signed and expires after 1 hour.
    • Exported reports carry sign-in links, not open file links.
  • AI processing

    AI runs inside AWS, not in a consumer chatbot.

    • AI features run on Amazon Bedrock with US-based inference.
    • Reading documents, finding personal details and processing media use Amazon Textract, Comprehend, Rekognition and Transcribe.
    • AI results are advice. People set every compliance status.
  • Records and history

    You can show who did what, and when.

    • An activity timeline on every standard.
    • Every signed Standard Summary Report version is kept.
    • Version history for every policy.
    • A log of every officer acknowledgment.

Follow a document

From upload to assessor, step by step.

Each step adds a protection. People in your agency see what their role allows, and an assessor reads the work only on a manual connected to their accrediting body.

  1. 1. Upload A signed-in user uploads a policy or proof. Sign-in needs a password and an emailed code, and the server checks the user’s role and permissions.
  2. 2. Redaction Personal and case details are found and redacted in Word, PDF, images, audio and video. The uploader reviews the list before publishing.
  3. 3. Library The published file is stored in Amazon S3 in the United States. Every link to it is signed and expires after an hour.
  4. 4. Review Your Review Manager reviews the standard. The Internal chat on each standard is visible only to your agency.
  5. 5. Signed report Your Review Manager signs the Standard Summary Report. Every version is kept, and exported reports carry sign-in links, not open file links.
  6. 6. Assessor Assessors see your evidence only on manuals connected to their accrediting body, only if they’re assigned to your agency, and they can’t change it.
How a document moves through Badge 6, and what protects it at each step. Inside your agency, people see what their role allows; an assessor reads it only on a connected manual they’re assigned to.

We only publish what’s confirmed.

If something on your checklist isn’t on this page, such as SOC 2, CJIS, single sign-on or data retention, ask us. You’ll get a written answer instead of a marketing line.

Ask a security question

For IT and purchasing

Questions your IT or purchasing team will ask

Something else? Ask us directly.

Where is our data stored?

Files are stored in Amazon S3 in the United States.

Who can see our documents?

People in your agency, according to their role. Assessors assigned to your agency read your evidence on the manuals connected to their accrediting body, and can’t change it. Badge 6 sets up that connection with your agency and the accrediting body. Role, module and permission rules are enforced on the server.

How does sign-in work? Do you support single sign-on or authenticator apps?

Every login needs a password and a 6-digit code sent by email. The code expires in 5 minutes and works once, and each user has one active session. If your agency requires single sign-on or an authenticator app, ask us.

Is our data encrypted?

Passwords are stored as bcrypt hashes, and every document link is signed and expires after an hour. For written details on encryption in transit and at rest, request our security documentation.

Do you have a SOC 2 report?

Ask us. We’ll give you the current status in writing rather than put a claim on a web page.

Is Badge 6 CJIS compliant?

Ask us. Tell us what your CJIS security officer needs to see and we’ll answer in writing.

Is our data used to train AI models?

AI runs on Amazon Bedrock with US-based inference. For a written answer on model training and data retention, ask us.

What happens to our data if we stop using Badge 6?

Ask us before you sign, and we’ll put the answer in writing for your contract.

Can you fill in our security questionnaire?

Send it to us through the message form and tell us your deadline. We answer only with what we can confirm.

This Is Accreditation: Simplified. This Is Badge 6.

Need the details in writing?

Ask for our security documentation, or send your agency’s questionnaire. We’ll answer with what we can confirm.