Appearance
Privacy Policy
This Privacy Policy explains how Zeeker Platforms, Inc. (“Zeeker”) handles personal data across Zeeker ID, Social, Explore, Chat, Admin, Embed, mobile apps, websites, APIs, support, legal operations, and related services.
Your choices matter. You can request access, correction, deletion, portability, restriction or objection, withdraw consent, appeal a rights decision, and opt out of legally covered sale, sharing, targeted advertising, or profiling. Use Your Privacy Choices or the Request Center.
1. Who is responsible
Zeeker Platforms, Inc.
230 E Ohio St., 410-1590
Chicago, IL 60611, USA
Zeeker is generally the controller or business for account, platform, safety, product, and legal processing. For limited organization-controlled features covered by the Data Processing Addendum, Zeeker may be a processor or service provider.
2. Data we collect
Data you provide
- Account and identity: email, phone number, authentication method, username, display name, password verifier, recovery and login records, age or birth date, and acceptance records.
- Profile: avatar, cover image, biography, website, pronouns or gender if provided, interests, language, country, region, city, and preferences.
- Content and social activity: posts, replies, messages, reactions, saves, shares, follows, community membership, polls, media, drafts, and content metadata.
- Admin and publisher data: organization, role, permissions, community settings, moderation actions, reports, audit activity, domains, site names, embed configuration, installation credentials, imports, feeds, source rights, and attribution records.
- Communications: support messages, feedback, surveys, legal requests, copyright notices, appeals, and evidence you choose to submit.
- Payments: purchase and transaction details; payment-card data is generally handled by the payment provider rather than stored in full by Zeeker.
- Optional device data: contacts, photos, camera, microphone, notification token, or precise location only when you enable a feature that needs it and the operating system grants permission.
Data collected automatically
- IP address, device and browser type, operating system, app version, identifiers, language, time zone, referring URL, pages and features used, clicks, searches, approximate location derived from IP, session timing, crash and performance logs, and security events.
- Cookies and similar storage described in the Cookie & Tracking Notice.
- Embed events such as widget configuration, page context, reactions, and interaction needed to deliver the embedded social experience.
Data from others
- OAuth and sign-in providers, based on the permissions shown during connection.
- Other users, when they mention, follow, message, invite, report, or upload information about you.
- Community administrators and publisher sites that configure Zeeker or import public material.
- Public websites, feeds, APIs, and licensed data providers for discovery, link previews, attribution, safety, and publisher-data features. See Publisher Data & Crawler Policy.
- Security, fraud-prevention, measurement, and service providers.
Data by app
| Surface | Core data and processing |
|---|---|
| Zeeker ID | Account identifiers, authentication/recovery, connected providers, session/security, age eligibility, and legal acceptance evidence shared across linked apps |
| Zeeker Social | Profile, public and restricted content, media, reactions, follows, communities, reports, ranking, moderation, and link-preview context |
| Zeeker Explore | Topic, country/region/city and interest preferences, searches, feed interactions, source links, freshness and ranking signals |
| Zeeker Chat | Participants, message content and attachments, delivery/read state, abuse reports, blocks, notification and safety metadata |
| Admin Center | Organization/community, role and invitations, settings, moderation actions, audit records, member handling, analytics and entitlements |
| Zeeker Embed / WordPress | Domain, site and community identity, widget configuration, installation credentials, page context, interaction events, claims, and publisher-selected public imports |
| Mobile apps | The matching web-app data plus secure session storage, app/device version, push token, crash data, and optional OS permissions such as media, camera, microphone, contacts, notifications or location |
Do not submit highly sensitive evidence through an ordinary form. We will provide a secure path when identity documents or restricted evidence are genuinely necessary.
3. Why we use data and our legal bases
| Purpose | Examples | Legal basis where required |
|---|---|---|
| Provide the Services | Create accounts, deliver posts/chat/embeds, personalize requested settings, sync apps | Contract |
| Secure and protect | Authentication, spam/fraud detection, abuse investigation, rate limits, backups | Contract; legitimate interests; legal obligation |
| Moderate and enforce | Review reports, label/restrict content, appeals, repeat-infringer records | Legitimate interests; contract; legal obligation |
| Improve and develop | Reliability, product research, aggregate analytics, feature and model evaluation | Legitimate interests; consent where required |
| Public content and AI | Search, recommendations, summaries, grounding, training/evaluation described in the User Terms | Contract/license; legitimate interests; consent where law requires |
| Communicate | Service, security, policy, support, and optional marketing messages | Contract; legal obligation; consent or legitimate interests |
| Meet legal duties | Rights requests, tax, preservation, regulator and court requests, child-safety reporting | Legal obligation; public interest |
| Operate the business | Billing, audits, corporate transactions, legal claims | Contract; legitimate interests; legal obligation |
Where we rely on legitimate interests, we assess necessity, reasonable expectations, and impact, with added safeguards for sensitive people or uses. You may object. Where consent is the basis, you can withdraw it without affecting earlier lawful processing.
We do not use acceptance of the User Terms as consent to optional analytics, marketing, sensitive-data processing, or other processing that requires a separate choice.
4. Public content, AI, and automated systems
Public profiles and content are visible to others and may be indexed, embedded, syndicated, summarized, licensed, and used for AI/ML as described in the User Terms and Public Content & Data Use Policy. Private messages and restricted content are excluded from public-data licensing and general-purpose model training.
Automated systems help rank feeds, recommend communities, detect spam and harmful content, translate or summarize, and support moderation. Signals may include your actions, relationships, content, settings, approximate location, language, freshness, quality, and safety information. You can change preferences and appeal consequential moderation decisions. Zeeker does not use solely automated decisions to make legal or similarly significant eligibility decisions about employment, housing, credit, insurance, or essential services.
5. How we disclose data
We disclose data:
- to people and communities you choose, based on visibility and sharing controls;
- to site publishers and administrators, for their communities, moderation, configuration, and aggregate analytics, with role controls;
- to service providers and subprocessors for cloud hosting, content delivery, email, notifications, analytics you permit, security, support, AI features, and business operations;
- to integration partners, when you connect an account or direct a transfer;
- to professional advisers and corporate transaction participants, under confidentiality and legal safeguards;
- to authorities or others, when reasonably necessary to comply with valid law, prevent serious harm, protect rights, or defend legal claims; and
- to the public, for public content and associated profile details.
Current categories of providers are listed on Subprocessors. Zeeker does not disclose private messages to public-data licensees.
YouTube API Services and embedded players
Zeeker uses YouTube API Services to find recent public news videos, check whether they can be embedded, associate them with independently captured news, and show a video reference. Public API data used for those purposes can include video and channel identifiers, watch links, titles, descriptions, publication times, thumbnail URLs, duration, embed or playability status, regional restrictions, and Made for Kids status. Zeeker does not request access to your YouTube account, credentials, subscriptions, playlists, or other authorized YouTube user data, and does not sell YouTube API data.
Before the embedded player loads, a card may display a thumbnail hosted by YouTube. Loading that thumbnail can disclose ordinary network and request information—such as IP address, browser/device details, referring page, and request time—to Google or YouTube. Zeeker does not make a separate speculative preconnection to YouTube or Google video hosts. Depending on the Zeeker surface, the privacy-enhanced YouTube player loads either when an eligible video becomes mostly visible for muted autoplay or when you select a play or unmute control. Player loading and playback can let Google or YouTube process device, network, cookie, advertising, interaction, and fraud-prevention information.
Mutable YouTube discovery signals are ordinarily refreshed or deleted within 48 hours. A published YouTube reference and its API-derived identifiers are deleted within 28 days unless Zeeker implements a compliant refresh sooner. Information held independently by Google or YouTube remains subject to their controls and retention practices. See the YouTube Terms of Service, Google Privacy Policy, and Cookie & Tracking Notice.
Sale, sharing, and targeted advertising
Zeeker does not sell personal data for money. Some jurisdictions define “sale” or “sharing” broadly to include certain advertising or cross-context measurement disclosures. If Zeeker engages in a covered practice, you may opt out through Your Privacy Choices, and we honor legally recognized universal opt-out signals such as Global Privacy Control where required. Zeeker does not knowingly sell or share the personal data of people under 16 for covered advertising.
6. International transfers
Zeeker is based in the United States and uses providers in multiple countries. Data may be processed outside your country, where laws differ. When required, we use recognized safeguards such as adequacy decisions, standard contractual clauses, the UK addendum, contractual protections, access controls, and transfer assessments. Contact us for information about a relevant safeguard.
7. Retention
We keep data only as long as reasonably needed for the stated purpose, then delete, de-identify, or securely isolate it. Factors include account status, user choice, feature needs, legal limitation periods, safety, fraud, disputes, backups, and deletion obligations.
| Data | Typical rule |
|---|---|
| Active account/profile | For the account lifetime |
| Public content | Until deleted or account action, subject to license-survival and downstream limits in the User Terms |
| Private messages | Until deleted under product rules or needed for safety/legal preservation |
| Authentication and security logs | Generally up to 24 months, longer for an active investigation |
| Legal acceptance evidence | For the agreement limitation period plus time needed to establish or defend claims |
| Support and ordinary legal cases | Usually up to 6 years after closure unless a shorter right or longer legal hold applies |
| Copyright, repeat-infringer, child-safety, or fraud records | As needed for statutory duties, enforcement, and claim defense |
| Analytics identifiers | Based on your saved choice, applicable regional consent or opt-out rules, and the provider setting disclosed in the Cookie Notice |
| Backups | Cycled on a limited schedule; data is not restored to active use after a completed deletion |
Specific features may show a shorter period. A valid preservation request or legal hold temporarily overrides ordinary deletion.
8. Security
Zeeker uses layered administrative, technical, and physical safeguards, including encryption in transit, restricted access, authentication controls, logging, private cloud storage, testing, and incident response. No system is perfectly secure. Protect your credentials and report suspected compromise promptly. See Security.
9. Your rights
Depending on location, you may:
- know and access personal data and processing information;
- correct inaccurate data;
- delete data;
- receive portable data;
- restrict or object to processing;
- withdraw consent;
- opt out of covered sale, sharing, targeted advertising, or qualifying profiling;
- limit certain uses of sensitive personal information;
- challenge a significant automated decision;
- appeal a denied privacy request;
- use an authorized agent; and
- complain to a privacy or data-protection authority.
Use the Request Center. We verify requests proportionately and will not discriminate for exercising a right. An agent must provide signed authority and may need the person to verify directly. We may deny or limit requests when an exemption applies, explaining the reason and appeal path.
You can also delete content, change visibility and preferences, disconnect providers, revoke mobile permissions, manage cookies, and delete or deactivate an account in available settings.
10. Children and teens
Zeeker is not directed to children under 13 and does not knowingly create their accounts. We take age, audience, privacy-by-default, advertising, recommendation, contact, and reporting protections into account. If you believe a child’s data is present, use the child-safety form. See Children & Teen Safety.
11. Publisher and public-source data
When Zeeker obtains contact or attribution data indirectly from a public page, feed, licensee, user, or publisher, the categories may include byline/name, public professional profile, publisher, article metadata, source URL, publication date, and rights/contact details. Purposes include linking, attribution, discovery, rights management, safety, and publisher communications.
The source, legal basis, rights signal, permitted uses, expiry, and deletion obligations should be recorded in Zeeker’s source-rights ledger. People and publishers can object, correct, or request removal. Detailed Article 14-style information appears in the Publisher Data & Crawler Policy.
12. Regional information
The Regional Terms & Privacy Notice explains additional EU/EEA/UK, US state, India, Brazil, Canada, and Australia rights. Mandatory local law prevails over inconsistent language.
13. Changes
We post the current version and archive material changes. We will provide prominent notice when a change materially affects rights or creates a new processing purpose and obtain consent where law requires it.
14. Contact and complaints
Use the Request Center for privacy rights, complaints, and appeals.
Zeeker Platforms, Inc.
230 E Ohio St., 410-1590
Chicago, IL 60611, USA
You may also complain to your local privacy authority. Where Zeeker must appoint a regional representative or data-protection contact for a launched service, the applicable details will be added to the Regional Notice.