How "proprietary" are Database Design Documents?

All my clients are schools and I'm happy to share my code with anyone that wants it. (I know everyone isn't in the same boat and I'm not judging)... but there are some confidential things in there. For example, I have various scripts which are hard-coded to send emails to certain people. Most emails are based on permission groups for staff members (for example the "leadership team" gets certain emails" but others are just one-offs so I hard-coded them.

The database itself has private student information (IDs, phone numbers, etc.).

Other than that I can't think of anything else that's "private" in the Database Design Document. I'm sure a VERY dedicated hacker could probably suss out some issues, but I don't think the DDR exports any passwords or secret keys or anything.

So if I purge my DDRs of emails, could I safely use them to train an AI that is then shared with other people?

I mean some of my code is not very clean, so that might be one reason NOT to do that... but just thinking out loud about how we might go about getting a better trained AI focused on Filemaker.

Your DDR may contain IP address, user accounts, authentication details, license keys, file paths, network info, etc.

The assumption is that the DDR contains everything.

"Save as ... " CLONE, produces a database with no records, although it retains all security settings, including accounts. You should probably remove most of those accounts before sharing.

Trap: If you have used key pair tables as the source for value lists, a CLONE will wipe out all that data.