Collection depends on whether someone is browsing the public site, submitting a contact request, or using a runvello workspace.
Public-site inquiries
When someone submits the contact form, runvello stores their name, email, company details, website, message, and request metadata needed for follow-up and abuse review.
Workspace records
Organizations may store client, lead, booking, contract, invoice, campaign, project, and asset records that they choose to manage inside the platform so the service can function as intended.
AI-assisted work
When a workspace user requests AI assistance, runvello sends the context needed for that action to the configured AI provider. Production uses the OpenAI API unless the deployment owner explicitly enables another supported provider. Text dispatch removes email addresses, phone numbers, and credential-shaped values. Customer images are sent only for an explicit visual-analysis action selected by the user. The workspace retains the source, output, and review history needed to show provenance; operational usage telemetry records counts and provider metadata rather than a second copy of the prompt. OpenAI states that API inputs and outputs are not used for training by default; default abuse-monitoring logs may retain customer content for up to 30 days unless approved data-retention controls apply.
Technical telemetry
Basic request, error, and operational telemetry may be processed to keep the app available, investigate incidents, and protect the service.
Payment-related records
runvello may store limited billing-related information such as subscription status, plan details, usage, transaction references, and Stripe customer or subscription identifiers, but not full payment card data.