In the event that Bitkub Online Co., Ltd. ("Company") experiences circumstances or situations that may affect its services, potentially leading to temporary service unavailability (such as system maintenance), or changes to operational systems related to its services, the Company will notify customers in advance through its official communication channels. The notification period will depend on the urgency and nature of the event, categorized as follows:
General announcements: These refer to announcements for events impacting a minority of customers, affecting no more than 3 systems, or known well in advance (such as a temporary suspension of the Call Center due to building electrical system upgrades). The Company will notify customers at least 24 hours prior to such events.
Urgent announcements: These cover announcements for events affecting no more than 3 systems but requiring urgent suspension, or impacting more than 3 systems (such as the level of a digital asset in the Company’s wallet system decreasing to or below a specified threshold, or emergency technical issues whether originating from the Company's systems or those of related service providers). The Company will notify customers as soon as possible, or within 30 minutes, but no later than 24 hours.
Sensitive announcements: These include announcements for events significantly impacting a large number of customers (or all customers), or events concerning the executive team or the Company as a whole. The Company will notify customers as soon as possible, or within 4 hours, but no later than 72 hours.
Please note that these notification periods may be subject to change based on circumstances and suitability.
To ensure you receive timely updates from the Company, we kindly advise that you closely monitor information and updates via the Company's official communication channels.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article