JCITY PROCURE锦城云采

JCITY PROCURE / SECURITY BOUNDARIES

Be explicit about controls, residency, and acceptance gaps.

Security design and local tests do not replace cloud residency verification, penetration testing, classified protection assessment, or other required reviews.

01

Engineering controls

The current source includes organization-scoped access, PostgreSQL row-level policies, hashed sessions, role separation, audit records, and fail-closed external publishing.

02

Mainland data requirements

Production data, identity, files, logs, keys, and backups must actually operate in Mainland China. Production residency and historical Tokyo Supabase flows have not yet been fully verified.

03

No certification claim

Code scans, unit tests, and local builds are not represented as passing classified protection, cryptographic application, electronic trading, CA, or other external certification.

SERVICE STATUS

Development preview. Electronic trading and external social publishing remain disabled until the required approvals, integrations, and acceptance evidence are complete.