Service Agreement

A project-specific template, not an accepted contract

This page is a framework for preparing your individual Service Agreement. It is not a completed agreement and does not identify a price, delivery date or contracting address for your project. An enquiry does not accept it. Aribify and the customer must complete and approve the project details before a paid commitment.

1. Parties and authorised contacts

• Aribify contracting party: legal name, business structure, correspondence address and authorised representative, as confirmed in the proposal.
• Customer: legal or personal name, billing details and authorised project contact.
• Project reference, proposal version, applicable policy versions and date of acceptance.

Public contact: hello@aribify.com · WhatsApp messaging ↗. Do not complete an agreement using invented identity or address details.

2. Scope and deliverables

List the pages, content, design files, functionality, platform, integrations and deliverable formats. State exclusions and who supplies copy, photographs, product information and brand assets. For stores, distinguish checkout integration from payment processing; for invitations, distinguish an event page from an RSVP database.

Record accessibility and browser/device requirements, language versions, editing access and any agreed search setup. Specify visibility, access controls and guest-data responsibilities for personal or invitation websites.

3. Milestones, price and revisions

Complete a milestone schedule covering scope approval, design review, working preview, testing and handover. For each milestone record the deliverable, objective acceptance criteria, planned date and customer dependencies.

Set the total fee, currency, taxes, payment stages, approved third-party costs and how proportional work is valued if cancelled. Identify revision rounds and what a round covers. Do not leave unspecified charges to be invented after work has begun.

4. Review and change control

Agree how feedback is supplied and how acceptance is recorded. A review should compare the delivered work with documented requirements. Record defects, the remedy and a reasonable timetable. Scope changes require a written description, price and schedule adjustment accepted by both parties before the additional work.

If customer inputs or external tools delay delivery, record the impact and revised plan. This template does not automatically accept work through silence.

5. Ownership, data and third-party tools

State which final materials transfer to the customer, when rights transfer, and which pre-existing or licensed components retain their original terms. Identify subscriptions, licence renewal responsibility, hosting access, backups and post-launch data handling.

Define authorised access to client accounts, confidentiality, guest-data collection where applicable, publication permission and a removal or handover procedure. Any portfolio permission or marketing consent is separate and optional.

6. Launch, support and cancellation

List the launch approval, live checks, files or access handed over, guidance provided, maintenance responsibilities and the exact support included. Record any support period in the individual agreement rather than assuming one from this template.

Attach the applicable Return, Cancellation & Refund Policy, which governs receipt time, proportionate deductions and refunds without removing mandatory consumer remedies. An additional money-back guarantee applies only if its completed terms are expressly supplied for that project.

7. Deliberate acceptance

Present the completed proposal and versions of all applicable documents before requesting acceptance. The acceptance control must start unchecked and be distinct from optional marketing:

I have reviewed and agree to the Terms & Conditions, Service Agreement, and Return, Cancellation & Refund Policy applicable to this project.

Record the accepted project reference, document versions, authorised customer, affirmative action and timestamp. Any digital acceptance endpoint must validate the action and project/document versions on the server. The present website has no project checkout or contract-acceptance endpoint; it does not collect this acceptance through the enquiry form.