We collect and store the initial registration request (including your website's IP address and UA string, often containing your WordPress version) – in return your site receives (and stores in wp_options) a unique account key and account key secret, which then allow your site to query other endpoints of the Pageviews API.
We collect and store for a limited time (aggregations for up to 7 days, raw logs for up to 52 weeks) all request logs to the pv.pjtsu.com and pageviews.io domains, including referrer headers and IP addresses. These are used to track and debug the service usage, find patterns of abuse, as well as scale the service.
We collect and store the counter keys provided by the API client (usually post IDs, but in custom implementations could also be more meaningful strings, such as tag-archive or search), as well as the numeric counter values (given with the v1/set endpoint).
Pageviews Sync is a service that synchronizes existing data from third-party services, such as Google Analytics, with your Pageviews counters. For this service to work, we require that you allow temporary, read-only access to your site data (post IDs, permalinks and Pageviews API keys), as well as your third-party service data (Google Analytics Reportig API, etc.)
Some premium features related to the Pageviews plugin (such as Pageviews Sync or Pageviews Premium/Extras) require a payment to be made. We use Stripe to securely process all our payments. We never store credit card details on our servers.
If you have any more specific questions, or wish your data to be purged from our logs and database immediately, please feel free to reach out to us via e-mail (firstname.lastname@example.org) and provide your account key and account secret strings (wp option get pageviews_config).