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

# Glossary

A glossary of common terms used across the Sprinto Trust Center to help you better understand key security, compliance, and access control concepts.

A glossary of key terms to help you navigate the security, compliance, and access control concepts in Sprinto’s Trust Center.

### Glossary

<table><thead><tr><th width="155.60546875">Term</th><th>Definition</th></tr></thead><tbody><tr><td>Access Requests</td><td>Requests made by external users to view restricted documents within the Trust Center.</td></tr><tr><td>Audit Logging</td><td>The process of recording system and user activity to ensure traceability and monitor anomalies.</td></tr><tr><td>Compliance</td><td>Adherence to recognised standards such as SOC 2, ISO 27001, HIPAA, etc.</td></tr><tr><td>Custom Domain</td><td>A domain owned by your organisation used to host the Trust Center instead of the default domain.</td></tr><tr><td>Data Rights Requests</td><td>Requests submitted by users under privacy regulations (e.g., GDPR) for data access or deletion.</td></tr><tr><td>Document Visibility</td><td>Settings that control whether a document is visible by default in a Trust Center profile.</td></tr><tr><td>Encryption at Rest</td><td>A security measure that encrypts data stored on disk.</td></tr><tr><td>Encryption in Transit</td><td>A security measure that encrypts data as it moves over networks (e.g., HTTPS).</td></tr><tr><td>Legal Requirements</td><td>Documents such as DPA, MSA, and Terms of Service that outline your legal posture.</td></tr><tr><td>NDA</td><td>A legal agreement that must be signed before accessing restricted documents.</td></tr><tr><td>Pentest Report</td><td>A report that outlines findings from penetration testing conducted on your systems.</td></tr><tr><td>Private Trust Center</td><td>A restricted view of the Trust Center accessible only to whitelisted users or domains.</td></tr><tr><td>Profiles</td><td>Custom views of the Trust Center tailored for specific stakeholders or use cases.</td></tr><tr><td>Publish</td><td>The act of making your Trust Center publicly accessible via domain or subdomain.</td></tr><tr><td>Sprinto NDA Template</td><td>A default NDA provided by Sprinto which can be enabled with predefined legal terms.</td></tr><tr><td>Team Tab</td><td>The section where admins can invite, view, and manage Trust Center collaborators.</td></tr><tr><td>Trust Center</td><td>A central hub to showcase your organisation's security and compliance posture.</td></tr><tr><td>Trust Center Updates</td><td>A section used to publish security-related announcements, changes, or incident reports.</td></tr><tr><td>Visibility Settings</td><td>Controls that determine which documents or sections are visible in each Trust Center profile.</td></tr></tbody></table>


---

# 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.sprinto.com/trust/trust-center/glossary.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.