Eng 3003 date of birth as Identity

[Vagoasdf]

Ticket ENG-3003

Description Of Changes

Adding Date of birth as an custom identity, alongisde with a Date Picker component so we can pass it to privacy requests up the line

This is in the context of a custom Dynamics CRM integration that would require a secondary identity besides the email for the cases where multiple contacts share the same email, (I.E a household all inscribed under the same email originally).

Code Changes

• Adding date as a possible custom field type on clients/privacy-center/components/common/CustomFieldRenderer.tsx
• Adding validation for date of birth field
• Adding the field to hooks and types

Steps to Confirm

1. Include the following on the config.json file of the privacy center, on the identity_inputs for one of the actions:

 "date_of_birth": {
          "label": "Date of Birth",
          "field_type": "date",
          "required": true
        }

2. Go to the privacy action center
3. Verify that the date of birth shows on the desired action
4. Emit an DSR with that action
5. On the Admin suite, verify that the privacy request shows the date as an identity

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ready	Preview, Comment	May 18, 2026 9:22pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
fides-privacy-center	Ignored		May 18, 2026 9:22pm

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)

See the Details below.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA db92983.

Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

Scanned Files

• clients/package-lock.json
• clients/privacy-center/package.json

[github-actions]

Title	Lines	Statements	Branches	Functions
admin-ui		6.94% (3176/45763)	6.35% (1682/26485)	4.8% (651/13542)
fides-js		79.17% (1977/2497)	66.25% (1249/1885)	73.31% (349/476)
privacy-center		82.53% (364/441)	79.74% (189/237)	74.07% (60/81)

[lucanovera]

Nice work! The feature works as expected and the code changes look good.
I made a small tweak to fix the full width class on the date picker that wasn't working:

Regarding the display date format, I'd advise you to consider for a followup if a MM/DD/YYYY format would be more appropriate here. That would apply if this feature is intended for a US audience. In admin-ui we've been using that format too, although it might be time we have a setting for that, I'll create a ticket.

I'd also advise to run the thorough security review skill on the backend changes for this as it touches on a sensitive logic such as identity resolution.