---
title: "Security & Data Handling | Fortune AI"
description: "Review Fortune AI's website safeguards and the security, access, retention, and deployment questions agreed before connecting cameras or operating data."
canonical: https://www.fortuneai.app/security/
language: en
---

[Home](https://www.fortuneai.app/) Security

# Security and data handling

Security starts by defining the approved camera views, data sources, users, retention, and operating purpose before deployment.

[Overview](#security-overview)[Website](#security-website)[Deployment review](#security-deployment)[Responsibilities](#security-responsibility)[Contact](#security-contact)

Security overview

## How does Fortune AI approach security?

Fortune AI begins with the minimum camera views, records, users, and outputs required for an agreed operating question. Before deployment, the customer and Fortune AI define access, data flow, retention, review responsibilities, and what happens when cameras, networks, or integrations are unavailable.

## No blanket claims

This public page is an overview, not a certification, penetration-test report, or substitute for the security terms agreed for a specific deployment. Ask for the architecture and control details relevant to your environment.

01 · Public website

## How is the public website protected?

- The production site is delivered over HTTPS through Cloudflare infrastructure.
- The demo endpoint accepts same-origin submissions, validates required fields and maximum lengths, rejects unsupported or oversized requests, and includes a honeypot field for automated spam.
- Demo requests and website-session records are stored in a website database and email delivery status is recorded for operational review.
- Public pages do not ask visitors to upload camera footage, passwords, or system credentials.

Do not use the public form for confidential footage or credentials. Email the team first to agree on an approved transfer method.

02 · Deployment review

## What should be agreed before connecting cameras?

### Scope and access

- Approved sites, cameras, zones, and operating purpose
- Authorized users and review responsibilities
- Private or excluded areas

### Data flow

- Camera and system connection method
- Identifiers, timestamps, and required integrations
- Where processing and outputs are delivered

### Lifecycle

- Retention and deletion requirements
- Logs, evidence access, and incident contacts
- Fallback when a camera, network, or integration fails

Security, privacy, and regulatory requirements vary by industry and location. Written deployment terms control over this general overview.

03 · Shared responsibility

## What remains the customer's responsibility?

Customers control their camera systems, physical locations, user authorization, applicable notices and consent, operating procedures, and decisions made from the output. Fortune AI and the customer should identify the system owner, evidence reviewer, exception owner, and emergency or fallback process before use.

Fortune AI measurements support operating review. They do not replace qualified safety, security, clinical, employment, or legal decisions.

04 · Security contact

## How do I report a security concern?

Email [business@fortuneai.app](mailto:business@fortuneai.app?subject=Security%20question) with a description of the concern and a safe way to contact you. Do not include passwords, private keys, or sensitive footage in the first message.

[Discuss deployment requirements](https://www.fortuneai.app/book/?source=security)

## Related information

[Read the privacy notice](https://www.fortuneai.app/privacy/)

[Review the deployment process](https://www.fortuneai.app/work-with-us/)

Security overview · Effective September 28, 2026

Questions: [business@fortuneai.app](mailto:business@fortuneai.app)