On this page
Private docs
Every Docsary site is public. Private sites are not available yet. Use Docsary only for content anyone may read, copy, or download.
Where things stand today
There is no password or per-reader access control on published sites. These approaches do not make content private:
| Approach | Remaining access |
|---|---|
| Leave a page unlinked | It can still appear in navigation, search, and the sitemap. |
| Skip a custom domain | The allocated docsary.com address still serves it. |
| Use a non-default version | Anyone can open its version URL. |
| Set crawler directives | Cooperative crawlers may exclude it; anyone can still request it. |
API access does not make content private
API keys control management access. A read-only key lets an agent inspect content without editing it, but the same pages remain publicly readable. Revoking the key does not remove public access.
Putting your own gate in front
A login, VPN, or proxy on your custom hostname protects only traffic passing through it. Readers can bypass that gate through the site's docsary.com address or a direct request presenting your hostname.
Do not rely on an external gate to protect a Docsary site today.
What is coming: private mode
Private mode is planned for Pro at no extra cost. It is intended to restrict every request, remove public addresses and listings, and prevent shared caching. Access would require a read-only key or a secret header supplied by your own access gateway.
This mode is not available. Hosted reader logins, magic links, and SSO connectors are not currently planned.
Recommendations, in short
- Host confidential material somewhere that enforces reader access.
- Use read-only API keys for tools that inspect public documentation.
- Never publish credentials or personal data that must remain private.
- Keep in mind that deleting content cannot recall third-party or offline copies.
Contact hello@robota.us to discuss your access requirements.