Workflow execution normally occurs on the Windows computer or execution environment you control. Account, payment, publishing, update, and AI-assisted features use online services when you choose them. Review these boundaries before using sensitive data.
Local automation data remains under your control unless a workflow or online feature is configured to transmit, upload, or publish it.
Orders, customer records, admin pages, exported files, and other business data can be processed on customer computers, servers, or internal networks. Enterprise delivery can integrate with existing directories, databases, and access policies.
Customers maintain platform accounts, passwords, verification codes, browser environments, and login sessions. For sensitive systems, use dedicated execution accounts, least privilege, and regular credential rotation.
Workflow files, runtime logs, error screenshots, and execution results normally remain local. Applications or files you intentionally publish are uploaded to online storage.
Runavelo transmits only the information needed for the online feature you request, but you remain responsible for reviewing the content you choose to send.
Email verification, sessions, plans, entitlement balances, and order status are processed by Runavelo services. Stripe processes payment details during checkout.
Prompts and the workflow, documentation, file, or error context you select are sent to the AI provider configured for the conversation. Do not include passwords, API keys, or regulated data unless you have reviewed that provider's controls.
Applications you choose to publish are uploaded to managed object storage. Software-update checks transmit the edition and version information needed to determine available updates.
For enterprise use, start with a frequent, rules-based workflow that a person can verify. Once validated, expand gradually to additional systems and accounts.
Rules-based processes such as repeated logins, data transfer, spreadsheet processing, order synchronization, bulk queries, report downloads, and notifications.
Processes involving fund transfers, irreversible submissions, sensitive approvals, or tightly controlled platforms should include human confirmation, allowlists, and permission isolation.
We do not promise to bypass third-party risk controls or guarantee that every page will remain stable indefinitely. Page redesigns, CAPTCHAs, and platform restrictions may require workflow updates.
Workflow credentials normally remain on the execution computer. Runavelo does not require you to send them to an AI provider or publish them. However, any secret included in a prompt, selected workflow context, uploaded file, log, or published application can be transmitted with that content. Use dedicated accounts, least privilege, and secret-free prompts.
Execution data such as orders, spreadsheets, screenshots, and logs is normally stored in local directories. Content you intentionally publish or send through an online feature follows the storage and retention rules for that feature and its provider.
The Enterprise edition can be evaluated for intranet deployment, offline activation, dedicated runners, and customer-managed execution machines. The final design depends on system entry points, network policies, account permissions, and operational requirements.
Automation does not promise to bypass third-party risk controls. When a redesign, CAPTCHA, dialog, or platform restriction interrupts a workflow, logs and screenshots can identify the failed step for human review or workflow adjustment.
High-risk actions such as fund transfers, irreversible submissions, sensitive approvals, and customer-data changes should not run entirely unattended. Add human confirmation, allowlists, permission isolation, and audit trails.