Privacy

Information handled by the site

• Free chapter requests. When you request chapter 1, the app stores the email address you submit in its waitlist records. It sends that address a chapter-link email through Polsia’s email service. The signup is also sent to Polsia’s submissions service; if that does not record it, the app may notify the configured company inbox.
• Chapter access. When you sign up, the app checks your email against the waitlist record before granting immediate browser access. The confirmation email contains a single-use claim link that expires after 24 hours. The app stores its token as a hash; when claimed, it creates a separate chapter-access record and gives that browser an HTTP-only, Secure, SameSite=Lax access cookie that can last for up to one year.
• 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.
• 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 or free chapter signup 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 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.

The app does not document a waitlist deletion schedule or an account-closure and data deletion process. It also has no separate marketing-consent control or unsubscribe flow on the free-chapter form. Whether signup addresses receive later promotional messages needs owner confirmation.