Trust & security

Security and trust

What we protect, what we do not accept, and where your responsibility begins.

Last updated November 2026Effective date November 9, 2026
Security facts
The short version, from the Terms and Privacy Policy
CUI, ITAR, classified dataNot accepted
Data in transitTLS
Customer content used for model trainingNo
Customer data soldNo
CMMC certificationNot claimed

Our posture

These are the controls and boundaries we can state plainly. Where a commitment is contractual, the Terms control. Where it is about data handling, the Privacy Policy controls.

Controlled data stays outside GFIN.

GFIN is not authorized or accredited to receive, store, or process classified information, Controlled Unclassified Information (CUI) as defined in 32 CFR Part 2002, or technical data controlled under the International Traffic in Arms Regulations (ITAR) or Export Administration Regulations (EAR). Customers must not upload or submit such information. A government contractor should keep controlled information in an environment authorized under its own contracts and use GFIN for non-CUI pursuit work. If we reasonably believe content is controlled, we may remove it and will notify the customer.

Read the Terms & Conditions

Access is authenticated and scoped.

Users sign in through authenticated accounts. Authorization is role-based, service-to-service calls are authenticated, and operations follow least-privilege access. Your organization manages its own team membership, roles, and credentials.

Traffic and storage are protected.

We use TLS for data in transit, cloud storage access controls, security monitoring, and audit logging. No system is perfectly secure. We investigate suspected events and notify affected customers as described in the Terms and Privacy Policy.

AI processing is bounded.

We do not use customer proposal content, uploaded documents, prompts, chat history, generated drafts, organization profiles, or workspace data to train foundation models or third-party AI models. We use provider API or enterprise channels, disable provider training and restrict retention where supported, and do not send proposal content to a provider that cannot support confidential no-training processing for that workflow. You review AI outputs before use.

Read the Privacy Policy

We do not sell customer data.

We do not sell customer data or share proposal content with advertisers or data brokers. Service providers process data only to operate the platform, and the Privacy Policy describes the provider categories and the access rules.

Shared responsibility

Security is a boundary, not a badge. We secure the platform and the service boundary. You classify your data, control who can reach it, and decide what to upload or paste into an AI workflow.

Go Fund It Now
  • Secure the platform and the service boundary.
  • Authenticate users and authorize access.
  • Monitor, log, and investigate security events.
  • Do not accept controlled data.
Your organization
  • Classify your data and keep CUI outside GFIN.
  • Manage team membership and credentials.
  • Review AI outputs before use.
  • Report suspected incidents and vulnerabilities.

The full matrix, version, and print-ready copy are in the shared responsibility statement.

Compliance scope

GFIN does not claim CMMC certification, FedRAMP authorization, or accreditation as a CUI enclave. This page describes controls and a boundary; it is not a certification or audit report. Government contractor customers remain responsible for their own CMMC assessment and for keeping controlled data in an authorized environment.

Report a vulnerability

Email [email protected]. The disclosure policy is at /.well-known/security.txt. Include the affected URL, a description, and reproduction steps. Do not include customer data or controlled information in a report.

Related

TermsPrivacyAccessibilityMethodologyEditorial policy