Privacy Policy

Effective date: July 22, 2026. This document is designed as a disclosure framework for Faseetr Review. The current site is a demonstration prototype and does not run live advertising tags, analytics, forms, accounts, newsletters or a consent-management platform.

Important demo limitation. Do not activate Google Ads, Google AdSense, Google Analytics, remarketing, measurement tags or other advertising technology on this prototype until the responsible publisher replaces the fictional contact information, lists the tools and partners actually used, and implements consent controls where required.

1. Controller and contact

For the purposes of this prototype, the stated publisher is Faseetr Review Demonstration Studio and the listed contact is [email protected]. These are fictional, non-working details. A live version must state the responsible organization, a genuine privacy contact route and the applicable jurisdiction.

2. Information that a live version may process

Depending on the tools that a publisher activates, a live version may receive or cause third parties to collect device and browser information, IP address, approximate location inferred from IP, page URLs, referrer information, interactions with content or ads, cookie identifiers, local-storage identifiers, consent choices and security-related information. The publisher must describe its actual collection and must not claim to collect less than its deployed technology collects.

3. Purposes and lawful basis

Potential purposes include delivering pages, securing the site, detecting fraud, remembering privacy choices, measuring audience activity, serving ads, limiting ad frequency, measuring campaign performance and, only where permitted and consented to, personalizing advertising. A live publisher must use an appropriate lawful basis for each purpose and respect user choices.

4. Advertising, Google technologies and third parties

If a live version uses Google advertising products, Google and selected advertising technology providers may process personal data and use cookies or similar technologies for ad delivery, measurement, frequency capping and, subject to user settings and consent, personalization. The publisher must clearly identify each party that may collect, receive or use personal data as a consequence of its Google implementation, give users accessible information about that processing, and keep the provider list accurate. The site should link users to Google’s privacy and advertising controls and to the privacy information of every selected provider.

5. Cookies and similar technologies

Cookies, pixels, SDK-like scripts, local storage and device identifiers can support essential functions, fraud prevention, preference storage, analytics and advertising. This prototype does not intentionally set advertising or analytics cookies. A live version must publish the cookies and purposes it actually uses, provide a working cookie-preferences control and honour opt-outs or consent withdrawals.

6. Consent for EEA, UK and Swiss users

For users in the EEA, United Kingdom and Switzerland, a privacy page alone is not a consent mechanism. Where required, the live publisher must obtain legally valid consent for cookies or local storage and for the collection, sharing and use of personal data for ad personalization; preserve consent records; give clear withdrawal instructions; and use a Google-certified CMP integrated with the IAB TCF when serving personalized ads in the applicable regions. If valid consent is not available, the publisher should configure only the advertising option permitted by the relevant policy and law, such as non-personalized or limited ads where supported.

7. Choices and controls

A live site must provide a persistent way to reopen privacy choices. Users can also manage browser cookies, device identifiers and Google advertising preferences using the relevant browser, device and Google controls. The future live publisher should document the exact links and settings supported by its implementation. No e-mail in this test build is monitored.

8. Sharing, transfers, retention and security

Information may be processed by hosting, security, measurement, advertising and consent providers according to their roles and policies. A live publisher must identify those providers, explain applicable international transfers, retain information no longer than reasonably necessary for stated purposes, and apply proportionate security safeguards. This prototype makes no operational retention commitments because it does not operate the listed services.

9. Rights and complaints

Depending on location and applicable law, users may have rights to request access, correction, deletion, portability, restriction, objection or withdrawal of consent. A live publisher must give a usable route for receiving and responding to these requests and identify any relevant privacy regulator. This prototype cannot process a request because its contacts are fictional.

10. Children, links and updates

The future live site should not knowingly collect personal information from children in violation of applicable law, should review the privacy practices of linked sites independently, and should publish a dated notice when material changes take effect. This template may be updated as Google policies, platform requirements and laws change.

11. Reference materials

For implementation guidance, a live publisher should review Google’s EU User Consent Policy, Google’s publisher consent-management requirements, Google’s Publisher Policies, and Google’s cookie information. These links are provided for reference, not as legal advice.