SECURITY & COMPLIANCE
Audiograms, questionnaires and medical histories are sensitive. Here are the controls we actually run.
- In transit
- TLS 1.3
- At rest
- AES-256-GCM (TDE)
- Keys
- KMS-managed · rotated
- Data residency
- Taiwan
- Compliance
- Taiwan PDPA
- Access
- Least privilege · audit log
Defense in depth
One audiogram, five layers of protection.
Follow one sample audiogram from the store to the database. Each layer guards on its own — no single line of defense.
- 01
Encrypted in transit
Every hop from store tablets and PCs to the cloud is encrypted with TLS 1.3 and forward secrecy — and service-to-service traffic is TLS too.
TLS 1.3Intercept the traffic and all you get is ciphertext.
- 02
Role-based access
One account per person, access by role: staff see the customers assigned to them, managers their own store, HQ the aggregate across stores.
RBACLeast privilege: only what the job needs.
- 03
Audit log
Key actions — viewing, adding, exporting, changing permissions — are logged: who, when, from which store, and what.
who · when · whatReviewable after the fact, with alerts on unusual access available per deployment.
- 04
Encrypted at rest, KMS keys
On write it is encrypted with AES-256-GCM (TDE). Keys are generated and held in a dedicated KMS, rotated on policy, and kept apart from data and backups.
AES-256 · KMSA leaked disk exposes nothing.
- 05
Hosted in Taiwan, under the PDPA
Application state stays in Taiwan and is collected, processed and used under Taiwan's PDPA. Data subjects can access, correct and delete it.
PDPAYour data stays yours — export and deletion per contract.
Compliance
Compliance status
Labelled honestly: “Aligned” and “Planned” items are not third-party certified, and we never show a badge we don’t hold.
01Taiwan Personal Data Protection Act (PDPA)
In complianceOur operative legal obligation in Taiwan, implemented across data handling.
Taiwan Personal Data Protection Act (PDPA)
In complianceOur operative legal obligation in Taiwan, implemented across data handling.
- Personal data collected, processed and used for specified purposes
- Data-subject rights to access, correct and delete
- Application state hosted within Taiwan
- Sub-processing bound by contract and confidentiality terms
02ISO/IEC 27001（ISMS）
Aligned, not certifiedBuilding controls toward the ISMS framework; not yet certified.
ISO/IEC 27001（ISMS）
Aligned, not certifiedBuilding controls toward the ISMS framework; not yet certified.
- Risk assessment and risk management
- Security policies and objectives
- Continuous monitoring, measurement and improvement
- Internal audit and management review
Scope follows contract and deployment; certification timeline is covered in the security package.
03HIPAA Security Rule
Aligned, not certifiedOur technology and processes align with its administrative, physical and technical safeguards.
HIPAA Security Rule
Aligned, not certifiedOur technology and processes align with its administrative, physical and technical safeguards.
- Risk analysis and management
- Security awareness training
- Security incident procedures
- Vendor management and contracts
- Facility access control and monitoring
- Workstation and device security
- Media disposal and destruction
- Access control (unique user IDs, automatic logoff)
- Audit controls and logging
- Integrity controls (no improper changes)
- Transmission security (TLS)
04ISO/IEC 27701（PIMS）
PlannedPrivacy-management extension, planned after 27001.
ISO/IEC 27701（PIMS）
PlannedPrivacy-management extension, planned after 27001.
- Personal-data processing flows and accountability
- Data-subject rights request handling
Evaluated against customer privacy-governance needs.
05SOC 2 Type II
PlannedOn our compliance roadmap; no audit under way.
SOC 2 Type II
PlannedOn our compliance roadmap; no audit under way.
No auditor or report yet. Until one exists, we can share a self-assessment of the corresponding controls — with no implication that an audit has been passed.
Technical controls
From client to backup, every layer has its own safeguard.
- In transitTLS 1.3
- EdgeWAF · DDoS
- Network isolationPrivate VPC
- At restAES-256-GCM
- Key managementKMS
- Backup & recoveryAES-256
- 01TLS 1.3 (TLS 1.2 minimum)
In transit
- All external traffic encrypted with forward secrecy against MitM
- Service-to-service traffic is TLS too
- 02API Gateway · WAF · DDoS
Edge
- API Gateway enforces authentication, authorization and rate limits
- WAF blocks OWASP Top 10 (SQLi, XSS, CSRF…)
- 03Private VPC · Zero Trust
Network isolation
- Backend and data stores sit in a private network, off the public internet
- Zero trust: no connection is trusted by default
- 04AES-256-GCM (TDE)
At rest
- Encrypted on write — a leaked disk exposes nothing
- 05KMS
Key management
- Generated and held in a dedicated KMS, rotated on policy
- Scoped per role and service; kept apart from data and backups
- Key usage and authorization changes are traceable
- 06AES-256 · immutable
Backup & recovery
- Encrypted with separate keys and locked immutable against ransomware
- Retention and recovery targets set per contract
- Recovery and data-export procedures available on request
Threats we mitigate
- Unauthorized access & brute force
- Credential & token theft
- Accidental deletion & misuse
- Scanning & injection attacks
- Insider privilege abuse
- Backup / key single points of failure
Access & audit
Layered by role — each gets only what the job needs.
HQ: totals across every store
- 01Headquarters
- Can seeAggregated data across all storesCan doPermissions, report export, system settings
- 02Store manager
- Can seeOwn store's data and customer recordsCan doAssign tasks, store reports, customer management
- 03Store staff
- Can seeCustomers assigned to themCan doAdd records, update progress, view recommendations
Audit & data scope
- Access logs: key actions are logged for review
- Anomaly alerts: configurable for unusual access (per deployment)
- Data covered: audiograms, questionnaires, medical-history summaries, consult and follow-up records, store activity logs
- Classification: sensitive (personal health info) / internal operations / general
Shared responsibility
- Encryption in transit and at rest
- Access control and roles
- Audit logging and monitoring
- Backup and disaster recovery
- Patching and updates
- Accounts and passwords
- Role and permission grants
- Revoking access when staff leave
- Devices and physical security
- Internal security SOPs and training
Data lifecycle
From collection to deletion, every step has a rule.
- 01
Collect
Collected for a specified purpose — only what the service needs.
- Specified purpose
- Classified: sensitive / internal / general
- 02
Use
Opened by role, key actions logged, encrypted in transit and at rest.
- Least privilege
- Audit log
- TLS 1.3 · AES-256
- 03
Retain
Backups are encrypted with separate keys and locked immutable; retention and recovery targets are set per contract.
- Separate keys
- Immutable backups
- Hosted in Taiwan
- 04
Export & delete
Your data stays yours — export and deletion per contract; data subjects can access, correct and delete.
- Export per contract
- Data-subject rights
Incidents
Incidents & subprocessors
Incident response
Once an incident affecting customer personal data is confirmed, we aim to notify affected customers within 72 hours, per contract and applicable law.
A defined process: detect, contain, root-cause, recover.
- Detect
- Contain
- Root-cause
- Recover
Subprocessors
A small set of cloud infrastructure and managed-service providers; application state stays in Taiwan. Full list provided under NDA.
FAQ
FAQ
Trust Center
Request the security package
Confidential — shared under NDA for your review, not as public downloads.
- Security whitepaper and controls list
- Data Processing Agreement (DPA) template
- Subprocessor list
- Penetration-test summary (as available)
This page describes the standard configuration; actual scope follows your engagement and contract.