Veyloom V markeyloom

Privacy Policy

How Veyloom handles account data, prompts, uploads, generated assets, and support requests.

Last updated: May 31, 2026

Questions about this page can be sent to support@veyloom.com.

Operator

Veyloom is operated by an independent developer / individual operator. Veyloom does not currently publish a registered company entity, and no personal street address is published.

Privacy questions and data requests can be sent to support@veyloom.com.

Information we process

We process account information such as email address, authentication provider profile details, credit balances, subscription status, support messages, prompts, uploaded media, generation metadata, and generated outputs.

We use this information to operate the product, provide generation history, secure downloads, manage credits, prevent abuse, and respond to support requests.

AI generation providers

Generation requests may be sent to third-party AI generation providers to create the requested image or video. Veyloom keeps operational identifiers, API paths, credentials, and access tokens protected.

We process user-submitted prompts through Creem Moderation before sending them to AI generation models. This helps us detect prohibited, unsafe, or abusive requests and enforce our Acceptable Use Policy.

Provider output URLs are temporary. Completed assets should be transferred to Veyloom-managed storage when available.

Veyloom does not actively use user content to train Veyloom-owned models. Third-party AI providers may process content under their own terms and data policies.

Third-party services

Veyloom may use infrastructure, storage, authentication, moderation, payment, and generation services such as Vercel, Supabase, Cloudflare/R2, Creem, and AI generation providers.

The final service list follows the actual production configuration. This policy does not publish API keys, provider secrets, internal routes, unpublished product IDs, or admin-only data.

Retention and security

Prompts are retained for generation records, user history, troubleshooting, and safety checks while the account exists. After account deletion, prompts are handled under the account deletion process.

Uploaded images, uploaded videos, and generated outputs are retained while the account exists for generation history, preview, download, and troubleshooting. Users may request deletion, and account deletion is handled under the deletion process.

Veyloom does not promise unlimited or permanent asset archival. Long-unused resources may later be subject to a cleanup policy after notice or policy update.

Payment, risk, security, and legal compliance records may be retained for the period necessary for those purposes. Log retention and data hosting regions are TBD and depend on the production configuration.

We use access controls, row-level security, and temporary signed downloads to reduce exposure of account and asset data.

Cookies and similar technologies

Veyloom may use cookies and similar technologies for authentication, security, analytics, and user preferences.

Authentication cookies and session cookies help keep you signed in. Security cookies help protect accounts and the service from abuse.

Analytics and preferences

Analytics data helps us understand page visits, feature usage, reliability issues, and product improvements.

Preference cookies may remember language, theme, interface choices, or similar settings when those features are available.

Managing cookies

You can control or delete cookies through your browser settings.

Disabling required cookies may affect login or core product functionality.

Your choices

Contact support@veyloom.com to request account, privacy, or data assistance.

You may contact support to request deletion assistance, opt-out guidance, or review of stored account content where available.

Some operational records may be retained where needed for security, billing, abuse prevention, payment reconciliation, or legal compliance.