1. Confirm the agreement before starting
Before you approve work, your proposal or service agreement should identify the supplier and client, scope and exclusions, deliverables, timeline, dependencies, revision limits, fees and currency, taxes, payment milestones and any external charges. Ask for clarification before accepting or paying. A signed or otherwise expressly accepted agreement controls if it differs from this policy, subject to mandatory law.
Prices for data analysis, data engineering, development or maintenance must state the actual capacity and deliverables included. A package name alone is not a promise of unlimited work, specific results or a production service-level agreement.
2. Monthly and recurring services
Your agreement must confirm the start date, billing cycle, included hours or deliverables, response arrangements, overage approval, minimum term if any, renewal process and cancellation notice. It must also state whether unused capacity expires or carries forward. A published monthly price alone does not authorise an automatic card charge or create a minimum commitment.
Ask us to confirm recurring terms in writing where they are missing. Additional work and third-party costs need approval. A different price or scope for a future period should be disclosed and agreed before that period is committed.
3. Changes, delays and acceptance
Request scope changes in writing. We will confirm the effect on cost, dependencies and delivery dates before proceeding. Delayed feedback, missing access or content and unpaid agreed milestones can affect the schedule; any pause and restart arrangement should be communicated.
Review deliverables against the agreed requirements and report specific defects within the review window in your proposal. Requested enhancements are scoped separately. Silence is not a substitute for an express launch approval. Confirm any launch support window and the responsibilities for renewals, monitoring and backups in writing.
4. How to cancel or pause
Email arcstacka@gmail.com from your registered contact address with the project reference and requested cancellation or pause date. We will confirm the applicable agreement, work status, outstanding commitments and practical handover steps. Sending a request does not automatically erase invoices or override a notice period already agreed.
Cancellation is assessed against work actually completed, approved non-cancellable third-party commitments and the terms accepted for that engagement. Payments already made are credited in the settlement. A pause should record the effect on access, stored materials, recurring provider charges and any restart schedule.
5. Refund assessment
There is no blanket “all payments are non-refundable” rule in this policy. If prepaid funds exceed amounts properly payable under the agreement and applicable law, we will calculate the unused balance and arrange any refund due. A refund is not automatically available simply because completed, conforming work is no longer required.
We will explain the calculation and proposed refund method and timing in writing. External charges are assessed against the approval and the provider’s refund rules, without removing any rights you have against ArcStack under applicable law. Mandatory cancellation rights and remedies for defective or undelivered services remain available where they apply.
6. Handover and complaints
The agreement determines which paid deliverables, source files, credentials and licences are handed over. Identify any client-owned domain or hosting accounts and ongoing provider costs before termination. Ask for an export and retention arrangement before access ends; cancellation does not guarantee immediate deletion of records needed for legal or accounting purposes.
For a billing or delivery complaint, contact arcstacka@gmail.com with the relevant references and requested resolution. We will assess it with you. Any agreed dispute procedure and applicable legal remedies continue to apply.