YOUR ACCOUNT. YOUR SITES. THE PUBLIC RECORD.
Privacy policy.
What is private, what becomes public, and how to ask about information concerning you.
01 / PRIVACY POLICY
Who this policy covers
WP ContentLedger is a project operated by Brian Winum. This policy explains the handling of buyer account information, PayPal purchase records, connected-site information and publication-certificate data for the WP ContentLedger websites and included service. It also covers people named in submitted publication evidence, not only paying buyers.
Last updated October 24, 2026. This policy covers the public websites and certificate data, and describes the buyer account and purchase handling planned for the $299 LTD. Purchases are not open yet. Publishing this policy does not activate purchasing, buyer enrollment or transactional email delivery.
The website publisher controls what it submits from its WordPress installation. PayPal, Cloudflare, video providers and external archives have their own privacy practices, as described below. The license and terms explain the commercial offer and certificate-retention commitment.
Back to contents ↑02 / PRIVACY POLICY
Information we handle
| Category | Examples | Why it is used |
|---|---|---|
| Buyer email and account | Buyer email, internal buyer ID, verification status, entitlement, verification events and delivery attempts. | Approve access, verify email, authorize site connections, provide essential account notices and help with access problems. |
| PayPal purchase and approval | PayPal payer email if different, transaction ID, amount, currency, payment date, approval date/operator, offer, purchase status and necessary internal notes. Complimentary approvals include their reason. | Confirm payment, prevent duplicate approvals, administer the offer, handle refunds and disputes, and maintain necessary accounting records. |
| Connected sites and usage | Site origin/domain, site and installation IDs, buyer-to-site association, public verification keys, connection proofs and status, monthly certificate usage and delivery/receipt records. | Verify authorized website control, connect the correct buyer, enforce independent allowances, preserve evidence identity and troubleshoot delivery. |
| Certificate evidence | Source URL, title, publisher-reported author/publisher and dates, content fingerprints, manifest/evidence packages, signatures, revision links, check results, archive references, timestamp proofs and withdrawal records, where submitted. | Publish inspectable evidence, check integrity and authorization, connect revisions, provide receipts and support withdrawal/export. |
| Support, audit and security | Messages you send us, troubleshooting details you choose to provide, approval/suspension/reactivation reasons, operator actions and timestamps; request metadata processed by hosting/security services. | Answer requests, review restrictions, investigate incidents, prevent abuse and protect service integrity. |
We obtain these records from you, PayPal payment information, sites you authorize and their submissions, your support communications, and operation of the service. A name, URL, fingerprint or public key can still relate to an identifiable person; we do not assume that all technical evidence is anonymous.
PayPal handles payment credentials. Our buyer-approval database does not require or store your full card number, PayPal password or bank-login credentials. Do not send those details, website passwords, private signing keys or unnecessary personal information through support.
Back to contents ↑03 / PRIVACY POLICY
Private account records and public certificates
Buyer emails, PayPal transaction records, internal notes and the private list linking a buyer to their sites are not fields intended for public certificate display. Authorized administration and service processing use them privately. A certificate’s public source domain can still reveal a connection to its publisher.
Certificates are intended to be public. Their source URL, title, attributed author and publisher, reported dates, revision history and evidence-check results can be visible to readers and automated tools. Associated evidence or export artifacts may contain additional submitted metadata and proofs. Only submit content and attribution you are authorized to publish.
Public certificate pages, public evidence and source pages may be indexed, copied, linked or archived by others. Do not place private buyer emails, unpublished client information or sensitive personal data into titles, author fields, public URLs or evidence packages. The service is not intended as private document storage.
Back to contents ↑04 / PRIVACY POLICY
How we use information
We use the information needed to fulfill the purchase and service, authenticate site connections, account for the 500-new-certificates-per-site monthly allowance, deliver transactional verification/connection messages and essential notices, provide support, maintain certificate history, process withdrawal/export requests and address fraud, security and legal obligations.
We do not sell buyer email or purchase records, use them for targeted advertising, or automatically enroll a purchaser into optional marketing emails. Transactional and essential service messages are separate from any future optional marketing choice. We would explain a materially different use before introducing it and obtain consent where required.
Where applicable data-protection law requires a legal basis, account/service fulfillment is based on taking requested steps and performing the service agreement; necessary accounting and lawful requests on legal obligations; and proportionate service security, integrity and support on legitimate interests, subject to applicable rights. Optional processing that requires consent must use that consent rather than treating a purchase or this policy as blanket permission.
Back to contents ↑05 / PRIVACY POLICY
Service providers and disclosures
- PayPal: processes the payment and handles its own account, payment and dispute data. We use the purchase information needed to approve and administer your order. See PayPal’s privacy statement.
- Cloudflare: provides the existing website/certificate infrastructure and is the planned platform for the production buyer dashboard and associated database/storage services. Hosting and security processing can involve request metadata such as IP addresses, URLs, timestamps and browser/request headers. See Cloudflare’s privacy policy.
- Transactional email: the launch verification and site-code flow needs the recipient address and message/link or code processed by the configured delivery infrastructure. Buyer verification and connection-message delivery will be enabled with the buyer service at official launch.
- Archive and timestamp services: when enabled, archive submission shares the public URL for an external capture, which can expose the source page’s contents. Timestamping uses a cryptographic commitment derived from evidence rather than placing the full article on Bitcoin. Public proofs and external records may persist independently.
- Support and necessary professional services: information you send through the linked contact site is handled through that site and its communication providers. Only information necessary to answer the request or meet accounting/legal obligations should be used.
- Required or protective disclosure: relevant records may be disclosed to comply with applicable law, respond to a valid legal process, address fraud or security incidents, or protect affected people’s rights. We do not treat this as permission to publish private buyer records.
Public certificate information is also disclosed to anyone who accesses the public record. Providers may process data in the United States or other countries. We do not promise a particular data-residency region. Where applicable law requires transfer safeguards or additional disclosures, those must be established for the actual production configuration.
Back to contents ↑07 / PRIVACY POLICY
How long records are kept
- Buyer account, site links and entitlement: kept as needed to administer access, preserve site identity, provide ongoing essential help and resolve account/security issues. Account closure or a refund triggers review of what is still needed; it does not automatically erase all associated records.
- Purchases, refunds and audit history: retained for necessary accounting, payment disputes, legal obligations, security and documented administration. The duration depends on applicable obligations and the purpose of the record; we do not promise one fixed retention period for every record.
- Accepted certificates and history: retained while the certificate service operates, subject to withdrawal, privacy, legal and abuse requirements described in the terms. Uninstalling or temporarily disconnecting a site does not automatically delete its certificates. Previously accepted certificates do not consume a new monthly allowance.
- Verification and connection records: links/codes have expiry and single-use controls. Expiry does not mean all delivery, verification or audit records are immediately erased. Verification messages contain a link or code and are not public certificate data.
- Support and operational records: kept for the time needed to resolve requests, maintain security, investigate problems and meet applicable obligations. Log, email-history and backup retention depends on the actual service configuration and purpose; no immediate or unconditional purge is promised.
When a record is no longer needed and there is no valid reason to retain it, it should be removed or de-identified through an appropriate process. Technical backups, integrity journals and immutable audit records can require separate handling; public suppression is not the same as erasing every stored copy.
Back to contents ↑08 / PRIVACY POLICY
Access, correction, deletion and other requests
You may contact Brian Winum about WP ContentLedger to ask about information concerning you, request access or correction, ask for an available export, or request restriction, withdrawal or deletion. Depending on the law that applies, you may also have rights to portability, objection, withdrawal of consent and complaint to an appropriate data-protection authority. We will handle requests within applicable legal requirements; not every right applies to every record or purpose.
Buyers can identify their account email and relevant transaction/site reference. If you are an author, reader, client or another person named in a certificate, you do not need to buy the plugin to raise a privacy concern: identify the certificate/source URL and the information in question. We may request proportionate information to verify identity and authority before disclosing or changing private data. Do not send passwords or full payment credentials.
We may need to retain limited records for legal obligations, disputes, security or legitimate integrity purposes, and we will explain relevant limitations rather than promise unconditional erasure. Contacting us is the request route; this page does not provide an automated deletion or data-export tool.
Back to contents ↑09 / PRIVACY POLICY
Certificate withdrawal, correction and outside copies
A public withdrawal can suppress certificate details while a limited audit record remains. Corrections may be represented by a new revision or an explanatory status rather than rewriting historical evidence. We will assess privacy or legal requests individually; an integrity policy does not override an applicable legal obligation to correct, restrict or erase personal information.
A refund ends the paid entitlement as described in the terms, but does not silently delete previously published evidence. Assistance with permitted withdrawal and available exports remains available. We cannot guarantee deletion from independent archives, search-engine caches, third-party copies, already distributed exports or public blockchain commitments. A fingerprint alone generally cannot reconstruct an article, but may still be linkable to other information.
Back to contents ↑10 / PRIVACY POLICY
Security and your responsibilities
Private account records are intended for restricted administration and service processing. The planned buyer service uses verification and site-control checks to authorize access. That buyer service is not open yet, and this policy is not a claim that production buyer authentication or email delivery is already enabled.
Access controls and operational safeguards reduce risk but cannot guarantee absolute security or loss-free storage. Protect your buyer email, site accounts, credentials and private keys; keep your own backups and portable evidence. Report a suspected exposure through the contact route without sending the exposed secret itself.
Back to contents ↑11 / PRIVACY POLICY
Policy updates and service closure
Material changes will be explained with an updated policy and appropriate notice, and consent will be sought when required. A planned permanent certificate-service shutdown follows the terms’ commitment to at least 90 days’ notice and an opportunity to export supported evidence where reasonably possible. Hosted public availability can end with the service; legal, security and accounting retention needs and independently held copies remain separate considerations.
This policy describes privacy handling; it is not a waiver of mandatory rights and does not itself authorize new collection, new providers or unrelated use of personal information.
Back to contents ↑12 / PRIVACY POLICY
Contact
For privacy questions or requests, contact Brian Winum about WP ContentLedger. Identify the record or website concerned and the action you are requesting. Brian Winum is the project privacy contact. We will update these disclosures as the buyer service opens or material processing arrangements change, including applicable provider, retention and regional information.
Back to contents ↑