Terms and Conditions

1. Website use and eligibility

Use the website lawfully and only for legitimate purposes. You must have the authority to act for any business you represent and to provide information or materials associated with a request. Do not use the site to interfere with its operation, attempt unauthorized access, distribute malicious code or submit information that infringes another person’s rights.

The site is intended to explain services and provide a starting point for business discussions. It is not a marketplace for immediate app purchases, a payment processor or a guarantee that any particular project will be accepted. An engagement begins only when the relevant scope and commercial terms have been agreed.

2. Information and illustrative material

Service descriptions explain the general type of work available. They do not describe an unlimited package or establish a particular timeline without a written scope. The website’s photographs and interface graphics are illustrative visual material and are not represented as customer projects, client endorsements or images of a specific operating location.

We aim to keep the descriptions useful and current. Technical choices, platform policies and service availability can change. If a detail is material to a purchase decision, it should be confirmed in the written proposal rather than inferred from a visual element or general headline.

3. Local form and communications

The project form validates information in the browser and displays a local confirmation. It does not send an email, submit a delivered request or create a stored company enquiry. The on-screen confirmation is not a booking, order confirmation or support ticket.

For an actual enquiry, cancellation request or complaint, communicate directly using the business contact details below. A binding notice under an active engagement must follow the method specified in that agreement. Do not assume that completing the website form provides notice to Fendrick Launch.

4. Proposals and project scope

A written proposal or statement of work should identify the services, deliverables, target platforms, agreed feature set, milestones, review arrangements, client responsibilities, exclusions and fees. Any assumptions about existing code, integrations, access or third-party services should also be documented.

Work outside the agreed scope is not automatically included. A request for an additional feature, platform, integration or substantial design change may require a change order, revised price or schedule. The parties should approve that change before the additional work proceeds.

5. Pricing, fees and taxes

Website prices are service-package ranges in United States dollars for the limited scopes described next to each service. The quoted service fee stays within the displayed range for the agreed package; listed project packages have a maximum service fee of $5,500. These packages do not cover every possible application. Work outside the package requires a separate written scope and fee.

Developer accounts, hosting, third-party subscriptions, paid services, applicable taxes and other excluded expenses remain separate unless the proposal expressly includes them. Any deposit, installment plan, recurring fee or invoice due date is stated in the project agreement or invoice. No payment is collected by the custom project form.

6. Payment and overdue amounts

The client is responsible for paying agreed invoices by their stated due dates and raising a genuine billing concern promptly with sufficient detail to review it. Payment for a milestone should correspond to the agreement’s defined work or reservation of resources; the website does not establish an unlisted payment schedule.

If an undisputed payment is overdue, we may pause affected work after notice and an opportunity to address the issue, where permitted by the agreement and applicable law. A pause may affect the schedule. Any additional charge or interest requires an applicable written term and must comply with law; it is not implied merely by these general terms.

7. Client responsibilities

The client provides an accurate brief, necessary content, access to authorized accounts and timely decisions. The client must have rights to supplied logos, text, images, data and existing code. The client is responsible for the lawful operation of its business, its application’s content and any regulated activity conducted through the application.

Client-owned developer, hosting and other platform accounts should remain under the client’s control unless a different arrangement is expressly agreed. Missing access, incomplete materials, delayed review or changing priorities can affect delivery. Any material effect should be discussed and documented.

8. Reviews, acceptance and changes

The agreement defines how deliverables are reviewed, how many review rounds are included and how acceptance is recorded. Feedback should identify the relevant screen or function and distinguish an agreed requirement from a new preference or additional feature.

Reported work that does not meet the agreed specification should be assessed against that specification. New requirements are handled through the change process. Silence alone does not create an undisclosed acceptance rule; if an agreement uses a review period or deemed acceptance provision, it should state that clearly.

9. Schedules and platform dependencies

Proposed dates are based on the agreed scope and known dependencies. Timelines may be affected by client decisions, change requests, third-party outages, credentials, existing code limitations and platform review. We do not guarantee app store approval, a specific review duration, downloads, revenue or business results.

Release assistance means preparing and supporting the agreed submission tasks. Apple, Google and other platform operators make their own eligibility and approval decisions. Additional work resulting from a changed platform requirement or a requirement outside the agreed scope may need separate approval.

10. Ownership and licences

The written agreement identifies custom deliverables and the ownership transfer. Unless that agreement states otherwise, the agreed custom deliverables are transferred to the client after full payment of the applicable project fees. The handoff should specify which source files, documentation and account access are included.

Pre-existing tools, reusable development materials, third-party software, fonts, libraries and open-source components retain their own ownership and licence conditions. To the extent permitted and necessary to use the delivered app, the applicable materials are licensed rather than assigned. The client must continue to observe their terms.

Providing project information does not authorize us to publish confidential material, client names or a case study. Public portfolio use should be agreed separately. The website’s brand, text and visual assets remain protected by applicable intellectual property rights.

11. Confidentiality and data handling

Each party should handle non-public information received for the project according to the written agreement and use it only for permitted purposes. Appropriate access should be limited to those who need it for the work. Confidentiality does not cover information lawfully public, independently developed or properly obtained from another source.

Development involving personal information or sensitive systems may require additional processing, security or compliance terms. These must be expressly identified. A general mobile development service description is not a representation that an app is certified for a regulated use or that every legal requirement is included in the project.

12. Maintenance and defects

Maintenance, ongoing availability, response times and included hours are determined by a separate package or written agreement. The website’s monthly maintenance package includes up to 10 hours of agreed work per month; emergency coverage, unlimited development and unused-hour rollover are not implied.

Any post-delivery correction period, warranty or support obligation should be defined in the agreement. Later changes by the client or third parties, unsupported operating systems, expired subscriptions or external platform changes may require a separate assessment. Mandatory rights remain unaffected.

13. Cancellation and termination

Cancellation is handled under the project agreement and the Cancellation and Complaints Policy. Fees for completed work and properly authorized, non-recoverable expenses may remain payable. An advance payment is reconciled against the work and commitments properly chargeable under the agreement.

Either party may have termination rights for a material breach, subject to the agreement’s notice and opportunity-to-remedy terms and applicable law. On termination, the parties should agree on the status of work, outstanding invoices, accessible paid deliverables and return or deletion of materials where appropriate.

14. Responsibility and limitations

Each party remains responsible for its own obligations under the agreement. To the extent permitted by law and subject to the written project terms, liability for a service claim is limited to the fees paid for the affected service during the preceding twelve months. The agreement may provide a different allocation for particular risks.

No limitation applies where it would be prohibited by law, including any liability that applicable law requires to remain unrestricted. These terms do not waive mandatory consumer protections or excuse fraud or other conduct that cannot lawfully be excluded. Claims should be assessed on their facts and the applicable agreement.

15. Law, disputes and updates

The parties should first try to resolve a genuine disagreement through the complaint process and a direct review of the relevant agreement and evidence. Unless a project agreement lawfully specifies otherwise, these terms are governed by Mississippi law, subject to any mandatory law that applies to the parties or transaction.

A dispute forum, arbitration agreement or special notice requirement is not created merely by the local enquiry form. Any such provision must be clearly agreed where needed. If a term is unenforceable, the remaining terms continue to apply to the extent permitted. An update to the website does not silently replace a signed project agreement.