3 ms·

Is this for GDPR compliance?

• ceejayoz 8y ago
  Almost certainly, but it's nice they're making it generally available. I've seen some sites' GDPR exports limited to EU customers, which seems like a dick move.
  • notimetorelax 8y ago
    The thing is, sites cannot use IP geolocation to decide if their users are EU residents or not. I think in the end it’s more expensive to try to manage this than to let everyone do the export and deletion.
    • sb8244 8y ago
      Don't you just need to provide access to the data within 30 days of asking for it? That would allow for not making it public but having it publicly available.
      • notimetorelax 8y ago
        I’m not a GDPR lawyer, but AFAIK export has to be satisfied within 7 days and removal within 30 days. Not sure what are the delays for a correction. I think the most expensive part could be the human time needed to make judgments on the residence of the requestor. Fully automated processes available to all the user based won’t have this extra cost.
  • Someone1234 8y ago
    Reminds me of California's labels in that way. Everyone mocks them, but some of them are legitimately useful e.g.: https://www.nrdc.org/experts/veena-singla/want-avoid-toxic-couch-chemicals-just-look-new-label https://www.nrdc.org/experts/veena-singla/want-avoid-toxic-c... Same thing here, because border specific stuff aren't worth the hassle, the lowest common denominator (in this case GDPR) becomes the new international standard. Additionally some US politicians have proposed copying parts of the GDPR into US law which would pretty much make this a permanent staple.
    • kodablah 8y ago
      > because border specific stuff aren't worth the hassle For GitHub maybe, not true for all (or even most?) non-EU businesses. For most, the "hassle" of ignoring the region requiring GDPR is much easier/safer than the compliance/risk of conformance.