5 ms·
For GDPR it is better to store ‘is legal drinking age’ instead of age or forbid even the birthdate
by rahkiin 3y ago
For GDPR it is better to store ‘is legal drinking age’ instead of age or forbid even the birthdate
- neilellis 3y agoUntil the legal drinking age changes :-)
- actionfromafar 3y agoThat’s why you need the SAAS, for compliance and i18n!
- rahkiin 3y agoIdeally you only verify at time of purchase and do not care afterwards until next purchase. Bare minimum to hold to laws
- jcrites 3y agoIdeally you also don't need to verify it more than once, though. Otherwise, it will be friction that detracts from the user experience.
- yard2010 3y agoFun fact: in some places in Canada the legal drinking age is 19
- epcoa 3y agoPlease elaborate what is “fun” about that fact? The drinking age is 19 in most of Canada, 18 is the exception. And the drinking age varies all over the world. It used to be between 21 in most of the US until the voting age was lowered to 18 in 1971. It was then either 18 or 19 in most states (generally the more liberal ones) until 1984 when the national minimum was passed. 19 really is sort of a sweet spot for socially liberal North America.
- loa_in_ 3y agoThen it's time to flush all entries, set the column to nullable or use an enumeration and re verify everyone on the next visit
- insanitybit 3y agoI don't think we need to design the entire "can you legally drink" SaaS, hopefully my example is clear enough and people can leverage the concept for more reasonable circumstances.
- xmcqdpt2 3y agoShow HN: drink.ly (YC W2023), a cloud-native, B2B drinking age verification SaaS, backed by Postgres
- azeirah 3y agoGiven that I keep getting ads on reddit about some API to predict age and gender from a given dataset of users and the OP of that ad keeps saying that it's hugely succesful, this business is practically guaranteed to succeed. Seriously, want to make some easy money? Build this.