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. Keeping Your Information Secret, Taking Care, and Keeping You in Control
We Put You First
We will keep your information confidential (secret) and treat it as critical to your business. The same applies to your login details, intellectual property (your code, designs, and ideas), access to your servers and systems, and business data.
We will not knowingly use your assets, documents, code, or systems for any purpose outside the work we agreed to do. The same applies to your business information that is not public.
We will explain our technical recommendations in clear business language. We will do this before you approve budgets, deadlines, or resources in the cloud (online servers and storage). We will also do it before you approve third-party tools (tools from other companies) or changes that affect security.
No Hidden Control
We will avoid unnecessary lock-in (when it is hard for you to move to another provider). We will write down the important things your system depends on, where the code is stored, and which service providers are used. We will also write down how login details will be handed over and who is responsible for each task.
You stay responsible for your business decisions. But we will tell you about known risks, tradeoffs (what you give up to get something else), assumptions, and anything that blocks delivery. We will do this as soon as reasonably practical (as soon as we reasonably can).
We will not use your systems for testing, demos, marketing, portfolio material (examples of our work), or staff training. The only exception is when we receive written permission.
Part 2. Honest Work and Taking Responsibility
Our Quality Promise
We will design and build with 5 things in mind. These are easy maintenance, clear and readable documents, practical security habits, screens that are easy to use on any device size, and support after launch.
We will not knowingly hide important defects (faults), security concerns, assumptions that turned out to be wrong, or unfinished work. We will not hide them when you review the work or when we hand it over to you.
We will use a written quality-control process that fits the size of the project. It includes checking that each feature works and that screens fit different device sizes. It also includes a review in different web browsers and notes on whether the work is ready to launch.
How We Work with Clients Around the World
We will communicate with respect across time zones, cultures, industries, and business departments. When a decision affects cost, scope (what work is included), security, or delivery, we will put it in a written summary.
We will not promise results that depend on third-party platforms, search engines, payment providers, or cloud providers. The same applies to results that depend on regulators (official bodies that set rules), end users, or market conditions.
This oath backs up every proposal and every engagement (piece of work we agree to do). But some documents take priority if their terms conflict with this oath. These are any signed master services agreement (main contract), statement of work (a list of the exact work), purchase order, or written contract.