GDPR Compliance

[kirillseva]

As you probably already know, in three days GDPR compliance must be implemented for all storage solutions that process data of European citizens.

In your README I noticed the following line:

π holds every file that could possibly exist!

This sounds extremely alarming as it looks like in three days use of this technology will be considered illegal. Please advice on how I would go about removing my personal data from π.

[pgerhardt]

Thinking out loud. We may be able to get to GDPR compliance by rounding Pi down to 3. Yes, we'll lose some data but we're really down to the wire here.

[kirillseva]

@pgerhardt that would prevent me from storing other data in πfs, such as drivers license, credit cards and social security numbers of US citizens, which is a crucial aspect of any sufficiently big entreprise system. Do you have any other solutions in mind?

[Croydon]

Maybe it is already enough if we censor the last few digits. Should be enough to make it not uniquely identifiable. Like it is often done with IP addresses.

[jeffli678]

Can anyone figure out how much would we be fined for such a huge violation?

[LoganDark]

I don't know. π stores every trade secret in the universe. I believe you should be able to look up what the fine will be in your π

[magicgoose]

If pi contains all the data that could possibly exist then the answer to this question

how I would go about removing my personal data from π.

can also be found in pi.

[berndjendrissek]

It is hard to prove whether π contains any given arbitrary string of digits. While the digits do not repeat (else it would be a rational number), this is no guarantee that all sequences of digits appear somewhere. Liouville numbers (such as 0.11000100000000000000000100..., the Liouville constant) are transcendental, just as π is, but (assuming base 10) the Liouville constant does not even contain the string "2". So I propose to close this issue as being unable to be reproduced, since I have seen no particular person's name in π's decimal expansion. The real bug is in the README that makes a false (or at least, unproven) claim.