> For the complete documentation index, see [llms.txt](https://docs.parcellab.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parcellab.com/docs/platform/security-compliance.md). # Security & Compliance Protect your customers’ data, reduce risk, and ensure secure, scalable access to parcelLab products. ## Overview > At parcelLab, security and compliance are built into everything we do. Our platform is independently audited, continuously monitored, and aligned with leading global standards to protect customer data, ensure regulatory readiness, and give enterprises confidence in the resilience of their digital operations. parcelLab is **SOC 2 Type II** certified through audits by Prescient Assurance, confirming controls for security, availability, confidentiality, and processing integrity. We are also **HIPAA** compliant to protect health data, with letters of attestation available on request. To validate defenses, we conduct annual penetration tests on backend and frontend systems with Cognition Team, following **OWASP** standards. Security doesn’t stop with yearly audits. We use continuous compliance monitoring tools to track access rights, asset inventories, and evidence collection every day. This gives customers assurance that controls are not only documented but actively enforced across our operations. Our privacy program covers both **GDPR** and **CCPA**, led by our Data Protection Officer at ePrivacy GmbH. Data is encrypted in transit and at rest and limited by contractual controls to prevent unauthorized transfers. Employees receive mandated privacy training, and our practices are independently verified with the ePrivacy Seal. parcelLab operates under a **Responsible AI framework** aligned with NIST AI RMF, ISO 42001, and the EU AI Act. Models are documented, validated for fairness and robustness, and overseen with human review where impact is high. Risks are tracked in a model risk register, and incidents follow the same strict security response timelines used for data protection. We are compliant with the European Accessibility Act (EAA). Our tracking pages and returns portals are audited against **WCAG 2.2 Level AA**, supported by manual and automated testing through Valantic. Ongoing monitoring and annual reviews ensure accessible experiences for all users. ## Learn More View the following topics for more in-depth information on security and compliance:


Certifications & Attestations	View our external audits and programs.	Certifications & Attestations
Single Sign-On (SSO)	See how you can implement SSO for the App.	Single Sign-On (SSO)
Data Retention Policy	Learn about our data retention policy.	Data Retention Policy
White Label Policy	Learn about how parcelLab maintains high email deliverability rates.	White Label Policy
Data Protection APIs	Find out how you can request GDPR data removal and data provision via API.	https://github.com/parcelLab/gitbook-documentation/tree/main/developers/security/data-protection.md

--- # 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.parcellab.com/docs/platform/security-compliance.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.