Trust Center
How SHC applications handle personal data, and what we do not claim. Certificate numbers appear only with evidence. PIPL work is done; FIPS, HSM and 商用密码 schemes stay not applicable until a module or certificate exists.
Certification register
0
In process
0
2010
16
Trust Center sections
Certification register
No certification is published yet. We publish a certificate only once the certificate number and an evidence URL exist — until then, in-process targets are listed instead of badges.
Compliance mapping
How our engineering maps to the obligations our customers are audited against. Four states — certified with evidence, done, in process with a target date, or not applicable with a reason. Blanks and “TBD” are not published.
- Done
Personal information protection (PIPL)
PIPL
Zafonyx Local handles personal data; controls are documented as the product is operated.
- Not applicable
Cryptographic module validation
FIPS 140-3
The current catalogue does not include a hardware cryptographic module in a validation programme.
Reason: No module is in a FIPS 140-3 validation programme.
- Not applicable
Cryptographic module validation (international)
ISO/IEC 19790
Same scope as FIPS 140-3: no module product is listed for this scheme.
Reason: No cryptographic module is listed for ISO/IEC 19790.
- Not applicable
Commercial cryptography product certification
商用密码产品认证
No commercial cryptography product certificate is in process or published.
Reason: No 商用密码产品认证 is in process.
- Not applicable
Common Criteria evaluation
Common Criteria
No Common Criteria evaluation is in process.
Reason: No Common Criteria evaluation is in process.
- Not applicable
Payment-terminal HSMs
PCI PTS HSM
Payments use WeChat Pay or Alipay; SHC does not ship a PIN-entry HSM.
Reason: No product handles payment-terminal PIN entry.
- Not applicable
Information security management
ISO/IEC 27001
No ISO/IEC 27001 certificate is published.
Reason: No ISO/IEC 27001 certificate is published.
Security posture
Security posture paragraphs publish only with named approval metadata.
Responsible disclosure
Report a vulnerability and we will confirm receipt, triage it against CVSS and agree a disclosure timeline with you.
Email the security team with a description, affected product and version, and any proof of concept. Please encrypt if you can; our PGP key fingerprint is published in security.txt.