Description:
When building apps that handle sensitive user data — think medical records, legal documents, financial information, personal journals — users need to trust that even the app builder can't casually browse their information.
Currently, RLS does a great job ensuring users only see their own data within the app. But as the admin, everything is still visible in the Data tab. For privacy-sensitive use cases, this is a dealbreaker for user trust and can create compliance concerns.
What I'd like:
A per-entity option (e.g., admin_visible: false) that:
Hides that entity's records from the admin Data tab
Keeps everything else working normally — RLS, backend functions, API calls
Requires a deliberate multi-step process to re-enable, so builders can credibly tell users "we cannot access your data"
Why the existing workarounds fall short:
External storage (S3/GCS) adds major infrastructure complexity and breaks the simplicity that makes Base44 great
Client-side encryption breaks any server-side processing (AI features, backend functions, automations)
Who benefits: Anyone building apps in healthcare, legal, finance, HR, education, therapy, or any space where users share personal information. This would be a meaningful differentiator for Base44 in the privacy-conscious market.
I'd love to see this on the roadmap — upvote if you're building something where user data privacy matters!
Please authenticate to join the conversation.
In Review
Feature Request
24 days ago

CD67
Get notified by email when there are changes.
In Review
Feature Request
24 days ago

CD67
Get notified by email when there are changes.