Data residency
All product data — workflow definitions, executions, agent conversations, entity records, telemetry, credentials — lives inside your own WordPress database. There is no Project Flash dashboard you log into for the product itself; the dashboard you have at setyenv.com only handles licensing and plugin downloads.
What this means concretely
| Type of data | Where it lives | Who sees it |
|---|---|---|
| Workflow definitions | Your wp_posts table (CPT pfw_workflow) | Only people with access to your WP admin |
| Workflow executions / timeline | Your wp_pfw_executions table | Only your WP admin |
| Agent conversations | Your wp_pfagent_sessions table | Only your WP admin |
| LLM API keys | Your WordPress option store (AES-256-GCM encrypted, derived from your wp-config salts) | Only your WP admin |
| Management entities and records | Your wp_pfm_* tables | Only your WP admin |
| Telemetry the plugin sends to setyenv.com | Site fingerprint (hashed), plugin version, last-seen ts. No record content, no PII. | Setyenv maintainer |
| License activations | The Setyenv portal | Setyenv maintainer |
What about LLM provider data?
When you use WP-PFAgent (or AI nodes in WP-PFWorkflow) with a provider like OpenAI, the request travels directly from your WP server to that provider's API using your keys. Setyenv never proxies your traffic. Whatever data residency or compliance terms you have with that provider apply — the plugin does not insert itself in the middle.