Terms of Service
Conditions for Nitroship application building, deployment and hosting, and the rights and duties of members and the Company.
This is a translation; the Korean version prevails.
Effective date: 2026-10-01
These terms apply to Nitroship, provided by 삼삼오오 (the ‘Company’). Please review them before registering or using a paid service.
Article 1 (Purpose)
These terms govern the rights, obligations, responsibilities and other necessary matters concerning use of Nitroship between the Company and members.
Article 2 (Definitions)
The terms used here mean the following.
- ‘Service’ means application building, deployment and hosting, domain connections, traffic and compute provision, billing and the related console, API and CLI.
- ‘Member’ means a person who creates an account and uses the Service under these terms.
- ‘Team’ is a unit for managing applications and billing. One team is created by default for each member at signup, and members may create additional teams and use teams together with multiple members according to their roles.
- ‘Application’ means a unit of deployments, domains and other resources managed by a team on the Service.
- ‘Member content’ means code, images, files and other materials that members upload or deploy to the Service.
- ‘User information’ means information stored on the Company's computing resources that a member or team owns or manages, including member content, application settings, environment variables and application end-user information.
- An ‘invoiced plan’ issues invoices based on usage each cycle; a ‘non-invoiced plan’ does not charge for usage exceeding included amounts.
- A ‘paid plan’ is a plan that carries platform or usage charges under the price book; a ‘free plan’ has neither platform nor usage charges under the price book. Invoiced and non-invoiced describe the billing method and are distinct from paid and free.
- The ‘Fair Use Policy’ is the policy at Fair Use Policy on prohibited conduct, usage standards and treatment of excess usage.
Article 3 (Applicable documents and priority)
These terms and the Fair Use Policy apply to the Service. If provisions conflict, the order is an individual agreement, service-specific conditions and price book, the Fair Use Policy, then these terms; a lower-priority document supplements matters not covered above it. Neither this order nor a separate agreement excludes mandatory protections for members or consumers under law. Personal data processing is governed by the Privacy Policy and applicable law.
Article 4 (Announcements and individual notices)
General announcements are posted on the Service. Where individual notice is required, the Company uses an available method such as the account email, team billing email or console notification. Operational team matters are directed to owners; payment and pricing matters are directed to owners and billing-role members or the billing email. Please keep email and billing details current. If the law specifies another method, that method applies.
Article 5 (Amending the terms and policies)
The Company publishes these terms and the Fair Use Policy, which is part of them. It announces the effective date, reasons and before-and-after content of amendments generally at least 7 days in advance. Changes disadvantageous or important to members are announced at least 30 days in advance and individually notified under Article 4. Members who disagree may terminate before the amendment takes effect; the Company obtains separate consent when required. In particular, increasing recurring charges for consumers or converting a free service to a paid one requires advance information and separate consent under Article 13(6) of the Electronic Commerce Act, in addition to the general amendment notice.
Article 6 (Registration and paid use)
People aged 14 or older may register after confirming that they meet this age requirement, providing accurate information and accepting the mandatory terms. The same age confirmation and acceptance apply to email and GitHub registration. The agreement is formed when the Company's acceptance reaches the applicant. The Company may reject applications involving false information, identity theft, unauthorized use of another person's payment method, a previous serious violation or an unlawful purpose; it may defer acceptance until capacity, payment or technical problems are resolved, and will explain the reason. Marketing consent is not a condition of registration. Paid services (payment method registration, paid plans and paid options) are available only to people aged 19 or older, and the Company obtains confirmation that the member is 19 or older immediately before payment.
Article 7 (Contracting parties and team permissions)
The member who is the team owner is the contracting party and fee payer for the team. When the billing profile identifies a business, that business is the contracting party, and the team owner confirms authority to represent it. Individual team members who have not separately agreed to guarantee payment are not personal guarantors of team charges. An owner manages the team, its members and applications; a member manages applications; a billing-role member manages billing settings; and a viewer has read access. The Service's permission guidance describes specific access rights. A team's applications, deployments, domains and other resources belong to the team, not to an individual by virtue of a change of owner or removal of a member. An owner must first transfer ownership to leave a team.
Article 8 (Duties of the Company and members)
The Company complies with applicable law, protects the Service and user information, and works to restore service promptly after an outage. Members can check usage and billing history in the team console and submit legitimate complaints to team@nitroship.co. The Company handles these promptly and, if resolution is delayed, explains the reason and expected handling schedule. Members must safeguard account credentials, manage their application's source, settings and end-user notices, and immediately report unauthorized use. They must keep team contact and billing details current and check usage by members to whom they granted permissions. Responsibility for the platform, security and metering within the Company's control is not shifted to members.
Article 9 (Service provision, changes and interruptions)
The Company announces scheduled maintenance in advance and promptly notifies members after an unannounced interruption caused by an urgent outage, disaster or security incident. Under Article 25 of the Cloud Computing Act and Article 16 of its Enforcement Decree, it gives notice without delay of a security incident, a leak of user information, or an unannounced outage lasting at least 10 consecutive minutes or occurring at least twice within 24 hours for a combined duration of at least 15 minutes. If the cause is not yet known, it first shares confirmed facts and ways to prevent further harm, then supplies the cause once known. It individually notifies members 30 days before materially reducing or ending a paid service and settles the undelivered portion. Availability commitments and service credits are governed by Article 10. Beta features and the beta /v1 API may change without compatibility aliases; important changes are announced in advance. An unverified custom domain may be cleared after the default period of 7 days following registration, so check its verification status and deadline in the Service.
Article 10 (Service Level Commitment)
The Company commits to monthly availability of at least 99% only for production hosts on paid plans. Free plans, preview hosts, beta features and beta APIs are provided as-is, without an availability guarantee or service credits.
Monthly availability is measured by the Company's monitoring of production host availability and calculated as ‘(total minutes in the month − downtime minutes) ÷ total minutes in the month’. Downtime means a period of at least 5 consecutive minutes during which the production host does not respond or returns server errors due to a Company-side cause.
Downtime excludes scheduled maintenance announced in advance under Article 9; failures caused by the member's code, images, settings, DNS or external services; restrictions or suspensions under the Fair Use Policy or the prohibited-conduct rules in Article 14; suspensions for budgets, included-usage overages or failed payments under Article 12; and actions taken at the member's request. Force majeure and wide-area outages at cloud or network providers that the Company could not have avoided with reasonable care are also excluded from downtime.
Monthly availability below 99% but at least 95% earns a service credit of 10% of that month's platform fee; availability below 95% earns 25%. Total service credits never exceed that month's platform fee. The member must claim by email to team@nitroship.co within 30 days after the month ends, identifying the team, application and incident time. After confirming the claim, the Company issues the credit as an operator-granted credit under Article 11 for application to later invoices; credits are not paid out in cash.
The Company's liability and the member's remedy for failure to meet the availability commitment itself are limited to the service credits in this article. This does not limit liability for damage caused by the Company's intent or gross negligence or consumers' statutory rights, including withdrawal and refunds under Article 13.
Article 11 (Fees, payment and credits)
Platform charges, region-specific traffic and compute usage, and the charges and included amounts for CDN modes and tiers follow the price book shown before payment and the team's billing settings. Non-invoiced plans do not charge for overages; an invoiced plan's invoice may include the preceding cycle's usage and, when applicable, the next cycle's platform charge. Monthly usage credits apply only to traffic and compute usage charges for that cycle, do not roll over and do not apply to platform or Flat Rate CDN tier charges. Credits granted separately by an operator, unlike monthly usage credits, are applied to the total of invoices in any billing currency. If a Flat Rate CDN tier's included amount is exceeded, the tier may automatically move up for the next cycle; overages beyond the highest tier are charged separately under the price book. Unit rates, currency, taxes, cycle and effective timing can be reviewed before payment. Registration and charging of the chosen payment method use Stripe or NicePay (KRW). For disputes over charges or overpayments, contact team@nitroship.co. After review, the Company returns overpayments or settles them lawfully.
Article 12 (Budgets, allowances and failed payments)
The budget set on an invoiced plan measures traffic and compute usage after monthly usage credits; platform and Flat Rate CDN tier charges are excluded. Delayed accounting and alerts mean it is not a hard cap on total invoiced charges. When suspension for an allowance overage or reaching a budget applies under the plan and the Company's billing suspension policy, the production host may stop serving; the same suspension does not apply to preview hosts. The Company emails the billing address after a failed payment and gives an opportunity to update the payment method. If payment remains unsuccessful after up to four attempts, the production host may stop serving; a successful payment removes suspension arising from that payment failure. Other reasons for suspension and charges incurred up to termination remain separate.
Article 13 (Withdrawal and refunds)
Where the Electronic Commerce Act applies to a consumer transaction, a member may request withdrawal at team@nitroship.co within 7 days including the day they receive the contract details (or, if later, the day service begins). If service differs from its description, advertising or contract, the request may be made within 3 months of receipt and within 30 days of when the discrepancy was or could have been known. Statutory restrictions on withdrawing for a portion already supplied apply only when legal requirements, including advance notice, are met; a separable portion not yet supplied is refunded separately. When a refund becomes due, the Company returns payment or requests cancellation within 3 business days and pays statutory interest for delay. It distinguishes delivered usage and cycle charges from undelivered portions and charges no penalty for withdrawal. Service not provided due to the Company's fault and overpayments are refunded or compensated under applicable law. Consumer withdrawal rules may not apply unchanged to business members, whose rights under individual agreements and applicable law remain protected.
Article 14 (Prohibited conduct and restrictions)
Members must not distribute unlawful or rights-infringing content, engage in phishing, fraud or spam, deploy malware or conduct unauthorized attacks, use another person's payment method, circumvent charges or limits, abuse resources or disrupt other members' service. The Fair Use Policy (Fair Use Policy), part of these terms, details prohibited conduct and usage standards. For a remediable violation, the Company gives notice of the reason, affected resource and remedy, and a 7-day cure period before restricting use as necessary. For a security incident, payment fraud, legal requirement or imminent harm to another member, it may immediately impose the narrowest necessary restriction, prioritizing a deployment, domain or application, and give notice without delay. Members may explain or appeal at team@nitroship.co; the Company reports the outcome and lifts a restriction when its cause is resolved. Repeated or intentional violations or serious violations not remedied are grounds for termination under Article 17. Good-faith vulnerability reporting in accordance with the Fair Use Policy alone will not be penalized.
Article 15 (Rights-infringement reports and response)
To report an invasion of privacy or reputation, copyright infringement or unlawful content, send the affected URL or domain, description and supporting material, and a reply address to team@nitroship.co. The Company reviews the report and its scope of control over the Service and, where applicable, handles removal or temporary measures and notice to the poster under Article 44-2 of the Information and Communications Network Act separately from cessation of reproduction or transmission, notice and legitimate restoration requests under Article 103 of the Copyright Act. Upon learning of public circulation of illegal sexual images or child or adolescent sexual exploitation material, it promptly removes or blocks access as needed. To the extent permitted by law and harm prevention, it informs the affected member of the grounds and appeal procedure, and preserves relevant material when necessary.
Article 16 (Member content and user information)
Rights in member content remain with the member or rightful owner. Members grant the Company a nonexclusive license only as necessary to provide, store, transmit and back up the Service and deploy within the public settings they choose. The Company does not use member content for AI model training or marketing. Under Article 27(1) and (2) of the Cloud Computing Act, it does not use user information outside the purpose of providing the Service or disclose it to a third party without consent. It follows statutory exceptions, such as a court's production order or a warrant issued by a judge, and lawful separate consent procedures. Members must manage rights in the content they deploy and required notices to application end users; the Company's trademarks and software remain the property of the Company or rightful owner.
Article 17 (Team deletion, account closure and termination by the Company)
A team's agreement ends when an owner deletes all active applications and deletes the team in the console; the same rule applies to a team created at signup. Account closure is requested by the member at team@nitroship.co and processed by an operator; teams in which the member is the sole member are deleted with the account upon closure. Before closure, the member must delete all active applications in teams in which they are the sole member and transfer ownership of, or delete, any team with other members of which they are the sole owner. Leaving a team with other members does not end that team's agreement. If arrears persist or an Article 14 violation is repeated, intentional or serious and unremedied, the Company may terminate after giving the reason, means of remediation and a 7-day opportunity to cure. For urgent risks, it may first impose a narrowly tailored restriction and promptly notify the member. For termination due to the Company or closure of the business, it gives individual notice 30 days beforehand of the date, reason, means of checking information and contact point, and also posts a business closure on the Service. It also identifies any refund due on termination. Usage fees through the end are finally billed, and automatic payment retries for unpaid invoices finish before the destruction deadline after termination, while uncollected transaction records are separately retained to the extent required by law. No platform fee is charged for the subsequent unused cycle.
Article 18 (User information at termination)
As a special contractual arrangement under Article 27(5) of the Cloud Computing Act, members retain the originals of their deployed source and settings, so the Company does not separately return user information when the agreement ends. Members must retain what they need before termination. Where the Company gives 30 days' notice of termination for its own reasons or business closure, members can inspect settings, environment variables and billing history in the console during that period. Within 7 days after termination caused by team deletion or account closure, the Company permanently deletes user information it holds by a method that prevents restoration. If an app is deleted independently of contract termination, the Company also permanently deletes that app’s user information in the same manner within 7 days of its deletion. B2 objects held by the Company are permanently deleted, including previous versions, when deletion is processed; the corresponding Cloudflare cached objects managed by the Company are also subject to destruction. The Company cannot delete copies already downloaded by members or third parties. Records subject to statutory retention, such as billing and payment transactions, are segregated from user information and retained for the required period, then destroyed. Processing of a member's own account personal data and exercise of rights are governed by the Privacy Policy.
Article 19 (Damages and exclusions)
The Company compensates members for damage caused by its intent or negligence in accordance with this article. To the extent permitted by law, it is not liable for damage caused by force majeure not attributable to it, member content, or members' own configuration or security management. An outage in underlying infrastructure selected and managed by the Company does not, by itself, remove its liability for intent or negligence.
When the member is a business (for example, where the billing profile identifies a business under Article 7), the Company's liability for ordinary negligence is capped at the total fees the team actually paid the Company in the 3 months before the incident. In that case, indirect damages, special damages and lost profits are not compensated. This cap and these restrictions on types of damage do not apply to damage caused by the Company's intent or gross negligence, damage to life or body, or members who are consumers.
The free plan is offered free of charge and as-is; the Company does not guarantee its availability or continued provision. A member who intentionally or negligently causes damage to the Company compensates it under applicable law. The limits in this article do not restrict liability that cannot be excluded by law or consumers' mandatory rights.
Article 20 (Dispute resolution and governing law)
The Company promptly handles complaints and disputes submitted to team@nitroship.co and, if handling is delayed, explains the reason and expected schedule. South Korean law governs disputes; litigation not resolved by agreement shall be brought before a court having jurisdiction under the Civil Procedure Act.
Supplementary provision
These terms take effect on 2026-10-01.