Terms of Service

Thank you for using Publishing Policy. We built this platform to help organizations define, publish, and be accountable to their own publishing standards. These Terms of Service (“Terms”) govern your use of the platform.

When we say “Company,” “we,” “us,” or “our” in this document, we mean Publishing Policy, currently operated by Roarke Clinton with plans to incorporate as a 501(c)(3) nonprofit organization. When we say “Service” or “Services,” we mean the Publishing Policy platform at publishingpolicy.org, including all features, content, and APIs. When we say “you” or “your,” we mean you as the person or organization using the Service.

By using the Service, you agree to these Terms. If you do not agree, do not use the Service. We may update these Terms in the future. Changes are tracked in our public GitHub repository. When we make significant changes, we will update the date at the top of this page. Continued use of the Service after changes constitutes acceptance of the updated Terms.

Preview period

We will provide clear notice when the Preview period is ending. You will have the opportunity to review your content and decide whether to continue before any permanence features take effect.

Account terms

1. You must be at least 13 years old to use the Service. If you are in the European Union, you must be at least 16 years old. By creating an account, you represent that you meet the applicable age requirement.
2. You are responsible for maintaining the security of your account. We use passwordless authentication via magic links sent to your email address. You are responsible for maintaining access to the email address associated with your account.
3. You are responsible for all content posted to and activity that occurs under your account.
4. You must be a human. Accounts registered by automated methods (bots, scripts, or other non-human agents) are not permitted.
5. Publisher accounts and reader accounts. Anyone can browse published policies without an account. Creating a publisher account allows you to create and manage policies. We may introduce reader accounts in the future that allow interaction features (such as reporting or voting) without the ability to create policies.
6. You may not use the Service for any purpose outlined in our Use Restrictions policy.

Content ownership and licensing

1. You own your content. The publishing policies, organizational information, and other content you create through the Service remain yours. We claim no ownership rights over your content.
2. Published policies are publicly licensed. When you publish a policy (move it from draft to published), you license that policy content under Creative Commons Attribution 4.0 International (CC-BY 4.0). This means anyone — journalists, researchers, the public — may share, quote, and reference your published policy with attribution. This license is irrevocable: once a policy is published, the public's right to examine and share it cannot be withdrawn. This is by design. A publishing policy exists to be examined by the public. An organization cannot use copyright to suppress scrutiny of its own stated commitments.
3. Drafts are not publicly licensed. Policies in draft status remain private and are not subject to any public license. The CC-BY 4.0 license applies only at the moment of publication. You may keep a policy in draft as long as you wish before deciding to publish.
4. During the Preview period. The CC-BY 4.0 license still applies when you publish a policy during Preview. However, because Preview policies can be fully deleted, deleting a policy during Preview also revokes the public license for that content. After the Preview period ends, publication and its CC-BY license are permanent.
5. You grant us a license to operate the Service. In addition to the public CC-BY license, you grant us a non-exclusive, worldwide, royalty-free license to store, display, distribute, and make available your content as part of the Service. This license exists solely to operate the Service as intended — to display your publishing policy publicly, include it in the directory, generate badges and share links, and provide related functionality.
6. Permanent public records. After the Preview period ends, publishing a policy creates a permanent public record. While you retain ownership of your content, the public record of what was published and when will persist even if you later deactivate the policy or delete your account. By publishing a policy after the Preview period, you acknowledge and consent to this permanence. See the “public nature” section below for details.
7. The platform's source code. The Publishing Policy codebase is source-available under the Business Source License 1.1 (BSL 1.1). The code is publicly viewable and contributions are welcome, but you may not use the code to operate a competing publishing policy or standards platform. See the LICENSE file in our repository for full terms. After the change date specified in the license, each version becomes available under Apache 2.0.
8. All content posted on the Service must comply with U.S. copyright law. You must have the right to post any content you submit.

The public nature of published policies

Publishing Policy exists to make publishing standards transparent and publicly verifiable. This section describes what that means for your content:

1. Published policies are public. When you publish a policy (change its status from “draft” to “published”), it becomes publicly accessible. It will appear in the public directory, have a shareable URL, and may be indexed by search engines. This is the core purpose of the Service.
2. Draft policies are private. Policies in draft status are visible only to you. You control when (and whether) to publish.
3. Version history is part of the public record. When you update a published policy, the previous version is preserved. This version history is publicly accessible. The ability to see how a policy has changed over time is an essential accountability feature of the Service. Each policy URL displays a chronological timeline of all versions with their start and end dates.
4. Published policies are permanent (after Preview). Once the Preview period ends, publishing a policy creates a permanent public record. A published policy can be deactivated — marked as no longer in effect — but it cannot be deleted from the public record. The historical record of what was published and when will always remain accessible. Think of it like a public filing: you can amend or supersede a filing, but the original record persists.
5. During the Preview period, everything is deletable. While the Service is in Preview, you can fully delete any policy you create. Nothing is permanent until after the Preview ends and you have explicitly confirmed your intent to make your policies part of the permanent record.
6. “No known policy” profiles. Any URL or domain can be looked up on the Service. If no policy exists for that URL, the Service will indicate that no known publishing policy has been registered. The absence of a policy is itself informative. This does not constitute an editorial judgment — it is simply a factual statement about the state of our registry.
7. You can deactivate (after Preview). You may deactivate a published policy, which marks it as no longer in effect. The policy will no longer appear as active in the directory, but the historical record — including all versions and their effective dates — remains publicly accessible. Cached copies may also persist in search engines and web archives.

Community interaction features

Publishing Policy is building toward community-driven accountability features. This section describes the terms governing those features as they become available:

1. Reporting. Users with accounts may report potential policy violations they observe. Reports are a way for the community to surface concerns — not a legal finding or a platform judgment. The Service provides the mechanism; the community provides the signal.
2. Community-driven evaluation. Over time, the Service may display aggregated community feedback about how well an organization appears to follow its own published policy. This feedback is community-driven, similar to product reviews or social media reactions. It reflects the collective perception of community members, not the editorial judgment of Publishing Policy.
3. Account required for interaction. Browsing published policies is free and does not require an account. Interacting with the platform — filing reports, providing feedback, or voting — requires a registered account so that interactions can be attributed and abuse can be managed.
4. Good faith participation. Community features must be used in good faith. Filing false or misleading violation reports, coordinating campaigns to manipulate scores or reputations, or using interaction features to harass organizations or individuals are violations of our Use Restrictions.
5. No guarantee of compliance verification. The platform surfaces community reports and aggregated feedback. We do not independently verify whether an organization complies with its own published policy. The Service is a transparency and accountability tool — not a compliance auditor or regulatory body.

Use restrictions

We outline specific prohibited uses in our separate Use Restrictions policy. In summary, you may not use the Service to:

• Impersonate an organization you do not represent
• Create policies that contain hate speech, threats, or illegal content
• File false or misleading violation reports
• Manipulate community scores or reputations
• Interfere with the security or operation of the Service
• Extract data from accounts that do not belong to you
• Use the Service in a way that violates applicable law

Violating these restrictions may result in suspension or termination of your account.

Domain verification and representation

1. When you create a policy for a domain or URL, you represent that you have the authority to speak for that domain or the organization it represents. Creating a policy for a domain you do not own or are not authorized to represent is a violation of these Terms.
2. Domain verification (via DNS record, well-known file, meta tag, or bio link) is available to prove ownership. Verification is reflected in your policy's certification tier and your organization's profile. However, verification is not mandatory to create a policy.
3. Verification is point-in-time. Domain verification confirms that you controlled a domain at the time of verification. Verification may expire and require renewal. We may periodically re-verify domain ownership to ensure accuracy. If your verification expires, your policy remains visible but its verification status will be updated to reflect that it is no longer current.
4. Domain ownership changes. Domains can be sold, transferred, or expire. If a domain changes hands, the previous owner's policy record remains permanently attributed to them — it represents their commitments during the period they controlled the domain. The new domain owner is not bound by the previous owner's published policies and cannot edit, claim, or inherit them. A new domain owner may verify their own ownership and create their own policy. The public record will clearly distinguish between policies published by different owners of the same domain over time.
5. Historical attribution persists. When you publish a policy, it is permanently attributed to you as the publisher — not to the domain itself. If you later lose control of the domain, the historical record remains: “Published by [your organization], who verified ownership of [domain] from [date] to [date].” This ensures that the permanent record accurately reflects who made which commitments and when.
6. We do not guarantee the accuracy or truthfulness of any publishing policy on the platform. A policy represents the organization's self-reported commitments. We do not verify whether organizations actually follow their stated standards.
7. If you believe someone has created a policy impersonating your organization, or if you are the new owner of a domain with an existing policy from a previous owner, contact us at team@publishingpolicy.org and we will investigate.

Cancellation and termination

1. The Service is currently free. No payment is required and no billing information is collected. If we introduce paid features in the future, we will provide clear notice and will not charge you without your explicit consent.
2. You may request cancellation of your account at any time by emailing team@publishingpolicy.org. During the Preview period, cancellation will delete all your account data, policies, and associated content. After the Preview period, account data will be deleted but published policy content will remain as part of the permanent public record, as described in our Privacy Policy.
3. We reserve the right to suspend or terminate your account if you violate these Terms or our Use Restrictions. We will make reasonable efforts to notify you before taking action, except in cases where the violation poses an immediate risk to the Service or other users.
4. Abuse — verbal, physical, written, or otherwise — directed at anyone associated with Publishing Policy will result in immediate account termination.

Uptime, security, and privacy

1. Your use of the Service is at your sole risk. We provide the Service on an “as is” and “as available” basis. We do not offer a service-level agreement, but we take the availability and reliability of the Service seriously.
2. We take measures to protect and secure your data through encryption in transit (TLS), encryption at rest, passwordless authentication, and row-level security policies in our database. For details, see our Privacy Policy.
3. When you use the Service, you entrust us with your data. You agree that we may process your data as described in our Privacy Policy and for no other purpose. We access your data only to provide the Service, debug technical issues, respond to support requests, or investigate potential abuse — and in each case, only to the minimum extent necessary.
4. We use third-party service providers (Supabase, Vercel, and Resend) to operate the Service. These providers process your data solely to deliver their services to us, as described in our Privacy Policy.

Liability

In plain terms: the Service hosts self-reported publishing standards and surfaces community feedback about those standards. We do not verify that organizations follow their stated policies. We are not liable if an organization violates its own published standards, or if a policy is inaccurate, incomplete, or misleading. We are not liable for the accuracy, fairness, or completeness of community-generated reports, scores, or evaluations.

The Service is a platform for transparency and community-driven accountability — not an enforcement mechanism or compliance auditor. Community feedback reflects the perceptions of individual users, not the editorial judgment of Publishing Policy. The value of a publishing policy comes from the public commitment itself and the accountability that transparency creates — not from any guarantee or warranty on our part.

Governing law and disputes

1. These Terms are governed by and construed in accordance with the laws of the United States.
2. Any disputes arising from these Terms or your use of the Service should first be addressed by contacting us directly at team@publishingpolicy.org. We believe most issues can be resolved through good-faith communication.
3. If a provision of these Terms is found to be unenforceable, the remaining provisions will continue in full effect.
4. Our failure to exercise or enforce any right or provision of these Terms does not constitute a waiver of that right or provision.

Contact

Questions about these Terms? Get in touch: