Privacy and data flow

Controller and merchant: Denis Miclea operating as Adept Web.

What moves where

1. The desktop app minimizes selected engineering context before sending a structured request to api.powersystems.dev.
2. The company-managed service sends only the context needed for the request to its server-side OpenAI Responses integration. Customer API keys, BYOK endpoints, shared Pro accounts, and provider selection are not part of the product.
3. Stripe receives checkout and payment information. PowerSystem stores entitlement and payment-state references, not full card details.
4. Engineering validation, approval, apply, and rollback authority remains local and deterministic.

Logs and receipts

Audit receipts record identifiers, hashes, model route, usage, outcome, and timing without prompt or response text. Operational security logs are access-controlled and retained only as needed for service integrity, billing, legal obligations, and dispute handling.

Customer choices

Use the verified support route for access, correction, deletion, export, or privacy questions. Requests may be retained when law, fraud prevention, payment disputes, or security obligations require it.