Beta security & trust

Ask about implemented controls and current limitations

This route records security and privacy inquiries for staff review. It describes only repository-backed controls and does not imply an external audit, certification, or public security program.

Beta evidence only. No certification, service level, procurement packet, response time, or document delivery is promised. Evidence reviewed October 3, 2026.

Recorded inquiryClosed direct storageAuthenticated routesDated evidenceExplicit limits
Beta Security & Trust visual

Data we may handle

The beta workflow handles several sensitive data classes

The platform may handle reference images, video links, stage names, public profile links, findings, URLs, evidence snapshots, takedown status, customer contact information, and identity or authority verification status.

Reference media

Images, links, and profile context used for monitoring and review.

Findings and URLs

Customer-visible records of likely misuse, source domains, and status.

Evidence snapshots

Sensitive previews or records that should be handled with controlled access.

Account information

Contact, billing, support, and role information needed to operate the service.

The beta workflow handles several sensitive data classes visual

Implemented boundaries

Current claims are limited to tested repository controls

Firebase rules deny direct browser reads and writes. Authenticated service routes derive customer context and enforce applicable entitlements for supported operations.

Direct storage denied

Firebase Storage rules deny browser access across object paths; supported access is brokered by service routes.

Direct database denied

Sensitive Firestore collections deny direct client reads and writes.

Customer context

Portal authorization derives customer identity from authenticated context rather than a browser-supplied customer ID.

Evidence registry

Each claim family links to an implemented control and dated test evidence in the versioned claim registry.

Current claims are limited to tested repository controls visual

Current limitations

An inquiry does not create evidence that does not exist

The repository evidence is engineering evidence for the beta. It is not an external audit, legal opinion, compliance certification, uptime commitment, penetration-test result, insurance representation, or completed procurement package.

Coverage is bounded by configured sources and eligible work. Findings require review, and prepared requests do not prove delivery, platform action, or removal.

  • No external audit representation
  • No availability or response-time promise
  • No universal source or media coverage
  • No automatic-removal promise
  • No certification or public-launch approval
An inquiry does not create evidence that does not exist visual

Security contact

Send a beta security or privacy inquiry

This form posts to the inquiry service for staff review. Do not include secrets, passwords, government identifiers, or unredacted sensitive media.

Internal/test route. Submissions are recorded as inquiries for staff review; no response time, document delivery, or security certification is promised.

Send a beta security or privacy inquiry form visual

Next step

Review the evidence-backed trust summary

Read the current controls and limitations before relying on any security, privacy, or coverage statement.