GM!

Can I share this highly controversial move on TwitteX?

No, we expect you to be responsible enough to have an internal standard and to have audited their processes against that standard.

Where is the internal audit report?

This is a very unsatisfactory answer.

NFC is not common in the US and Europe, yet.

This is discriminatory towards people who don't want or can't afford a phone with NFC capabilities.

Granted, I'm in the US, so I'm not your targeted market, but... This kind of stuff will limit your market with those that could be your most staunch supporters.

OK, sure, but WTF does NFC have to do with that.

I block NFC permissions anyway, so... Screw them.

It would be nice to have a description of the process you're using internally, to mask, shuffle, encrypt, archive, disassociate, etc. the data, to protect against accidental leaks or malicious internal or external parties, and to ensure the data is only visible and discernable and associateable with a particular customer in a particular use case and at a particular time by a particular class of employee.

Also, what is the archiving system you have in place and for how long are you legally required to store each peace of data? Will data be auto-expunged after that date and when a customer account is dormant for X length of time or ends their account?

Also, where will the physical location where the data will be stored? Will it be live local, remote inhouse, cloud, or offline?

If you have a live, associated list of e-mails, how do we know it won't get leaked or hacked, a la Ledger?

Is there a Data Security and Storage Plan, where we can see these rules?

GM ☕️😎🫂💜

I TOLD YOU THEY WAS HIRING!!! ⚡️

nostr:note1km5cuy056ql4l5sl2nnulrjt3vruanxf7rgua065v7wlzzx64p3qd0m222

Need a Diplom Informatiker with Java, angular, python, lead dev for 10, agile, 20 years retail and investment banking? But I need to escape the EU.

#jobstr