1. Scope and Deliverables
Every project starts with a defined scope. We outline deliverables, platform targets, and success criteria before work begins. This scope is the single source of truth for the project. If you request new features, additional screens, or changes that were not part of the original scope, we will provide an estimate for the added work and timeline impact before we proceed.
Deliverables may include design files, working prototypes, brand assets, and documentation depending on the engagement. If a deliverable is not listed in the scope, it is not included. We do not ship anything that we have not agreed to in writing.
2. Project Timeline
Timelines are based on the approved scope and the responsiveness of both teams. We provide an estimated schedule with major checkpoints and review dates. If approvals or feedback are delayed, the timeline shifts accordingly. If we are responsible for a delay, we communicate early and adjust the schedule to keep the project healthy.
For time-sensitive launches, a timeline buffer may be included to allow for testing, bug fixes, and final polish. We prefer realistic timelines over rushed outputs, as quality and performance require proper iteration.
3. Revisions and Approvals
Each phase includes a reasonable number of revision rounds. Revisions are intended to refine the agreed direction rather than restart the work from scratch. If requested changes fall outside the original direction or scope, they may be treated as a new phase or billed separately.
Approvals are provided in writing. Once a phase is approved, the next phase begins. If a previously approved phase is reopened, additional time and cost may apply. This ensures that progress remains stable and predictable.
4. Payments and Invoicing
Payments are milestone-based for larger engagements or defined in the proposal for smaller projects. Work begins when the initial payment is received. For ongoing collaborations, invoices are issued on the agreed schedule. Late payments can pause work and impact delivery dates.
All invoices are payable within the timeframe stated on the invoice. We reserve the right to withhold final deliverables until full payment is received. This protects both parties and keeps the financial process clear and fair.
5. Client Responsibilities
Clients are responsible for providing necessary content, brand guidelines, access credentials, and timely feedback. If we do not receive required inputs, the project timeline may shift. We communicate what we need and when we need it to keep the process efficient.
You confirm that any assets you provide are licensed or owned by you. We are not responsible for third-party claims related to assets provided by the client.
6. Intellectual Property
Upon full payment, ownership of final approved deliverables transfers to the client. We retain the right to display the work in our portfolio and promotional materials unless a confidentiality agreement states otherwise.
Working files, sketches, or unused concepts remain the property of AppPixel Studio unless explicitly included in the scope. We may reuse general design methods, code patterns, or non-proprietary ideas across projects.
7. Confidentiality
We treat all client information as confidential unless you authorize us to share it. This includes business plans, user data, and product strategy. If you require a formal non-disclosure agreement, we are happy to sign one before work begins.
Confidentiality also applies to our internal workflows and proprietary methods. We do not share internal documentation or non-public client materials without permission.
8. Third-Party Tools and Services
Projects may rely on third-party services such as hosting, analytics, or asset libraries. The client is responsible for costs related to these services unless otherwise stated. We can recommend options and assist in setup, but we do not control third-party uptime or pricing changes.
If you choose a third-party service, you agree to its terms and privacy policy. We are not liable for service failures or policy changes outside our control.
9. Support and Maintenance
Post-launch support is defined in the scope. If maintenance is included, we provide it for the specified period. Additional support after the initial period can be provided via a separate support agreement.
Support covers functional issues related to the delivered work. It does not include new features or major redesigns unless included in a follow-up scope.
10. Project Pause or Cancellation
If a project is paused for more than 30 days due to client inactivity, we reserve the right to reschedule based on our availability. If a project is canceled, completed work is billed and delivered for the phases finished at the time of cancellation.
Deposits are non-refundable once work has begun. This protects time already invested and resources allocated to the project.
11. Liability and Warranty
We deliver work that meets the agreed scope and quality standards. We are not liable for indirect damages such as lost revenue, lost data, or business interruption. Our total liability is limited to the amount paid for the project.
If issues are discovered within a reasonable period after delivery, we will correct them within the bounds of the original scope. This does not apply to changes made by third parties or modifications outside our control.
12. Acceptance
By engaging AppPixel Studio and approving project milestones, you acknowledge that you have read and accepted these terms. If you have questions, contact us before the project starts so we can clarify and align expectations.
