Access, Security & Data Handling
Production systems deserve more care than trial-and-error prompting. This page explains what access each service asks for, what we do with it, how a change is approved — and what we will never do.
Every engagement runs under the same access rules. They do not change based on how urgent the work is or how large the system is.
If you have already pasted a credential anywhere, treat it as exposed and rotate it. If a message appears to ask you for a password, assume it is not from us and email hello@apprescuedesk.com before responding — we do not need your passwords to do this work.
The question is different for each service, so the access is too. We begin with the minimum that can answer it — and production customer data is never the default input.
Least privilege,Diagnosis
Read-level logs, configuration and recent-change evidence first.
RLS Review
Schema, policies, migrations, roles and synthetic test accounts. Production customer data is not the default input.
Readiness Audit
Repository, provider settings, architecture evidence, critical workflows and operational artifacts.
Independence Assessment
Ownership, repository, runtime, database, authentication, storage, provider and domain inventories.
Implementation or migration
Only the privileges required for the approved change, test, reconciliation and rollback.
Diagnosis and change are deliberately separated. Investigating your system does not authorise us to modify it.
Symptoms, recent changes, logs, configuration and connected services — at read level, before touching anything.
You receive the finding or root cause, the proposed change and a fixed or capped price. Work begins only after you say yes.
Where it is possible and meaningful, we back up, duplicate or document the affected configuration, schema or code before a material change.
Preview, staging or a branch where one exists; production only when there is no alternative and you have approved it.
You receive a short written summary of every change made and how the affected workflow was verified end to end.
At closure we list the access to remove and the credentials to rotate, and we remove ourselves where the platform allows it.
Where a specialist is needed, we disclose the role before access is granted. Specialists use named accounts, minimum privilege and the same confidentiality, approval, evidence and access-revocation rules.
App Rescue Desk stays accountable for engagement scope and QA. We do not subcontract where the customer agreement does not allow it.
AI may assist with redacted log summaries, test-case suggestions, finding normalization or report drafting. It does not approve or make production changes.
Customer secrets, production credentials, private repositories and personal data are not sent to external AI systems without an approved contractual basis and explicit handling controls. Final findings and production decisions are reviewed by a human.
These require enhanced contract, data-processing, insurance and specialist review. Where those conditions are not available, the engagement is declined.
App Rescue Desk is an independent service run at pilot scale — a working process, not a compliance programme.
If you believe you have found a vulnerability in this website, or that an access grant related to your engagement has been misused, email hello@apprescuedesk.com with the details. We acknowledge reports during published desk hours and tell you what we intend to do. Please do not test against systems you do not own.