AUTHROBODocs

Delete an app (and clean up your client)

What happens when you delete an app in AuthRobo, and the checklist to tidy up your own codebase and providers afterward.

Updated July 3, 2026

Deleting an app is permanent and immediate. Open the app in the dashboard, scroll to Danger zone, and choose Delete app — you'll be asked to confirm.

What AuthRobo removes

Deleting the app cascades to everything AuthRobo stores for it:

  • The app itself (its client_id / client_secret).
  • Every end-user under the app, and their linked social/password identities.
  • All active sessions and refresh tokens (so existing logins stop working).
  • Enabled sign-in methods and any provider credentials you saved.
  • The app's billing links (subscription rows).

Tokens already issued keep verifying until they expire (they're signed JWTs), but no new ones can be minted and /users/me lookups will 404.

What AuthRobo does NOT touch

  • Your client codebase — that's yours; see the checklist below.
  • Your Stripe account — if you used Stripe Connect, only the link is forgotten; your Stripe account and its data remain.
  • Your provider apps — your Google/LinkedIn/GitHub OAuth apps stay as they are.

Client-side cleanup checklist

Once the app is deleted, tidy up the consuming app so it doesn't call a client that no longer exists:

  1. Remove the env vars — AUTHROBO_ISSUER_URL, AUTHROBO_CLIENT_ID, and AUTHROBO_CLIENT_SECRET (and any NEXT_PUBLIC_AUTHROBO_CLIENT_ID).
  2. Remove the UI — delete @authrobo/react buttons/components (AuthRoboButton, AuthRoboAuth) and the provider if you wrapped your app in AuthRoboProvider.
  3. Remove the SDK calls — any @authrobo/sdk usage (exchange, verify, getUser, billing helpers). Uninstall the packages if nothing else uses them: npm rm @authrobo/react @authrobo/sdk.
  4. Remove the callback route — the redirect_uri handler you added just for AuthRobo (e.g. /auth/callback).
  5. Invalidate stored tokens — clear any AuthRobo access/refresh tokens you cached in your own sessions or database.
  6. Provider redirect URLs — if a Google/LinkedIn/GitHub app was used only for this integration, remove AuthRobo's callback from its authorized redirect URLs (or delete the provider app).
  7. Custom domain — if you'd set up a white-label auth domain, remove its DNS CNAME record.

That's it — nothing else phones home to AuthRobo.

Ready to build? Create your app → or browse the API reference.