Ownership
Confirm the partner controls or is authorized to test the target.
Security and responsible testing
Responsible testing with explicit boundaries.
Authorize the scope, isolate sensitive access and stop production runs before irreversible actions.
Authorization starts before the first request.
The manifest records who owns the target, which domains and accounts are in scope and what the runner may do.
Scope
List domains, routes, accounts, tools and data that the run may access.
Actions
Separate read, reversible write and irreversible actions before execution.
Stop gate
Define the exact state where a public or production run must stop.
The environment determines the allowed depth.
A result always carries its audit mode, fixtures and authorization context.
Public
Read public content and perform reversible local interactions. Stop before account creation, submission or transaction.
Authenticated
Use approved test accounts and scoped permissions. Avoid production customer data and destructive changes.
Sandbox
Complete controlled scenarios with fixtures and test payment methods. Never cross into production.
Production stop gates are part of the test contract.
The runner may reach a review state, but it does not complete an irreversible action without a separately approved sandbox protocol.
- Payment or purchase confirmation
- Booking or appointment confirmation
- Lead, application or account submission
- Deletion, cancellation or destructive update
- External message or notification
- Change to production customer data
Controls protect the run and its evidence.
Security state is reported honestly, including limitations and controls that are still being operationalized.
Isolation and egress
Limit reachable targets and external destinations to the approved scope.
Secrets
Keep credentials server-side, scoped and out of screenshots, logs and prompts.
Data minimization
Collect only evidence needed to reproduce and verify the finding.
Redaction
Remove PII, tokens, payment, financial and medical data from report-safe artifacts.
Retention
Assign an explicit retention window and deletion path to sensitive artifacts.
Observability
Record agent, environment, tools, actions and interventions for later review.
Evidence should explain the result without leaking the user.
The collection level is selected before the run and reduced when a lower level can prove the same assertion.
Capture
Record only approved screens, traces and structured events.
Minimize
Remove unrelated content and avoid broad account or page exports.
Redact
Transform sensitive fields before an artifact enters a report or shared workspace.
Retain
Keep the artifact only for the agreed operational and review period.
Report security issues with minimal sensitive detail.
Use the published security contact, describe the affected asset and wait for a secure exchange path before sending secrets or personal data.
- Security contact: security@aiscovery.io
- Policy and canonical contact are published in /.well-known/security.txt
- Do not include credentials, tokens or customer data in the first message
- Testing still requires explicit authorization
No unverified compliance claims.
Aiscovery does not display SOC 2, ISO, encryption or subprocessor claims until formal evidence, scope and current documentation are available.
Security questions
Can Aiscovery test a site we do not own?
Only when the applicant can demonstrate appropriate authorization from the owner.
Do public audits make purchases or bookings?
No. They stop before irreversible confirmation or payment.
Can sensitive screenshots appear in a report?
Report-safe artifacts must be minimized and redacted according to the agreed evidence policy.
Define the boundary before testing the journey.
Apply with an owned workflow, approved environment and the constraints your security team needs reviewed.