Privacy Policy

AiML SuperAgent Privacy Policy

How AiML SuperAgent collects, uses, stores, and protects website, checkout, subscription, and API-key information.

Effective date
June 3, 2026
Mailing address
8 The Green Suite-A
Dover, DE 19901
United States

Who We Are

AiML SuperAgent provides a framework, website, subscription checkout, and customer API-key system for AI coding assistant operations.

You can contact us at privacy@aimlsuperagent.com or by mail at 8 The Green Suite-A, Dover, DE 19901, United States.

Information We Collect

We collect information you provide directly, information created by your use of the website, and information received from service providers that help us run the service.

  • Contact information, such as email address and name when you subscribe, contact us, or complete checkout.
  • Checkout and subscription information from Stripe, such as customer ID, subscription ID, checkout session ID, payment status, plan selected, and billing email.
  • API-key records, including key prefix, hashed key value, plan, status, usage count, and last-used timestamps. We do not store the full plaintext API key after it is shown.
  • Website analytics and visitor information, such as page URL, referrer, language, device/browser information, IP-derived metadata, scroll depth, and product interaction events.
  • Newsletter signup information, including email address, signup source, page URL, and related visitor metadata.

How We Use Information

We use collected information to operate, secure, improve, and support AiML SuperAgent.

  • Process subscriptions and payments through Stripe.
  • Issue, verify, monitor, and protect customer API keys.
  • Provide customer support and billing support.
  • Understand website usage, improve onboarding, and measure product interest.
  • Detect abuse, debug production issues, and protect the service.
  • Send operational emails and, when requested, newsletter or product updates.

Payment Processing

Payments are processed by Stripe. We do not collect or store full payment card numbers on our servers. Stripe may process payment, billing, tax, fraud-prevention, and identity information under its own terms and privacy policy.

Analytics And Cookies

The website may use cookies, local storage, Vercel Analytics, Google Analytics, Google Tag Manager, and first-party visitor logging to understand traffic and product usage. Where the site presents consent controls, you can adjust non-essential analytics preferences through those controls.

Sharing Information

We do not sell customer API keys or billing information. We share information only as needed to operate the service, comply with law, process payments, provide analytics, secure the platform, or complete business administration.

  • Stripe for checkout, subscription, invoice, and payment processing.
  • Vercel and hosting/infrastructure providers for deployment, logs, analytics, and runtime operation.
  • Database, email, analytics, and security providers used to operate the website and services.
  • Professional advisors or legal authorities when required by law or to protect rights, safety, and security.

Data Retention

We keep information for as long as needed to provide the service, maintain billing and tax records, secure the platform, resolve disputes, and comply with legal obligations. API-key hashes and subscription records may be retained after cancellation to prevent abuse, preserve audit history, and support billing records.

Your Choices

You may request access, correction, deletion, or other privacy assistance by emailing privacy@aimlsuperagent.com. We may need to verify your request and may retain information when required for billing, legal, security, or fraud-prevention purposes.

Security

We use practical technical and organizational safeguards. API keys are generated using secure random values and stored as hashes, but no internet service can guarantee perfect security. Customers are responsible for keeping their API keys confidential.

Changes To This Policy

We may update this Privacy Policy as the service changes. The effective date above shows when this version became active.