01
Account and access data
LinePrism uses account, email, access, preference, and billing state to provide sign-in, paid access, private signal surfaces, support, and billing management.
Privacy
This launch-ready draft describes the minimum data posture, authentication, billing, analytics, and cookie handling expected for public launch.
Request accessMVP boundary
These pages describe the public website and controlled-access product direction. Live data, auth, payments, and real alert delivery stay disabled until provider and account setup is complete.
01
LinePrism uses account, email, access, preference, and billing state to provide sign-in, paid access, private signal surfaces, support, and billing management.
02
Payment details are handled by Stripe. LinePrism stores subscription and entitlement state needed to grant or revoke access, but does not store raw card details.
03
PostHog may be used for privacy-light product and funnel analytics such as page views, pricing views, request access, sign-in, checkout, billing portal, signal page, and Track Record events. GA4 should be added only if marketing measurement is deliberately enabled.
04
Germany/EU and worldwide customers require consent-friendly analytics and cookie handling. Aggressive marketing cookies, advertising pixels, or session replay should not be added without a separate owner privacy decision.
05
Public pages may show transformed signal artifacts and aggregate reviewed outputs. Raw provider feeds, full line histories, and provider secrets are not public website content.
06
Support, privacy, account, and billing questions should be routed to info@lineprism.com.
Owner approval