Security

Zeeker uses layered safeguards designed for the nature and risk of its social, identity, chat, admin, embed, and data services.

Program

Controls include, as appropriate:

• encryption in transit and protected storage;
• private network and cloud access controls;
• least-privilege identity, role separation, and credential rotation;
• secure session handling, rate limits, abuse detection, and audit logs;
• dependency, code, configuration, and infrastructure review;
• backup, recovery, availability, and change procedures;
• incident triage, containment, investigation, remediation, and notification;
• vendor risk and confidentiality requirements; and
• data minimization, retention, and deletion workflows.

No security program eliminates all risk. Zeeker continually adjusts controls as products and threats change.

Your responsibilities

Use unique authentication, protect email/phone recovery methods, review active roles and integrations, revoke stale credentials, keep software current, and report unexpected account or installation activity. Administrators and developers have additional duties under their supplements.

Report a vulnerability

Do not exploit, persist, destroy, exfiltrate, publicly disclose, or access other people’s data. Stop after obtaining the minimum proof and report the issue through the Request Center with “Security vulnerability” in the details.

Good-faith research that respects these limits, avoids privacy and service impact, and gives Zeeker reasonable time to remediate will not be treated as malicious solely because it identified a flaw. This is not authorization to violate law or third-party terms.

Security and privacy incidents

If Zeeker confirms a personal-data breach, we notify affected customers, people, and authorities as required, based on risk and legal deadlines. Notices describe known facts, likely impact, and protective steps without compromising containment.