Appearance
Publisher, Embed & White-Label Terms
These Publisher, Embed & White-Label Terms (“Publisher Terms”) supplement the User Terms for Zeeker Embed, publisher dashboards, website widgets, the Zeeker WordPress plugin, archive migration, publisher integrations, and entitled white-label services. Account holders accept both documents. A WordPress administrator provisioning without a Zeeker account must affirmatively accept these Publisher Terms in the plugin, where Zeeker records the version and evidence supplied by the installation.
In these Publisher Terms, “Operator” means the organization responsible for the connected site, app, or community. “Operator Experience” means the Operator-branded site, app, community, embed, or widget. “White-Label Integration” means an Operator Experience for which Zeeker has enabled a contractual white-label entitlement. “Operator Legal Hub” means the Operator-branded, publicly accessible legal page described in section 3.
1. Authority and verified configuration
You represent that you control the site or organization you connect and can bind it. You have all rights and permissions required for domains, organization and community names, branding, imported posts and comments, user data, analytics, and instructions you provide.
If you connect on behalf of another party, you must disclose that relationship and obtain its authorization. Zeeker may verify control by account role, domain email, DNS record, .well-known token, plugin secret, or reasonable documentation.
Zeeker may use the verified domain, Operator or community name, authorized account contact, enabled features, region, and other existing configuration to prepare default disclosures and the managed Operator Legal Hub. This is intended to avoid asking for the same information again. You must keep that configuration accurate and complete any additional field that Zeeker reasonably identifies as necessary for the selected feature or applicable law.
2. The publisher service
Zeeker may provide inline or floating conversations, reactions, communities, moderation, account integration, analytics, import tools, SSO, APIs, legal-page hosting, and related configuration. You choose where an integration appears and which optional features to enable.
Except for an entitled White-Label Integration, do not conceal that Zeeker operates the social layer or remove required Zeeker attribution, legal, consent, reporting, or publisher-information links.
3. White-label presentation and the Operator Legal Hub
An entitled White-Label Integration may omit the Zeeker name, marks, attribution, and links to Zeeker’s public legal portal from its public user interface. The integration may instead show the Operator’s approved name, marks, and one neutral Legal & privacy link to an Operator Legal Hub. This limited permission applies only to the entitled configuration and does not transfer Zeeker technology or marks, create a resale right, or permit an Operator to claim it developed or owns the underlying service.
The Operator Legal Hub must be available from the Operator Experience and identify the Operator as the organization responsible for that experience. It must provide or clearly link to:
- terms governing visitors and members;
- a privacy notice and cookie or similar-storage disclosures and controls;
- community or acceptable-use rules;
- content, safety, privacy, and rights-reporting paths; and
- a working Operator contact.
By default, Zeeker may generate, publish, and maintain an Operator-branded hub from the existing verified configuration, selected features, regional settings, and standard Operator templates. Acceptance of these Publisher Terms authorizes that initial managed publication; the Operator need not complete a separate legal questionnaire, approval step, or re-enter information already verified in the service. The Operator may instead configure its own compliant legal URL. In either case, the Operator must review the published hub promptly, correct inaccurate details, keep its public link and managed contact route working, and supply a legally required fact that cannot be derived from configuration.
The public Operator Experience does not need to link to or expressly name Zeeker where Zeeker permits omission and applicable law does not require identification. The private agreement between Zeeker and the Operator—including these Publisher Terms, the applicable order, and the DPA—continues to govern. If a feature makes Zeeker an independent service offered directly to an end user, or applicable law requires a provider or recipient to be identified, Zeeker may require a proportionate disclosure before that feature is enabled. White-label presentation must never be used to give a false or materially incomplete privacy notice.
Until Zeeker expressly enables tenant-managed identity and acceptance for a White-Label Integration, a public interface that omits Zeeker identification is limited to isolated, public, read-only use without sign-in, accounts, contributions, Chat, profiles, or exits into the Zeeker network. Any direct Zeeker account, identity, contribution, or connected-network feature is a separate direct service and must use the Zeeker disclosure, co-branding, and terms Zeeker specifies for that feature.
The managed hub and standard templates are operational defaults, not legal advice or a guarantee that the Operator has satisfied every law. The Operator remains responsible for facts and obligations specific to its business, audience, features, and locations.
4. Operator terms and content-rights flow-down
Before allowing a person to create content or an account in an Operator Experience, the Operator must make its governing terms available and obtain acceptance where required. Those terms must authorize the Operator and its contracted technology and hosting providers to process content and data as needed to deliver, secure, moderate, support, and improve the configured service.
For content the Operator elects to make public through the service, the Operator must obtain rights sufficient for the public uses it enables. If the Operator enables distribution, syndication, commercialization, search, recommendations, or AI/ML features, its terms and notices must clearly cover those uses and permit the Operator to grant the corresponding sublicenses. The Operator may use Zeeker’s maintained standard Operator terms for this flow-down instead of drafting terms from scratch, but must not enable a use that exceeds the rights actually obtained.
“Publisher Content” means content, metadata, branding, archives, media, comments, and other material that you voluntarily upload, import, transmit, or authorize Zeeker to retrieve through a connected feed or API. You retain your ownership. For Publisher Content intentionally made public through the Services, you grant Zeeker the license in section 5 of the User Terms, including operation, display, indexing, syndication, commercial use, and AI/ML use, unless a signed order form expressly narrows those rights. You represent that the Operator’s terms, direct permission, or other lawful authority allows you to grant that license. For nonpublic configuration or Customer Personal Data, Zeeker receives only the rights necessary to provide, secure, support, and comply with law, subject to the DPA where applicable.
These Publisher Terms apply only when an Operator affirmatively accepts them. They do not convert unrelated, publicly accessible publisher material into Zeeker-owned content. Zeeker’s separate rules for open-web data are in the Publisher Data & Crawler Policy.
5. Publisher Content and imports
You represent that:
- you own Publisher Content or have authority to provide it and grant the applicable license;
- notices and terms shown to authors, commenters, subscribers, and visitors permit the transfer and configured uses;
- imported comments exclude email addresses, IP addresses, private notes, authentication data, and content not intended for publication;
- attribution, author, license, deletion, and embargo requirements are accurate and preserved; and
- you will promptly transmit corrections, withdrawals, and deletion signals.
If selected, WordPress migration may transfer public post titles, excerpts, images or image URLs, taxonomy, public bylines, permalinks, dates, and approved public comment text with display name, public avatar/profile URL, permalink, and date. The plugin is designed not to transfer commenter email or IP address.
You are responsible for confirming that public comments can be republished in the Operator Experience and for giving any required notice. Zeeker may reject or quarantine material that lacks provenance, violates policy, is private, or is subject to a rights restriction.
6. Visitor privacy, data roles, and cookies
The Operator is responsible for the lawfulness of its instructions, collection, features, audience, and public disclosures. For eligible Customer Personal Data processed solely on the Operator’s documented instructions, the Operator is controller/business and Zeeker is processor/service provider as stated in the DPA. Zeeker remains independently responsible for the limited processing identified in the DPA and Privacy Policy.
Before enabling optional analytics, personalized recommendations, advertising, precise location, or SSO, configure the appropriate notice, choice, and lawful basis for each visitor’s region. Do not send Zeeker special-category, highly sensitive, or regulated data unless a written agreement expressly permits it.
Do not suppress required consent or opt-out controls, force an optional choice, or load optional tracking before valid consent where prior consent is required. Respect Global Privacy Control and other legally recognized signals. A managed Operator Legal Hub may provide the standard disclosure and preference surface, but the Operator remains responsible for choosing lawful settings and honoring saved choices across its own technologies.
7. Privacy and rights requests
The Operator must provide an accessible route for people to exercise applicable privacy, content, copyright, and consumer rights. It must verify and answer requests for processing it controls and promptly send Zeeker the instructions or information reasonably needed for Customer Personal Data. Zeeker will provide assistance as stated in the DPA.
The Operator will cooperate with verified correction, removal, restriction, preservation, and deletion requests concerning material or data it supplied. If authority is disputed, provide evidence through the case rather than restoring material unilaterally. The Operator Legal Hub may use a managed reporting route so the Operator does not need to build separate forms, but that does not transfer the Operator’s legal duties to Zeeker.
8. Moderation and safety
The Operator must publish rules suitable for its audience and features, configure and staff proportionate moderation, and provide a working reporting route. Escalate urgent reports; do not present an ordinary moderation queue as an emergency service.
Operator rules must be clear, lawful, non-discriminatory, and consistent with the Community Guidelines. Zeeker may enforce platform safety requirements regardless of Operator settings. The Operator must cooperate with lawful preservation, removal, child-safety, intimate-image, and other urgent safety workflows and make legally required notices or reports for processing it controls.
9. Security and installation data
To provision and secure an installation, the plugin or dashboard may send the site URL and name, chosen community and presentation, software and plugin versions, locale, random installation credentials, configuration, health signals, and authorized administrator information. The WordPress plugin does not need to send WordPress passwords.
Installation credentials are confidential. Keep them secure and rotate or reconnect after compromise. Do not copy an installation secret to an unrelated domain. Notify Zeeker promptly of suspected unauthorized access affecting the integration and cooperate with containment and legally required notices.
10. Technical and branding restrictions
Do not:
- remove legal, consent, reporting, or safety controls except for the specific attribution and legal-link substitution permitted by section 3;
- use a White-Label Integration without the required entitlement or outside an approved Operator domain;
- intercept credentials, impersonate Zeeker, or imply that Zeeker endorses the Operator;
- bypass origin, domain, rate, entitlement, or access controls;
- use the Services to create a materially misleading clone;
- inject malware or collect data through undocumented fields;
- frame authenticated pages outside supported embed methods; or
- benchmark or probe the Service to exploit vulnerabilities rather than report them responsibly.
Comply with the Developer Terms for APIs and automation.
11. Suspension, disconnection, and legal-hub continuity
You can disable an integration, stop imports, disconnect credentials, or request deletion through product controls or the Request Center. Zeeker may suspend a configuration for security, policy, rights, legal, entitlement, or nonpayment reasons.
Zeeker may pause publication or a White-Label Integration if the Operator Legal Hub, contact, required choice control, or reporting path is unavailable or materially inaccurate. Where reasonable, Zeeker will allow correction before suspension. Ending the white-label entitlement ends the permission to omit Zeeker attribution and substitute Operator legal links.
12. Service levels and support
Unless a signed order form says otherwise, no uptime or support service level is promised. Beta features may change or be discontinued. Fees, quotas, and entitlements shown at purchase or in an order form apply.
13. Liability and indemnity
The business disclaimers, indemnity, and liability limits in the User Terms apply. Your organization will defend and indemnify Zeeker against claims arising from a domain, data, or content you lacked authority to connect; inaccurate Operator identity or legal-hub information; privacy notices, choices, or responses you failed to provide; Operator moderation or safety duties; or Publisher Content that violates third-party rights, except to the extent caused by Zeeker.
14. Acceptance and changes
Publisher acceptance is separately versioned. Material changes require renewed acceptance before publisher dashboard, claim, provisioning, import, publication, configuration, or white-label actions. Public legal, reporting, privacy-choice, and disconnection paths remain available.
Version 2026-07-29 is preserved in the policy archive.