Subscription scoping/filtering/privacy ?

[Flavelius]

Hi, I'm trying to find out whether spacetimedb could be a fit for my needs.
From what I could gather from the docs I see a huge issue that I need some more info about, where the docs' chatbot wasn't insightful.
As far as I see every client can potentially subscribe to data it doesn't own because all data in a public table is readable by everyone, or am I missing something?
Client subscriptions can not be filtered/sanitized?

I have no prior experience with this kind of technology, so some of my assumptions might be incorrect.
I assume that reading/receiving data on a client can only be done with subscriptions. And subscriptions are controlled by clients.

The chatbot suggested using special view-tables for filtered public data, but these have the same everyone-can-query-everything-in-them issue as far as I see.

Can subscription control for clients be disabled and handled by the server?

Any clarification is welcome

[Jacadasag-dev]

I believe this is the case. Main reason why I'm not using it. A really good design would be to allow a parameter to be passed with a subscription request. CLIENT -> REQUEST SUBSCRIPTION(idvalue=1) -> SpacettimeDB -> Select * From [TABLE] Where 'id' = [idvalue]