Privacy Policy.

01 / Scope of this policy

This Privacy Policy explains the current API Market Exchange interface, including the website, browser-wallet connection, server-side network checks and PostgreSQL cache. It does not describe independently operated wallets, exchanges, model providers or blockchain explorers. APIME is the name of this experiment; it does not identify a model provider as the operator.

Browsing does not require registration or a wallet. The application does not request your name, email, phone number, payment information, recovery phrase or private key. There is currently no in-app privacy request form or published privacy contact address.

02 / Information handled when you visit

Your browser requests pages, images and the network-status endpoint from the host. Hosting and security services can process IP addresses, request URLs, timestamps, response codes, browser information and related connection metadata to deliver and protect the website. Do not include sensitive information in a page URL or query string.

The application does not install advertising trackers, Vercel Web Analytics, Speed Insights or behavioural analytics scripts. It does not implement fingerprinting, cross-site profiling, an advertising identifier or an account database. Infrastructure logs and security measures are distinct from these application features.

03 / Wallet information

If you choose to connect, your browser wallet shares a public account address and current chain ID with the page. The app uses them to display the connected account and identify its network. The address and terms acknowledgement remain in page memory and are not sent by the app to its RPC endpoint, database or an analytics service.

The connection clears when you reload, disconnect, change accounts or change the wallet network. Clearing the site’s state does not necessarily remove permissions retained by your wallet. Your wallet provider may independently process connection information under its own policy. A public address may still be linkable to a person through public transactions or other information.

04 / RPC requests and database cache

The browser calls APIME’s own network endpoint. The server then requests the configured chain ID and latest block from its RPC provider, which may be Alchemy depending on the operator’s configuration. These requests contain the server’s service credentials and network queries, not the visitor’s wallet address or forwarded browser IP headers. The RPC provider sees the server connection and can maintain its own service logs.

The database stores a short-lived cache of public chain information: chain ID, block number, block time and time checked, plus a database-health timestamp. Cache keys contain a hash of the configured RPC endpoint rather than the endpoint or API key. This cache does not store wallet addresses, consent records, visitor IP addresses or browsing profiles. Database access credentials remain server-side.

05 / Purposes and applicable grounds

Information is handled to deliver requested pages, display a wallet connection you initiate, report network availability, reduce duplicate network requests and protect the service. We do not sell visitor information or use it for targeted advertising. The present application does not make automated decisions with legal or similarly significant effects about visitors.

Where data-protection law requires a lawful basis, service delivery and security may rely on legitimate interests in operating and protecting the website, subject to applicable rights and balancing requirements; processing needed to comply with law may rely on a legal obligation. A terms checkbox is not blanket consent to unrelated personal-data processing. Optional tracking or new collection would require updated disclosures and, where required, a separate choice.

06 / Service providers and external links

Vercel hosts the site and may process request and security metadata. The configured RPC and PostgreSQL providers support network reads and caching. Their processing, hosting locations, backups and operational logs depend on the actual services and plans configured by the operator. We do not claim that data remains in a particular country or that every provider has the same retention period.

Provider logos and card images are served from the site. The OpenRouter catalogue is bundled as a snapshot, so browsing it does not send an inference request to OpenRouter. If you follow an external link, that destination receives your connection and may process information under its own policy. Public blockchain data is also independently accessible to third parties.

Vercel Privacy Notice ↗

07 / Retention and deletion

Wallet and acknowledgement state last only for the current page session and clear on the events described above. Network responses are reused for up to 20 seconds in the app’s cache. Expiry means that a response is no longer used, not that its database row or backups are erased at that exact time. A row is overwritten on a later successful check; unused rows may remain until maintenance or database removal.

Hosting, security, RPC and database-provider logs or backups can be retained separately under provider settings and operational requirements. We have not verified one fixed retention period across those services. Where records are retained for security, dispute handling or legal obligations, the relevant need and applicable law determine retention. Public blockchain history is not controlled or deletable by APIME.

08 / Cookies and browser storage

The application does not set advertising cookies or persist the wallet address or acknowledgement in localStorage, sessionStorage or an app cookie. Ordinary browser caching of website files can still occur. A hosting platform’s access protection or security features may use its own cookies, and browser extensions and wallets control their own storage.

You can control cookies and cached website data through browser settings and wallet permissions through your wallet. Changing these settings may affect external services. No optional-tracking consent is inferred from merely browsing or connecting a wallet.

09 / Choices and privacy rights

You can browse without connecting, disconnect your wallet and avoid external links. Depending on your location and applicable law, you may have rights to request access, correction, deletion, restriction, portability or objection, and to complain to a relevant data-protection authority. These rights have conditions and do not necessarily require deletion of records that must lawfully be retained.

The current release has no account profile, email subscription, identity-verification process or self-service data-request portal. A request about information handled independently by your wallet or another destination may need to go to that provider. Do not send a recovery phrase, private key or an unnecessary identity document as part of any request.

10 / Security and international processing

The app keeps database and RPC configuration on the server and returns limited status information rather than credentials or raw provider errors. Network checks have time limits and do not offer a public transaction or arbitrary RPC relay. These measures reduce exposure but cannot guarantee that a service will never experience unauthorised access, error or interruption.

Hosting and service providers may process information outside your location. Applicable transfer requirements depend on the operator, destination, service agreements and law. This policy does not certify a particular transfer safeguard or compliance arrangement that has not been verified.

11 / Children and policy changes

The experiment is intended for adults, as described in the terms. The app does not knowingly request children’s personal information or operate a children’s account service. Do not submit personal information about a child through public metadata or external communications.

Changes to collection, wallets, charts, analytics or external integrations will be described in an updated policy. The version and publication date identify this notice. This policy describes current implementation and does not promise that future features will collect the same information.