Privacy Policy

01Scope and contact

This policy describes information handled by the ytcpm.online website and its calculation API. Contact [email protected] with privacy questions or requests. Do not send passwords, access tokens or private YouTube reports.

02Browser-based calculators

The earnings estimator and dedicated CPM/RPM calculators perform calculations in your browser. Typing calculator inputs does not submit them to the calculation API. No YouTube sign-in or connected channel access is provided by these tools.

03Channel Auditor requests

When someone runs a public channel audit, the submitted channel URL or @handle is sent to the YouTube Data API by our server so the public channel, video and playlist data can be retrieved. The submitted identifier is used for that request and the resulting public figures are shown in the browser. No YouTube account is connected, no credential is requested and no private or owner-only channel data is accessible through this feature.

Audit responses are not written to the calculation database. Short-lived in-memory caching of public API responses and rate-limit counters are used to protect availability; those entries are not linked to an account. If optional paid features are enabled later, a signed, HttpOnly cookie records the purchased access so the service can recognise it; it does not contain YouTube credentials or channel access tokens.

04Direct API requests

When someone calls POST /api/calculate directly, the service can store the validated calculation inputs, results and a timestamp in its configured database. These fields include views, niche, country, content type, season and ad-impression rate. Calculation rows do not include an IP address, cookie identifier or user-agent field.

The API Usage Monitor displays usage summaries, not private YouTube analytics. Avoid submitting personal or confidential information. Calculation records are not associated with an account, but that does not mean every item of technical information processed by the service is anonymous.

05Security and infrastructure information

The API uses short-lived in-memory, IP-based request counters for rate limiting. Expired counters are reset or cleaned up during subsequent requests; they are not written to the calculation database.

Hosting, reverse-proxy or network providers may process connection information such as IP addresses, request paths and timestamps to deliver and protect the website. Their operational logs are separate from calculation records. Actual infrastructure retention depends on the deployment configuration; this policy does not promise that infrastructure logs never exist.

06Cookies and third-party resources

The current application does not set advertising or analytics cookies and does not include third-party analytics scripts or social tracking pixels. Fonts and flag images are self-hosted. Our separate Cookie Policy explains the distinction between browser storage, cookies and server-side records.

Following an external reference takes you to another website, whose privacy practices apply there.

07Retention and protection

Stored API calculation records support usage reporting. The application does not currently implement automatic deletion on a fixed retention schedule. Do not assume that an API submission will be deleted after a specific number of days.

We aim to limit information to what is needed to operate the service. No internet service can guarantee absolute security. Do not enter secrets or sensitive personal information into these tools.

08Your privacy requests

Depending on applicable law and the information involved, you may have rights to access, correction, deletion, restriction or objection. Contact [email protected] with enough context to describe the request, without sending unnecessary personal information. We may need proportionate verification before acting.

There is no user-account record or YouTube account connection in the current app. That does not remove rights that may apply to technical information or correspondence. Availability of a particular right depends on applicable law.

09Privacy rights for international visitors

People in the European Economic Area or United Kingdom may have rights under applicable data-protection laws, including the GDPR or UK GDPR where applicable. These can include access, correction, erasure, objection and the ability to raise concerns with a supervisory authority. Which obligations apply depends on the processing and the operator’s circumstances; these references are not a statement that every provision applies to this website.

California residents and people in other US states may have rights under applicable state privacy laws, such as the CCPA as amended by the CPRA in California, where the relevant scope and thresholds are met. Visitors in India may have protections under India’s Digital Personal Data Protection framework as provisions take effect and apply. We do not claim that an identical request process, deadline or remedy applies everywhere.

Tell us your country or region only if it helps explain your request. Do not send government identification in an initial email. If verification is needed, we should seek only proportionate information, not account passwords or tokens.

10International access and processing

Visitors can access the website from different countries. Hosting, network routing and support correspondence may involve systems outside the visitor’s home country. The application code alone does not establish provider locations, transfer mechanisms or contractual safeguards.

We do not claim that all information remains in the EU, UK, India or any other specific region. Where applicable law requires transfer safeguards or notices, the operator must assess actual provider arrangements. Contact us if location or transfer information is important to your use.

11Children and sensitive information

These tools do not need a child’s identity, health details, payment information or other sensitive personal data. Please do not submit that information. If you believe a child has provided personal information, contact us with the relevant page or interaction so the concern can be investigated without sending additional sensitive details.

12Policy changes

Changes to these practices will be reflected in this policy and its update date. New tracking or account features require a fresh review of disclosures and any applicable consent requirements before deployment.