PRIVACY
This page describes the data flows in the current IFAH website, Player and Studio releases. The project implementation contains no analytics, advertising trackers or optional telemetry.
IFAH PLAYER
The Player keeps its library history, current field state and interface preferences in local application storage. The desktop Player has no IFAH account connection and does not send listening activity or field data to IFAH. The hosted web Player requests its page and bundled sample Editions from the website.
IFAH STUDIO
Studio stores documents, recovery data, recent items and preferences locally. Recordings are saved to the device. A random installation identifier and signed licence certificate are kept in the operating system credential vault.
ACTIVATION
Activation sends the licence key, random installation identifier and platform to the IFAH licensing service over HTTPS. The service stores a hash of the licence key rather than the raw key, plus the installation identifier, platform and certificate issue time. Hashed key and request-IP buckets are used to limit repeated activation attempts. Studio documents, audio and activity are not sent with activation.
MICROPHONE · CAMERA
The Player interface does not request microphone or camera access. Studio requests microphone access only when audio input is armed; processed recordings can then be saved locally. Optional camera-driven Studio features request camera access when activated and process frames on the device with a bundled model. Camera frames are not sent to IFAH.
WEBSITE · DOWNLOADS
The site is served by Cloudflare Pages and downloads and licensing pass through Cloudflare Workers. Normal web requests necessarily disclose request information such as IP address, user agent and requested URL to Cloudflare. IFAH adds no analytics or advertising tracker to those requests.
CHECKOUT · CONTACT
Starting a purchase asks the IFAH service to create a Checkout session for the existing Studio price, then redirects to Stripe. Stripe receives the payment and contact details entered there. IFAH stores the Stripe event, session and payment identifiers needed to issue the secure claim and licence; the site has no customer account system. The Inquiry form sends the name, email, optional practice or context and question you enter to the IFAH inbox through Cloudflare Workers and Email Service. Turnstile receives the verification token and request information needed to reject automated submissions. IFAH does not add inquiries to a website database.