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

# Security

How Kick protects your financial data and what you should know about privacy.

Your financial data is sensitive, and Kick is built to protect it. Here's what you should know about how Kick handles your data and keeps your account secure.

***

### Data encryption

All data transmitted to and from Kick is encrypted in transit using TLS. Data at rest is encrypted using AES-256 - the same standard used by banks and major financial institutions. Your credentials are never stored in plain text.

***

### Bank connections

Kick connects to your financial institutions through Plaid, a trusted third-party service that powers bank connections for thousands of financial apps. Kick never sees or stores your bank login credentials - authentication happens directly through Plaid's secure, encrypted flow.

***

### Access controls

Kick uses role-based access control so you decide exactly who can see and do what in your workspace. You can add or remove team members at any time, scope access to specific entities, and change roles as your needs evolve.

→ [Roles & Permissions](https://docs.kick.co/reference/roles-and-permissions.md)

***

### Data retention

Kick retains your financial data for as long as your account is active and as long as necessary to provide the service. Data may also be retained where required by law or for legitimate business purposes such as fraud prevention. Backup copies may exist in secure systems for a limited period as protection against data loss.

***

### Privacy

For full details on how Kick collects, uses, and protects your personal information, see the [**Privacy Policy**](https://www.kick.co/legal#privacy) and [**Terms of Service**](https://www.kick.co/legal#terms-of-service).

For privacy-specific questions or requests, contact [**privacy@kick.co**](mailto:privacy@kick.co).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/reference/security.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
