Terms of Service

These Terms of Service are between you and BLINKHOST LTD, a Nigerian company registered under CAC number 9479867 ("BlinkHost", "we", "us"). They govern your use of BlinkHost's websites, control plane, developer tools and cloud services. Nothing in these Terms excludes a right or remedy that applicable law does not permit us to exclude.

1. The service

BlinkHost provides a cloud development and hosting platform, including project workspaces, connected source control, browser-based frontend development, isolated backend previews, production deployments, edge delivery, custom domains, backend modules, managed database tooling, project assets, storage and observability. Features, limits and support differ by plan and are described on our pricing and documentation pages.

2. Eligibility, accounts and authority

You must be at least 18 or otherwise legally able to contract, provide accurate information, protect credentials and promptly report suspected compromise. You are responsible for authorised users and activity under your account. If you use BlinkHost for an organisation, you represent that you have authority to bind it. Do not share an account where named user access is available.

3. Plans, prices, tax and changes

Our pricing and checkout pages identify the plan or add-on, billing interval, included limits, price, currency, renewal terms and applicable taxes before purchase. Prices are displayed in US dollars. You must provide accurate billing and country-of-consumption information. Payment-processing fees charged to BlinkHost are our operating costs unless a customer charge is clearly disclosed before purchase. Material price changes apply from a future billing period after reasonable notice and any consent required by law. Enterprise service is arranged through a separate order or agreement.

4. Payment, renewal, cancellation and refunds

Payments are handled by the processor disclosed at checkout. You authorise collection of the displayed total. Paid plans and recurring add-ons renew automatically after you authorise recurring collection at checkout. You may turn off renewal before the next charge; access normally continues to the end of the paid term. Failed or unverified payment does not extend paid entitlement. We may use a reasonable grace period and proportionate downgrade. Refunds and service remedies follow the Refund and Cancellation Policy and mandatory law.

5. Your content and responsibilities

You retain ownership of your code, data and other content. You grant BlinkHost a limited licence to retrieve content from an integration you authorise and to host, reproduce, transmit, process and display it only to provide, secure and support the service. BlinkHost writes to a connected repository only when an authorised user enables that access and requests the action. You must have the necessary rights and lawful basis, comply with the Acceptable Use Policy, protect secrets, configure appropriate access, and maintain exports or backups proportionate to your risk.

6. Security, suspension and changes

We use reasonable technical and organisational safeguards, but no online service is risk-free. We may limit or suspend affected access where reasonably necessary to address a security threat, illegal activity, material breach, non-payment, platform-integrity risk or urgent maintenance. Where safe and lawful, we will give notice and an opportunity to remedy. We aim to minimise impact and restore service promptly.

7. Intellectual property and feedback

BlinkHost and its licensors own the platform, software, branding and documentation, excluding your content. Subject to these Terms, we grant you a limited, revocable, non-transferable right to use the service during the applicable term. We may use feedback without payment or obligation, but will not publicly identify you without permission.

8. Third-party services

BlinkHost uses third-party infrastructure and service providers to operate the platform and supports integrations that you choose to connect. You control the account and repositories authorised for a source-control integration and can revoke that provider access. A third party's terms may govern your direct use of its service. BlinkHost remains responsible for its obligations under these Terms and applicable law.

9. Service standard and remedies

We will provide the service with reasonable care and skill. Except for express commitments and non-excludable rights, it is provided on an "as available" basis. If a paid service is not supplied, is materially defective or does not conform to an applicable commitment, contact us so we can investigate and, as appropriate, restore or re-perform it, provide credit, or issue a full or proportionate refund.

10. Liability

Neither party excludes liability for fraud, wilful misconduct, death or personal injury caused by negligence, or liability that cannot lawfully be limited. To the extent permitted by law, neither party is liable for indirect or consequential loss that was not reasonably foreseeable. For business customers, aggregate liability for other claims is limited to amounts paid for the affected service in the 12 months before the event. This section does not reduce mandatory consumer, confidentiality, intellectual-property or data-protection remedies where the law prevents that result.

11. Termination and data export

You may stop using free service or cancel paid service. We may terminate for an uncured material breach, illegality or serious security risk. Where practicable, we will provide reasonable notice and an opportunity to export content. Retention and deletion follow the Privacy Policy, legal duties, plan limits and documented backup cycles.

12. Disputes and Nigerian law

These Terms are governed by Nigerian law. Contact billing@blinkhost.me from an authorised address with the organisation, invoice or non-secret transaction reference, dates, amount, concise issue and requested resolution. We will review objective account, transaction and service evidence in good faith. The parties may agree to mediation; otherwise a competent Nigerian court may hear the dispute. This does not waive a right to complain to the FCCPC, NDPC, payment provider or another competent authority, or to exercise a statutory chargeback or remedy.

13. Changes and contact

We publish the current version and effective date. Material changes receive reasonable advance notice and renewed acceptance where required; urgent security or legal changes may take effect sooner with an explanation. Questions: billing@blinkhost.me.

Source templates, collaboration and Agency handoffs

You retain ownership of source you publish as a template. By making a template available, you grant BlinkHost the limited rights needed to store, scan, reproduce, display and deliver that template through the service. You also grant each authorized installer a worldwide, non-exclusive licence to use, copy, modify, build and deploy the installed source for their own projects, subject to any clearly disclosed third-party licence. You must have the rights needed to publish every included file and must not include secrets, personal data, client-confidential material or content you cannot redistribute.

Template publishers are responsible for the accuracy of their descriptions, declared dependencies, permissions and licences. BlinkHost may block, withdraw or limit a template or publisher to address security, infringement, fraud, legal or platform risk. Withdrawal prevents new installations but does not transfer ownership of source already lawfully installed. Automated scans reduce risk but do not guarantee that source is secure, suitable, error-free or free of third-party claims; users must review source before production use.

Workspace owners and administrators are responsible for the people they invite to source collaboration, the files and roles they grant, and timely revocation. Presence, synchronization, review suggestions and automated recommendations assist human work; they do not replace the customer's code review, testing, security assessment or deployment approval.

An Agency project handoff takes effect only when an authorized destination owner or administrator accepts it using an authorized repository. The initiating Agency confirms it has authority to offer the transfer; the recipient confirms it has authority to accept. Acceptance changes workspace ownership and access, removes prior repository role grants, and makes the destination workspace's plan, limits and billing applicable. Domains, paid add-ons, third-party accounts and contractual support obligations transfer only where BlinkHost or the relevant provider expressly confirms them.

Live source co-editing

Live co-editing synchronizes participating users' changes to a shared project document. Workspace owners and administrators control membership and guest access and are responsible for granting the minimum role and file scope required, choosing an appropriate expiry, and removing access when it is no longer needed. Each participant must be authorized to view or change the source they open.

When a connection is interrupted, the browser may retain unacknowledged edits locally and retry them after reconnecting. Customers should follow the editor's recovery message, compare recovered source before publishing and keep an independent copy of critical work. Network delay, device storage controls, browser data removal, conflicting sessions or service interruption can affect whether an unacknowledged local edit is recoverable.

Co-editing, presence and project autosave do not create a Git commit, push a branch or deploy a project. An authorized user must review the resulting source and use the relevant commit or publish action. Customers remain responsible for code review, testing, security assessment, licences and deployment approval.

Microsoft Marketplace orders

Orders placed through Microsoft Marketplace are billed and invoiced by Microsoft under the terms associated with that purchasing account. Microsoft controls the Marketplace payment method, tax document, cancellation process and refund process. BlinkHost controls access to the service and applies a Marketplace plan only after Microsoft confirms the subscription. You are responsible for selecting the intended BlinkHost workspace and maintaining authorized access to both accounts.

Marketplace and direct-payment subscriptions retain separate billing records. A payment, credit, cancellation or refund in one channel does not change the other unless BlinkHost and the relevant provider confirm that change. Conflicting, delayed or incomplete provider information may temporarily delay an entitlement change while we reconcile it; it does not authorize duplicate use or duplicate collection.

Referral and partner programmes

Only a currently published programme creates a potential referral benefit. Its stated eligibility, attribution period and benefit terms apply. The first valid attribution is retained. Self-referrals, existing-customer referrals, duplicate or misleading identities, reversed or disputed purchases, automated activity and conduct that breaches the programme terms may be rejected or withheld. BlinkHost may pause a programme prospectively and may review evidence before approving a benefit. These controls do not limit a customer's non-excludable legal rights or access to paid services.

Files uploaded through your applications

Hosted Object Storage lets your applications accept and deliver supported files. You are responsible for having the rights, notices and permissions needed to collect, store and use those files, and for applying appropriate access controls in your application. Storage use counts toward the allowance for your plan. BlinkHost may reject, quarantine or remove files that are unsafe, unlawful, prohibited by the Acceptable Use Policy or harmful to the service.

Asynchronous function runs

Event, scheduled, and background functions may be delivered more than once when a run is retried after a timeout or temporary failure. You are responsible for making handlers idempotent where repeated processing could create duplicate changes or charges. Function runs remain subject to your plan limits, runtime policy, published execution limits, and usage charges. Cancellation cannot reverse work already completed by your application.