Trust Center
Our guarantees and policies, in writing.
This is every promise we make to agencies, what each one means on a real project, and the clause in our Partner Agreement that makes it binding. If you want to check us before you sign, start here. Each section has its own link, so you can send one to your team.
- On time, or a full refundEvery fixed-price project has a deadline in writing. Miss it for a reason on our side, and you get the whole fee back.Read the policy
- Zero-Poach GuaranteeYour client never hears from StudioPartner. It’s in the contract, with no end date.Read the policy
- We work inside your agencyOn your email, in your tools, under your brand.Read the policy
- Escrow on your first projectYour first project’s money sits in escrow and is released milestone by milestone as you approve the work.Read the policy
- Confidentiality & consent-first portfolioYour client’s work stays invisible unless you both say yes, in writing.Read the policy
- NDA by defaultA mutual NDA covers you before you share anything.Read the policy
- You own the IPYou own everything we make for you, the day it’s paid for.Read the policy
- Quality standardsWe build it exactly as designed, and check it before you ever see it.Read the policy
- SEO-safe launch checklistEvery redirect mapped. You sign off before we touch DNS.Read the policy
- AccessibilityBuilt to WCAG 2.2 AA, and documented.Read the policy
- Security & access handlingWe treat your client’s access and data as carefully as our own.Read the policy
- How we use AIAI speeds up routine work. A senior person checks everything it touches.Read the policy
On time, or a full refund
Every fixed-price project has a deadline in writing. Miss it for a reason on our side, and you get the whole fee back.
What this means for you
- Every fixed-price project order has a delivery date in writing, set in your time zone.
- Miss it for a reason on our side and 100% of that order’s fee comes back within 10 business days.
- The clock pauses only while we’re waiting on you, your client or a third party either of you controls, for force majeure, or while work is suspended for an unpaid invoice. We log every pause in writing on the day it happens.
- Our own staffing, illness, holidays, tools and QA issues never pause it.
- The full policy below also covers our other guarantees: the First-Project Guarantee, the 30-day bug warranty, continuity and your-hours service levels.
Read the full policy
What it covers
Every fixed-price project order: packages, items from our price list, add-ons ordered as projects, rush orders (at the rush date) and the pilot. It doesn’t cover care plans, capacity plans, the Dedicated Developer or hourly work, which have service levels instead (below).
The deadline
Your signed order states the deadline as a calendar date. It is the turnaround in your signed order, in business days (Monday to Friday) in your time zone, counted from the business day after the Ready-to-Start checklist is complete. Public holidays don’t pause the clock, yours or ours.
The Ready-to-Start checklist
- the signed order
- the brief
- final copy, or an agreed content deadline
- brand assets or Figma files
- hosting and domain access, or staging on your subdomain
- email accounts for our team on your domain, and access to your tools
- your first project funded in escrow, or the deposit paid on later projects
What “on time” means
The order is handover-ready by 23:59 your time on the deadline date: the complete build on staging (or the final files, for design-only orders and audits), past our internal QA, with the handover doc ready. Launch isn’t the trigger, because go-live depends on you and your client. If a template, page or feature in the order is missing or doesn’t work, it hasn’t been delivered, and the clock keeps running.
When the clock pauses
Day for day, and only for these:
- Review time beyond the included windows: 2 business days per design round, 3 business days on staging.
- Missing or late content, assets or data, or an answer to a question we’ve marked Blocking.
- Access not given, or revoked: email seats, tools, hosting, DNS or logins.
- Scope changes you approve. Each one is quoted in writing within 1 business day with the days it adds, and never started without your written OK.
- Third parties you or your client control, such as the client’s host, app approvals, payment-gateway checks or domain transfers.
- On later projects only: an invoice unpaid past its due date.
- Work we suspend for an unpaid invoice, after 7 days’ written notice.
- Force majeure, narrowly defined in the Partner Agreement.
Never a pause
Our staffing, illness or holidays, issues found in our own QA, our tools, and the time we spend on included revisions.
The logging rule
We log every pause in writing, in your tool, on the business day it starts and the day it ends, with the new deadline. A pause we didn’t log that day doesn’t count. You can dispute a logged pause within 2 business days.
The refund
100% of that order’s fixed-price fee, refunded within 10 business days. Third-party costs bought at cost for the project (licences, apps, fonts, stock) aren’t part of the fee and aren’t refunded.
- First project: the escrow provider returns the funds it holds, and we repay any released milestones.
- Later projects: we refund what you paid for that order and cancel its unpaid invoices.
After a refund, you choose
- Refund and stop: no IP transfers, and neither side uses the work.
- Refund and finish: we finish the work free, and the IP transfers to you at handover.
Limits
- One refund per order. An order refunded under this guarantee can’t also be refunded under the First-Project Guarantee.
- It doesn’t apply to force majeure, narrowly defined in the Partner Agreement, or if you were in material breach of that agreement when the deadline passed and we had told you in writing before the deadline.
- It is the sole and exclusive remedy for late delivery.
First-Project Guarantee
Pick any one item and treat it as a trial. Not happy with it? We fix it within 5 business days, or you don’t pay.
- Tell us within 5 business days of the staging handover.
- We fix it within 5 business days.
- If you’re still not happy, tell us within 5 business days of the fix, and the escrow provider returns your funds.
- Once per agency. It doesn’t apply if the brief changed materially after kickoff, or to work already used in production.
- If you don’t pay, the work and its IP stay with us, and the work is never used.
30-day bug warranty
Anything we built that breaks in the first 30 days after launch is fixed free, however small.
- A defect is anything that doesn’t match the approved design, or doesn’t work.
- The 30 days start at launch, or 30 days after the order was handover-ready, whichever comes first.
- Not covered: changes made by others, third-party updates after handover (unless the site is on a care plan with us), hosting outages, content added after handover, materials you supply, and use outside the browsers and devices agreed in the order.
Continuity
Every project has an assigned Project Manager. Because the work and every message live in your tools, your Project Manager’s named backup can pick it up with the full history. If your Project Manager is away for more than 2 business days, the backup takes over. Our staffing, illness and holidays never pause your deadline.
Your-hours service levels
On projects and on care and capacity plans:
- Your assigned Project Manager works your business day.
- First reply within 2 working hours, your time, during a project.
- A written update every week, posted in your tool.
- These are service targets. Only the on-time guarantee comes with a refund.
In the contract: Partner Agreement, On-time guarantee
Zero-Poach Guarantee
Your client never hears from StudioPartner. It’s in the contract, with no end date.
What this means for you
- StudioPartner, any affiliated company and every team member will never contact, pitch, quote or work for your clients, or the prospects you name to us.
- For StudioPartner and its affiliates it has no end date. It holds during our partnership and after it.
- Team members are bound while they work with us, and their contracts carry matching terms that we enforce after they leave.
- If we ever speak to your client, it’s because you asked us to, and we do it as your team, from your email and in your tools.
- If your client contacts us directly, we decline and tell you within 1 business day.
- If we ever break it, the remedy is written into the Partner Agreement.
Read the full policy
Who is bound
- StudioPartner.
- Any affiliated company: any business under common ownership or control with StudioPartner.
- Every team member who works on your account, employed or contracted, while they work with us. Their contracts carry matching terms, and if a former team member breaks them, we enforce them at our cost if you ask.
Who is protected
- Every client you’ve sent us work for.
- Every prospect you’ve named to us in a brief, quote or pilot, even if the project never went ahead.
What we never do
As StudioPartner, as an affiliated company, or as individuals:
- contact your clients by any channel: email, phone, social media, events, or ads aimed at them
- pitch or quote them
- accept work from them, directly or through someone else
- add their contacts to any list
- put our tracking, credits or links in their sites, code or metadata
What isn’t contact
Work you ask for, done from the accounts you created for us on your domain or inside your tools, is part of being your team. It never mentions StudioPartner, and it stops when you say so.
If your client contacts us
- We don’t discuss the project, and we don’t confirm or deny that we work with you.
- We send a neutral decline.
- We tell you within 1 business day.
- We never take on the account, even if the client says they’ve left you.
Release
Only you can release a client from this guarantee, in writing. For example, if you close your agency and want us to support them.
No end date
For StudioPartner and its affiliates, the guarantee has no end date. If the law where you are limits how long a promise like this can last, it lasts for the longest period that law allows.
If we break it
- We refund every fee you paid us for that client’s projects.
- We account to you for any fee we, or an affiliated company, received from that client.
- We pay the liquidated damages set out in the Partner Agreement for each client affected.
Why it holds
Our people work only from accounts you own. There is no StudioPartner channel to your client, you can read every message, and access ends when you switch the accounts off.
In the contract: Partner Agreement, Non-solicitation
We work inside your agency
On your email, in your tools, under your brand.
What this means for you
- You create an email account on your domain for each of our people on your project, and all project communication happens there.
- We work in your chat, project tool, Figma, Git and hosting accounts, as part of your team.
- Nothing of StudioPartner reaches your client: no emails, domains, credits, invoices or file metadata.
- You can read everything we send, and everything we make lives in your systems from day one.
- You pay for the seats, and you switch them off whenever you choose.
| Work | We use | If you don’t have one |
|---|---|---|
| Chat | Your Slack or Teams, as a member or a single-channel guest | Email on your domain |
| Projects | Your Asana, ClickUp, Jira, Trello, Linear or Basecamp | A free workspace set up in your name |
| Design | Your Figma organisation, with files created in your team | A free Figma team you own |
| Code | WordPress and Webflow: on your or your client’s hosting and account. Shopify themes and headless builds: your GitHub, GitLab or Bitbucket organisation, with commits from your-domain email | A free organisation you own, never ours |
| Hosting, CMS, Shopify | Collaborator or staff accounts on your or your client’s account | Set up by you or your client |
| Credentials | Your password manager, shared to our your-domain accounts | A shared vault you own, which we help set up |
| Docs and video | Your Google Drive or Notion, with walkthroughs in your branding | Ordinary files, saved to your drive |
Read the full policy
Your email, your identity
- For each team member you create an account on your domain, such as firstname@youragency.com.
- We use it for all project communication: with you, and with your client only if you ask.
- Signatures follow your format. Calendar invites and calls come from your accounts, on your Google Meet, Zoom or Teams.
- We never set up forwarding to StudioPartner addresses. Your admin can enforce this.
Nothing of ours reaches your client
Before you see a build, someone who didn’t build it searches for our names and domains in:
- emails, domains, calendar invites and meeting links
- invoices: we invoice you, never your client
- staging URLs: your subdomain or the client’s host, never a StudioPartner domain
- footers, code, HTML comments and generator tags
- file metadata: Figma owner, document and PDF authors, image data, Git authors, theme and plugin headers, CMS usernames
- tracking scripts or pixels of ours: there are none, ever
Client contact
- By default we don’t contact your client. You run the relationship.
- If you want us in client conversations, we join as your team, from your email, with you copied.
- We never discuss pricing, other clients or StudioPartner with your client.
- Our people use their real first names and never claim to be your employees. Asked directly, they say they’re on your agency’s web team (which is true), and questions about your company go to you.
Your side
- You provide the email and tool seats our team uses. You own them, so you pay for them.
- Your contract with your client must allow you to subcontract.
- Our people remain StudioPartner’s team. Using your accounts doesn’t make them your employees.
Onboarding, on day one
- You create the email accounts and enforce two-factor sign-in from your admin console.
- You invite them to your chat, project tool, Figma, Git and hosting.
- You share the project vault in your password manager.
- You point the staging subdomain, or confirm your client’s host.
- We confirm every account works, in writing, and the deadline clock can start.
Offboarding
At handover (unless you’re on a care or capacity plan), at the end of a plan, or whenever you choose, without notice:
- We confirm in writing that everything is in your systems. There’s nothing to hand back: the work was built in your accounts from day one, and the rights pass to you once the order is paid.
- You switch the email accounts off and remove our people from every tool. Our checklist lists every seat you gave us.
- We list any keys or tokens created during the project, so you can rotate them.
- We delete any local working copies within 30 days of handover, unless you’re on a plan, and confirm it in writing.
- Revoking access mid-project pauses the deadline clock. It never costs you anything else.
In the contract: Partner Agreement, Working under your identity
Escrow on your first project
Your first project’s money sits in escrow and is released milestone by milestone as you approve the work.
What this means for you
- Your first fixed-price project order, including a pilot, is funded with Freelancer.com, an independent escrow provider. The money sits there, and it reaches us only as milestones release.
- Funds release one milestone at a time: when you approve it, or automatically after 5 business days if you don’t respond.
- If we miss the deadline, the funds still held come back to you.
- After your first project, we bill you normally. Monthly plans are never escrowed.
| Order size | Milestones | When funds release |
|---|---|---|
| Under $1,000 | 1 | 100% at handover-ready |
| $1,000 to $3,000 | 2 | 40% at design approval, 60% at handover-ready |
| Over $3,000 | 3 | 30% at design approval, 40% at staging approval, 30% at handover-ready |
Read the full policy
How it works
- We send your order with its milestones.
- You fund the full order with the escrow provider, which verifies both of us.
- We work. At each milestone, you review.
- You approve and that milestone’s funds release to us, or you raise defects and we fix them first. With no reply within 5 business days, the milestone releases automatically.
- When the final milestone releases, the IP in the work is assigned to you.
What’s escrowed
An agency’s first fixed-price project order, including a pilot. If you start with a monthly plan, your first fixed-price project order is still escrowed. Care plans, capacity plans and the Dedicated Developer are never escrowed.
Build-only orders
On an order built from your Figma, design approval means your approval of the first built template.
The provider
Freelancer.com, an independent escrow provider, holds the funds and handles disputes under its own terms.
Refunds
If we miss the deadline, or under the First-Project Guarantee, the provider returns the funds it holds, and we repay any released milestones within 10 business days.
Currency
Order sizes above are US dollar prices. For an order in another currency, the band is set by our published US dollar price for the same items. Escrow is funded in the order’s currency, or in US dollars if the provider doesn’t support it.
After your first project
- Projects up to $3,750: 50% deposit to book, 50% at handover-ready.
- Projects over $3,750: 40% to book, 30% at design approval, 30% at handover-ready.
- Monthly plans: billed monthly in advance. The Dedicated Developer has a 3-month minimum, then runs monthly.
- Invoices are due on the payment term in your order. Growth and Studio Partners get net-14 on final invoices.
In the contract: Partner Agreement, Escrow on your first project
Confidentiality & consent-first portfolio
Your client’s work stays invisible unless you both say yes, in writing.
What this means for you
- Nothing we build for you is shown anywhere without your written consent and your client’s, which you collect. We never ask them.
- By default your work is invisible: it doesn’t appear in our portfolio, social posts, award entries or client logos, and there are no “built by” credits.
- You can withdraw consent at any time, and the work is removed within 5 business days.
- Only our own team works on your project. We never pass it to other freelancers or vendors without your written consent.
Read the full policy
Confidential by default
Everything about your projects is confidential: your client’s identity, briefs, designs, code, credentials, content, pricing and results. So is the fact that you work with us.
Uses that need consent
- our work page and case studies
- social media, Dribbble and Behance
- award entries
- sales decks and proposals to other prospects
- client logos and testimonials
- review sites such as Clutch
- naming the client anywhere
- anonymised descriptions, such as “a dental group”
Two keys, in writing
Consent is written: a signed form, or an email from someone authorised to give it. It needs your consent and your client’s, which you collect. It sets the scope: named or anonymised, which visuals, which numbers, the logo, and for how long.
Withdrawal
- Removed from our site and sales materials within 5 business days.
- Removed from social media where the platform allows.
No sub-outsourcing
Your project is worked on only by StudioPartner team members bound by our agreements. We never pass it to third-party freelancers or vendors without your written consent.
What we hold
Very little, because the work lives in your systems. How we handle access, data and deletion is set out under Security & access handling.
In the contract: Partner Agreement, Publicity and consent
NDA by default
A mutual NDA covers you before you share anything.
What this means for you
- A mutual NDA is built into our Partner Agreement, signed at onboarding, before you share any client information.
- It lasts 3 years after our relationship ends. Credentials and trade secrets stay protected for as long as they remain confidential.
- The white label relationship itself is confidential.
- Need one before you’ve signed anything? We send the same mutual NDA on its own.
- Prefer your own NDA? Send it over; if the terms are reasonable, we’ll sign it.
Read the full policy
Parties and purpose
You and StudioPartner, including its affiliated companies and team members, for evaluating and delivering white label work.
What’s confidential
- your clients’ identities
- briefs, designs and code
- credentials
- pricing and business information
- the existence of the white label relationship itself
What each side must do
- Use it only for that purpose.
- Share it only with people who need to know it and are bound by the same terms.
- Protect it with at least the care we give our own confidential information, and never less than reasonable care.
What it doesn’t cover
Information that is public, already known, independently developed, or that the law requires to be disclosed, with notice to the other side where the law allows.
How long
3 years after the relationship ends. Credentials and trade secrets stay protected for as long as they remain confidential.
At the end
On request, each side returns or destroys the other’s confidential information.
In the contract: Partner Agreement, Confidentiality
You own the IP
You own everything we make for you, the day it’s paid for.
What this means for you
- When an order is paid in full, all rights in the designs, code and content we create for it are assigned to you, and you can pass them on to your client.
- On your first project, paid in full means the final escrow milestone has released.
- The work sits in your accounts from day one: Figma in your team, the site on your or your client’s hosting (and code in your repo where the build uses Git), admin accounts in your or your client’s name.
- There’s nothing to hand back and nothing locked to us. Third-party tools stay under their own licences.
Read the full policy
Assignment on payment
All rights in an order’s deliverables are assigned to you when that order is paid in full. Until then you have a licence to review the work, and nothing more.
What’s covered
- design files
- front-end and back-end code
- custom plugins, sections and components
- documentation
- copy and assets we create
Our pre-existing materials
Starter themes, components and snippets we bring to a project stay ours. You get a perpetual, irrevocable, worldwide, royalty-free licence to use and modify them with the deliverable, and the licence transfers with it, so your client has it too.
Third-party materials
Plugins, themes, apps, fonts, images and open-source code stay under their own licences. We list them in the handover doc and buy them in your or your client’s name where possible.
Moral rights
Where the law allows, we waive our moral rights in the deliverables, or agree not to assert them.
No lock-in
Every account is in your or your client’s name and every credential is in your vault, so you never need us to reach your own work.
If a refund is taken
- Under the First-Project Guarantee, or an on-time refund where you choose to stop: no IP transfers, and the work is never used.
- An on-time refund where you choose that we finish free: the IP transfers at handover as normal.
Showing the work
We keep no right to show what we made for you. That needs your written consent and your client’s, as set out under Confidentiality.
In the contract: Partner Agreement, Intellectual property
Quality standards
We build it exactly as designed, and check it before you ever see it.
What this means for you
- Someone who didn’t build it checks the build against your design before you see it.
- We test every build at 6 breakpoints on real devices, in the 4 main browsers.
- You get the staging link only after our internal QA has passed.
- We fix defects free, always. A change is quoted first, and we never start it without your written OK.
Read the full policy
Design fidelity
- We build from your approved Figma, using its styles and variables.
- Someone who didn’t build it checks the build against the design before handover.
- You get side-by-side design and build screenshots at every breakpoint.
Responsive and browser testing
- 6 breakpoints: 360, 390, 768, 1024, 1280 and 1440 px, and fluid between them.
- An iPhone 13 mini, an iPhone 12 and a OnePlus 13s; a 13-inch MacBook Air and a 16-inch MacBook Pro; a 24-inch 1080p and a 27-inch 4K Windows display.
- The latest 2 versions of Chrome, Safari, Firefox and Edge.
Platform standards
- WordPress: WordPress Coding Standards, Bricks Builder or a custom theme chosen per project, and a few reputable plugins. If Elementor is a hard requirement, we work in it. We don’t use Divi.
- Shopify: Online Store 2.0 sections and blocks, Theme Check clean, no unnecessary apps.
- Webflow: a documented class system and documented CMS collections.
- Headless: TypeScript, linting and formatting, a component library, and Lighthouse checks in the pipeline.
Internal QA before you see anything
- The developer checks their own work.
- Someone who didn’t build it runs our QA checklist: function, forms, links, responsive, cross-browser, accessibility, performance, SEO basics, copy against what you supplied, and a search for any trace of our name.
- You review on staging. You only get staging after our internal QA passes, and passing it is part of what on time means.
Code review
Shopify themes and headless builds live in Git in your organisation, so every change is visible to you. WordPress and Webflow sites are built and checked on a staging copy.
Performance
- Targets we build to on key templates, measured in a lab test on a mid-range phone at handover: LCP under 2.5 s and CLS under 0.1, with responsiveness checked. We don’t guarantee them, and apps, scripts or content added later can change them.
- Shopify: mobile Lighthouse 80+ on the home, collection and product templates, measured at handover. Apps and content your client adds later can change the score.
Defects, changes and acceptance
- A defect is anything that doesn’t match what you approved, or doesn’t work. Defects are always fixed free.
- A change is anything different from what you approved. It’s quoted in writing within 1 business day with the days it adds, and never started without your written OK.
- For the deadline clock, review takes 2 business days per design round and 3 business days on staging. To approve a stage or raise defects, you have 5 business days. If you do neither by then, that stage is accepted. Using the work in production also counts as acceptance.
Documentation
A handover doc in your branding and, where your order includes it, a walkthrough video, plus a technical doc: plugins and apps, licences, hosting, where credentials live, and how to update.
Things we never do
- use nulled plugins or unlicensed fonts
- hide credits or links
- add tracking scripts of our own
- ship untested updates to production
In the contract: Partner Agreement, Acceptance and defects
Free to use on any build: Website launch checklist
SEO-safe launch checklist
Every redirect mapped. You sign off before we touch DNS.
What this means for you
- Every old URL is mapped to a new one before we build.
- Staging is never indexable.
- You (or your SEO lead) sign off the checklist before anyone touches DNS.
- We crawl the live site on day 1, 7 and 30, and fix anything we built that doesn’t work, under the 30-day warranty.
- The aim is to keep what the site already has. Nobody controls search rankings, so we never promise rankings or traffic.
Read the full policy
Every rebuild comes with a completed copy of this checklist. Steps marked (†) use your Search Console or analytics exports, or delegated access. If you’d rather run those steps yourself, we don’t need access to your client’s accounts.
A. Discovery, before the build
- A full crawl of the current site, archived: URLs, status codes, titles, meta, H1s and canonicals.
- Top pages by organic traffic and backlinks (†).
- The new URL structure agreed with you before we build.
- A 1:1 redirect map, old to new, all 301s. No chains, and no mass redirects to the homepage.
- A baseline of indexed pages, Core Web Vitals, top rankings and structured data (†), plus an inventory of tracking and conversion events.
B. Build
- Staging password-protected and set to noindex.
- Titles and meta descriptions carried over, or rewritten to your spec.
- One H1 per page, heading order kept, and self-referencing canonicals.
- Clean, lowercase, hyphenated URLs with one trailing-slash rule.
- Structured data added and validated, alt text carried over, and images compressed with their sizes set.
- Internal links pointing at final URLs, and pagination, filters, site search and hreflang handled as agreed.
C. Pre-launch QA
- Every mapped redirect tested (301 to 200), with no chains or loops.
- A staging crawl with zero internal errors, and an XML sitemap listing only live, indexable, canonical URLs.
- Production robots.txt ready, and noindex removed from every page meant to rank, checked page by page.
- Speed, mobile rendering and JavaScript-rendered content checked on key templates.
- A real 404 page, analytics and conversion events set up for production, and every form tested end to end.
- Your written sign-off on this checklist before any DNS change.
D. Launch day
- Launched in the client’s quiet hours, scheduled in your time zone.
- SSL live, with HTTP to HTTPS and canonical-host redirects.
- Live robots.txt and sitemap, with the sitemap submitted in Search Console (†).
- The top 50 URLs by traffic spot-checked.
- A temporary sitemap of old URLs submitted, so Google recrawls the redirects (†).
E. After launch
- Crawls of the live site on day 1, 7 and 30. Anything we built that doesn’t work is fixed under the 30-day warranty.
- Search Console coverage and 404s watched for 30 days (†).
- Core Web Vitals field data checked at 28 days (†).
- A post-launch report in your branding: what changed, what we fixed, and what we recommend next.
- We recommend keeping the redirects permanently, and for at least 12 months.
What we don’t promise
Rankings and traffic depend on search engines, competitors and your client’s content. This checklist protects what the site already has; it can’t promise rankings or traffic, and neither do we.
In the contract: Partner Agreement, Warranty
Free to use on any launch: Website launch checklist
Accessibility
Built to WCAG 2.2 AA, and documented.
What this means for you
- We design and build to WCAG 2.2 Level AA, within the limits below.
- We test every template with automated tools and by keyboard, plus screen-reader spot checks.
- You get accessibility notes and an unbranded accessibility statement template for your client’s site.
- We build to the standard and document what we did. That isn’t a certificate of legal compliance.
Read the full policy
The standard
We design and build to WCAG 2.2 Level AA.
Limits
- third-party embeds, widgets and apps
- content your client adds later
- existing content we didn’t touch
- third-party themes: when a build starts from one, we check and fix the common WCAG 2.2 AA failures in what we build and customise, and note anything in the theme we can’t change
Design checks
- colour contrast
- visible focus states
- targets of at least 24×24 px
- no information carried by colour alone
- a reduced-motion alternative for any motion
Build checks
- semantic HTML and landmarks
- a skip link
- everything works by keyboard
- ARIA only where it’s needed
- labelled form fields with clear errors
- alt text for every meaningful image
- caption support for video
Testing
- automated checks (axe) on every template
- a manual keyboard pass
- screen-reader spot checks with VoiceOver and NVDA on key templates
Deliverables
- accessibility notes in the handover doc
- an unbranded accessibility statement template for your client’s site
Context for your clients
Laws such as the European Accessibility Act and the ADA make accessibility a legal question for many of your clients. We build to the standard and document what we did. We don’t certify that your client’s site or business complies with any law, and this isn’t legal advice.
For a site we didn’t build
Accessibility remediation to WCAG 2.2 AA is an add-on, priced per template on our pricing page.
In the contract: Partner Agreement, Warranty
Security & access handling
We treat your client’s access and data as carefully as our own.
What this means for you
- We work only through named accounts that you create and control. No shared logins.
- Every account we use has two-factor sign-in.
- Credentials come through password-manager shares only, never by email or chat.
- Local working copies are deleted within 30 days of handover, unless you’re on a plan.
- If a security incident affects your client’s data, we tell you, never your client, within 24 hours.
Read the full policy
Access
- Our people use the email and tool accounts you create. You can see, audit and revoke every one at any time.
- Named accounts only, with the least access the job needs.
- Credentials shared only through a password manager, ideally your vault. Never by email or chat.
- Two-factor sign-in on every account we use, yours and ours.
- You switch our access off at handover unless you’re on a care or capacity plan. You can revoke it at any time.
Devices
Encrypted, managed, auto-locking and kept up to date. No client data on personal devices.
Build practices
- software from official sources only, never nulled
- dependencies kept up to date
- security headers set
- WordPress hardened: file editing off, login protection, XML-RPC off unless needed
- Shopify apps given only the permissions they need
- a backup before we change a live site, where the platform allows
Data
- We hold only what the project needs. Most of it lives in your systems.
- Local working copies are deleted within 30 days of handover, unless you’re on a plan, and deleted or returned sooner on request.
- Our Data Processing Addendum, at /legal/dpa, sets out how we process personal data for you and lists the sub-processors we use.
Incidents
- If we find a security incident affecting your client’s site or data, we tell you within 24 hours. We never contact your client.
- We give you what you need to meet your own notification duties.
People
Everyone on our team signs confidentiality terms before they get access.
In the contract: Partner Agreement, Data protection and security
How we use AI
AI speeds up routine work. A senior person checks everything it touches.
What this means for you
- We use AI tools for routine work only: code assistance, QA automation, and first drafts of alt text and docs.
- A senior team member reviews every AI-assisted output before it reaches you.
- Your client’s confidential data never goes into AI tools that train on inputs.
- Don’t want AI on a project? Say so in the brief, and we’ll work without it.
Read the full policy
Where we use it
- code assistance
- test and QA automation
- first drafts of alt text and documentation
- cleaning up content during migrations
Where we never use it
- confidential client data in tools that train on inputs
- AI-written code merged to your repo without review
- AI-generated images without your approval and a licence check
- messages to your client written by AI and sent without a person reading them
Review
AI-assisted work goes through the same review and internal QA as everything else.
Opting out
Per project, at no extra cost. Tell us in the brief.
In the contract: Partner Agreement, Use of AI
Every promise on this page is in the contract you sign.
Next, you send a short brief and we reply with a fixed price and a delivery date in writing. You pay nothing until you sign the order.