Privacy Policy

Privacy Policy

This policy summarizes the current FlowRising handling of analytics, guest continuity, saved recommendations, and affiliate interactions.

Policy intent

FlowRising should stay calm, trusted, clear, and respectful even when recommendations are optional.

Current product behavior

FlowRising stores certain experience data locally in the browser, including My Flow List items, Complete My Room completion state, Flow Scan history snapshots, and Crystal Tree ritual progress so the product can feel continuous between visits.

FlowRising also issues an anonymous guest identity for complimentary Flow Scan access, continuity, and pacing. That identity may use a browser-visible local guest record plus a signed HTTP-only guest session cookie.

FlowRising also sends first-party product analytics events to its own analytics service so the team can understand traffic, feature usage, content performance, affiliate interaction, product health, and operational issues.

Analytics and identifiers

Analytics events may include an anonymous guest identifier, session identifier, approximate device context, page path, referrer, event metadata, and approximate geographic fields when available.

FlowRising is designed to avoid storing unnecessary personal information in analytics payloads and to hash or abstract sensitive identifiers where appropriate.

For guest continuity and anti-abuse controls, FlowRising may also store hashed network, browser, or device signals such as hashed IP, hashed user-agent, and hashed browser fingerprint values rather than storing raw values when it can avoid doing so.

Guest limits and entitlement controls

Complimentary guest features such as Flow Scan may use server-side usage counters to enforce daily limits, protect service quality, and control AI costs.

These counters are tied to anonymous guest identity and related anti-abuse signals, not to a personal profile unless a user later creates or connects an account.

What is not placed in affiliate links or analytics payloads

FlowRising does not place names, birthdays, addresses, email addresses, relationship details, Flow Score values, room photographs, or other sensitive personal report data into affiliate-link parameters.

Analytics payloads should describe product behavior and engagement, not expose private room imagery or sensitive personal reading data.

Google services and future account features

FlowRising may also integrate services such as Google Analytics 4 and Google Search Console for marketing and SEO reporting, while retaining first-party analytics as the primary product-intelligence layer.

As guest accounts, saved progress, and admin systems expand, this policy should continue evolving to reflect the live production architecture accurately.

Related pages

Explore the supporting policy pages.