This page explains how StackRefit engagements normally work. It is a plain-language summary, not a replacement for a signed proposal, statement of work, order form, or other written agreement.
If there is any conflict between this page and a written agreement signed or accepted by both parties, the written agreement prevails.
StackRefit provides practical modernization services for legacy PHP, WordPress, WooCommerce, Laravel, and Linux systems.
Our work usually starts with a technical audit, followed by optional stabilization, upgrade, documentation, automation, or care work where appropriate.
StackRefit is operated by StackRefit.
Contact: [email protected]
StackRefit may provide services such as:
The exact scope, deliverables, price, timeline, and access requirements are agreed separately for each engagement.
Most engagements start with an audit.
The audit is designed to understand the system before recommending or performing changes. It may include review of runtime versions, framework or CMS versions, plugins, dependencies, database setup, server environment, deployment process, backups, documentation, and operational risks.
Unless agreed otherwise, audits are read-only and do not include production changes, penetration testing, load testing, emergency support, or full security certification.
A project starts when we both agree on the scope, price, timeline, and commercial terms in writing.
Agreement may happen by signed contract, accepted proposal, email confirmation, payment of an invoice, or another clear written approval.
Any work outside the agreed scope may require a separate estimate, change request, or new engagement.
To deliver the work, the client must provide accurate information, timely access, and reasonable cooperation.
This may include:
Delays in access, approvals, or information may delay the engagement.
StackRefit prefers the lowest level of access needed to complete the agreed work.
For audits, access should normally be read-only where practical.
For implementation work, higher access may be required. In those cases, the client remains responsible for granting, limiting, monitoring, and revoking access as appropriate.
StackRefit does not intentionally make changes to production systems unless that work is clearly agreed.
Legacy systems can be fragile. Even careful work may uncover hidden issues, outdated dependencies, undocumented assumptions, or environmental problems.
Before implementation work begins, the client should ensure that appropriate backups, restore paths, and rollback procedures exist.
Where StackRefit identifies that backups or rollback processes are missing or untested, this may be treated as a risk or prerequisite before further work.
Deliverables depend on the engagement.
For an audit, deliverables may include a written report, risk register, stack inventory, prioritized recommendations, and a practical roadmap.
For implementation work, deliverables may include code changes, configuration changes, documentation, upgrade notes, handover materials, or agreed operational improvements.
Unless agreed otherwise, deliverables are provided in a practical working format, not as formal legal, compliance, or certification documents.
StackRefit may work with agencies on a white-label basis.
Where white-label work is agreed, StackRefit may provide reports or support behind the agency's brand and may avoid direct client contact unless invited.
The agency remains responsible for its own client relationship, pricing, promises, and commercial terms with its end client.
Fees are agreed before work starts.
Some services may be fixed-price. Others may be quoted as phased work, retainers, or time-based work.
Unless otherwise agreed:
Either party may request to postpone or cancel an engagement before work begins.
If work has already started, the client remains responsible for fees covering work performed, committed time, third-party costs, and any non-refundable agreed amounts.
For fixed-price audits or short engagements, cancellation terms may be stated in the proposal or invoice.
Both parties should treat non-public business, technical, commercial, and access information as confidential.
StackRefit will not intentionally disclose client confidential information except where needed to perform the work, comply with law, use professional advisers, or with the client's permission.
The client should not send unnecessary personal data, secrets, credentials, or sensitive information unless required for the engagement.
StackRefit aims to access only the data reasonably needed for the agreed work.
Where possible, we prefer read-only access, temporary credentials, staging environments, redacted datasets, and limited access windows.
The client is responsible for ensuring that any personal data or third-party data shared with StackRefit may lawfully be shared for the engagement.
Additional data processing terms may be agreed where required.
Legacy systems often depend on third-party services such as hosting providers, payment processors, plugins, APIs, SaaS tools, repositories, monitoring tools, email providers, or analytics platforms.
StackRefit is not responsible for third-party outages, policy changes, pricing changes, security issues, licensing restrictions, or limitations unless specifically agreed in writing.
StackRefit provides professional technical review, recommendations, and implementation support.
We do not guarantee that a system will be free from bugs, vulnerabilities, downtime, data loss, compatibility issues, or future maintenance needs.
Recommendations are based on the information, access, and scope available during the engagement.
StackRefit audits and modernization work may identify security, operational, or maintainability risks.
Unless expressly agreed, our work is not a formal penetration test, legal compliance audit, financial audit, ISO certification, GDPR audit, PCI audit, or security certification.
Clients should obtain specialist legal, compliance, or security advice where needed.
Unless otherwise agreed, the client keeps ownership of its pre-existing systems, code, content, data, and materials.
StackRefit keeps ownership of its pre-existing tools, templates, methods, know-how, checklists, and internal processes.
Work product created specifically for the client is assigned or licensed to the client as stated in the proposal or agreement, subject to payment of all amounts due.
StackRefit may not publicly identify a client, agency, project, system, or end client without permission.
For white-label engagements, StackRefit will not publicly reference the end client unless explicitly agreed.
To the maximum extent permitted by law, StackRefit is not liable for indirect loss, lost profits, lost revenue, loss of goodwill, business interruption, loss of data, or consequential damages.
Any liability is limited to the amount paid by the client for the specific engagement giving rise to the claim, unless a different limit is agreed in writing or applicable law requires otherwise.
Unless otherwise agreed in writing, these terms and any engagement with StackRefit are governed by the laws of Romania.
The parties will first try to resolve disputes in good faith before starting formal proceedings.
StackRefit may update this page from time to time.
The version that applies to a specific engagement is the version in effect when the engagement is agreed, unless both parties agree otherwise.