Piano Software

Overview

Piano Software (Piano.io) is a subscription management, audience development, and paywall platform used primarily by digital media publishers — news organizations, trade publications, and content businesses that monetize through subscriptions and paid content access. Piano manages the full subscription lifecycle: enforcing metered and hard paywalls, presenting subscription offers, processing payments, managing subscriber accounts, and providing audience analytics.

Piano is used by major global publishers including national newspapers and business media outlets across Europe, North America, and Asia-Pacific.

What This Script Does

Piano's script (cdn.tinypass.com/api/tinypass.min.js — Piano's infrastructure still operates under the legacy Tinypass domain) deploys as a core content access and audience layer:

Paywall enforcement: Piano evaluates each page load against the publisher's paywall configuration — whether content is gated, whether the visitor has exceeded their free article meter, and whether they have an active subscription. For metered paywalls (e.g., "5 free articles per month"), the script tracks article consumption in first-party cookies and validates against Piano's servers.

Meter tracking cookies: First-party cookies maintain the visitor's article meter count across sessions. Cookie names vary by publisher implementation but typically include Piano-prefixed identifiers. For registered users, meter state is maintained server-side against the user account.

Subscription offer delivery: When a visitor hits the paywall or a configured trigger point (specific article count, high-value content, engagement level), Piano renders a subscription offer — presenting the publisher's plans and pricing. Offers are dynamically targeted based on the visitor's engagement level and consumption history.

Subscriber authentication: Piano's script verifies active subscription status server-side and grants or restricts access to premium content. Authentication uses a Piano session token stored in a cookie or localStorage.

Audience analytics and segmentation: Piano collects content consumption data — article reads, section preferences, visit frequency, engagement depth — and builds audience segments for subscription offer targeting and publisher analytics. This profiling layer goes beyond what is strictly necessary for paywall enforcement.

Payment processing: When a visitor subscribes, Piano handles the checkout flow, collecting payment details through its integrated payment processing infrastructure (typically Stripe or similar) and creating the subscription record.

Consent & Compliance

Piano has a layered consent profile:

• Paywall enforcement (Conditional): Metering and access control — tracking article reads and subscription status — can be argued as strictly necessary for the content service. Publishers cite Article 6(1)(b) (performance of a contract) for subscribers and legitimate interests for metering anonymous visitors. This is contested in some EU member states where DPAs have ruled that metered paywalls require consent if behavioral data is collected.
• Audience analytics and offer targeting (Consent required): Piano's audience segmentation and engagement-based offer targeting goes beyond strict paywall necessity. Profiling visitor behavior to optimize conversion is an analytics and marketing function requiring consent or a legitimate interests assessment.
• GDPR / ePrivacy: Piano supports IAB TCF 2.x integration and consent-based loading of its analytics components. French CNIL and German DPA guidance on publisher consent models is relevant for EU deployments.
• CCPA: Content consumption tracking and audience segmentation data constitute personal information. Publishers should disclose Piano in their privacy policies.

Should You Block This Without Consent?

Conditional. Piano's paywall enforcement and subscription management are integral to the publisher's content model and may qualify as strictly necessary. The audience analytics and behavioral targeting components require consent. Where Piano's functional and analytics layers cannot be separated, obtain consent for the analytics components while preserving access control functionality.