LEGAL / EFFECTIVE 28 OCTOBER 2026

Privacy notice

How Podnivo handles developer account, workspace and API operations data.

Data we process

We process the account name, email, password hash, workspace profile and choices submitted during registration. For security, console sessions retain a bounded user-agent string and client address. API request logs retain the workspace, key identifier, method, endpoint group, status and duration—not raw query parameters or a full request path.

Email verification

Resend processes the destination email address and transactional message data to deliver account verification emails. Verification tokens are single-use; Podnivo stores their hash and temporarily keeps an encrypted delivery copy until the message is sent.

Listener data

Listener subscriptions, history and playback progress belong to the customer workspace that submits them. Workspaces can export or delete a listener through the API. Podnivo does not combine listener records across tenants.

Payments

Paddle acts as merchant of record for paid subscriptions and processes checkout, tax, payment method, invoice and subscription information. Podnivo stores Paddle customer, subscription, price, status and billing-period identifiers needed to provision the plan; it does not store full card details.

Purpose and control

We use this data to authenticate accounts, operate quotas, provide billing, diagnose API health and prevent abuse. Product email is optional. To request access, correction, export or deletion of developer account data, contact [email protected].

Processors and transfers

The final launch notice must identify the legal entity, hosting providers, Resend, Paddle, retention periods and any applicable transfer safeguards. Counsel should review this notice against the deployed infrastructure.