Last updated July 28, 2026

Privacy, kept simple.

Marco does not operate advertising, newsletters, or visitor profiles on this website. The AI Discovery Observatory stores privacy-preserving aggregate request counts, never IP addresses, complete user-agent strings, cookies, identities, or full referrer URLs.

Information Marco collects

This website does not ask visitors to provide names, email addresses, phone numbers, payment details, or other personal information. Marco does not use this site to place advertising cookies or build visitor profiles.

AI Discovery Observatory

The site maintains a first-party aggregate ledger to distinguish AI crawlers, user-triggered AI retrieval agents, search crawlers, and human referral sources. It stores the calendar day, public path, actor class, declared bot family or source category, verification label, aggregate request count, and last-seen time. It does not store an IP address, complete user-agent string, cookie, visitor identity, search prompt, or full referrer URL.

Aggregate counts are published on the Observatory. A bot can imitate a user-agent label, so declared agents are shown separately from requests identified as verified bots by the hosting network. Citation observations are entered by the site owner after a dated manual check and contain no visitor personal information.

Founder Revenue Lab inputs

Questions entered in the public Founder Revenue Lab are processed in the visitor’s browser against a bundled synthetic fixture. The demonstration has no form submission, user account, Stripe connection, API-key field, or application database.

Internet Country applications

A voluntary membership application asks for a participation class, public display name, optional public HTTPS profile, and a short contribution statement. Approved records can be published in the public registry after review. Pending names, purposes, and review details are not public.

To limit automated submissions, the application service creates a short one-way request fingerprint from network and browser request information plus the calendar day. It does not retain the raw network address or complete user-agent string in the application table. Do not submit government identifiers, credentials, secrets, private contact details, or sensitive personal information.

Public MCP endpoint inputs

The public MCP endpoint can receive JSON-RPC methods, tool names, and tool arguments sent by a compatible client. It uses those inputs only to search the published knowledge corpus, select or calculate from the bundled synthetic fixture, or compare an illustrative scenario. It has no application database, user account system, Stripe connection, or credential field. Do not include API keys, customer records, private exports, or other sensitive information in MCP requests.

Hosting and technical data

The hosting platform and a visitor’s browser, network provider, or device may process limited technical information needed to deliver and secure the website and MCP endpoint, such as request headers, network addresses, timestamps, route names, or error records. Those services operate under their own privacy terms and are not controlled by Marco. The site’s own aggregate ledger does not retain network addresses or complete request headers.

External links

Links to Instagram, LinkedIn, X, Threads, GitHub, ChatGPT, Stripe documentation, and independent directories leave this website. Those services may collect information under their own policies. Review their policies before using them.

Children

This site is a general public profile. It is not designed to collect information from children. The voluntary application is intended for adults and should not contain sensitive personal information.

Questions or corrections

For a correction to public information on this website, contact Marco through his verified Instagram or LinkedIn profile. Do not send sensitive information in an initial message.