Base44 Security Scan Flags Private Fields on Public Records
Base44Base44's security scan now flags private fields, such as email addresses or payment identifiers, on records that anyone can read. The Security tab offers to hide each flagged field. The record stays readable while the sensitive field stays private.
Key Takeaways
- The security scan now detects private fields on publicly readable records.
- Examples include email addresses and payment identifiers.
- The Security tab offers a fix to hide each flagged field.
- Records stay readable while the sensitive field is kept private.
- The check targets a common mistake in apps that mix public and personal data.
- It adds to Base44's recent security scan improvements around data access.
A New Check in the Security Scan
Base44's security scan now looks for private fields on records that are readable by anyone. Examples include email addresses and payment identifiers. When a record is public but contains a field like this, the field could be exposed to visitors who were never meant to see it.
One-Click Hiding
For each flagged field, the Security tab offers to hide it. Hiding keeps the record itself readable, so the app keeps working for public use, while the sensitive field is no longer exposed.
Why It Matters
Public data tables are common in apps built by non-specialists, and mixing public and personal data in one record is an easy mistake. This check catches that pattern automatically and gives a direct fix, extending the scan's recent work on access rules for user data.