vequro
← Back to Vequro

Privacy

Last updated October 2, 2026.

What Vequro processes

Vequro may process account information, project content, prompts, Lukas conversations, app versions, usage records, billing records, domain configuration and payment-integration metadata needed to operate the service.

AI processing

Prompts and relevant project context may be sent to Vequro's configured AI provider to generate requested output. Vequro is designed so customers do not need to place their own AI provider secret keys into browser code.

Payments

Vequro subscription billing and merchant payments inside customer apps are handled through separate Stripe flows. Stripe may process payment and account information under its own terms and privacy practices.

Infrastructure

Vequro uses infrastructure providers to host the application, database and related services. Custom-domain features may use Cloudflare infrastructure where configured.

Security

Vequro uses server-side access controls and is designed to avoid exposing provider secret keys to generated frontend applications. No internet service can guarantee absolute security.

SMS support

If you initiate an SMS support conversation with Vequro, Vequro may process your phone number, message content, routing code, delivery status and related message metadata to route, deliver, secure and audit the support conversation. Vequro uses messaging providers such as Twilio to transport SMS/MMS traffic. The SMS support flow is for customer care and is not used for purchased lists, cold outreach or unsolicited marketing. Reply STOP to opt out or HELP for help. Message and data rates may apply. All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties.

Your choices

You can choose what project content you submit. Do not place passwords, private keys or other credentials into prompts or generated app content.

Contact and updates

This policy may be updated as Vequro's production infrastructure and legal entity details are finalized. Before a broad public launch, the operator should add the official business contact and jurisdiction-specific disclosures that apply.