This pre-launch draft describes usage limits, maintenance, outages, attacks, and closure for Malkko, provided by smulsmul. The Privacy Policy and applicable law also govern privacy incidents. Paid-service provisions apply only after paid products and the relevant agreement are introduced.
1. Current availability
- Administrators create invited accounts. Public registration and paid checkout are unavailable.
- Current English learning is text-based and depends on external AI, networks, and the operating server.
- No separate uptime SLA or uninterrupted availability commitment is being sold.
- Paid-allowance deductions, automatic refunds, and automatic data export are not represented as implemented.
2. Usage limits
The preparation environment has a common limit of 400 AI requests per account per day, resetting at 9:00 a.m. Korea Standard Time, alongside short-term limits by feature. Request counts can differ from delivered results and include some failures and retries.
You may need to retry later after a limit or during a processing queue. Automated attempts to evade limits are prohibited. Before any paid service begins, technical safeguards, paid counting, deduction, restoration, and limit behaviour must be separately disclosed.
Changes reducing total provision require advance notice. Existing paid periods and allowances must be fulfilled or addressed through reasonable alternatives or refunds.
3. Maintenance and emergency restrictions
Major planned maintenance is normally announced at least 24 hours in advance, including expected start and end times and affected features. The scope and timing should minimise disruption.
Urgent threats such as exploitation, account compromise, DDoS, or overload may require restrictions before notice. Restrictions must be proportionate in scope and duration. Confirmed reasons, impact, progress, and user actions are communicated without delay.
A maintenance notice does not authorise indefinite interruption or remove settlement or damages obligations.
4. Reporting and assessing outages
Email smulsmul2020@gmail.com with:
- Your username and the incident time and time zone.
- App or browser and device type, affected feature, and error shown.
- Whether the issue continues and, if useful, a screenshot with personal data removed.
Do not send passwords, session cookies, API keys, or full learning conversations. The Operator reviews service records and reports together; users are not required to prove matters accessible only through internal server records.
Start and end times depend on actual core-feature availability and evidence. Partial outages are assessed by affected scope and duration. Device, connectivity, and service-side causes are distinguished based on facts.
5. DDoS, hacking, and other attacks
On suspected attacks, the Operator restricts affected paths, protects accounts and sessions, preserves relevant evidence, cooperates with providers and security authorities, restores service, and addresses recurrence. A potentially compromised system is not reopened without appropriate checks solely to accelerate restoration.
An external attack does not create a blanket liability exemption. Safeguards, response, foreseeability, controllability, fault, and actual harm must be assessed. Damages liability is distinct from settlement for undelivered paid service.
Ordinary delay, a network security incident, and a personal data breach are investigated separately. Absence of a confirmed leak is not presented as proof that no leak occurred. Known facts and open questions are communicated separately.
6. Incident reports and user notices
Applicable Korean network-security incident reporting is completed within 24 hours of awareness, and additional findings are reported within the statutory deadline.
Where an attack causes interruption or loss of functionality for two hours or longer, compromises user information or creates that possibility, or otherwise meets statutory notification conditions, affected users are notified without delay. Two hours is not a general waiting period or an extension to reporting duties.
Notices include known timing, causes and harm, response progress, protective user actions, remedies, and contact details. If causes are unknown, confirmed facts are notified first and updated when more is established.
Accounts currently have no registered email or telephone field. A lawful individual-notice channel must be established before launch. Website substitution is used only where legally permitted, such as a justified inability to identify contact information, and for the required period. A generic public notice does not replace every individual notification.
Separate personal-data breach notification and reporting duties are also assessed and met. This policy and internal targets do not extend statutory deadlines.
7. Restoration and refunds
There is no paid amount to refund for the current free preparation service. The Operator explains feasible restoration and learning adjustments. Free access does not exempt security and privacy duties or legal liability arising from fault.
After paid launch, confirmed core-feature non-delivery is assessed against the affected period, allowance, and contract. The proposed default is an extension for the undelivered time or refund of the corresponding amount, with the user’s preference confirmed. Incorrect deductions for undelivered results are restored.
More favourable applicable law, dispute-resolution standards, or separate agreements prevail. The cause alone does not justify rejecting all refunds. Cash refund rights are not replaced by credits without consent. Calculations, request routes, and deadlines also follow the Paid Service & Billing Terms.
8. Account restrictions and appeals
Restrictions for security or prohibited conduct are explained with the reason, scope, duration, restoration conditions, and appeal process. Urgent restrictions receive notice without delay afterwards.
Appeals go to the support email. The Operator reviews the evidence and the user’s explanation, communicates the outcome, and removes restrictions when their justification ends. Violations do not automatically forfeit every remaining paid entitlement; settlement and actual damages are assessed separately.
9. Planned closure
A planned full closure normally receives at least 30 days’ notice, including individual notice through available channels, covering:
- Reason, date, and features available before closure.
- When new charges and renewals stop, and refunds for undelivered paid service.
- Learning-record access, copy requests, and request deadlines.
- Deletion of accounts, learning records and backups, and separately retained statutory records.
- A post-closure contact for support, refunds, and privacy requests.
Automatic export is not currently implemented. Before closure, the Operator must verify and explain the available copy scope, format, and secure delivery method. If an unavoidable emergency prevents advance notice, known reasons and follow-up measures are communicated promptly. Settlement and statutory rights remain.
10. Contact and changes
- Operator: smulsmul / Beomjun Kang / Business Registration No. 815-31-01725
- Outage, security, account, and settlement contact: smulsmul2020@gmail.com
Policy changes state their content and application date. Material adverse changes follow the advance-notice procedure in the Terms of Service. Posting a document does not replace required consent, reporting, or notification.