>_ Privacy Policy

Last updated: April 28, 2026

0. Data Controller

For the purposes of the EU General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), the California Privacy Rights Act (CPRA), and analogous state and international privacy regulations, the data controller for personal information collected through TerminalFeed.io is Pizza Robot Studios LLC, a California limited liability company with a principal mailing address at 3705 W Pico Blvd #B, Los Angeles, CA 90019, United States.

Privacy requests, including requests to access, delete, correct, or port your personal information, and "Do Not Sell or Share My Personal Information" requests under CCPA / CPRA, may be submitted to [email protected]. We respond to verifiable requests within the timeframes required by applicable law.

1. Introduction

TerminalFeed.io ("we", "our", "us") operates the terminalfeed.io website (the "Service"). This Privacy Policy explains how we collect, use, and protect information when you use our Service. We are committed to protecting your privacy and being transparent about our data practices.

2. Information We Collect

Automatically Collected Information: When you visit our Service, our servers and third-party services may automatically collect certain information including your IP address, browser type, operating system, referring URLs, pages viewed, and access times. This data is collected via server logs and cookies.

Cookies and Tracking: We use cookies and similar technologies for analytics and to improve the user experience. Third-party services we use, including our hosting provider Cloudflare, may also set cookies. We may in the future use advertising cookies if and when advertising partners are integrated.

Personal Information: We do not require account creation or collect personal information such as names, email addresses, or payment details directly. Any information entered into the dashboard (such as layout preferences) is stored locally in your browser via localStorage and is never transmitted to our servers.

Local Storage: TerminalFeed uses your browser's localStorage to save your dashboard layout preferences, panel visibility settings, and cached API data. This data never leaves your browser and is not accessible to us or any third party.

3. How We Use Information

We use collected information to:

• Operate and maintain the Service
• Analyze usage patterns to improve the Service
• Detect and prevent abuse or security issues
• Comply with legal obligations

4. Third-Party Services

Our Service uses the following third-party services that may collect data:

• Cloudflare: Provides hosting, CDN, DDoS protection, and security services. Cloudflare may collect IP addresses and request metadata for security purposes. See Cloudflare's Privacy Policy.
• CoinGecko, CoinCap, Mempool.space, Finnhub, USGS, NASA, ESPN, and other API providers: We fetch publicly available data from these APIs on behalf of your browser. No personal information is shared with them beyond standard HTTP request headers (IP address, user agent).
• Cloudflare Speed Test (speed.cloudflare.com): Provides download and upload speed measurement for the WiFi Health Monitor tool. Speed tests are conducted using Cloudflare's public speed test endpoints. See Cloudflare's Privacy Policy.
• Cloudflare DNS (1.1.1.1): Provides DNS resolution speed testing for the WiFi Health Monitor tool via DNS-over-HTTPS. Receives DNS queries when a WiFi test is run. See Cloudflare's public resolver privacy commitment.

4A. WiFi Health Monitor Tool — Data Practices

The WiFi Health Monitor tool at terminalfeed.io/wifi has the following specific data practices:

What the WiFi Tool Collects:

• Your public IP address is processed by our own Cloudflare Pages Function to retrieve your approximate geographic location and ISP information. This data comes from Cloudflare's built-in request metadata and is never sent to a third-party IP lookup service.
• DNS queries for common domains (google.com, cloudflare.com, amazon.com, netflix.com) are sent to Cloudflare's public DNS-over-HTTPS resolver (cloudflare-dns.com) to measure DNS resolution speed. These queries are subject to Cloudflare's public resolver privacy policy.
• HTTP requests are made to Google's connectivity check endpoints (generate_204) for latency and speed measurements. Standard HTTP request headers (IP address, user agent) are transmitted as part of these requests.

What the WiFi Tool Does NOT Collect:

• We do not store or transmit your speed test results, health scores, or diagnostic information to our servers or any third party.
• We do not access your local network, router settings, WiFi configuration, connected devices, or any information about your home network topology.
• We do not scan for nearby WiFi networks, access points, or signal strength data.
• Test history is stored only in your browser's session memory and is cleared when you close the page. No test data persists between visits.

Third-Party Data Sharing:

• Cloudflare receives speed test requests when you run a test (speed.cloudflare.com). See: Cloudflare Privacy Policy.
• Cloudflare receives DNS queries when you run a test. See: Cloudflare public resolver privacy.
• Google receives HTTP requests for connectivity checks. See: Google Privacy Policy.

Browser APIs Used:

• Network Information API (if supported by your browser) — to detect connection type and estimated bandwidth. This data stays in your browser.
• Performance API — to measure request timing. This data stays in your browser.

No WiFi Tool data is sent to TerminalFeed.io servers. All measurements and diagnostics are computed client-side in your browser.

4B. Premium API Tier: Data Practices

The Premium API tier described in Section 17 of our Terms of Service involves collecting and processing additional data beyond the core dashboard. This Section explains what we collect, why, and how long we keep it.

What we collect for the Premium API:

• Sender wallet address. When you, or an autonomous agent acting on your behalf, send USDC to our published Base mainnet wallet to purchase credits, we record the sender wallet address as part of the payment confirmation flow. Wallet addresses are pseudonymous but, under EU GDPR, UK GDPR, the California Consumer Privacy Act, and similar laws, may constitute personal data because they uniquely identify a transacting party. We use this data to credit the correct bearer token, prevent replay of the same transaction hash, screen for sanctions and anti-money-laundering concerns where appropriate, and respond to lawful requests from regulators or law enforcement.
• Transaction hash. The Base mainnet transaction hash is recorded server-side and used to enforce one-time credit issuance under the replay-protection rule in Section 17.4 of the Terms.
• Bearer token (hashed). We do not store the raw bearer token. We store a one-way cryptographic hash of the token together with the associated credit balance, issuance timestamp, and, where applicable, revocation status.
• Per-call telemetry. For each Premium API call, we record the bearer-token hash, the endpoint called, the response status, the credits decremented, and a timestamp. Request payloads and response bodies are not stored in plaintext beyond the short-lived in-memory cache used for performance.
• Email correspondence. If you email [email protected], [email protected], [email protected], or any other Service mailbox in connection with a payment, token, billing, or account matter, we receive your email address and the contents of your message and may retain them for support, audit, and anti-abuse purposes.

What we do not collect for the Premium API:

• We do not collect names, government IDs, KYC documents, postal addresses, phone numbers, dates of birth, or fiat payment-card details. The Premium API has no human registration flow.
• We do not collect, store, or sell the contents of Premium API responses on a per-user basis beyond the short-lived in-memory cache used to amortize upstream calls.
• We do not embed third-party analytics, advertising, or tracking pixels in Premium API responses.

Cross-site sharing with TensorFeed. Premium credits and bearer tokens are jointly redeemable on terminalfeed.io and tensorfeed.ai under Section 17.8 of the Terms. The TensorFeed payment Worker, also operated by Pizza Robot Studios LLC, is the system of record for credit balances. Wallet addresses, transaction hashes, bearer-token hashes, and per-call telemetry generated on either site are processed by the same operating entity for the unified credit-accounting system. No third-party data processor outside Pizza Robot Studios LLC and our infrastructure providers (currently Cloudflare, Chainalysis sanctions screening, and the Base mainnet network itself) receives this data for the cross-site bundle.

Blockchain analysis and sanctions screening. The Base mainnet ledger is a public blockchain, and any party, including us, can inspect on-chain transactions involving the published wallet. We screen every inbound credit-purchase transaction against the Chainalysis public sanctions API, which checks the sender wallet against the United States OFAC SDN list and other major sanctions regimes. Where such screening identifies a sanctioned address, an address with material exposure to known illicit activity, or another concern under Section 17.9 of the Terms, we may decline the credit grant and freeze any associated bearer token under Section 17.11 of the Terms. The Chainalysis service receives only the wallet address being screened; it does not receive any personal information that we do not already hold on-chain.

Retention for Premium API data. Wallet addresses, transaction hashes, bearer-token hashes, per-call telemetry, and related billing records are retained for so long as the associated credit balance remains active and for a further period of seven (7) years thereafter, consistent with general United States tax and financial-record retention guidance and applicable state law. Email correspondence is retained for up to twenty-four (24) months unless a specific ongoing reason justifies longer retention (for example, an unresolved dispute, a pending support matter, or a law-enforcement preservation request). After the applicable retention period elapses, records are deleted or anonymized, except where applicable law requires longer retention.

Your rights for Premium API data. Because the Premium API is wallet-authenticated rather than identity-authenticated, we cannot, in most cases, link a wallet address back to a specific natural person without information that you provide. To exercise GDPR, UK GDPR, CCPA, CPRA, or analogous rights with respect to Premium API data, you may need to demonstrate control of the wallet address in question, for example by signing a challenge message we provide. Verifiable requests should be sent to [email protected] and will be handled within the timeframes required by applicable law.

5. Advertising

We may display advertisements on the Service in the future through advertising partners such as Google AdSense. If and when advertising is enabled, advertising partners may use cookies to serve ads based on your prior visits to our website or other websites. You will be able to opt out of personalized advertising by visiting Google Ads Settings.

For more information about how Google uses data, visit How Google uses data when you use our partners' sites.

6. Data Retention

Server logs and analytics data are retained for up to 12 months. Cloudflare analytics data is retained according to Cloudflare's data retention policies. You can clear locally stored data at any time through your browser settings by clearing localStorage for terminalfeed.io.

7. Data Security

We take reasonable measures to protect the information collected through our Service. The site is served over HTTPS, protected by Cloudflare's security infrastructure, and we do not store any sensitive personal data on our servers. However, no method of transmission over the Internet is 100% secure, and we cannot guarantee absolute security.

8. Children's Privacy

Our Service is not directed to individuals under the age of 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us so we can take appropriate action.

9. Your Rights

Depending on your jurisdiction, you may have the right to:

• Access the personal data we hold about you
• Request correction of inaccurate personal data
• Request deletion of your personal data
• Object to processing of your personal data
• Request restriction of processing your personal data
• Data portability

Since we collect minimal data and do not require accounts, most information can be managed through your browser settings. To exercise any of these rights, please contact us at the email address below.

10. International Users

TerminalFeed is hosted on Cloudflare's global network. If you access the Service from outside the United States, please be aware that your information may be transferred to, stored, and processed in the United States or other countries where Cloudflare operates servers.

11. Do Not Track

We respect Do Not Track (DNT) browser signals. When we detect a DNT signal, we do not engage in any additional tracking beyond what is necessary to operate the Service.

12. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated revision date. We encourage you to review this page periodically for any changes. Your continued use of the Service after any changes constitutes acceptance of the updated policy.

13. Contact

If you have questions or concerns about this Privacy Policy, please contact us at [email protected].