Skip to content
OhFuckOhYeah
HomePricingFAQCustomer login
Legal

Installation Policy

Scope and prerequisites for the $380 USD software-plus-installation package.

Effective date: August 4, 2026

This Installation Policy applies when a customer purchases the $380 USD package. That price is the total for the current OhFuckOhYeah software licence plus the initial installation service described below.

1. Customer-provided environment

The customer must provide a registered domain or authorized subdomain, compatible hosting, SSL capability, database credentials, file or control-panel access, and any permissions reasonably necessary to install and test the Software. The customer remains the account owner for all third-party services.

2. Included installation work

  • review the supplied hosting environment for the published minimum requirements;
  • upload and deploy the protected Software build in the selected domain's web root;
  • create or connect the customer-provided database and apply the required schema;
  • configure core environment values supplied by the customer;
  • activate the purchased one-domain licence;
  • confirm that the public application and administration login load and perform the basic expected installation checks;
  • coordinate by email or telephone when the customer chooses to provide credentials or must complete an external account step.

3. Bunny.net and processor credentials

R18 Entertainment cannot create, approve, fund, or own the customer's Bunny.net or payment processor account. If the customer has already created an account and requests credential-assisted configuration, the parties may coordinate access necessary for the initial setup. The customer may instead enter credentials through the Software administration area after handoff.

4. Excluded work

Unless separately quoted in writing, installation does not include:

  • purchasing or creating domains, hosting, Bunny.net, processor, email, or other third-party accounts;
  • processor underwriting, approval, compliance submissions, reserves, disputes, or payment-policy advice;
  • custom themes, custom features, source-code modifications, migrations, integrations not included in the purchased release, or repairs to unrelated software;
  • uploading customer videos, images, categories, performers, courses, pages, terms, subscriber records, or other catalog data;
  • operating, moderating, marketing, monitoring, backing up, or maintaining the customer's platform after handoff;
  • ongoing support, future versions, updates, server administration, malware cleanup, or performance tuning;
  • work made necessary by unsupported hosting restrictions, third-party outages, invalid credentials, or customer changes after completion.

5. Scheduling and cooperation

The customer must respond within a reasonable time, provide valid access, make required third-party decisions, and avoid changing the environment while installation is in progress. Delays caused by missing information, unavailable credentials, processor approval, DNS propagation, host restrictions, or third-party services extend the completion time.

6. Credentials and security

The customer should create temporary or limited credentials where possible and rotate them after handoff. R18 Entertainment will use supplied credentials only for the agreed work and reasonable troubleshooting related to that work. The customer is responsible for removing access when it is no longer required.

7. Completion standard

Installation is complete when the purchased build is deployed in the agreed compatible environment, the database is connected, the licence is activated, and the main public and administration entry points pass the initial operational verification. Completion does not depend on the customer having uploaded content, obtained processor approval, funded Bunny.net, completed branding, or launched publicly.

8. Customer changes after handoff

Problems caused by later customer edits, deleted files, changed credentials, expired services, host migration, domain changes, plugins, unsupported code changes, third-party policy changes, or compromised accounts are not part of the original installation service.

9. Refunds

Installation scheduling and work are subject to the No-Refund Policy. Work becomes non-refundable once environment review, coordination, deployment, configuration, or other installation activity begins, except where mandatory law requires otherwise.

© R18 Entertainment. All rights reserved.Terms · Privacy · Refund policy