Access policy

Temporary access, only after scope approval.

First contact is for public website details only. Access is requested only after the fault is scoped, the price is approved, and the payment route is agreed.

Do not send

  • Personal passwords or 2FA codes.
  • Recovery codes, payment logins, or registrar master credentials.
  • Root server credentials unless a manually approved repair requires a safer route.
  • Encryption keys, recovery material, or unrelated secrets.

Preferred access

  • A temporary user created for the repair.
  • Least-privilege permissions for the agreed work.
  • Staging access where available.
  • Backup confirmation before production changes.
Workflow

How access is handled.

  1. We inspect public evidence and provide the proposed scope.
  2. You approve the scope and payment route.
  3. You create a temporary access account for the agreed repair only.
  4. We complete the repair, verify it, and send the close-out report.
  5. You revoke the temporary access after delivery.
Stop conditions

When we pause.

We pause for manual review if the repair touches payment processing, bookings, personal-data forms, DNS, databases, root server access, legal/medical/financial content, regulated content, or anything outside the approved scope.