> For the complete documentation index, see [llms.txt](https://trustcenter.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trustcenter.syntphony.com/products/syntphony-commerce-and-payments/loyalty/conformity.md).
# Conformity
Certifications
**Syntphony Loyalty** is built to provide businesses with a secure and efficient loyalty management system, ensuring compliance with international standards. Our asset holds the following certifications:
* **ISO 20000** – Guaranteeing our **24x7 Team Operations** maintain best-in-class IT service management practices for seamless performance.
* **ISAE 3402 (SOC1 & SOC2) Report** – Verifying our **IT security controls**, ensuring data integrity, confidentiality, and compliance with financial reporting requirements.
* **PCI-DSS Level 1** – Providing the highest level of security compliance for **payment data protection**, allowing secure processing of loyalty transactions and customer rewards.
* **Spanish National Security Scheme (ENS)** certification, ensuring the protection of citizen data in electronic procedures. Backed by the ENS, it demonstrates absolute commitment to privacy and user confidence in secure and efficient electronic processes.
ENS Certification
---
# 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://trustcenter.syntphony.com/products/syntphony-commerce-and-payments/loyalty/conformity.md?ask=&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.
