6 ms·

I had to rewrite my Google privacy policy at least 4 times before they accepted it. This is the current accepted one: https://victorribeiro.com/privacy_policy.

by atum47 2y ago

I had to rewrite my Google privacy policy at least 4 times before they accepted it. This is the current accepted one: https://victorribeiro.com/privacy_policy.html https://victorribeiro.com/privacy_policy.html (i copied from somewhere else and changed it). This is the one they rejected: https://victorribeiro.com/privacy_policy.txt https://victorribeiro.com/privacy_policy.txt

dvngnt_ 2y ago
I mean... the accepted one is better formatted. i would have done the same tbh
- jpalawaga 2y ago
  it took something easily readable and straightward and transformed it into something nobody is going to read. Is that really better?
  - dvngnt_ 2y ago
    for a business yes
kbenson 2y ago
I appreciate that the version they indirectly encouraged you to use by rejecting the other one is much more clear about how you not only don't store anything, but don't collect anything. For the pedanticists here which might argue you can't collect anything without storing it, I suspect there's a lot of wiggle room there (even if only in the developers mind and not legally), and the additional information is useful to guard against that. For example, getting paid to receive and forward data, or to send it directly to a third party may be something a developer could do and thing they are complying with "we don't store your data". Technically correct, probably not legally correct, but unlikely to matter legally unless noticed and they are sued. Much better to be explicit about things as long as it's still easily readable.
- refulgentis 2y ago
  It's cute, but: it's a lie. Data is stored. We (privacy advocates) won, there's legislation now, this stuff is real, The Man cares. You can't handwave, saying you don't "store" or "collect", or whatever verb you like that, to you, means "we don't do anything bad" -- when you're in that territory, ex. Google's privacy policy becomes "we don't sell your data" --- can you imagine? There's precious few applications that don't "store", "collect", etc. The other move I see is people going with "we don't store/collect data": I assume they're trying to claim they don't store data server-side, but very frequently in my experience, they are are storing data server-side, just what they perceived as trivial (ex. cloud sync when the product is cloud only, that's not "we" storing "your data", it's us syncing because you asked!) If you feel good & witty writing your privacy policy, and end up with a single sentence one, something went wrong. If you're sufficiently small you'll probably get away with it, but...ugh. This also presents a significant opportunity: it's hard to find a good privacy policy, that actually handles all the regulatory obligations you now have as a developer, and isn't just legalese amounting to "We take it, keep it, let us know if we should get rid of it"
  - atum47 2y ago
    I honestly packed all the code inside of a APK and distribute it via Google app store. I make no request to get out send any data. How am I collecting or storing any data?
    - refulgentis 2y ago
      > no request to get out send any data Correct: that means you are not relaying data to a network, or retrieving data from a network. Your claim was "We don't store your data, period." I can't know for sure, but for the vast majority of applications, data is stored somewhere, be it on the device, or on the server. High scores? Game state? Levels completed? You sure you're not storing data? That's why it was rejected. Don't get me wrong, I don't think you're doing anything shady, I don't think you're doing it in the general terms people worry about, I very much doubt anyone will find out, or care if they did. It's just a useful example of something that plays well in the HN comments section but not in the real world, I didn't even realize until a few months back. These are de facto legal statements now. Every store requires them, and they're not paying a lawyer to double check them for you. You can get away with it on side project games, but it's not something you can get away with at a business.
qwertox 2y ago
Cool homepage, but the Qubes game doesn't load :(
- atum47 2y ago
  I'm loading it from itch.io and apparently they always break something. Next free time i got I'll load the game from my own server. Sorry about that. You can play it on Android for free if you want
Y_Y 2y ago
That apostrophe in the first sentence doesn't belong. Apostrophe rules are impossible even for natives, but I thought you might like to know.
- atum47 2y ago
  ...of its user? I'll update ASAP.
chronogram 2y ago
The rejected one makes me expect data is still being processed, or stored by third parties. The new one has a lot of fluff but at least it is clear that it doesn't collect anything and doesn't retain anything.
Rygian 2y ago
I would also reject the "We don't store your data, period". That's like a pharmacist telling customers "we didn't add poison to this medicine".

by atum47 2y ago

dvngnt_ 2y ago

I mean... the accepted one is better formatted. i would have done the same tbh

jpalawaga 2y ago
it took something easily readable and straightward and transformed it into something nobody is going to read. Is that really better?
- dvngnt_ 2y ago
  for a business yes

kbenson 2y ago

I appreciate that the version they indirectly encouraged you to use by rejecting the other one is much more clear about how you not only don't store anything, but don't collect anything. For the pedanticists here which might argue you can't collect anything without storing it, I suspect there's a lot of wiggle room there (even if only in the developers mind and not legally), and the additional information is useful to guard against that. For example, getting paid to receive and forward data, or to send it directly to a third party may be something a developer could do and thing they are complying with "we don't store your data". Technically correct, probably not legally correct, but unlikely to matter legally unless noticed and they are sued. Much better to be explicit about things as long as it's still easily readable.

refulgentis 2y ago
It's cute, but: it's a lie. Data is stored. We (privacy advocates) won, there's legislation now, this stuff is real, The Man cares. You can't handwave, saying you don't "store" or "collect", or whatever verb you like that, to you, means "we don't do anything bad" -- when you're in that territory, ex. Google's privacy policy becomes "we don't sell your data" --- can you imagine? There's precious few applications that don't "store", "collect", etc. The other move I see is people going with "we don't store/collect data": I assume they're trying to claim they don't store data server-side, but very frequently in my experience, they are are storing data server-side, just what they perceived as trivial (ex. cloud sync when the product is cloud only, that's not "we" storing "your data", it's us syncing because you asked!) If you feel good & witty writing your privacy policy, and end up with a single sentence one, something went wrong. If you're sufficiently small you'll probably get away with it, but...ugh. This also presents a significant opportunity: it's hard to find a good privacy policy, that actually handles all the regulatory obligations you now have as a developer, and isn't just legalese amounting to "We take it, keep it, let us know if we should get rid of it"
- atum47 2y ago
  I honestly packed all the code inside of a APK and distribute it via Google app store. I make no request to get out send any data. How am I collecting or storing any data?
  - refulgentis 2y ago
    > no request to get out send any data Correct: that means you are not relaying data to a network, or retrieving data from a network. Your claim was "We don't store your data, period." I can't know for sure, but for the vast majority of applications, data is stored somewhere, be it on the device, or on the server. High scores? Game state? Levels completed? You sure you're not storing data? That's why it was rejected. Don't get me wrong, I don't think you're doing anything shady, I don't think you're doing it in the general terms people worry about, I very much doubt anyone will find out, or care if they did. It's just a useful example of something that plays well in the HN comments section but not in the real world, I didn't even realize until a few months back. These are de facto legal statements now. Every store requires them, and they're not paying a lawyer to double check them for you. You can get away with it on side project games, but it's not something you can get away with at a business.

qwertox 2y ago

Cool homepage, but the Qubes game doesn't load :(

atum47 2y ago
I'm loading it from itch.io and apparently they always break something. Next free time i got I'll load the game from my own server. Sorry about that. You can play it on Android for free if you want

Y_Y 2y ago

That apostrophe in the first sentence doesn't belong. Apostrophe rules are impossible even for natives, but I thought you might like to know.

atum47 2y ago
...of its user? I'll update ASAP.

chronogram 2y ago

The rejected one makes me expect data is still being processed, or stored by third parties. The new one has a lot of fluff but at least it is clear that it doesn't collect anything and doesn't retain anything.

Rygian 2y ago

I would also reject the "We don't store your data, period". That's like a pharmacist telling customers "we didn't add poison to this medicine".