Why we ask for access (and why it's safe)

At some point during your project, we will ask for access to one or more of your online accounts. This can feel a bit unsettling — handing over access to important systems is a big deal. This guide explains exactly why we ask, what we use it for, and the limits we place on ourselves.

Why access is necessary

Building and maintaining a website requires working directly inside your systems. There is no way to update your WordPress site, change a DNS record, or configure your hosting plan without being logged in.

We could ask you to make every change yourself, but that would slow your project down significantly and increase the risk of errors. Our job is to handle the technical work so you do not have to.

Here are the most common reasons we ask for access:

You stay in control

Granting us access does not transfer ownership of anything. You are always the account owner.

Here is what that means in practice:

• You can remove our access at any time. We will show you how in How to revoke our access later.
• Many platforms keep an activity or change log you can read, so you can check what we changed and when.
• We will never change your billing details, add payment methods, or transfer ownership of your accounts.

What we never do

Our access policy:

• We only ask for the minimum access needed to complete the work.
• We use invite-based access (a separate login) rather than your personal password whenever the platform supports it.
• We do not share your credentials with third parties. Internally, they are stored in an encrypted password manager accessible only to our team.
• We release access at the end of a project unless you have an ongoing care plan.

How we ask for access

When we need access, we will send you a clear, specific request — usually via ClickUp or email. That request will tell you:

1. What platform or account we need access to.
2. What role or permission level we need.
3. Why we need it and what we plan to do.

If we ever ask for something that is not on this list, or if a request feels unclear, please ask us. We are happy to explain.

The difference between access and ownership

It helps to think of access like a key to your office. A key lets someone in so they can do their job. It does not make them the owner of the building.

We use the key to do the work. The building — your website, your accounts, your data — is always yours.

Common questions

What if I don't feel comfortable sharing access?

That is completely valid. Tell us what makes you uncomfortable, and we will find an alternative approach. In some cases, we can walk you through making changes yourself. In others, we may be able to use a more limited access method. We will always work with you to find something that feels right.

Will you be able to see my private emails or personal data?

It depends on the platform. For example, if you add us as an admin on Google Workspace, we could technically access mailboxes — but we have no reason to and we will not. If this is a concern, let us know and we will use the most limited access role that still lets us do our work.

What happens to our access when the project ends?

At the end of every project, we send you a checklist to review and revoke any access we no longer need. If you are on a care plan, we keep a minimal level of access to handle ongoing maintenance. See How to revoke our access later for the full process.

How do I know you are who you say you are?

Always verify access requests through a channel you already trust — our usual ClickUp task, or a reply to an existing email thread. We will never ask you for sensitive access out of the blue from an unfamiliar address. If something seems off, call us.

Related guides

• How we keep your logins safe
• Delegate access vs. sharing a password
• Access checklist for a new project
• How to revoke our access later
• Sharing passwords safely