Your Mac device stays central
The deployment model is built around your own device rather than shifting sensitive work into shared environments.
Privacy
Privacy is part of the deployment model, not a footnote.
The service is built around your Mac device, a non-admin user, and clear support boundaries so the setup respects how sensitive work should be handled.
Core principle
We only deploy to your Mac device on a non-admin user.
This principle helps keep the implementation closer to least privilege. It also makes the site promise concrete and easy to understand.
Non-admin user only
We do not require an admin-level install path as the default approach, which reduces risk and keeps stronger boundaries in place.
Validation before installation
We confirm the need and constraints before recommending a setup, especially where privacy or work-managed hardware is involved.
Clear support boundaries
You know what we configure, what stays under your control, and when a work-managed environment needs employer approval.
Personal Mac devices
Usually the cleanest path.
Personal Mac devices often make it easier to deliver a straightforward setup with clear ownership boundaries and fewer policy conflicts.
Work-managed Mac devices
Need extra care.
A work-managed device may require employer approval or IT review. The site should set that expectation early so the service stays realistic and privacy-aware.
Start with your workflow
Describe the work first and we will validate the right setup path.
That helps us understand whether the privacy model and the device situation fit your needs before anything is deployed.