> For the complete documentation index, see [llms.txt](https://docs.taloflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taloflow.ai/security/security-operations/physical-security.md).

# Physical Security

Taloflow’s production infrastructure is hosted on **Akamai Connected Cloud (Linode)**. Physical security controls are primarily the responsibility of Akamai and its data center partners.

### Facility controls

Data center physical controls are designed to prevent unauthorized access to systems and storage.

Akamai (Linode) describes using layered facility controls, including:

* Perimeter security (for example, fencing)
* Multi-factor facility access (for example, swipe card + PIN)
* Biometric checks (for example, face/eye scanners) and man-traps at some facilities
* Trained security guards at some facilities
* 24/7/365 monitoring
* Visitor badging and access logging
* Visitor escort requirements

Taloflow personnel do not require routine physical access to data center facilities. Platform operations are performed through controlled, authenticated administrative access.

Linode equipment is typically located in locked cages and cabinets. Access is restricted to authorized personnel with clearance.

### Compliance attestations

Akamai publishes security and compliance information for its services. For the most current third-party attestations and certifications, reference Akamai’s Trust Center:

* [Akamai Trust Center](https://www.akamai.com/trust-center)

If you need specific documentation for a vendor review, contact Taloflow via the [Support Hub](broken://spaces/-MQkUmzRViVxDERN9vKk/pages/7w2btLpaU63hhnW4Dd7q).

### Data location

Taloflow is deployed in specific Akamai Connected Cloud regions. If you have data residency requirements, contact Taloflow to confirm current region options.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.taloflow.ai/security/security-operations/physical-security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.