Terms of Service (v3, EN)

Last updated: July 28, 2026 (version 3)

Introduction

Welcome to ijalfauzi.com. These terms explain what you can expect when visiting my website, and — if you buy a package — the agreement between us. By visiting this website you agree to the website terms; by paying for a package — a deposit, or the full price where its appendix says so — you agree to the engagement terms as well, so please read them carefully.

These terms are published in English and in Bahasa Indonesia. This English version governs purchases made in US Dollars. If you buy in Indonesian Rupiah, the Indonesian version is the one that governs our agreement.

Who you are dealing with

Provider: Ijal Fauzi, an individual freelance web developer based in Indonesia
Website: ijalfauzi.com
Email: [email protected]

Website Guidelines

When visiting ijalfauzi.com, you agree to:

Follow Indonesian law
Not reproduce, duplicate, or copy content without my explicit permission
Not engage in any unlawful activities
Not attempt to gain unauthorized access to any part of the website

Intellectual Property

All content on this website, including but not limited to text, images, graphics, code, and portfolio works, is my intellectual property
My work portfolio showcases projects I’ve completed and have the right to display
You may not reproduce or distribute any content from this website without my written permission

Comments

When you submit comments on my website, you:

Retain ownership of your content
Grant me the right to display, modify, or remove your comments
Agree not to post harmful, offensive, or inappropriate content
Understand that I may moderate or remove comments at my discretion

Service Inquiries

If you contact me about website or development work without buying a package:

Submitting an inquiry does not create a binding agreement
Terms for custom or negotiated work are agreed separately in writing
I may decline any request
Pricing for custom work is discussed case by case

Package Engagement Terms

This section applies when you buy a fixed-scope package from this website. It is the agreement between us for that work. It does not apply to custom or negotiated projects, which are agreed separately.

1. What you are buying, and what it costs

Scope. What each package includes, what it excludes, and what you need to supply is set out in the appendices at the end of these terms. Those appendices are the specification for the work. A package page on my website may describe the same package in a shorter, less formal way — where the two differ, the appendix to the version of these terms you accepted is what governs.

Price. The price of each package is shown on its package page when you order, and is shown again at checkout before you pay. Your order confirmation states the full package price and the amount charged on that order, in the currency you were charged. Where the package is paid by deposit, it also states the deposit amount and the balance due after approval; where the appendix says the package is paid in full at checkout, there is no deposit and no balance. That confirmation, together with these terms, is our agreement on price.

The price is fixed for the scope in the appendix. Anything outside that scope is a separately quoted change order, which you approve before I start it. The price shown is the total price for the package; no tax is added at checkout.

Where an appendix sets out different mechanics for payment, scheduling, release, handover or refunds for its package, that appendix governs for that package, and the general sections below apply only so far as they are consistent with it. This matters for packages that are paid in full at checkout and run for a fixed period rather than to a launch: their appendix, not the general sections, describes how their work starts, is released, and ends.

2. How payment works

The packages on this website are sold on a deposit basis, which works as follows. Each package page states how that package is paid for; if I ever offer one payable in full at checkout, its page and appendix will say so and the balance steps below simply will not apply to it.

You pay a 50% deposit to book the work. The deposit is exactly half the package price, shown on the package page before you pay.
The remaining 50% becomes payable after approval (section 4), through a payment link I send you.
Indonesia: payment is by manual bank transfer in Indonesian Rupiah. Your order is marked paid once I have confirmed the transfer arrived.
International: payment is by PayPal and is charged in US Dollars. Any currency conversion or fee charged by your bank or card issuer is yours.
An unpaid bank-transfer order may be cancelled after about 7 days.

3. Kickoff

Kickoff is a recorded event: I confirm to you in writing that your schedule has started. That happens once I have received the content, access, and assets the appendix for your package says you need to provide. Until kickoff, no work has begun.

4. Approval

I deliver the work to a staging site for your review. Approval happens in one of two ways:

You confirm acceptance in writing; or
Seven business days pass after I deliver staging and give you written notice, without you reporting a material failure to meet the agreed scope.

If you report a scope-based problem within that period, the review period pauses until I deliver the corrected work, and then resumes.

Approval — including approval by the passage of time — makes the remaining balance due. It does not waive hidden defects, and it does not shorten the post-launch support period in section 9. No balance is ever charged automatically; you always pay it yourself through the link I send.

5. Revisions

Basic WordPress includes one consolidated round of revisions.
Business WordPress includes two consolidated rounds.
Custom Web Apps & Tools includes two consolidated rounds.

Each round should be submitted as a single feedback list within the review period. Corrections needed because the delivery does not meet the agreed scope do not consume a revision round — those are simply fixed. Requests outside the agreed scope, or further preference changes after the included rounds, are a separately approved change order.

6. Cancellation and refunds

Before kickoff, and before any work or approved third-party costs have begun, your deposit is refunded in full.
After kickoff, the deposit is credited against work actually completed and documented, plus any third-party costs you approved that cannot be recovered. Any unused portion is refunded to you.
Before approval, the total cancellation charge is capped at the deposit — you owe nothing beyond it.
After approval (written or by passage of time), the remaining balance is due.
If I cancel, or cannot deliver the agreed scope, you receive a full refund for the work not delivered.

Refunds are returned by the same route you paid. Bank-transfer refunds are manual outbound transfers and may take a few working days.

7. If the balance is not paid

The balance is due within seven calendar days of approval. Until it has cleared, the work stays on my staging site: there is no launch, no production access, and no handover. I will send reminders over the following 30 days.

After 30 days unpaid, the project is archived and removed from active scheduling. Archiving means the work is kept offline — it is not deleted, and the retention period is described in the Privacy Policy that applies to your order. Your deposit remains applied to the work completed, and the outstanding balance remains due; archiving does not cancel it. Resuming later depends on my availability and may need a separately approved reactivation quote if your environment or scope has changed.

8. Handover, and what transfers

Launch, production credentials, and the project-specific deliverables are handed over once the balance payment has cleared.

What transfers to you is the work made specifically for your project. Third-party licences, my reusable tools and components, pre-existing code, and platform software (for example WordPress, plugins, and themes) remain subject to their own ownership and licence terms — buying a package does not transfer ownership of those to you.

9. Post-launch support

Basic WordPress: 14 days, defects only.
Business WordPress: 30 days, defects only.
Custom Web Apps & Tools: 30 days, defects only.
Ongoing Improvements: not applicable. That block is itself the support arrangement, so the defect window in this section does not apply to it.

Support covers failures of the delivered work to meet the agreed scope. It does not cover new features, preference changes, errors in content you supplied, changes made by third-party services, hosting changes, or modifications made by you or another provider. The period begins at launch, or at handover if launch is delayed or handled by you.

10. What I need from you

Fixed-scope work depends on you supplying the content, access, and assets listed in the appendix for your package, and responding within the review period. If those are delayed, my schedule moves accordingly. I will tell you in writing when that happens.

11. If something goes wrong

If the delivered work does not match the agreed scope, tell me and I will correct it — that is the first remedy, and it does not consume a revision round. If we cannot resolve it that way, section 6 governs cancellation and refunds.

Nothing in these terms removes rights you have under Indonesian consumer law that cannot be waived by agreement.

12. Complaints and disputes

Please raise any complaint with me first, by email to [email protected], with your order number. I aim to respond within 3 working days and to resolve matters directly wherever possible.

If we cannot resolve a dispute between us, it will be settled under Indonesian law. Indonesian consumers may also use the consumer dispute resolution channels available to them under Indonesian law.

Appendix A — Basic WordPress

This appendix is the specification for the Basic WordPress package, as referred to in section 1.

What is included

Up to 5 pages — for example Home, About, Services, Contact, and one more.
A premium theme, installed and styled to your brand.
A mobile-responsive layout across phones, tablets, and desktop.
Basic on-page SEO: page titles, descriptions, and an XML sitemap.
A contact form delivering to your inbox.
Google Analytics installed and verified.
A 1-hour handover session so you can run the site yourself.
One consolidated round of revisions, as described in section 5.
14 days of post-launch support, defects only, as described in section 9.

What is not included

Writing your copy, or entering large amounts of content.
Custom plugin or feature development.
An online store or WooCommerce setup — that is the Business package.
Ongoing maintenance, which is available separately as a retainer.
Third-party costs such as domain registration, hosting, premium plugin or theme licences, and stock imagery, unless the appendix says otherwise.

What you supply

Your text and images for each page.
Your logo and any brand assets you want used.
Domain and hosting access sufficient for me to launch the site.
Your feedback within the review period described in section 4.

Indicative timeline

About 2–4 weeks from kickoff (section 3). This is an estimate, not a fixed delivery date, and it moves if the materials above arrive late or feedback is delayed — see section 10.

Appendix B — Business WordPress

This appendix is the specification for the Business WordPress package, as referred to in section 1. The limits below are what the fixed price covers — they exist so that “custom work” has an agreed size rather than an open one.

What is included

Up to 15 pages.
Custom theme development — designed and built for your brand, not adapted from a template.
WooCommerce setup, if you sell online, including up to 30 products loaded by me.
Up to 2 small custom features — for example a booking enquiry form, a filtered listing, or a calculator. We agree which two before kickoff. “Small” means it fits within the schedule for this package; anything larger is quoted separately.
One integration with a third-party service you already use (for example a payment gateway, a CRM, or a mailing list).
Advanced SEO setup across the pages in scope.
One analytics dashboard so you can see what is working.
A 2-hour handover session.
Two consolidated rounds of revisions, as described in section 5.
30 days of post-launch support, defects only, as described in section 9.

Going past any of these limits is not a problem — it is simply a separately quoted change order, which you approve before I start it.

If the two custom features turn out not to cover what you need, you are not stuck with it. We agree which features they are before kickoff, and at that point you can pick different ones that fit within the allowance, accept a quote for the extra work, or cancel before kickoff and have your deposit refunded in full under section 6. Before kickoff, you will not be held to a package that turns out not to fit. After kickoff, section 6 still applies — the deposit is credited against work actually done and any unused part comes back to you.

What is not included

Writing your copy, or entering large amounts of content.
Payment-gateway or merchant accounts and their KYC — I handle the integration; the accounts stay in your name.
Ongoing maintenance, which is available separately as a retainer.
Third-party costs such as domain registration, hosting, premium plugin or theme licences, payment-gateway fees, and stock imagery, unless the appendix says otherwise.

What you supply

Your text and images for each page, and your product data if you sell online.
Your logo and any brand assets you want used.
Domain and hosting access sufficient for me to launch the site.
Accounts and credentials for any third-party service you want integrated.
Your feedback within the review period described in section 4.

Indicative timeline

About 4–8 weeks from kickoff (section 3). This is an estimate, not a fixed delivery date, and it moves if the materials above arrive late or feedback is delayed — see section 10.

Appendix C — Custom Web Apps & Tools

This appendix is the specification for the Custom Web Apps & Tools package, as referred to in section 1. This is a starter build at a fixed price: the limits below are what that price covers, so that “custom” has an agreed size rather than an open one.

What is included

One discovery session, after which I write down what we agreed. That written spec names each screen and each type of record before kickoff, and together with this appendix it is the specification for your build.
Up to 8 primary application screens, holding up to 5 straightforward types of record arranged within that 8-screen limit. The two limits work together — five kinds of record do not each get their own set of screens.
Standard create, view, edit, delete, search, filtering and simple relationships between records.
One login system with up to 2 kinds of user — for example staff and administrator.
A responsive interface built on an established component or admin UI system, styled to your brand colours and logo.
One integration using a documented third-party API, limited to one agreed flow of data in one direction.
Deployment to your hosting, in one environment.
Two consolidated rounds of revisions, as described in section 5.
30 days of post-launch support, defects only, as described in section 9.

What is not included

These are all still possible — they are simply quoted separately, because each one changes the size of the build:

Complex approval workflows, advanced calculations, reporting and dashboards beyond simple lists, real-time features, or serving multiple separate organisations from one system.
A bespoke product design system. The package uses an established UI system styled to your brand, not a design language built from scratch.
Two-way synchronisation, real-time processing, or integrating with an undocumented API.
Bulk import, cleanup, or migration of your existing data.
Native mobile apps for the App Store or Play Store.
Ongoing hosting, monitoring or maintenance, which is available separately as a retainer.
Third-party costs such as hosting, domains, paid APIs, and service subscriptions.

What you supply

A clear description of what the tool needs to do, and who will use it.
Representative sample data for building and testing — enough to work with, in a readable format such as a spreadsheet. Bulk import or migration of your full dataset is quoted separately.
Accounts and credentials for any service you want integrated.
Hosting the app can be deployed to, or approval for me to arrange it at your cost.
Your feedback within the review period described in section 4.

Indicative timeline

About 6–10 weeks from kickoff (section 3). This is an estimate, not a fixed delivery date, and it moves if the materials above arrive late or feedback is delayed — see section 10.

Going past any of these limits is not a problem — it is simply a separately quoted change order, which you approve before I start it. If the discovery session shows the build you need is larger than this starter scope, you can accept a quote for the difference, reduce it to fit, or cancel before kickoff and have your deposit refunded in full under section 6.

Appendix D — Ongoing Improvements

This appendix is the specification for the Ongoing Improvements package, as referred to in section 1. It is a prepaid 90-day block of work at a fixed price, paid in full at checkout — the balance steps in section 2 do not apply to it. It is not a subscription: it does not renew, and nothing is charged again unless you buy another block.

Who this is for

This block is for a system I already maintain, or one I have approved in writing before you check out. Being an existing client does not by itself qualify a system I have not seen. If the system is new to me, ask me first — I will look at it and confirm in writing whether I can take it on, at no cost. If a block is bought for a system I have not approved in writing, I refund it in full and no work starts.

What is included

Up to 24 hours of my work in total across the 90-day window — an average of about eight hours per 30 days, not a monthly allocation. You may use the hours at your own pace within the window, subject to the one-active-request limit and agreed scheduling.
Feature updates, bug fixes, performance improvements and small integrations to a site or application I already maintain, previously built, or approved in writing before you checked out.
One active request at a time, worked in the order you prioritise them. You can reorder the queue whenever you like; I work the top item.
Priority placement in my queue, subject to work already committed when you purchase.
A written changelog of what shipped, and how many of the 24 hours remain, sent as work completes.
Each request handled on staging first where a staging environment exists, then released with your go-ahead.

What is not included

These are all still possible — they are simply quoted separately, because each one changes the size of the work:

Any single request I estimate at more than 8 hours. I tell you the estimate first; larger pieces become a separately quoted change order so a block is never silently consumed by one item.
A new build, a full redesign, or a new application. Those are the packages in Appendices A to C.
Two-way synchronisation, real-time processing, or integrating with an undocumented API.
Bulk import, cleanup, or migration of your existing data.
Hosting, backups, uptime monitoring and security monitoring, which are the Care retainers, not this block.
Emergency or out-of-hours response. Response times are in the next section and are not a 24/7 commitment.
Work on a site or application I have not approved in writing before checkout — see “Who this is for” above.
Third-party costs such as hosting, domains, paid APIs, and service subscriptions.

What you supply

Working access — administrator login, hosting or server access, and the code repository where one exists.
One point of contact who can prioritise requests and approve releases.
A written description of each request: what is wrong or wanted, and where to see it.
Your go-ahead on staging, which I ask for within five working days. That is a requested response period, not a deadline that costs you anything: waiting for you does not pause or extend the 90-day window, and nothing goes to production without your written approval. Section 4’s automatic approval after seven business days does not apply to this package — silence is never treated as approval here.

How the hours are counted

Time counts when I am working on your request: investigating, writing and reviewing code, testing, and deploying it. It is recorded in 15-minute increments.
Ordinary messages about a request are not counted. A meeting you ask for is counted, and I will say so when you book it.
Before I start anything I send you a written estimate in hours, and I do not begin until you approve it. That estimate is also how you know what the request will cost you from the block.
If a request turns out to need more than its approved estimate, I stop at the estimate and come back to you with the reason and a revised figure. I never quietly spend more of your block than you approved.
If it takes less, only the actual time is counted.
Each changelog entry states the time counted for that request and the balance remaining, so the running total is always something you can check.

The 90-day window, and what happens to unused time

The window is 90 calendar days. It starts when your payment is confirmed — for bank transfer, that is when I confirm the transfer has arrived, not when you send it.
Unused hours expire at the end of the 90 days. They do not roll over into another block and they are not refunded. If the queue is empty, ask me for work — I would rather spend the hours than have them lapse.
If I accept and estimate a request before the window closes, I finish it even if the work runs past day 90. The deadline applies to when requests are accepted, not to when I deliver them.
The block does not renew automatically. Continuing is a fresh purchase, decided by you.
First response within two working days of a request. Scheduling of the work itself is by agreement, based on its size and the queue.

Ending it early, and refunds

This section sets out the refund position for this package, and it replaces section 6 for it. Section 6 describes deposits, kickoff and approval, none of which exist here — this block is paid in full at checkout and has no balance stage.

Before I have started the first request, the fee is refunded in full, no questions asked.
After that, either of us can end the block by written notice, effective when it is received. I then deduct only:
- time actually worked, recorded in 15-minute increments as set out above;
- third-party costs you approved that cannot be recovered; and
- capacity I had committed to an approved request and could not reasonably reallocate — and only where I can evidence it. If I cannot evidence it, I do not deduct it.
I refund the remaining balance to you, through the same payment route you paid by, on the timetable set out below.
A notice I receive before the window expires is settled under this section, and the day-90 expiry cannot cancel that refund: expiry applies to hours left unused while the block is still running, not to a block you have already ended.
If I am the reason the block cannot continue — I become unavailable, or I decline work that falls inside this appendix — I deduct only work actually delivered and approved third-party costs that cannot be recovered. I do not deduct committed capacity in that case, and I refund everything else. I tell you in writing rather than let the window quietly run out.
What happens once notice is received: I accept no new requests. For an approved request already in progress, you choose — ask me to stop and hand it over as it is, or let me complete it within its approved estimate. I give you the final calculation within five working days after that work stops or finishes, and I initiate any refund within seven working days of giving it to you.
Hours that simply lapse unused at day 90 are a different matter and are covered by the window section above, not by this one.
Nothing here limits your rights under Indonesian consumer law.

Going past any of these limits is not a problem — it is simply a separately quoted change order, which you approve before I start it. If a request turns out to be larger than the block can hold, you can accept a quote for the difference, reduce the request to fit the remaining hours, or leave it for a later block.

Website Availability

I aim to keep the website running smoothly but cannot guarantee uninterrupted access
I may modify, suspend, or discontinue any part of the website at any time
I am not liable for downtime or technical issues beyond my control

External Links

My website may contain links to other websites
I am not responsible for the content or privacy practices of linked websites
Clicking on external links is at your own risk

Communication

By contacting me through the website, you agree that:

I may reply by email or, if you share the details, through a messaging app such as WhatsApp or Telegram
Communication will be related to your inquiry, your order, or your comments
Your contact information will be handled as described in the Privacy Policy

Disclaimer

The website is provided “as is” without any warranties
I do not guarantee the accuracy or completeness of any information on the website
Portfolio examples represent past work and do not guarantee identical results

This disclaimer applies to the website. It does not limit my obligations for work you have paid for, which are set out in the Package Engagement Terms above.

Liability

For website visits, I am not liable for indirect damages, loss of data, technical issues, or problems arising from third-party services.

For paid package work, my liability is limited to the amount you paid for that package — except where Indonesian law does not allow that limit, and except for my own obligations to correct, refund, or deliver as set out above. Nothing in these terms transfers my responsibility for my own work to you.

Changes to Terms

I may modify these terms at any time, and changes take effect when posted.

Your order is governed by the version of these terms you accepted when you paid. A later change does not alter an engagement already under way. Each version is kept published so you can always read the exact terms your order was made under.

Contact Information

For questions about these Terms of Service, please contact me at:

Email: [email protected]
Website Owner: Ijal Fauzi

Governing Law

These Terms of Service are governed by the laws of Indonesia.

Severability

If any provision of these terms is found to be unenforceable, the remaining provisions will remain in effect.