Cookie Policy

SmartAPIs.net should default to no non-essential cookies on the public site. If analytics, advertising, personalization, or optional third-party embeds are introduced, consent handling should be added before those cookies are set.

1. Current product posture

SmartAPIs.net REST and MCP access are API-key based and should not depend on browser cookies for core developer or agent access. The marketing site and future dashboard should stay operational with minimal cookie dependence.

2. Cookies that may be used

Strictly necessary cookies for secure sessions, billing redirects, or abuse protection.
Security cookies or similar identifiers for bot mitigation and operational defense.
Preference cookies for language or simple UI choices if those features are added.

3. Cookies that should stay off by default

Analytics cookies that are not essential to service operation.
Advertising or cross-site tracking cookies.
Personalization cookies that are not necessary for the requested service.

4. Third-party services

Stripe, Cloudflare, Google Cloud, and future support or analytics vendors may set cookies or similar identifiers in some flows. SmartAPIs.net should inventory those behaviors before broader launch and disclose them clearly.

5. Consent posture

If SmartAPIs.net adds any non-essential analytics, marketing, or personalization cookies, a consent banner or equivalent consent flow should be added before those cookies are activated for users in applicable jurisdictions.