Ternwork / Privacy
Privacy
This notice describes data flows visible in the current Ternwork app. Several details needed for a final launch notice are not established by the app and are listed below for the owner to confirm.
Last updated: owner confirmation required
Information handled by the site
- Waitlist signups. If you submit an email through the waitlist, the app stores it in its waitlist records. The signup is sent to Polsia’s submissions service; if that does not record it, the app may notify the configured company inbox.
- Chapter access. To read Chapter 1, you need a reader account. The app stores a separate entitlement against your account when access is first granted, with no expiry configured. The chapter is returned only to a signed-in account with that entitlement. This access is separate from the full-guide purchase entitlement for Chapters 2–13.
- Reader accounts. Account registration asks for your name, email, and password and sends an email-verification message. The account service stores account and session records. Session records have optional fields for an IP address and user agent.
- First-party funnel measurement. The browser keeps a random, app-generated identifier and the initial utm_source value, when present, in session storage for the current tab. For its first eligible public-site visit, the app records that identifier with the visit time, a source label (a normalized utm_source when present, otherwise an external referrer hostname, otherwise “Direct / no referrer”), and a coarse device category inferred from the request’s user agent. This funnel record does not store the raw user agent, IP address, full referrer URL, or other UTM values. When signup is opened to return to Chapter 1, the app records a signup start; it records a completion only after reader account creation succeeds. These pseudonymous events support source-and-device cohort conversion and abandonment reporting. An incomplete start is classified as abandoned after 24 hours; newer starts remain in progress.
- Messages to Ternwork. The site’s contact links open an email to ternwork@polsia.app. The site has no contact form; a message sent this way is handled by your email provider and the recipient’s email service.
Full-guide access
The site advertises the full digital guide for €9.99 one-off, with online access to all chapters including updates. The configured one-time hosted checkout amount is $11.34 USD. Visitors can start checkout from the pricing page.
When a signed-in, verified customer starts checkout, the app sends the fixed USD amount and account email to Polsia’s hosted checkout flow. Card entry takes place on that hosted page. After a successful return, the app verifies the buyer-paid USD total, Full guide product name, and purchaser email before saving the checkout session ID, account ID, USD amount in cents, currency, product name, and verification time. It then creates an account-bound entitlement. Paid chapters remain unavailable until that verification and save succeed.
Optional visitor analytics
A deployment can enable a Polsia page-view beacon by supplying its analytics configuration. When enabled, the browser stores a random visitor identifier in local storage and requests a pixel from the configured Polsia API host with the site slug and that identifier. The app code does not establish whether this is enabled in production, what further information the service collects, or how long any analytics data is kept.
Ternwork also uses Meta Pixel ID 1657142709108013. It sends PageView events on page loads and client-side navigation, Lead events after a new reader account succeeds, and Purchase events after a Stripe payment is verified and guide access is confirmed. Purchase includes the verified payment amount and currency. This notice does not specify a legal basis or retention period for these events.
Uses, providers, and retention
The visible app flows use the submitted details to deliver the requested chapter, operate reader accounts and gated guide access, and route signup notifications and email inquiries. The app also uses pseudonymous first-party funnel events for internal source-and-device signup reporting. The app integrates with Polsia email and submissions services. The owner has not supplied the applicable legal purposes or bases, a complete processor and subprocessor list, international-transfer details, or data-retention periods. No retention period is set here for the anonymous funnel records; the owner still needs to set it.
The app does not document a waitlist deletion schedule or an account-closure and data deletion process. Account creation has no separate marketing-consent control or unsubscribe flow. Whether account addresses receive later promotional messages needs owner confirmation.
Details to confirm before launch
The owner must add the legal operator’s name, address, and country; confirm the designated privacy and data-request contact; set out purposes and legal bases, service providers and transfers, analytics status and retention, signup-email use, and the retention, deletion, and account-closure process. The visible address ternwork@polsia.app is an existing inquiry destination, but the app does not establish that it is the designated privacy contact. Confirm that before treating it as such.