---
title: "Discussion on \"Supabase anon key exposed: is it a problem?\" | Hashnode"
description: "Discussion on \"Supabase anon key exposed: is it a problem?\". Short answer: the anon key being visible is normal. Whether that's a problem depends entirely on your Row Level Security. The service_role key is a different story."
url: "https://hashnode.com/posts/supabase-anon-key-exposed-is-it-a-problem/6ad298218915d2bf894dc24b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Supabase anon key exposed: is it a problem?](https://lastmilekit.hashnode.dev/supabase-anon-key-exposed-is-it-a-problem?utm_source=hashnode&utm_medium=feed)

Short answer: the anon key being visible is normal. Whether that's a problem depends entirely on your Row Level Security. The service\_role key is a different story.

Oct 16 · 5 min read · lastmilekit.hashnode.dev  
Read the article

-   [#supabase](https://hashnode.com/tag/supabase)
-   [#security](https://hashnode.com/tag/security)
-   [#web-development](https://hashnode.com/tag/web-development)
-   [#vibe-coding](https://hashnode.com/tag/vibe-coding)
-   [#vibecoding](https://hashnode.com/tag/vibecoding)

## Written by

[Last Mile](https://hashnode.com/@lastmilekit)

@lastmilekit

  
[View profile](https://hashnode.com/@lastmilekit)

Launch kit + free pre-launch URL check for vibe-coded apps.

Launch kit + free pre-launch URL check for vibe-coded apps.

## Responses 2

Markdown supported · ⌘↵ to post

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/supabase-anon-key-exposed-is-it-a-problem/6ad298218915d2bf894dc24b/comment/6ad2b884a305ffe66918868e)

The test question 'if a stranger calls every table directly with the anon key, what do they get?' is the clearest way to frame this, because it moves the focus from hiding the key to what RLS actually allows. Noting that the newer sb\_publishable\_ and sb\_secret\_ formats exist alongside the legacy JWT keys is helpful too. The warning not to paste a possible service\_role key into a third-party decoder is easy to miss and worth the space.

[Last Mile](https://hashnode.com/@lastmilekit)

[Oct 19](https://hashnode.com/posts/supabase-anon-key-exposed-is-it-a-problem/6ad298218915d2bf894dc24b/comment/6ad2b884a305ffe66918868e#reply-6ad615b35e216481d8be9348)

Thanks. That reframe is the whole point: the anon key is meant to be public, so the real question is what RLS lets it do. Quick habit: after every new table, curl it with only the anon key while logged out. If rows come back, RLS is off or too loose.
