Account access
A successful sign-in establishes access to a SiloID account. It does not, by itself, establish a person’s legal identity.
SiloID Trust Center
Identity deserves
clear boundaries.
Understand what your account verifies, how access works, and where to get help.
Contact verification
Verified email or phone status means control of that contact method was checked. It is not a government-ID check, background check, or guarantee of trustworthiness.
Document verification
Document submission and approval are different steps. A pending review must not be presented as a verified identity. Check the specific verification method and status before relying on a result.
Application access
Registered applications use SiloID handoffs rather than collecting your SiloID password. Access is bounded by the application’s registered permissions and your account’s current status.
Protections reviewed in the current service
- Password verification uses stored password hashes.
- Sign-in forms use request-forgery protection and same-origin form submission.
- Browser handoffs validate registered applications and active sessions and issue short-lived codes.
- Changing your password signs out other SiloID sessions.
These controls reduce risk; no online service can promise absolute security. This statement is not an independent security certification.
Protect your identity
Check the domain before signing in. Do not enter your Google, bank, or email-provider password into SiloID. Never share verification codes or private keys. Only upload identity documents through a clearly identified, approved verification flow that explains its purpose and handling.
For an initial report, describe the affected page and issue without including passwords, tokens, identity documents, or other people’s data. A dedicated vulnerability-reporting and response policy is still being finalized.