Request passwords
Zenzo public pages will not ask visitors to provide a GitHub, Google, workplace, or recovery-code password.
Clear signals, no credential traps.
A public product page should be easy to identify and should not pressure anyone to hand over an account. This page explains the official Zenzo public surface and the checks visitors can use before following a link.
Official public presence
Use verifiable destinations.
| Purpose | Official destination | What to expect |
|---|---|---|
| Public Zenzo site | samkomedved319-dev.github.io/zenzo-landing-page/ | Product information, documentation, policy pages, and an early-access link. |
| Public source | github.com/samkomedved319-dev/zenzo-landing-page | Public site source and commit history. GitHub may ask you to sign in only for GitHub actions you choose to take. |
| Early access | Linked from the official site | A request form. It should never ask for an existing GitHub or Google password. |
Before you continue
A quick link check
01
Read the domainCheck the full address bar rather than relying on a page title, logo, or a message that contains the link.
02
Check the actionPublic Zenzo pages should provide information. An unexpected request for a password, authorization grant, or recovery code is a reason to pause.
03
Verify independentlyOpen the official repository or Pages address yourself instead of following a suspicious or time-sensitive message.
Human review notice
Public information is not internal access.
The human-review explanation is public so applicants and visitors can understand that people review consequential work. Internal review records are not exposed through the public site, and the staff review notice does not perform authentication.
- Do not enter credentials into a page merely because it uses Zenzo branding.
- Do not treat a public URL as a staff-only access path.
- Review the human-review notice for the page’s explicit non-login statement.
What Zenzo public pages will not do
Signs to stop and verify.
Imitate a login flow
The public site does not present a Zenzo sign-in screen. An unfamiliar sign-in prompt should be verified independently.
Create false urgency
Public product information should not threaten account loss or pressure you to act immediately to preserve access.
Found something that does not match these signals?
Do not enter credentials or authorize access. Return to the official Pages address or the public repository directly and compare the destination before taking any further action.