Last updated: July 5, 2026
PlopKit is a project operated by an individual based in Canada. This Privacy Policy explains what information we collect, how we use it, and your rights regarding that information.
By using PlopKit, whether as a site owner (publisher) or as a commenter on a site that embeds a PlopKit widget, you agree to the practices described in this policy.
This policy applies only to the hosted version of PlopKit at plopkit.com. If you run a self-hosted instance, this policy does not apply — you (the operator) are responsible for your own privacy practices and any applicable legal obligations regarding data collected through your instance.
This policy applies to two groups of people:
When you create a PlopKit account, we collect:
We do not collect or store your OAuth provider password. Authentication is handled entirely through the OAuth provider (e.g. Google).
Payment information (such as credit card details) is collected and processed directly by Stripe. PlopKit never sees or stores your payment details.
When someone posts a comment through a PlopKit widget, we collect:
We do not collect commenter email addresses, or any account information. Comments are posted anonymously unless the publisher is commenting on their own site, in which case their comment is marked with an owner badge.
We use IP addresses for rate limiting to prevent comment spam. IP addresses are held temporarily in server memory only and are never written to a database or stored on disk. They are cleared whenever the server restarts.
We do not currently use any analytics tools. If we add analytics in the future, we will update this policy to disclose the specific tool(s) used, what data they collect, and how you can opt out where applicable.
PlopKit uses a session cookie to keep publishers signed in. This cookie is set by Better Auth, our authentication library, and is strictly necessary for the platform to function. It does not track you across other websites.
The PlopKit widget does not set any cookies, but it does use browser localStorage to remember a commenter’s display name and commenter identity (a randomly generated ID used to identify comments made from the same browser and to allow commenters to delete their own comments). This data is stored locally in the commenter’s browser and is never transmitted to our servers unless they post a comment or request a deletion.
We do not use advertising cookies or third-party tracking cookies.
We use the information we collect to:
We do not sell your data. We do not use your data for advertising.
We do not sell or share your personal information with third parties for their own purposes. We do work with the following third-party services:
Publisher account data: Kept until you delete your account
Sites and widgets: Kept until you delete them or your account
Approved comments: Kept until deleted by the publisher or you delete your account
Pending comments (awaiting moderation): Automatically deleted after 30 days if not approved
Soft-deleted comments: Permanently deleted after 7 days
Session cookies: Expire when you sign out or the session expires
IP addresses (rate limiting): In-memory only, cleared on server restart, never persisted
Billing and subscription data: Subscription records are managed by Stripe and retained according to Stripe’s data retention policy. Monthly widget load counts are reset on the 1st of each month.
When a publisher deletes their account, all associated data is permanently deleted in a cascade: sites, widgets, widget settings, and all comments are removed from our database. Stripe subscription and billing records are subject to Stripe’s own retention policies.
As a Canadian user, you have rights under the Personal Information Protection and Electronic Documents Act (PIPEDA):
Publishers can delete their account directly from the Account page in the PlopKit dashboard.
PlopKit is not directed at children under the age of 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us and we will delete it.
We may update this Privacy Policy from time to time. When we do, we will update the “Last updated” date at the top of this page. We encourage you to review this policy periodically.
If you have any questions or concerns about this Privacy Policy, please contact us at: