These policies are written for business use in every country. They are strict website terms and notices about how we work. But they do not replace a signed agreement or independent legal advice.
Who this is for: Business clients, possible clients, vendors (suppliers), and website visitors around the world
Important: If a signed project agreement conflicts with a website policy, the signed agreement takes priority.
Part 1. How We Deliver, Keeping to the Agreed Scope, and Quality Checks
How Every Project Is Set Up
Every engagement (piece of work we agree to do) begins with discovery and scope confirmation (agreeing what work is included). It also begins with assumptions, milestones (key stages), dependencies (what the work relies on), and acceptance criteria (the tests for accepting work). Last, it begins with stakeholder roles (who does what), communication channels, and time-zone expectations.
We may refuse to begin implementation (building the work) until certain things are clear enough. These are client access, content, licenses, credentials (login details), technical contacts, platform decisions, and approval authority (who can approve).
Any work outside the confirmed scope needs written approval. We may pause out-of-scope work until changes to cost, timeline, technical risk, and responsibility are accepted.
Quality Checks
Testing and quality checks may include reviews of requirements and design, checks on different screen sizes, and form testing. They may also include browser testing, basic accessibility care (so people with disabilities can use it), and a basic security review. They may also include deployment checks (checks when the work goes live), backup planning, and handover documents.
Before launch, you must review the work wherever you control these things. They are business accuracy, legal wording, branding, pricing, regulated claims (claims that laws control), product data, or market-specific compliance (rules for a certain market).
A release (a version of the work we deliver) counts as accepted when any one of these happens. You approve it in writing. You use it in your business. You do not reject it within the agreed review period. Or you pay the related milestone invoice without written notice of a defect.
Part 2. Support, Security, Handling Changes, and Communication Worldwide
Which Support Requests Come First
We decide which support requests come first based on impact on the live system, security risk, and how many users are affected. We also look at the support level in your contract and whether we can make the problem happen again. Business urgency and whether we have the information we need from your side also count.
We are not responsible for outages, delays, policy changes, account restrictions, price increases, bugs, deprecations (features being retired), or downtime caused by others. By others, we mean third-party platforms, cloud (online servers and storage) providers, payment gateways (online payment services), and plugins (add-on software). We also mean APIs (ways for two apps to talk to each other), DNS (domain name settings) providers, and your own vendors (suppliers).
Some kinds of support may need a separate support agreement or emergency approval. This applies to emergency support, support outside working hours, and migration support (moving to a new system). It also applies to audit response, compliance evidence (proof that rules are followed), and responding to incidents (problems) in live systems.
Security, and Communication Across Countries
Some items must be shared only through approved secure channels. These are passwords, access keys for APIs, tokens (digital access passes), private keys, production data (live system data), and regulated information. We may reject credentials (login details) that are shared in an unsafe way.
For global clients, we use written summaries and demo checkpoints (planned times to show the work). We also use decision logs (written records of decisions) and async updates (messages you can read at any time). We do this to reduce unclear points across time zones and departments.
We may suspend (pause) or terminate (end) service where requests involve unlawful conduct, unsafe access, or abusive communication. The same applies where they involve unpaid invoices, unauthorized systems, or misuse of intellectual property (rights to code, designs, and ideas). It also applies where they involve a material (serious) breach of the agreed terms.