Privacy at Influxus · version mvp-2026-08-19
Clear guidance should include clear data practices.
Influxus collects the information needed to operate accounts, publish creator recommendations, and understand whether the Shopper Journey is useful. This Shopper Journey implementation does not use cross-site advertising trackers.
Shopper Journey analytics
When you view a Creator Passport, product, Recommendation Receipt, or routine, save or compare an item, or follow a Buy link, Influxus records that action with the relevant creator and product context. This helps creators and Influxus understand which guidance supports better decisions.
A random first-party journey identifier is stored in an HttpOnly cookie for approximately 30 minutes. It connects actions within a short visit. It is not a fingerprint and is not used to follow you across other websites.
What we deliberately avoid
Shopper Journey events do not store raw IP addresses, full browser user-agent strings, merchant account credentials, or payment-card information. Buy links take you to an external merchant, whose own privacy terms then apply.
Accounts and choices
Signed-in actions may also be associated with your Influxus account so saved products and comparisons work across devices. You may sign out to prevent new Shopper Journey events from being associated with that account in your browser.
Signed-in members can submit an account deletion request from the Account page. The request enters a review queue so identity, scope, and audit requirements can be checked before destructive work.
Retention
Influxus has internal, configurable MVP retention periods for decision events, feedback, referral relationships, and deletion request audits. Those operational defaults are pending legal review before automated deletion or anonymization is enabled, so this notice does not promise a final retention period yet.