LOCALON / TRUST CENTER
Everything you need to review,
in one place.
Who runs it, what works today and what does not yet, and who owns the data — the first things reviewers check.
01Operator
- Name
- LocalON OS
- Representative
- Kim Haktae
- Business reg. no.
- [to be confirmed]
- Address
- [to be confirmed]
- Phone
- [to be confirmed]
02Product status
The same screen can be at different stages. All apps on this site are currently demo UI.
| Stage | Meaning | Scope |
|---|---|---|
| Demo UI | Runs in the browser with demo data. No payments, SMS or real agency integration. | [to be confirmed] |
| Implemented | Runs on real servers and databases and has passed internal testing. | [to be confirmed] |
| Planned integration | Connected after contract and API terms are confirmed with external agencies and businesses. | [to be confirmed] |
| Pilot | A local government signs an agreement and residents actually use the service. | [to be confirmed] |
03Operating and data principles
- Data ownership — Residents' personal data, transaction data and public information are held by the local government. Only aggregated or pseudonymised data is used for analysis and AI, never for profit.
- Regional operating rights — The regional operating organisation handles settings, modules and releases; payment keys, authentication keys and audit logs are held only by the responsible officials.
- Security responsibility — Designed for public-sector security standards: separation of privileges, encryption, audit logs, backup and recovery. Certification status: [to be confirmed].
- Incident response — Monitoring and backup per regional installation, so national transactions do not sit on one server. Response-time commitments are written into the agreement.
- Open-source scope — The shared foundation, data standards and integration specifications are permanently open. Only secrets and real data stay private.
04Review materials
One-page overview PDF (Korean) Technical architecture summary Regional proposals Request full proposals and cost materials (company or institution email) Open-source plan Public GitHub repository — coming soon
05What counts as evidence
Deployed
A region with a signed agreement where residents use the service. None at present.
In discussion
Presentations and meetings held, materials exchanged. [Region names published only with the partner's consent]
Demo example
The demo apps, regional proposals and the regions, shops and amounts on screen. All are examples, not deployments.
06After you contact us
- ConsultationWe reply within 2 business days
- RequirementsRegion, department, integrations and schedule (30 min)
- Demo15 minutes of real screens plus Q&A, on site or online
- Pilot discussionScope, period, roles and data terms drafted as an agreement