Permission before consequence
Approvals are recorded and checked against the action they authorize. A required approval must exist before the corresponding action can proceed.

Praxa keeps permissions, remembered context, and consequential actions subject to controls you can review.
Our approach
Approvals are recorded and checked against the action they authorize. A required approval must exist before the corresponding action can proceed.
Optional sources have separate consent controls. Review your settings, revoke connections, and inspect or remove supported memories. Accepting the terms does not turn on optional sensors or context sources.
The Privacy Notice describes processing, retention, providers, and your choices. The Terms of Use describe responsibilities and service conditions. Report security concerns to team@praxa.io.
Controls & documentation
Explore the product controls and published policies that help you make an informed choice.
Inspect and correct supported memories. Decide which optional sources you enable.
Manage your data choicesReview the access you grant to connected services, and revoke connections when your needs change.
Explore integrationsRead how information is processed, retained, and shared with service providers, together with your choices.
Read the Privacy NoticeReview the responsibilities and service conditions that apply when you use Praxa.
Read the termsContext by choice
Optional sources have separate consent controls. Accepting the terms does not switch on optional sensors or context sources.
Review data controlsActions with authority
Preparation and coordination are distinct from an action that requires approval. A required approval must match the action it authorizes.
Understand the technologyReport a security concern
Send the affected page or feature and a clear description to our team. Leave passwords, API keys, and other secrets out of your message.
Email the teamteam@praxa.io