Should we add Precise Location to our SDK's privacy manifest if we use the current SSID?

Does this mean we should add the data type "Precise Location" to the privacy manifest of our SDK?

The guidance here is if you are requiring a user to accept the usage of CoreLocation in your app as part of it's functionality then you should also include this in the Privacy Manifest so that it can be aggregated as part of the App Privacy report. See an example here for precise location.

I'm not sure I understand your answer: is that a "Yes" or a "No"?

We don't use CoreLocation, but (from your link):

Information that describes the location of a user or device with the same or greater resolution as a latitude and longitude with three or more decimal places.

Does the SSID pinpoint a location with that high precision?

(If so, we should add this data type, according to this documentation)

Yes; you need precise location.

That entitlement and that permission gets you SSID and BSSID, and those are accurate and unique values.

Or in short, yes, list precise location.

It's axiomatic: you need to have precise location to use the API (text swiped from another reply):

    * @method fetchCurrentWithCompletionHandler:completionHandler:
     * @discussion This method returns SSID and BSSID of the current Wi-Fi network when the
     *   requesting application meets one of following 4 requirements -.
     *   1. application is using CoreLocation API and has user's authorization to access precise location.
     *   2. application has used NEHotspotConfiguration API to configure the current Wi-Fi network.
     *   3. application has active VPN configurations installed.
     *   4. application has active NEDNSSettingsManager configuration installed.
     *   An application will receive nil if it fails to meet any of the above 4 requirements.
     *   An application will receive nil if does not have the "com.apple.developer.networking.wifi-info" entitlement.