Operations
Security and Data Handling
A plain-language summary of how server/mobile/client keys, context data, and operational safeguards fit together when you evaluate Zenmanage for production use.
Platform key model
Zenmanage authenticates evaluation requests with server, mobile, and client keys per environment. This keeps development, staging, and production separated while also ensuring each SDK class receives only the payload shape intended for it. Store all keys in the same secret-management systems you use for other application credentials.
Data handling posture
Zenmanage public policy states that personal information is protected by commercially acceptable means, while also making clear that no transmission or storage method is perfectly secure. Full legal detail lives in the privacy policy.
Context and caching considerations
Only send the context fields and attributes that you actually need for evaluation. Context data is part of request handling, so unnecessary attributes increase data surface without improving rollout quality. If you cache rules or evaluated values in your own systems, treat that cache as a copy of runtime decision data and protect it accordingly.
Public SDK docs describe local rule caching and fallback behavior. That can improve reliability, but it also means your own infrastructure may temporarily hold copies of evaluation state. Make sure retention and access controls match the sensitivity of the attributes you send.
For the complete legal and privacy description, review the privacy policy.
Next step
Take the next integration step in your own stack.
Start with the quickstart that matches your runtime, then return to the reference pages when you need exact request and payload details.