Subject: Account recovery request — project wunmkbijqnzsmwfjjymc (proof of ownership included)

[devsmurf]

Hello Supabase Support,

I have lost access to the email address registered to
my Supabase account, and password reset attempts on the
inboxes I currently control do not deliver a reset
email. I am therefore writing from a different email I
own (cursorpro35@gmail.com). This is a critical project
and I would deeply appreciate your help in recovering
dashboard access. I am happy to follow any verification
process you require.

Project I am trying to recover

• Project ref: wunmkbijqnzsmwfjjymc
• Database host: db.wunmkbijqnzsmwfjjymc.supabase.co
• Project status: currently paused (due to inactivity)
• Approximate creation date: 3 September 2025 — derived
  from the iat claim (1756902135) of the project's anon
  JWT

Candidate registered emails — please check whether the
account is bound to either of these:

• enesirin6@gmail.com
• cursorpro01@gmail.com

(I have tried password reset on both addresses and did
not receive a reset email, which is why I am contacting
support directly.)

Proof of ownership — information that only the project
owner could possess

1. Postgres database password — I currently hold the
   database password for the postgres user on
   db.wunmkbijqnzsmwfjjymc.supabase.co. Last 6 characters
   of the password: txI95f. On request, I can connect to
   the database and execute any read-only query you
   specify (for example SELECT current_database(), now();)
   and return the exact output as live proof.
2. Anon API key (NEXT_PUBLIC_SUPABASE_ANON_KEY) — JWT
   issued for ref=wunmkbijqnzsmwfjjymc, role=anon,
   iat=1756902135, exp=2072478135. Last 6 characters of
   the signature: qlABSM.
3. Service role key (SUPABASE_SERVICE_ROLE) — JWT
   issued for the same project, role=service_role,
   identical iat/exp. Last 6 characters of the signature:
   DJNy2o. (Full key not shared in email for security
   reasons — I can provide it through a channel you
   designate.)
4. New-format publishable key — I also hold a
   sb_publishable_… key that was generated for this
   project. First 20 characters: sb_publishable_KmPrv.
5. Personal access token (now expired) — I have an
   sbp_… personal access token previously issued under
   this account. Prefix: sbp_2a5023…. It now returns
   Unauthorized, which itself confirms the account exists
   but the session is invalidated.
6. Local .env.local file — I retain the original
   .env.local from the project, with all of the above keys
   intact. I can share screenshots, file timestamps, or
   partial contents on request.

Please let me know:

• Which verification steps you require to confirm
  ownership
• Whether the registered email on the account can be
  updated, or whether the project can be transferred to a
  new Supabase account I create
• Any preferred secure channel for sharing the
  remaining key material

Thank you very much for your time. I am available to
respond immediately to any follow-up questions.

Best regards,
Enes Şirin

[GaryAustin1]

You need to reach out to support@supabase.com

It will not get handled from Github.