Integrations Policy

lol.gl may use infrastructure providers such as Vercel, Supabase, AWS, S3-compatible storage, and related services to host the application, run API routes, store product data, store user uploads and generated media, authenticate users, process webhooks, and operate scheduled jobs.

Authentication features may include password login, passkeys/WebAuthn, phone verification where enabled, magic-link fallback for operational recovery, and Sign in with Apple or other OAuth-style providers where configured. Users must only use identities and accounts they are authorized to access.

Payments and billing may be handled through payment providers such as Stripe, including checkout, subscriptions, usage metering, saved payment methods, customer billing records, webhooks, and, where offered, agent wallet or virtual-card controls.

Payment information is handled through provider-hosted or provider-secured payment flows where available. Users may not use lol.gl to evade payment provider rules, card network rules, sanctions screening, fraud controls, chargeback processes, or spending limits.

The product can execute or verify access for AI and media providers such as OpenAI, Anthropic, Google, AWS Bedrock, xAI, NVIDIA, ElevenLabs, Hume, Runway, Luma, Recraft, Ideogram, Adobe, and similar model or media services. Availability depends on product configuration, provider access, model availability, and user-supplied credentials where applicable.

When users bring their own provider keys, those credentials are used only to verify access and run configured workflows. Users remain responsible for provider terms, usage limits, content policies, model access approvals, account standing, billing setup, and rights to prompts, uploads, outputs, and generated media.

Users may not use lol.gl to bypass model safety rules, provider quotas, restricted model access, content licensing limits, abuse checks, or account review decisions.

Domain, deployment, and location features may use external services for domain search, deployment status, address autocomplete, place details, maps or geography data, and related provider verification.

Users are responsible for accurate domain, address, business, and ownership information submitted to external platforms. Provider approvals may require matching business identity, verified domains, billing records, DNS records, callback URLs, privacy links, and support contacts.

When a provider asks for a company website, privacy policy, terms, abuse contact, support email, or product description, use lol.gl, the pages linked from /legal, and support@lol.gl.

Provider submissions should describe the actual feature being enabled. Examples include transactional email, payment processing, domain verification, model API access, media generation, storage, authentication, or deployment. Do not submit a broader or riskier use case than the product path actually uses.

If a provider grants production access, marketplace access, API access, model access, domain verification, or billing approval, the product use must stay consistent with that approved use case. Material changes may require updated provider registration or re-review.

Integrations are subject to account permissions, provider limits, product configuration, audit trails, spend controls where available, human review for high-risk actions where applicable, and suspension when activity creates legal, safety, financial, or provider risk.

Report suspected abuse, credential misuse, provider-rule violations, fraudulent payments, unauthorized account access, or unsafe automation to support@lol.gl. Include account details, provider names, timestamps, URLs, message IDs, or webhook IDs where available.