AInforce

Security and trust

Review the evidence for your deployment.

Security decisions need more than a checklist of green badges. Use this page to scope your review and ask the AInforce team for the details that apply to the service you plan to use.

SOC 2 readiness, not an audit report

We are organizing SOC 2 readiness work, with Type I preparation before Type II operating evidence. This page does not establish certification, an auditor engagement, a completed examination, or a report delivery date. Ask the team for the current evidence and scope.

Questions to resolve before connecting data

Data collected and purpose

Public-source scans, uploaded discovery files, browser monitoring, and connected AI traffic have different scopes. Review the selected workflow and what it sends before providing access.

Access and permissions

Confirm administrator roles, organization boundaries, connector permissions, and credential handling for your deployment. A marketing demo is not an access-control assessment.

Hosting and data location

The public website and the application are separate services. Confirm the service, region, processors, and contractual location commitments for your intended deployment; do not assume the website's hosting determines application residency.

Encryption and key management

Request the configuration for the actual service and data path, including transport protection, storage encryption, key ownership, and backup handling. No specific protocol version or customer-managed key option is promised here.

Retention and deletion

Agree which records are retained, their configured lifetime, deletion procedures, and any legal or backup exceptions. Do not assume a report disappears automatically after an advertised interval.

Model providers and integrations

Confirm which data reaches each provider, its processing terms, the supported connection method, and whether the integration observes activity or can enforce policy. Provider model-training and retention terms need separate review.

Discovery is not the same as prevention

An external signal or DNS match is a reason to investigate, not proof that an employee submitted sensitive data. Browser discovery does not establish gateway coverage. Data inspection and runtime controls depend on supported, configured traffic paths.

Ask the team

For security questionnaires, procurement questions, or requests for supporting documents, contact info@ainforce.ai. Send responsible disclosures to security@ainforce.ai. Agree a secure channel before sending sensitive evidence.