MarcoFLY Framework Cookie Policy

This page explains the use of cookies, session storage, and other browser-side technical tools used by the MarcoFLY Framework web app as of the update date shown above.

Current platform status

As of this policy date, the public web app is not configured to issue its own profiling or marketing cookies and does not include advertising tools, marketing analytics, or behavioural tracking pixels.

Technical checks carried out on the public version did not show Set-Cookie headers intentionally emitted by the platform’s main public endpoints. This does not exclude that external providers or future services may require this policy to be updated.

Technical tools in use

• browser sessionStorage used to reduce repeated requests for the same home visit during the same browser session
• technical requests to platform endpoints to retrieve public stats, generate prompts, and validate activations
• requests to Google favicon service / gstatic to display compatible AI platform logos
• requests to external services strictly needed to render some informative elements or resolve the network provider, as described in the Privacy Policy

Home page session storage

The home page uses a session key named mff-home-visit-tracked-v1 to reduce duplicate requests during the same browser session.

The public visit counter is also deduplicated server-side by IP address, when available, so the same IP does not increase the public count on every page load.

This information remains in the browser until the session ends and is used only for technical and internal statistical purposes related to the framework census.

Purposes

• technical operation of the platform
• consistent counting of home visits and public census activity
• minimal telemetry, security, and abuse prevention
• display of framework usage data, confirmations, and status

Consent and legal basis

The technical tools currently in use are intended for platform functionality, internal operational monitoring, and correct registration of framework activations and confirmations.

For any future profiling, marketing, or other non-essential tracking tools, the platform must be updated with the appropriate notice and consent mechanisms before those tools are activated.

Connected providers

• Vercel for hosting and app infrastructure
• Supabase for data persistence
• Google favicon service / gstatic for retrieval of compatible AI platform logos
• ip-api.com and ipwho.is for network provider lookup when required
• flagcdn.com for rendering some country flags shown in the interface

If the project later introduces third-party analytics, non-technical cookies, or additional tracking tools, this page must be updated before those tools go live.