Skip to main content

Security and Privacy Quick Answers

When a customer, IT team, or procurement reviewer asks for Blast Audit security details, the fastest path is to send them to the exact legal and admin pages that already exist in the dashboard. This article gives you the short version.

Written by William Karkegi
Updated over 2 weeks ago

When a customer, IT team, or procurement reviewer asks for Blast Audit security details, the fastest path is to send them to the exact legal and admin pages that already exist in the dashboard. This article gives you the short version.

Who this is for

  • Workspace owners handling security review questions

  • Sales or onboarding contacts supporting customer reviews

  • Teams collecting legal and access-control answers

Before you begin

  • You may still see Copilot Audit in a few older labels.

  • The dashboard includes both public legal pages and admin-only integration pages.

  • Do not promise a control is configured just because the page exists. Check your own workspace first.

How to do it

  1. Send the right legal document, not a marketing page.

Blast Audit has public pages for Privacy Policy, Terms and Conditions, End User License Agreement (CLUF), Data Processing Agreement, and Security / Vulnerability Disclosure (VDP).

  1. Explain who can access what.

The dashboard states that dashboard access is reserved for workspace admins.

Regular users can still use the Excel add-in.

In user invites, Owner means full administrative access for billing, seats, and permissions, while Member is the standard role.

  1. Point reviewers to identity controls.

Under Integrations, the dashboard has pages for Single Sign-On and Directory Sync.

Those pages cover SSO and SCIM setup status for your workspace.

  1. Use the DPA for processor questions.

If the reviewer asks how Blast Audit handles customer data on your behalf, send the Data Processing Agreement first.

Use the Privacy Policy for collection and handling questions.

  1. Use the security page for vulnerability reporting.

The Security / Vulnerability Disclosure (VDP) page is the right answer for good-faith security research and vulnerability reporting.

  1. Escalate only the unresolved questions.

If a reviewer asks for something not covered by those pages, collect the exact question and send it through support instead of improvising.

Expected result

  • The reviewer receives the exact document title they asked for

  • You describe roles as Owner and Member, not generic custom terms

  • You separate legal documents from workspace-specific integration status

Avoid this

  • Sending homepage or pricing links instead of legal pages

  • Saying all users get dashboard access

  • Claiming SSO or SCIM is configured without checking your workspace

  • Mixing Blast Audit branding with older Copilot Audit labels and confusing the reviewer

If it still doesn't work

  • Start with the public legal pages first

  • Add your workspace-specific answers only after you verify them in Users, Single Sign-On, or Directory Sync

  • If procurement asks for a custom written answer, include the exact request in a support packet

Read next

  • Create Account and Sign In

  • Complete Dashboard Onboarding

  • Invite Members and Assign Roles

  • Configure SSO and Directory Sync

  • Build a Support Escalation Packet

Did this answer your question?