Privacy policy

wowsuchai is a public catalog of AI models, developer platforms and applications, run by App Forge Labs LLC. This page explains what the service stores about the people who use it.

Public visitors

Reading the catalog, the feeds and the API documentation needs no account. The service does not set tracking cookies, does not build profiles of anonymous readers and does not track individual feed consumers.

The web server keeps short-lived operational logs (the request path, the time and the network address) to keep the service running and to limit abuse.

Analytics

Pages are measured with Umami, a privacy-friendly analytics tool that sets no cookies and stores no personal data: it counts page views, referrers, device type and country, and a few actions such as requesting a recommendation or a feed. Visitors cannot be identified or followed across sites.

Newsletter

If you sign up for the daily or weekly brief by email, the service stores your email address, the briefs you chose, whether and when you confirmed, and which briefs were sent to you. Nothing is sent until you confirm through the link in the confirmation email; an unconfirmed link expires after 48 hours.

Emails are delivered by Resend, which processes your address to deliver them. Every brief email has a one-click unsubscribe link; after you unsubscribe the service keeps your address only as unsubscribed, so it is never emailed again without a new confirmed signup. To have the address deleted entirely, write to the contact address below. Signups are rate-limited with a short-lived counter per network address, which is not linked to your subscription.

Browser error reports

When a page fails in your browser, the page sends a short error report to our server: the error message, the page path and the technical location of the failure. Reports contain no content you typed and are kept in operational logs only.

Tool setup requests

The text you describe your use case in is used only to answer that request and is deleted when the answer is ready; it is sent only to model providers that do not train on it. To count the 3 free tool setups per day, the service stores a one-way hash of your network address with the day and a count, never the address itself or your text.

Before a free request, Cloudflare Turnstile checks that the browser is not an automated script. Cloudflare processes signals from your browser and your network address for that check, under its own privacy terms. The service receives only whether the check passed.

Accounts

You can sign in with Google or with a one-time link sent to your email address. For an account the service stores your verified email address, the name Google returns (or the first part of your address), which sign-in methods you used, and a session cookie that is secure, HTTP-only and same-site. A visitor session lasts 30 days and is extended while you use it; signing out deletes it. Sign-in links expire after 15 minutes and are stored only as a hash until used.

Sign-in emails are delivered by Resend, which processes your email address only to deliver the message. API keys are stored only as a hash, with a name you choose and when each key was last used.

Payments

Credit packs are paid through Stripe, which collects and stores your card or other payment details; wowsuchai never sees them. We keep the Stripe Checkout Session identifier and a ledger of your credits (purchases, grants, one entry per delivered tool setup, refunds), so we can show your balance and answer refund requests.

For x402 payments the service stores the paying wallet address, the amount, the network, the settlement status and the transaction hash. Payments on the Base network are public by nature.

Administrators

Catalog administrators sign in the same way. For them the service also keeps an audit log of the corrections they make. Operator reasons and identities are never shown publicly.

Browser error reports

When a page fails in your browser, the page sends a short error report to our server: the error message, the page path and the technical location of the failure. Reports contain no content you typed and are kept in operational logs only.

Sources we collect

The service collects public announcements, documentation, changelogs, model cards and releases, and stores snapshots of those public pages for one year as evidence.

How long we keep it

Account data and API keys are kept while your account exists; ask us to delete your account at any time. The credit ledger and payment records are kept as long as accounting and tax rules require, even after an account is deleted. Daily free-use counts are kept for a few days. Tool setup results are deleted after 7 days on the web and 24 hours on the API.

Contact

Questions about this policy, and requests to see or delete your data, go to [email protected].