Privacy Policy

Effective date: June 14, 2026

1. Overview

Parkstatic provides a WordPress plugin, a GitHub Action, and a hosted deploy relay that together let you build your site in your own repository and serve it from your WordPress domain. This policy explains what information we collect, how we use it, and what stays on your own infrastructure.

This policy covers parkstatic.site (our marketing and documentation website), the Parkstatic hosted service, the Parkstatic WordPress plugin, and the Parkstatic GitHub Action.

2. Two audiences

Site operators are people who install the Parkstatic plugin, purchase a license, connect a GitHub repository, and deploy your site. Most of the data described in this policy relates to site operators.

Visitors to your public website are people who browse the pages served by Parkstatic on your domain. The Parkstatic plugin does not add cookies, analytics, or other tracking to those pages. Your own privacy practices for site visitors remain your responsibility.

3. Parkstatic website

When you visit parkstatic.site, our hosting provider may record standard web server logs (such as your IP address, browser type, requested page, and timestamp) for security and reliability. We do not use advertising trackers or third-party analytics on this website.

Browsing our website does not require an account and does not transmit data from your WordPress installation.

4. Hosted deploy service

When you complete Deploy setup with an active license, your WordPress site registers with the Parkstatic hosted service so deploys can be authenticated and routed to your site. Registration happens only after you start that setup; the plugin does not contact our servers before then.

During registration, the plugin sends the information needed to identify your site and deliver future deploys—such as your site URL and credentials used to authenticate deploy requests. We store credentials in a form that cannot be used to recover the original secret, and we verify that you control the site before completing registration.

When you deploy through the GitHub Action, the service temporarily processes:

  • Your built site packaged as a zip archive
  • Basic deploy metadata, such as the Git commit, branch, and repository name associated with the build

The zip is stored in private cloud storage for a limited time while your WordPress site downloads and extracts it. After a successful deploy, the archive is deleted promptly. Failed or incomplete deploys may leave the archive in storage until the retention window expires so you can investigate.

We do not store your GitHub credentials, source code, or repository contents beyond the temporary deploy archive described above. The hosted service runs on third-party cloud infrastructure operated on our behalf.

5. WordPress plugin

The plugin stores configuration in your own WordPress database, including your GitHub repository URL and onboarding progress. Deploy credentials are handled securely and are not stored in plain text in the database.

The Site settings screen (metadata, favicon, and social previews) works entirely from your WordPress database and does not contact Parkstatic or Freemius.

Deployed static files are written to your WordPress installation on your server. Uninstalling and deleting the plugin removes Parkstatic options and those files from your WordPress installation.

Aside from registration and receiving deploy notifications described above, the plugin does not send your WordPress content, visitor data, or admin credentials to Parkstatic.

6. GitHub Action

The Parkstatic GitHub Action runs entirely inside your GitHub Actions environment. It reads your repository to install dependencies, build your project, prerender pages, and upload the resulting zip to the Parkstatic deploy endpoint.

You store your deploy secret as a GitHub repository secret. GitHub manages that secret; Parkstatic never receives access to your GitHub account or personal access tokens.

GitHub's own privacy policy governs data processed by GitHub Actions on GitHub's infrastructure.

7. Payments and licensing

License purchases and subscription management are handled by Freemius. When you buy a Parkstatic license, Freemius collects the billing and account information needed to process your payment (such as your name, email address, and payment details). That information is processed under Freemius's privacy policy, not stored by Parkstatic directly.

When you choose to purchase or activate a license from the Deploy screen, the plugin opens Freemius's connect flow in your browser. That step is explicit and optional until you decide to buy or activate a plan.

The plugin links you to our checkout page in your browser during onboarding. No personal data is transmitted from your WordPress site to complete checkout; it is a standard outbound link to the payment flow.

See also Freemius's Terms of Service.

8. How we use information

We use the information described above to:

  • Authenticate deploys and route them to the correct WordPress site
  • Verify that a site controls its registered deploy token
  • Temporarily relay build artifacts between GitHub Actions and your WordPress site
  • Operate, secure, and troubleshoot the hosted service
  • Enforce license terms through the plugin's integration with Freemius

We do not sell your personal information. We do not use deploy artifacts or site registration data for advertising or profiling.

9. Cookies and tracking

The Parkstatic WordPress plugin does not set cookies or tracking mechanisms for visitors to your public website.

parkstatic.site does not use third-party advertising or analytics cookies. Your browser may store ordinary session data required to load pages.

10. Data retention

  • Deploy archives: kept in private storage only for a limited time, usually deleted immediately after a successful WordPress download
  • Instance registration records: kept while your site remains registered; you can stop future processing by uninstalling the plugin and requesting removal of your instance record
  • WordPress plugin data: kept on your server until you delete the plugin
  • Billing records: retained by Freemius according to their policies and applicable law

11. Security

We use industry-standard measures to protect data in transit and at rest, including encrypted connections between the GitHub Action, our hosted service, and your WordPress site. Access to deploy artifacts is restricted to authenticated requests from your registered site.

No method of transmission or storage is completely secure. If you believe your deploy credentials may have been compromised, contact us or follow the guidance in the plugin documentation to rotate them.

12. International transfers

Our hosted service may process data in countries where our infrastructure providers operate. Where required by applicable law, we rely on appropriate safeguards for cross-border transfers.

13. Your rights

Depending on where you live, you may have rights to access, correct, delete, or restrict processing of personal data we hold about you, or to object to certain processing and to data portability.

To exercise these rights, contact us using the details below. You may also lodge a complaint with your local data protection authority.

14. Children

Parkstatic is a developer and site-operator product. We do not knowingly collect personal information from children under 16.

15. Changes to this policy

We may update this privacy policy from time to time. Material changes will be posted on this page with an updated effective date. Continued use of the service after changes take effect constitutes acceptance of the revised policy.

16. Contact

If you have questions about this privacy policy or want to exercise your data rights, email contact@parkstatic.com or reach out through the support channels listed on parkstatic.site.

See also our Terms of Service.