Version History
Effective dates and changes for each document. Superseded versions remain readable.
When you register, you agree to the version of each document in force at that moment. If a document is later amended, the version you agreed to stays available at the addresses below, and archived copies are never edited.
Terms of Service
| Effective | Status | Main changes | Archived copy |
|---|---|---|---|
| 1 October 2026 | In force | First issue. | View |
Privacy Policy
| Effective | Status | Main changes | Archived copy |
|---|---|---|---|
| 1 October 2026 | In force | First issue. | View |
App Permissions
| Effective | Status | Main changes | Archived copy |
|---|---|---|---|
| 1 October 2026 | In force | First issue. Sets out the permissions Koroute and WellHour request, when each is requested, what happens if declined, and what is sent to our servers. | Same as current |
How versions are kept
Archived copies are fixed at an address containing their effective date:
/en/terms/<effective-date>.html— for example /en/terms/2026-10-01.html/en/privacy/<effective-date>.html— for example /en/privacy/2026-10-01.html- The Korean documents use the same structure without the
/en/prefix.
The Terms of Service and Privacy Policy addresses always point to the version currently in force. Archived copies are never edited once published; even a typo is corrected by issuing a new dated version, because members have already agreed to the text as it stood.
Notice of amendments
Amendments are announced in the Services at least 7 days before they take effect (30 days for changes unfavourable to members or otherwise significant), stating the effective date and the reason. Unfavourable changes are also notified individually. The full procedure is in Article 3 of the Terms and section 15 of the Privacy Policy.