Skip to main content

Legal and trust

Preview draft

A single place to review FVI's privacy information, contract outlines, security reporting and company details. Each document below is a local preview awaiting factual and legal approval.

Local preview

Owner and legal verification required before publication

This draft leaves material facts and commitments unresolved. It is not an operative notice, policy or agreement, and it does not claim regulatory or accessibility compliance.

  • Confirm the legal entity and address against primary records.
  • Complete purpose-by-purpose lawful bases and retention schedules.
  • Map all processors, regions, transfers, contracts and security measures.
  • Approve MSA, DPA, subprocessor notice terms and security disclosure policy.
  • Measure accessibility and verify the published support route.
  • Complete cookie/network inventory and confirm statutory notice requirements.
  • Add verified company, tax and regulatory registration particulars.

Open a document to see its current scope and the exact fields still requiring confirmation. Draft status applies to every document on this hub.

  1. Privacy noticeHow the public Falcon Veritas website handles enquiry, chat and optional analytics information, and the facts still needed for a complete service notice.
  2. Master service termsA structured preview of the terms a bank procurement team will need to review. No commercial or legal term on this page is effective until approved and executed in a final agreement.
  3. Cookies and browser storageAn inventory of storage and external resources observed in the public marketing source. The page distinguishes browser preferences from optional analytics and flags the checks still needed against the deployed site.
  4. Data processing termsA procurement-oriented Article 28 schedule outline for review. It is not an executed DPA, and it does not attach or incorporate standard contractual clauses.
  5. Subprocessor registerA transparent working register of providers visible in the public marketing implementation. It is not yet a complete contract-ready register for customer services.
  6. Security disclosureHow to report a suspected vulnerability affecting an FVI-managed public site or service, with clear limits on what this preview can promise.
  7. Acceptable useA working outline for safe, authorized use of FVI services. The final rules must align with executed customer terms, deployment and API documentation.
  8. AccessibilityFVI targets a usable, keyboard-accessible public experience. This statement separates that design target from measured conformance evidence.
  9. Company informationThe legal identity and address supplied by the owner, alongside statutory registry and tax fields that still require source verification.