Privacy and data handling
Privacy Policy
This policy explains how the current HandFuture website handles hand images, external resource requests, browser storage, site delivery, aggregate analytics, Google advertising, and regional consent choices. It is effective and updated on 2026-07-26.
Publisher: HandFuture ยท Updated:
Scope and date
This policy applies to the public HandFuture website and its in-browser interactive feature. Its effective date and latest update date are both 2026-07-26.
The disclosures below describe data flows that can currently be confirmed from the site code and deployment configuration. Third-party services process the data they receive under their own policies.
Hand images
Only after a visitor chooses a file does browser FileReader read the image. The browser then decodes it into an in-memory HTMLImageElement, which is passed directly to the on-device MediaPipe hand detector for hand-joint detection and preview, with no intermediate drawing step. The image is not sent to a HandFuture application server.
The selected image, the decoded HTMLImageElement, landmark coordinates, and reflection card stay in current page memory and are not written by HandFuture to persistent browser storage. Reset, refresh, tab close, or browser memory management removes these in-memory states.
External resource requests
After a visitor selects a hand image, the browser loads the MediaPipe hand-detection model files from the cdn.jsdelivr.net content delivery network. On every page load, the site also loads Google Fonts font files from fonts.googleapis.com and fonts.gstatic.com.
These requests fetch model and font assets only. Like any web request, they can expose ordinary request metadata such as the visitor's IP address and browser user agent to cdn.jsdelivr.net, fonts.googleapis.com, and fonts.gstatic.com. They do not include the selected hand image, landmark coordinates, or any HandFuture-specific telemetry.
Browser storage
The site writes only three local-storage keys, all of them interface preferences: palm-reading-storage stores disclaimer acceptance only; language-store stores the language preference; and palm-theme stores the theme preference. These keys do not store the hand photo, the decoded image element, or landmark coordinates.
Visitors can inspect and clear everything stored locally for handfortune.com through their browser's site-data or privacy settings. Clearing it resets the related preferences, and the site may show the disclaimer again on a later visit.
Language suggestion
To suggest a language on the unprefixed home page, HandFuture checks the saved language preference first and then the browser languages. Only when neither identifies a supported language does the page request a two-letter, IP-derived country code from a same-origin Vercel endpoint; a URL that already names a locale bypasses this process.
This feature does not obtain or store the full IP address and does not create a location profile. Vercel may process request data needed to derive the country code under its hosting service and policies; the endpoint returns only the country code or null to the HandFuture page, never a city or more precise location.
Vercel hosting and analytics
Vercel provides hosting. Delivery logs for site content are handled by the hosting provider under its service and policies, and aggregate Vercel Web Analytics reports site usage. HandFuture analytics events do not include the palm image.
See the linked Vercel Analytics privacy documentation below for how Vercel designs Web Analytics and handles related data.
Google advertising
The site includes Google AdSense advertising code. That script may request network resources from Google and use cookies or other browser storage according to the visitor's consent state and Google policy. Ad display and available controls also depend on Google's service state.
Using an ad blocker, or the site not being approved to show ads, does not restrict access to HandFuture content or its local interactive feature. See the linked Google Privacy Policy for Google's handling of service data.
Regional consent
Before personalized or non-personalized ads are served where Google requires consent management, a Google-certified CMP will be enabled through AdSense Privacy & messaging. Until that setup is complete, the CMP is not described as a currently operating feature.
Google's requirement for publishers to use a certified CMP is linked below. When consent controls are presented, visitors can use that interface to select or adjust the available choices.
Cloudflare DNS
In the current configuration, Cloudflare provides authoritative DNS only. It is not the active HandFuture content proxy or host; Vercel delivers the site content.
Choices and rights
Visitors can decline to select a hand image, clear site data, use browser cookie and storage controls, and adjust choices when a consent interface is presented. Disabling some browser features may reset preferences or affect third-party advertising, but the articles remain accessible.
For provider processing and provider-specific choices, consult the official Vercel and Google policies linked below. Any rights that apply by law remain subject to applicable law and the procedures offered by the party that actually processes the data.
Contact
The privacy-policy address is privacy@handfortune.com. This address is monitored only after domain email routing is enabled. Working Cloudflare Email Routing is a release prerequisite; until routing and real delivery are tested, the address should not be treated as a current contact channel.