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

# Welcome to Veilio !

<figure><img src="/files/XkQTWYx5uZiuQKeZ0XuH" alt=""><figcaption></figcaption></figure>

Veilio helps you protect sensitive customer data by replacing raw values (email, phone, IDs) with secure tokens.

Your application stores tokens. When needed, your backend can retrieve original values with controlled detokenization calls.

***

#### Why teams integrate Veilio

* Reduce sensitive data exposure in application databases
* Keep existing product workflows with minimal code changes
* Improve auditability and compliance readiness (GDPR, crypto-shredding, SIEM)

***

#### What you will build in this guide

1. Generate and configure an API key
2. Tokenize a sensitive value
3. Store and use the returned token
4. Detokenize only when needed
5. Ship to production with security best practices

***

#### Integration paths

| Path                 | Best for                               |
| -------------------- | -------------------------------------- |
| **Quickstart**       | First working flow in 5 minutes (curl) |
| **SDK Javascript**   | Node.js / TypeScript backends          |
| **SDK Python**       | Python backends                        |
| **HTTP Integration** | Any language, full control             |
| **API Reference**    | Complete endpoint list                 |

***

#### Jump right in

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-bolt">:bolt:</i></h4></td><td><strong>Quickstart</strong></td><td>Implement Veilio in minutes</td><td></td><td></td><td><a href="/pages/7FvWQMF0kTK7HGhlQfmo">/pages/7FvWQMF0kTK7HGhlQfmo</a></td></tr><tr><td><h4><i class="fa-leaf">:leaf:</i></h4></td><td><strong>Veilio</strong></td><td>Learn more about Veilio</td><td></td><td></td><td><a href="/pages/lWdZgI2P4YIODQ7uazsl">/pages/lWdZgI2P4YIODQ7uazsl</a></td></tr><tr><td><h4><i class="fa-globe-pointer">:globe-pointer:</i></h4></td><td><strong>Suggestion</strong></td><td>Any idea is valuable</td><td></td><td></td><td><a href="/pages/QPzbTvC6XsT5gERiU43E">/pages/QPzbTvC6XsT5gERiU43E</a></td></tr></tbody></table>

***

#### Advanced topics

| Topic                      | Page              |
| -------------------------- | ----------------- |
| Historical CRM import      | Migration Mode    |
| Account exit / portability | Offboarding       |
| Dataset upload & sharing   | Datasets Upload   |
| Retention & shredding      | Data Lifecycle    |
| Go-live checklist          | Go-live Checklist |

***

#### Related links

* Product website: <https://veilio.xyz>
* Documentation: <https://docs.veilio.xyz>
* Contact / Demo: <https://veilio.xyz/contact>


---

# 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.veilio.xyz/documentation/readme.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.