Appearance
Developer Terms
These Developer Terms supplement the User Terms for APIs, SDKs, widgets, webhooks, bots, service accounts, data exports, and integrations.
1. Access and registration
Use only documented access methods and credentials issued to you. Keep keys secret, separate development and production, rotate compromised secrets, and give Zeeker accurate contact, application, callback-domain, purpose, and privacy information.
Zeeker may review an integration and limit scopes, users, rates, data fields, or features. Approval or technical access does not endorse an app or transfer ownership of Zeeker or user data.
2. User direction and consent
Request the narrowest scopes needed. Give users clear notice of data collected, purpose, recipients, retention, and deletion. Obtain valid consent where required and provide a working disconnect and deletion path.
Do not use dark patterns, bundle optional purposes, or condition basic service on unrelated data access. Do not ask users to share Zeeker passwords or tokens.
3. Data use restrictions
You may use data only for the disclosed, approved integration purpose. You must not:
- sell or broker personal data;
- build surveillance, facial-recognition, background-check, credit, employment, housing, insurance, or other eligibility products;
- infer sensitive traits or target ads from private or sensitive data;
- combine Zeeker data with brokered dossiers;
- harass, discriminate, reidentify, deanonymize, or expose private data;
- train or evaluate AI/ML using Zeeker data without separate written authorization expressly covering that use;
- retain data after the user disconnects or the purpose ends, except a documented legal obligation; or
- ignore deletion, correction, visibility, or tombstone events.
Public API access does not itself grant a license to user content. Your use must fit the User Terms license, user direction, and any separate agreement.
4. Security
Use encryption in transit and at rest, least privilege, access logging, secure development, vulnerability management, dependency updates, incident response, and appropriate tenant isolation. Notify Zeeker promptly of suspected unauthorized access or loss and cooperate with containment and user/regulatory duties.
Do not cache access tokens in client-visible code or log full secrets. Delete or rotate exposed keys immediately.
5. Technical conduct
Respect rate limits, pagination, robots and publisher controls, backoff, quotas, schema versions, idempotency, and documented caching. Do not evade restrictions, scrape undocumented endpoints, probe other tenants, interfere with availability, misrepresent user agents, or reconstruct prohibited data.
Bots must be labeled, attributable, and controllable. Automated posting or messaging must not spam or manipulate engagement.
6. User experience and branding
Do not imply that Zeeker sponsors your integration without permission. Follow brand guidance and preserve Zeeker attribution, consent, reporting, and legal links in widgets. Do not create deceptive interfaces or obscure whether an action affects Zeeker.
An integration with a current contractual white-label entitlement may replace Zeeker attribution and public Zeeker legal links with the approved Operator branding and Operator Legal Hub described in the Publisher, Embed & White-Label Terms. This narrow exception does not permit removal of consent, reporting, safety, or rights controls; concealment of a legally required data recipient or controller; or white-label use on an unapproved domain. Direct Zeeker account or service interactions remain subject to any disclosure Zeeker identifies as necessary for that feature.
7. Audit and suspension
Keep records sufficient to show scopes, user authorization, data flows, subprocessors, retention, and deletion. On reasonable notice, provide information needed to assess compliance. Zeeker may suspend credentials immediately for security, legal, abuse, or user-harm risk.
On termination, stop access, delete data and derived personal profiles, revoke tokens, and certify deletion if requested. Provisions on restrictions, security, audit, liability, and deletion survive.
8. Additional terms
The Publisher, Embed & White-Label Terms apply to publisher sites and widgets. The DPA applies only where its stated role conditions are met. A signed developer or data-license agreement controls where it expressly conflicts.
Version 2026-07-29 is preserved in the policy archive.