Effective date: October 31, 2026
This Installation Policy applies to the optional one-time $100 USD initial installation service. An eligible software licence must be purchased first. Installation is a separate payment made through the signed-in customer account and applies to an eligible software purchase belonging to that same account. It does not include another software licence, REG-KEY, download entitlement, or additional production domain.
1. Customer-provided environment
The customer must provide a registered domain or authorized subdomain, compatible hosting with SSL capability, 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;
- prepare the application data storage required by the purchased build;
- 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 through email or the existing private issue form when the customer must complete an external account step; do not email passwords or private access keys.
3. Bunny.net and processor credentials
R18 Entertainment LLC 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
After verified installation payment, support contacts the purchase email within 24-48 hours to begin coordination. This is a contact window, not a completion guarantee. The completion time depends on the customer's access, environment, prerequisites, responses, and third-party services.
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 LLC 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, its required application storage is configured, 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
The completed installation purchase is final and non-refundable under the No-Refund Policy except where mandatory law requires otherwise. Environment review, coordination, deployment, configuration, and other installation activity do not create a separate recurring fee or another software licence.