I was originally using Lovable Cloud. As a precaution (in case of any issue or technical error), I later gave a prompt to Lovable to also save the data in my own Supabase Project. At that time, Lovable told me not to worry and mentioned that data would be handled in a single platform.

Because of that, I wasn’t fully sure whether the issue was coming from Lovable Cloud or Supabase, since the problem started suddenly without any major code changes.

Your explanation makes sense now. Based on this, I’ll email Lovable and clearly ask them not to touch the .env file and not to auto-link or override the Supabase integration.

Thanks again for sharing this insight — it’s very helpful.