Appearance
Publisher & Embed Terms
These Publisher & Embed Terms (“Publisher Terms”) supplement the User Terms for Zeeker Embed, publisher dashboards, website widgets, the Zeeker WordPress plugin, archive migration, and publisher integrations. 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.
1. Authority
You represent that you control the site or organization you connect and can bind it. You have all rights and permissions required for domains, 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.
2. The publisher service
Zeeker may provide floating or inline conversation widgets, reactions, communities, moderation, account integration, analytics, import tools, SSO, APIs, and related configuration. You choose where the widget appears and which optional features to enable.
Do not conceal that Zeeker operates the social layer or mislead visitors about data recipients. Preserve accessible links to Zeeker’s Terms, Privacy Policy, cookie controls, reporting, and publisher information.
3. Site and installation data
To provision and secure an installation, the WordPress plugin or embed 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 plugin does not need to send WordPress passwords. Archive import is described below.
Installation credentials are confidential. Keep them secure and rotate or reconnect after compromise. Do not copy an installation secret to an unrelated domain.
4. Publisher Content
“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. You grant Zeeker the license in section 5 of the User Terms for Publisher Content you intentionally make public through the Services, including operation, display, indexing, syndication, commercial use, and AI/ML use, unless a signed order form expressly narrows those rights. For nonpublic configuration or customer-controlled data, Zeeker receives only the rights necessary to provide, secure, support, and comply with law.
You represent that:
- you own Publisher Content or have authority to grant the license;
- your notices to authors, commenters, subscribers, and visitors permit the transfer and uses you configure;
- 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.
These Publisher Terms apply only when a publisher 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. WordPress archive migration
If selected, 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 on Zeeker and for giving any notice required by law or your site terms. Zeeker may reject or quarantine material that lacks provenance, violates policy, is private, or is subject to a rights restriction.
6. Visitor privacy and cookies
You and Zeeker may each be independently responsible for processing on an embedded site. Before enabling optional analytics, personalized recommendations, advertising, location, or SSO, configure lawful notice and consent for the visitor’s region. Do not send Zeeker sensitive or special-category data unless a written agreement expressly permits it.
Do not suppress consent controls, force an optional choice, or load optional Zeeker or third-party tracking before valid consent where required. Respect Global Privacy Control and other legally recognized signals.
The Data Processing Addendum applies only where its role requirements are met; it does not make Zeeker a processor for independent platform processing.
7. Moderation and safety
Your community must comply with the Community Guidelines. Configure and staff moderation appropriate to the audience and risk. Escalate urgent reports; do not use an ordinary moderation queue as an emergency service.
Zeeker may enforce platform rules regardless of publisher settings. You may adopt additional rules if they are clear, lawful, non-discriminatory, and do not conflict with Zeeker’s safety requirements.
8. Technical restrictions
Do not:
- alter the widget to hide attribution, legal, consent, reporting, or safety controls;
- intercept credentials or impersonate Zeeker;
- 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.
9. Takedowns, opt-outs, and disconnection
You can disable a widget, stop imports, disconnect credentials, or request deletion through product controls or the Request Center. Zeeker may suspend a configuration for security, policy, rights, legal, or nonpayment reasons.
When a verified rights owner requests correction, removal, or data-use restriction, you will cooperate in applying the request to material you supplied. If you dispute authority, provide evidence through the case rather than restoring material unilaterally.
10. 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.
11. Liability
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 or content you lacked authority to connect, privacy notices or consents you failed to provide, or Publisher Content that violates third-party rights, except to the extent caused by Zeeker.
12. Acceptance and changes
Publisher acceptance is separately versioned. Material changes require renewed acceptance before publisher dashboard, claim, provisioning, import, or configuration actions. Public legal, reporting, and disconnection paths remain available.