> For the complete documentation index, see [llms.txt](https://puregamma-ai.gitbook.io/puregamma-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://puregamma-ai.gitbook.io/puregamma-ai/puregamma-ai/trust-and-operations/security-privacy-and-compliance.md). # Security, privacy & compliance ## Core security posture PureGamma uses authenticated API boundaries, server-side provider credentials, tenant-aware data access, signed integration requests, and operational logging. The browser and iOS client do not receive Stripe, model, broker, exchange, Plaid, or relay secrets. ## Sensitive connection data Read-only connector tokens and API materials belong in server-controlled configuration and must be encrypted before durable storage where the connector is implemented. Users must never supply private keys, seed phrases, withdrawal permissions, or trading-enabled exchange keys. ## Payment and webhook integrity Stripe webhooks are signature-validated and deduplicated by event identifier. Billing writes are designed to be idempotent and unknown plan mappings are routed for manual review rather than silently granting access. ## Data and product boundaries Portfolio connections are analytical only. Research, reports, and signals are informational. Live trading is disabled. The product is not a broker-dealer, investment adviser, exchange, custodian, or wallet provider. ## Responsible use Do not treat product output as personalized investment advice. Review sources, validate assumptions, consider your own risk tolerance, and consult qualified advisers where appropriate. Privacy and legal terms governing your deployment remain controlling. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://puregamma-ai.gitbook.io/puregamma-ai/puregamma-ai/trust-and-operations/security-privacy-and-compliance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.