How to secure sensitive form data in databases
Contact form submissions accumulate high-liability personal data like names, phone numbers, and free-text messages that site owners rarely need to query. Because forms automatically collect this information and nobody ever deletes it, sites are left holding sensitive records they never actually wanted.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Leaving form entries sitting in the database in plaintext indefinitelyDid this help you?
- 2Relying on standard server-side security or host-level protectionsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“Form submissions, and I don't think it's close.”source ↗
“It is the highest-liability data on most sites — names, phone numbers, and whatever people type into a free-text "message" box — and it is the one place where "you can't query it" costs approximately nothing.”source ↗
“Most site owners never wanted that data, they just have it because a form put it there and nobody ever made the decision to delete it.”source ↗
Where this came up
People with this problem also raised
- 17How to use AI for accounting without breaking client confidentiality
- 2How to manage and match large external lists without importing them all
- 2Why is rushed custom software so insecure?
- 2Accidentally sent confidential internal email to the wrong person
- 4Why does a CRM get so messy as outbound volume grows?
- 2How to secure vendor emails on personal devices without MDM