A user of your replication package has identified what would appear to be PII in your data files:

(PROVIDE SAMPLE FILES HERE)

Please verify if this is, in fact, the case, and if not appropriate as per your IRB approval, revise the files to remove the PII (replacing with fake identifiers, and removing names). Our revision policy is here: https://www.aeaweb.org/journals/data/revisions-policy, and we verify compliance.

As a precaution, we have unpublished your current deposit.

[NOTE] As a reminder, no data with PII should be published in the main replication package. If you have PII in your dataset, and are allowed to publish it with restrictions, please contact us for the best solution, but do not include it in the main replication package.

We recommend using the J-PAL maintained PII-Scan for R https://github.com/J-PAL/PII-Scan or PII-Scan for Stata https://github.com/J-PAL/stata_PII_scan to get an idea of potential PII in your dataset.

⚠️ 📢 You remain ultimately responsible for ensuring that no PII is included in the published replication package.

If this is a violation of your IRB protocol, you may need to notify your IRB about this breach. You can mention that the above measures have been undertaken. You can find the number of downloads of your replication package listed on the openICPSR website.

Please let us know if we can help in any way to rectify this issue.

Sincerely,