Privacy Manifest

[wlxo0401]

Privacy Manifest

[gwynne]

Such a manifest is somewhat pointless for Vapor, since it is not primarily intended for use on Apple platforms and there is no code specific to any relevant macOS or iOS APIs or data. The manifest ends up looking like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>NSPrivacyCollectedDataTypes</key>
	<array/>
	<key>NSPrivacyAccessedAPITypes</key>
	<array/>
	<key>NSPrivacyTracking</key>
	<false/>
	<key>NSPrivacyTrackingDomains</key>
	<array/>
</dict>
</plist>

I'm not actively against adding this manifest to the Vapor package, but I'm not clear on whether it would be useful to do so.

@0xTim Any thoughts?

[wlxo0401]

@gwynne

Thank you for your quick response.

I thought I should add a privacy manifest to every library I've added to the app even if I'm not using a specific API, is it not??

[0xTim]

@wlxo0401 you only need to add a manifest if they store user data or are part of a list of popular xcframeworks (https://developer.apple.com/support/third-party-SDK-requirements/)

Since Vapor is neither, you don't need one. If however you receive an email saying you do, please create another issue and we can liaise with DTS to clear it up