Is the Supabase anon key safe to put in my app?

Yes. The anon (publishable) key is made to be seen by everyone, but only while Row Level Security, the database's rules about who may read each record, is on for your tables.

A key is a long password your app uses to prove who it is to another service, here Supabase, which holds your app's data. Supabase's documentation says the publishable key, the newer form of the anon key, has low privileges and is designed to be exposed in web pages and mobile apps, because Row Level Security limits what it can reach.

That protection depends on your rules. If a table has RLS (Row Level Security) off, or a policy (one of those rules) that lets everyone read, the anon key can reach that data, and the key is in every visitor's browser. The browser is the program people use to open websites, such as Chrome or Safari, and anyone can look at what it receives.

The key that must never be there is the secret (service_role) key, which skips RLS entirely and opens everything.

Sources

Each source below was read on 2026-11-16. Documentation changes over time, so check the source for the current wording.

  • Supabase documentation, API keys, accessed 2026-11-16
  • Supabase documentation, Row Level Security, accessed 2026-11-16