> For the complete documentation index, see [llms.txt](https://docs.tidelight.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tidelight.app/trust-and-safety/privacy-and-account-safety.md). # Privacy and account safety How Tidelight handles your workspace and sources. ## Privacy and account safety Your saved briefs, watchlists, and strategy runs belong to your account. Database access policies scope private records to their owner. ### Your sources Mini fetches allowlisted public hosts. It limits fetched pages to 2 MB and rejects redirects to unapproved hosts. Pro stores the excerpts you submit with their source links. Read sources carefully before sharing them. ### Account protection You can enroll an authenticator app for additional verification. Passkey support becomes available after the production provider and relying-party domain are configured. ### Keep credentials private Never add API keys, private links, or secrets to a brief. Credentials remain server-side and should not be committed to source control. --- # 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.tidelight.app/trust-and-safety/privacy-and-account-safety.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.