Frequently Asked Questions
Straight answers before you pay .
Answers on the bug fix service — what it covers, what it costs, how access works and what we deliberately don’t promise. Assessment products are covered further down.
- Incident desk
- Mon–Fri, 08:00–21:00 TRT (UTC+3)
- Incident diagnosis
- $99, credited toward any repair
- Questions
- hello@apprescuedesk.com
- Assessments
- Scope and price confirmed before payment
The bug fix service
one way inWhat does the bug fix service actually cover?
One incident in a live web app: a login, payment, data flow, email, deployment or domain that used to work and is broken now. It starts with a paid Incident Diagnosis — a human traces the failure across your app and the services around it, then hands you the evidence, the affected component and a fixed or capped repair price. See which production failures a web app bug fixing service can repair.
The repair itself begins only after you approve that scope and price in writing. One bug, one fix — no retainer, no feature backlog. If what you need is evidence about an app that still works (data isolation, launch readiness, a migration), that is an assessment, covered at the end of this page.
What if the app has never worked correctly?
Tell us anyway — we say whether it fits before you pay.
The diagnosis is for restoring something that used to work, so a workflow that never ran in production is a different job. Describe what broke and we tell you which it is; a full build or open-ended implementation backlog stays outside scope either way.
Platforms & limitations
honestly boundedDo you only support Lovable?
No. We work on web applications built on React, Next.js, TypeScript, Node.js, Supabase, PostgreSQL and Stripe, together with the authentication, email, API, deployment and domain services around them.
Apps built with an AI builder such as Lovable, Bolt or v0 sit inside that stack — they run on the same React, Supabase and Stripe pieces. What we don’t take on: WordPress and other CMS, marketing or brochure sites, native mobile apps, and PHP/Laravel or Rails stacks.
Do you fix websites, WordPress or online stores?
No. We work on web applications, not sites. WordPress and other CMS, Shopify or Webflow stores, marketing and brochure sites, and native mobile apps are outside the stack.
If you are unsure which one you have, describe what broke and we will tell you before you pay.
Do you support older projects, or an app built by someone who has since left?
Yes, after verifying the actual repository and runtime. We don’t need the person who built it — we read the code and the connected services ourselves.
We don’t assume every project uses the same framework, deployment model or payment path, whether it was written by hand or generated by an AI builder.
What if the cause is a third-party outage?
We can identify and document the external blocker and recommend a safe next step or workaround where one exists.
We can’t repair infrastructure controlled by a third party — but confirming the fault isn’t in your app is itself a useful answer.
Are you affiliated with Lovable, Supabase or Stripe?
No. App Rescue Desk is an independent service and is not affiliated with or endorsed by Lovable, Supabase, Stripe or any other third-party platform.
Timing & process
How quickly do you respond?
Paid incidents are reviewed by a human within 15 minutes during published incident-desk hours.
Assessment delivery is measured in business days and confirmed after scope and access are agreed. It isn’t covered by the 15-minute incident response objective.
Will you change production immediately?
No. Diagnosis and assessment don’t authorise production changes.
Any implementation begins only after you approve the exact scope, price, risks, test plan and rollback or forward-fix path.
Pricing & deliverables
you pay for a resultWhy pay for a diagnosis or assessment before implementation?
The paid entry product is a usable deliverable in its own right: evidence, risk, a bounded decision and an implementation scope.
It prevents open-ended debugging, premature rewrites and blind production changes.
Can you guarantee a fix?
We guarantee the agreed paid deliverable within a qualified scope, subject to the access and dependency limitations in the Terms.
We don’t guarantee that every provider outage, lost-data event, security incident or migration can be repaired safely.
Access, security & data
Will you need my passwords?
No. Don’t send passwords, API keys or access tokens by form, email or chat.
We prefer customer-controlled screen sharing, collaborator invites or minimum-privilege temporary roles. The access & security page sets this out in full.
Can you recover deleted or corrupted data?
We can investigate available backups, database history and recovery options, but we don’t guarantee recovery of deleted or corrupted data. Anyone who guarantees that without seeing your system is guessing.
A potential data-loss incident may need a separate, agreed scope before anything is changed.
Execution & follow-on work
Do you offer ongoing maintenance?
No. This is one-off work — one bug, one fix. We don’t sell retainers, monthly plans or an open-ended feature backlog.
Assessments
for apps that still workWhich assessment fits which question?
The RLS & Data Isolation Review when role or tenant isolation is uncertain, the Readiness Audit when launch or real-user production risk needs assessing, and the Independence Assessment when platform dependency, external deployment or a migration needs planning.
All three are fixed-scope, priced before payment, and don’t include production changes unless a separate execution scope is approved.
Is the RLS Review a penetration test?
No. It’s a scoped configuration and data-isolation review.
It isn’t a penetration test, compliance certification or active-breach investigation.
Can you guarantee zero downtime or zero data loss during migration?
No. We define the assumptions, rehearsals, acceptance criteria, cutover controls and rollback so those risks can be managed honestly.
What happens after an assessment?
You can use the report independently.
Where implementation is justified, we provide a fixed or capped scope tied directly to selected findings, milestones, acceptance criteria and rollback.