Terms of Service

1. The service

IPFSHost provides managed static website hosting on the InterPlanetary File System (IPFS) and compatible content-addressed storage — similar in workflow to modern static hosts (Git or ZIP deploy, preview URLs, custom domains, SSL, rollback), with pinning and gateway delivery operated by us.

You may connect GitHub or GitLab repositories, upload ZIP archives of built sites, attach custom domains, promote deployments, and use our REST API for automation. Each successful publish receives a content identifier (CID) that addresses your build output on the network.

We do not operate general-purpose compute, PHP/MySQL runtimes, server-side rendering, or databases on pinned site content. APIs, auth backends, and dynamic logic must run on infrastructure you control and be called from the browser or your edge layer.

Service tiers, rate limits, storage quotas, and feature flags may change. We may label parts of the product as alpha or beta; those areas may change or be withdrawn with limited notice.

2. IPFS pinning & delivery

When you deploy, IPFSHost pins your static assets to storage nodes and exposes them via our HTTPS gateways and your custom domains. Content is immutable per CID — redeploying produces a new CID while prior versions may remain addressable until unpinned or replaced per your rollback settings.

Because IPFS is a peer-to-peer network, content may be cached or replicated by cooperating nodes and retrieved through public gateways while actively pinned. We cannot guarantee that every third-party copy disappears immediately when you delete a site; see the Acceptable Use Policy and Privacy Policy for takedown and data handling.

Gateway path routing for single-page apps (history mode) requires that your build includes the correct fallback paths (e.g. index.html) — documented at /developers.

3. Accounts & security

You must provide accurate registration information and keep credentials confidential. You are responsible for all activity under your workspace, including API keys and OAuth-linked Git access.

Invite-only or alpha registration may apply. You must be at least 16 years old (or the minimum age in your jurisdiction). If you register on behalf of a company, you represent that you have authority to bind that entity.

We may require email verification before full dashboard access. We may suspend or terminate accounts that violate these Terms, the Acceptable Use Policy, or law, or that threaten platform or network integrity.

4. Your content & IPFS

You retain ownership of content you deploy. You grant IPFSHost a worldwide, non-exclusive license to host, pin, cache, transmit, and display your content solely to operate the service (including gateways, backups, and replication to storage nodes you do not manage).

Content on IPFS is addressed by cryptographic hashes (CIDs). Identical bytes produce the same CID. Published builds may be retrievable via public gateways or third-party IPFS nodes while pinned or cached, even after you delete a site from the dashboard — see our Acceptable Use Policy and takedown process.

You represent that you have all rights necessary to deploy your content and that it does not infringe third-party rights or violate law.

5. API & automation

API keys are tied to your workspace and project scopes. Treat secrets like passwords — revoke compromised keys immediately. Automated deploys and uploads must respect rate limits and Acceptable Use rules.

We may log API usage for security, billing, and abuse prevention. Breaking changes to the API will be communicated via documentation or changelog where practicable.

6. Acceptable use

Use of the service is subject to the Acceptable Use Policy. Prohibited material includes malware, phishing, illegal content, and other categories listed there. We may remove pins, block delivery, or suspend accounts without prior notice where required by law or to protect users and infrastructure.

7. Third-party services

Git providers (e.g. GitHub, GitLab), DNS registrars, email providers, optional external pinning partners, and public IPFS gateways are third-party services. Their terms apply to your use of those services. We are not responsible for outages or actions of third parties.

8. Plans, fees & taxes

Free and paid plans may be offered with usage limits (storage, bandwidth, build minutes, domains). Current limits are shown in the dashboard and may change with notice where required.

Paid fees, if applicable, are billed according to the plan you select. Taxes may apply. Failure to pay may result in suspension of deploys or downgrade to free limits.

9. Availability & disclaimers

The service is provided "as is" and "as available". We strive for high availability but do not guarantee uninterrupted access, permanent retention of every CID, or compatibility with every framework without static export.

Maintenance, incidents, and third-party network conditions may affect deploys and site delivery. Status information is published at /status.

10. Limitation of liability

To the maximum extent permitted by law, IPFSHost and its operators shall not be liable for indirect, incidental, special, consequential, or punitive damages, or loss of profits, data, or goodwill, arising from use of the service.

Our aggregate liability for any claims relating to the service in a twelve-month period is limited to the greater of (a) amounts you paid us for the service in that period or (b) fifty US dollars (USD $50), except where liability cannot be limited under applicable law.

11. Indemnification

You agree to indemnify and hold harmless IPFSHost from claims, damages, and expenses (including reasonable legal fees) arising from your content, your use of the service, or violation of these Terms or applicable law.

12. Termination

You may stop using the service and request account deletion through the dashboard or support. We may terminate or suspend access with notice where practicable, or immediately for serious violations.

Upon termination, we will cease new pinning and delivery under your account subject to technical retention and backup cycles described in the Privacy Policy.

13. Changes

We may update these Terms. Material changes will be posted on this page with an updated effective date and, where appropriate, notified by email or in-dashboard notice. Continued use after the effective date constitutes acceptance.

14. Governing law & disputes

These Terms are governed by the laws applicable to the operator of IPFSHost, without regard to conflict-of-law rules. Courts in that jurisdiction shall have exclusive venue for disputes, unless mandatory consumer protection laws in your country require otherwise.

Contact us first at the address below to resolve disputes informally.

15. Contact

Legal & Terms: legal@ipfshost.io

Support: support@ipfshost.io