Skip to main content
WinPathPUBLIC EVIDENCESOURCE-LINKEDEXACT FRESHNESSHUMAN DECISION
Legal · Security

Verified controls, with the verification boundary visible.

Last updated: August 27, 2026

This document is part of WinPath’s standard site terms and policies. It is under ongoing counsel review and subject to revision; the version posted at this URL is the version in effect. Where a signed enterprise, pilot, or design-partner agreement exists between WinPath and a customer, that agreement supersedes these site terms to the extent of any conflict.

WinPath AI, LLC, a Florida limited liability company, builds from public federal procurement records first. This page states only controls that have been implemented and checked, and distinguishes a scoped test from a platform-wide certification.

01Public-Input Boundary

The promoted fit-review path collects scheduling and contact information and does not request file uploads or confidential pursuit materials. Do not send active opportunity lists, capture strategy, proposal material, pricing, classified information, controlled information, or source-selection-sensitive material through a public channel.

02Scoped Tenant-Isolation Evidence

A July 9, 2026 QA test used a non-administrator customer account and verified that it could read its own client record, pursuits, and decisions while receiving no foreign tenant rows from those tested paths. That is useful evidence for those paths; it is not proof that every table, route, function, or storage object has been tested.

Additional customer-facing surfaces must pass the same tenant-isolation test before they are included in the verified boundary.

03Authentication and Sessions

Customer authentication uses Supabase Auth. Server-side customer routes derive the signed-in user and tenant association from the authenticated session rather than a client-supplied tenant identifier. Password recovery and sign-out paths are part of the production browser smoke test.

04Application and Data Controls

  • Public evidence demonstrations are read-only.
  • Customer-specific outputs and external delivery are default-off behind explicit server-side gates.
  • Archived experimental methods and receipts remain outside customer-write paths.
  • Unavailable evidence remains visible and labeled rather than being replaced with a zero.
  • Application errors can be reported through the support path for human triage.

05Platform Properties

Browser traffic is served over TLS. The application runs on Vercel, while database, authentication, and storage services use Supabase. Any encryption or infrastructure property supplied by those vendors is a vendor property, not a WinPath certification. WinPath does not claim SOC 2, ISO, FedRAMP, or an independent penetration-test result.

06Monitoring and Public Scheduling

Error monitoring is configured through Sentry. The promoted public conversion hands off to the scheduling provider and does not accept file uploads. Any WinPath-hosted public submission surface must use server-side validation, rate limiting, and bot protection appropriate to that surface.

07What Is Not Yet Verified Platform-Wide

  • A complete authorization matrix covering every customer table and mutating route.
  • An independent penetration test or third-party security certification.
  • A claim that every background job or integration has maintained a multi-week uptime record.
  • A claim that confidential customer data is required for a public demonstration.

08Report a Security Issue

Report a suspected vulnerability or an incorrect security statement to security@winpath.ai. Include the affected URL, the behavior observed, and a safe reproduction path. Do not include sensitive federal or customer information in the initial report.