Last updated: 31 October 2026
Easy Podcast Pro (“we”, “us” and “our”) operates easypodcastpro.com and provides podcast-player products for WordPress and Wix. The individual operating the business is identified in section 20. Contact us about this policy at contact@easypodcastpro.com.
We determine the purposes and means of processing for our own website accounts, customer entitlements, support and business records and act as the controller for that processing. This does not make us the controller for every activity performed by an independently operated WordPress or Wix site, payment provider or podcast host. The product-specific sections below explain those distinctions.
This policy distinguishes our website and WordPress services from our Wix application. Part A applies to our website and WordPress product, account, purchase, licensing and support services. Part B applies to Podcast Player installed on a Wix site. Part C applies to both, where relevant.
Using the Wix app does not require an Easy Podcast Pro website account or a WordPress product purchase. A Wix site’s owner is responsible for the content they publish and the privacy information they provide to their own visitors.
Part A: Website and WordPress products and services
1. Website enquiries and support
When you contact us through a form or email, we use the information you provide, such as your name, email address, website address, purchase details and the contents of your request, to respond and provide support. Please do not include passwords, full payment-card details or access tokens in support messages.
2. Comments, profiles and website uploads
If comments are available and you post one, the website collects the submitted comment information and technical details, including your IP address and browser information, for moderation and spam prevention. Comments may be reviewed before publication. An email-address hash may be sent to Gravatar to check whether you have a profile image. Approved comments and any associated public profile image can be visible to other visitors. See Automattic’s privacy notice.
If you create an account on our website, we store your username and email address to operate the account, send password-setting or password-reset messages and administer access to services. Any name, address or other optional profile information you supply is also stored. You can review and change available profile fields through your account; changing a username may require assistance.
If you upload images or other media to our website where that feature is available, remove location and other confidential metadata before uploading. Published files and metadata may be accessible to visitors, including through website interfaces. This website-upload provision does not describe a feature of the Wix app, which does not offer media uploading.
3. Website cookies
Our WordPress website uses cookies for functions such as account sessions and login preferences. Where comment cookies are offered, choosing to save your details can retain your name, email address and website address for approximately one year, so you do not need to enter them again for another comment.
A temporary login-page cookie may check whether your browser accepts cookies and is removed when the browser closes. Standard login cookies generally last two days, screen-preference cookies approximately one year, and a selected “Remember Me” login approximately two weeks. Logging out removes the login cookies. Actual duration can also depend on browser settings and security controls.
Embedded media, checkout providers and other external services may use their own cookies. We use consent for optional cookies and similar technologies where required by law and respect the consent choices you make.
You can manage or remove cookies through your browser settings. Blocking cookies may prevent login, checkout or other website functions from working correctly.
Website analytics and custom website features
We use Koko Analytics on our WordPress website to understand aggregate visits, pageviews, popular pages and referring websites. It runs on our website rather than sending analytics to a separate analytics service. Its developer describes the plugin as storing aggregated counts rather than personal visitor profiles. Hosting servers still receive normal connection information when handling requests, as explained in section 7. See Koko Analytics.
Koko Analytics supports Cookie, Cookieless and None tracking methods. If Cookie mode is enabled, its _koko_analytics_pages_viewed cookie expires at midnight in the website’s time zone, in less than 24 hours. Cookieless and None modes do not use that cookie. A cookieless mode is not, by itself, a declaration that every privacy or device-access rule is inapplicable. See the developer’s tracking-method explanation.
Our other website features are custom coded rather than using a separate marketing-email, form or anti-spam service identified for those purposes. This does not mean that information voluntarily submitted to an account, contact form or email is never processed: section 1 describes support requests and section 7 describes hosting. Freemius and PayPal may send their own transaction and service messages under their respective arrangements.
4. Current WordPress purchases: Freemius
We use Freemius for current WordPress product purchases and related payment, subscription and licence services. Depending on the transaction, information processed can include your name, email address, billing location and tax information, the product and plan purchased, transaction status and licence or subscription details. This information is used to fulfil purchases, administer entitlements, handle billing and tax requirements, and respond to support requests.
Payment credentials are handled through the checkout provider and its payment-processing arrangements. Do not send us full card numbers or payment passwords. Freemius describes its own handling of information and the providers it uses in its privacy policy.
Freemius provides the checkout as merchant of record, including payment, subscription and applicable transaction-tax administration. That commercial role does not mean it is an independent controller for every item of customer data: its Vendor Terms and Data Processing Addendum also describe processing vendor-provided personal data on the vendor’s behalf. Our customer-support and entitlement processing, Freemius’s own service processing and the responsibilities assigned in the applicable agreements should be distinguished.
Where a WordPress product uses a Freemius connection for licence activation or updates, the connection may also process the installation and licence information needed for those services, such as a site URL, product version, activation status and account details. Any optional usage-data collection is subject to the notices and choices presented for that integration; purchasing a product does not by itself authorize unrelated tracking.
We may send purchase confirmations, renewal reminders, licence-related messages and relevant service or security communications. We do not treat a support enquiry or app installation as permission to send unrelated promotional messages.
5. Legacy WordPress orders: Easy Digital Downloads and PayPal
We retain the Easy Digital Downloads system for earlier purchases, associated account and licence records, and occasional eligible legacy renewals. It is not our main checkout for new WordPress purchases. Legacy records may include customer names, email addresses, billing information, order and transaction references, licence keys and renewal history.
Where a legacy transaction uses PayPal, PayPal processes the payment under its privacy statement. The records maintained through Easy Digital Downloads on our website remain subject to the website-storage and retention provisions in this policy. Moving current purchases to Freemius does not automatically erase earlier purchase records.
6. WordPress licence activation and updates
When a WordPress product licence is activated, checked, renewed or deactivated, the relevant licensing service may process the licence key, site address, account or order reference, activation status and technical connection details, including an IP address. We use this information to administer the purchased support and update service, prevent misuse of that service and diagnose licensing problems.
The main WordPress plugin’s player functionality is separate from these purchase and licensing services. Information handled for a paid update or activation service should not be confused with a claim that the player itself creates listener accounts or keeps an Easy Podcast Pro listening-history database.
How the WordPress player handles podcast data
On a site that installs Podcast Player, the WordPress server fetches the selected RSS feed and stores podcast metadata and episode information in that site’s WordPress storage for playback, browsing and later feed updates. Those records are controlled by that site’s operator; they are not automatically copied into our customer-account database. The podcast feed host receives the server’s request. Listener browsers request audio and remote artwork from the relevant media or artwork host, which can receive IP addresses and other normal connection information. A site’s configuration, imported artwork and other plugins can change which host serves an asset.
In the inspected WordPress implementation, Pro playback resume, when enabled by the site owner, uses a first-party ppCookie containing the episode/source reference and playback position. It is set for seven days, updated during playback and removed when the episode ends. Pro listening statistics are a separate optional feature controlled by the site’s settings. These are WordPress Pro features, not descriptions of the free Wix app. The site operator is responsible for its enabled features, notices and any required visitor consent. The website account/comment cookies in section 3 are separate from this player cookie.
Paid licensing, update checks and any opted-in Freemius connection are described above. We do not describe the WordPress software as making no external requests: RSS, media, licensing and any enabled integrations have their own request flows. Contact the operator of the WordPress site hosting a player about that site’s stored podcast data, optional statistics or visitor-cookie choices.
7. Website hosting, logs and backups
Our website is hosted with Hostinger, and we use Hostinger’s automatic backups. Hosting and backups can include the website database, account and legacy purchase records, files and operational logs. Servers may process normal request information, such as IP addresses, request times, browser details and error information, to deliver and protect the website. See Hostinger’s privacy policy.
The Hostinger arrangements described here concern our website and its records. They do not mean that the Wix app’s podcast archive is hosted in the same website database.
8. Embedded content and external links
Website pages may contain embedded videos, images or other third-party content. Loading that content can send information to the third-party service, which may use cookies or associate the request with an account you hold there. Following an external link also takes you to a service with its own practices.
Examples include Google/YouTube, X and WordPress.org. Their policies apply to their own services.
9. Website and WordPress record retention
Comments and related moderation information may be retained indefinitely to support discussion and moderation. Website account information is retained while the account is maintained and where reasonably needed for account administration, security or legal obligations. You can request account closure or deletion of personal information, subject to information we must retain.
We retain purchase, licence and renewal records, including legacy records, while needed to establish customer entitlements and for the accounting, tax, audit and limitation periods applicable to the transaction. An unresolved dispute or legal preservation obligation can require longer retention. We assess support correspondence by whether a request remains open, whether its history is needed for an existing customer relationship and any applicable legal requirement. Security logs are retained for investigating operational incidents and protecting the service, rather than as a permanent customer activity history. Removing information from an active website does not necessarily remove every backup immediately; backup copies remain subject to the hosting provider’s backup cycle and applicable retention requirements.
Part B: Podcast Player for Wix
10. Information used by the app
The app uses Wix’s site ID and app instance ID to identify the site and its app installation, the RSS feed selected by the site owner and the owner’s settings to provide the player. For a duplicated site, Wix can also supply the origin instance ID linking it to the original installation. The current app code does not request an owner’s email address to connect or play a feed. Information an owner sends us in a support message is separate.
The app stores public podcast metadata, episode information and notes, feed-check status and refresh information in app-owned collections on the Wix site. Podcast material can contain names, biographies and other information supplied by its publisher.
Presentation choices are stored as widget settings. Feed-check preferences are stored for the app installation. Site owners should connect only podcast feeds and artwork they are entitled to publish, and should not put confidential credentials into URLs intended for use in a public player.
Listeners do not need to create an Easy Podcast Pro account to listen. The current app does not implement its own listener-account system, advertising-tracking system or listening-statistics feature. This does not mean that Wix, the site owner, network providers or podcast hosts process no information about a request.
11. Wix, feed hosts and media providers
The app runs on Wix infrastructure and uses Wix services for authentication, app hosting and app data. Wix handles information according to its own privacy policy and applicable platform terms. Platform and operational SDK services may process diagnostic, security, request and performance information to operate the app and platform.
To build and update the podcast archive, the app requests the selected RSS feed from its host. During source checks, it uses Cloudflare’s DNS service to resolve the feed host name. The DNS lookup concerns the host name; it is not a feature for recording individual episode plays. See Cloudflare’s privacy policy.
Audio and artwork are requested from the podcast’s media hosts or the external artwork URL chosen by the site owner. These requests can disclose a listener’s IP address, browser information and other normal connection information to the receiving host. Following, sharing or downloading links may involve another service and its own privacy practices.
The free Wix app does not use our WordPress Freemius checkout or legacy Easy Digital Downloads/PayPal licensing system to authorize playback. If a Wix app user separately buys a WordPress product, that transaction falls under Part A.
12. Copies of Wix sites
When a site is duplicated, the app can restore the saved podcast archive and feed-check preferences to the new installation using the original installation identified by Wix. Widget settings may also be copied by Wix. The destination then has its own installation data; changes to its podcast settings do not update the source installation through this restoration process.
13. Retention, uninstallation and deletion requests
The app retains its current podcast archive and refresh state to serve the player. Earlier archive revisions may remain temporarily to support an episode list already open in a browser. Cleanup occurs during later app activity, so removal of an older revision is not guaranteed at a fixed elapsed time.
Removing a widget does not by itself establish deletion of installation data. Uninstalling the app can make its collections inaccessible while Wix retains data that can be restored on reinstallation. Uninstalling and reinstalling should therefore not be treated as a method of permanently erasing podcast data. We do not set a guaranteed retention period for Wix’s retained platform copies.
For an access or deletion request, email contact@easypodcastpro.com, identify the Wix site and describe the information involved. We may request proportionate evidence of your authority over the site before acting. We will assess the request under applicable law, address data within our control and explain when Wix or another provider must handle platform-controlled data. We do not promise an immediate purge of every platform log or backup, or offer a self-service erasure control that the app does not contain.
14. The Wix site owner’s responsibilities
A site’s owner chooses the podcast and any other content, integrations and consent tools on that site. The owner is responsible for providing appropriate privacy information to visitors and obtaining any permissions or consents their use requires. That site’s privacy notice and the relevant hosts’ policies should be read alongside this policy.
For personal information processed solely to provide the owner’s configured player on their instructions, we act on the owner’s behalf to the extent applicable data-protection law treats that activity as processing. For our own support correspondence, security administration and legal records, we determine the purposes and act as controller. Wix’s separate roles and obligations are governed by its applicable platform agreements, including its User Data Processing Addendum. A privacy notice does not replace any data-processing agreement that applicable law requires.
Part C: Practices applying across these services
15. Purposes and legal grounds
Where the GDPR or UK GDPR applies to processing for which we act as controller, the following describes the purposes and relevant grounds:
| Activity | Legal ground and purpose |
|---|---|
| Account administration, purchased entitlements, licence services and support needed to perform an agreement with you | Performance of that agreement or requested pre-contract steps. |
| General enquiries and support from someone who is not a contracting customer | Legitimate interests in answering requests and assisting users, subject to their rights. |
| Accounting, tax records and legally required disclosures | Compliance with the applicable legal obligation. |
| Security, fraud prevention, service diagnostics, moderation and proportionate record keeping | Legitimate interests in operating reliable services, protecting users and addressing misuse or disputes, subject to their rights. |
| Optional cookies, device-access features or communications for which consent is required | Consent, obtained before the relevant activity where required. An optional analytics or playback cookie is not treated as necessary merely because it is useful. |
Where we process site-owner-controlled data solely on their instructions, the owner determines the appropriate legal ground; the controller grounds above are not a substitute for the owner’s obligations. You can withdraw consent for an activity that depends on consent without affecting earlier lawful processing.
16. Disclosure and international processing
We do not sell or rent your personal information. We disclose information as needed to the providers described in the relevant part of this policy, personnel and contractors who need it for their work, professional advisers where necessary, and authorities where disclosure is legally required. Access by personnel and contractors is subject to appropriate confidentiality obligations.
Our providers or personnel may process information in countries other than your own. The applicable provider arrangements and legally required safeguards govern those transfers. Merely visiting the website is not treated as a substitute for a specific consent or safeguard required by law.
For example, Freemius’s published policy describes adequacy decisions, EU Standard Contractual Clauses and, where relevant, the UK International Data Transfer Agreement or UK Addendum as potential transfer mechanisms. Wix’s User Data Processing Addendum describes safeguards for relevant site-visitor data. These are provider-specific arrangements; we do not claim that every provider or transfer is covered by the EU–US Data Privacy Framework or by one identical contract. Where a restricted transfer is our responsibility, we must use a lawful mechanism applicable to that transfer. Contact contact@easypodcastpro.com for information about applicable safeguards and how to obtain a copy, subject to necessary redactions.
17. Security and incident communications
We use reasonable technical and organizational measures intended to protect information against unauthorized access, loss or misuse. Security practices differ between the website, payment providers and Wix-managed services. No internet service can guarantee absolute security.
For our website and WordPress customer services, we will notify affected customers by email no later than 48 hours after becoming aware that customer data has been lost, stolen or potentially compromised. Applicable shorter legal deadlines take priority. We also notify the relevant authorities where required. For Wix-related incidents, we will make notifications required by applicable law and the relevant Wix agreements, and provide affected users information as required.
18. Your rights and choices
Depending on the law that applies, you may have rights to request access, correction, erasure, restriction or a copy of personal information, to object to certain processing, to withdraw consent, or to complain to the relevant data-protection authority. These rights can be subject to legal conditions and exceptions.
You can manage available website profile fields, browser cookies and any integration consent choices presented to you. For help exercising a right, contact contact@easypodcastpro.com. We may need to verify the requester’s identity or authority. Some records may need to be retained for accounting, legal, security or dispute-related purposes, or handled by the relevant payment or platform provider.
Request response times
We respond without undue delay and within the deadline set by the law applicable to your request. For GDPR/UK GDPR rights requests, this is generally one calendar month, with an extension of up to two further months where legally permitted; we will explain a necessary extension within the initial period. Where California’s CCPA applies, access, correction and deletion requests generally have a 45-calendar-day response period, with an additional 45 days where permitted and notified. Some requests, including applicable opt-outs, require faster action. Any identity checks, clarification or extension must follow the relevant law; they do not automatically restart every deadline. If we cannot comply, we explain the reason and available complaint or review route where required.
US state rights, where applicable
If an applicable US state privacy law covers our processing, you may have rights to know/access the categories and specific information held about you, correct or delete it, obtain a portable copy, and opt out of a sale, sharing for cross-context behavioural advertising or targeted advertising as defined by that law. Additional rights can include limits on certain sensitive-data uses and an appeal of a denied request. We do not discriminate against you for exercising a legally protected privacy right. An authorized agent may contact us, subject to proportionate authorization and identity checks.
The categories described in Parts A and B include identifiers/contact and account details, commercial/purchase and licence records, technical connection information, support or comment content, and the site/installation and public podcast information described there. The same sections identify their sources, purposes and recipients; section 9 and section 13 describe retention criteria. This is not a claim that we collect every category from every visitor.
We do not sell or rent personal information. A browser’s Global Privacy Control signal concerns applicable sale/sharing opt-outs; it is different from a general cookie preference or a universal request to erase records. Where the law requires us to act on a recognized opt-out signal, we must apply it to the covered processing. You can also contact us to exercise an applicable opt-out. A site owner independently operating a player is responsible for its own advertising, analytics and consent configuration.
Children and podcast audiences
The player does not require a listener account or submission of a child’s name, email address or date of birth to play audio. A public podcast page can have an audience that includes children; its owner is responsible for assessing the audience and meeting any child-specific notice, consent and configuration requirements. The absence of a listener-account feature does not mean that media hosts or the platform receive no technical request information.
If you believe a child has provided us with personal information that we should not hold, contact contact@easypodcastpro.com. We will assess the circumstances, applicable age/consent rules and appropriate steps, including deletion where required. We do not represent a single age of 13 or 16 as the legal threshold for every service and country.
19. Changes to this policy
We may update this policy as services or requirements change. We will show the revised date here and provide notice of material changes through this page and, where required, through an appropriate service notice or direct communication. Any additional notice or consent required by law will be respected.
20. Contact
For website, WordPress or Wix app privacy questions and requests, contact Surendra Mohnot, operating as Easy Podcast Pro, at contact@easypodcastpro.com. Please state which product or service your question concerns.