> For the complete documentation index, see [llms.txt](https://docs.firecal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firecal.app/my-certs/keep-a-cert-private.md).
# Keep a Cert Private
Some Certs are just for you.
Your [Sharing Preferences](/sharing-and-followers/sharing-preferences.md) decide who can see your Certs. If there's one Cert you'd like to keep to yourself, you can mark it private.
## Tap to Open
When looking at your Locker, **Tap a Cert** to open it, then tap the **Info Icon** (the circled **i**) in the top right corner to open **Cert details**.
## Turn On Private
Scroll down to **Privacy** and turn on the **Private** switch. You'll see **This cert is now private. Only you and people you explicitly share it with can see it.** The people you've invited to the Cert by name (under **Sharing**, just below) keep their access. To go back to following your Sharing Preferences, turn the switch off again.
A private Cert is hidden from your Followers and your Orgs' Members. It's also left out of whole-locker share links, unless you created the link with **Private: On**. To stop access through one of those links, tap **More>Locker share links** and revoke it.
{% hint style="info" %}
**Important:** CertLocker isn't meant for identity documents or other highly sensitive material, even on private Certs. And if your department added a Cert to your Locker or relies on it for compliance, its Officers and Admins may still see it.
{% endhint %}
---
# 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.firecal.app/my-certs/keep-a-cert-private.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.
