A privacy and security pledge

Update - <2022-10-18 Tue> - I just also found out about The Santa Clara Principles - it’s not exactly what I’m thinking about, but it’s interesting as a model and has input from the EFF, ACLU, and The Brennan Center for what it’s worth.

I’m thinking about building a piece of software…more than that actually. Been designing it for a while now and there are certain values I’m trying to bring to the project. Things to do with what I want and feel is right around privacy, data-ownership, security. Values that I want the software I buy and use to hold as well. It got me thinking that I’d like to sign some kind of pledge of user-goodwill on topics like these.

I found the Student Privacy Pledge 2020 and this resembles what I’m looking for “…a voluntary but legally binding industry pledge…”. I want the more broad version that goes beyond just students…and I want it vetted, or even better written, by a substantial data privacy advocate like the EFF.

Draft of something like the following, first from the users’ perspective and then followed by the statements I as a software company will agree to.

I, the user:

  • want to own my data
  • want to have a choice in the services where that data gets stored
  • want to have the option to only store data on my device
  • want to have any centralized data store with end-to-end encryption
  • want to know by sight that my data is encrypted in transit (bring green browser locks to mobile apps)
  • want to be able to sell access to my data and reap some benefit (discounts, pay, other perks)
  • want to be able to revoke that sale and know my data is destroyed
  • want to be able to specify the duration from 1 month to 1 year and beyond
  • want to control the marketplace for my data

I, the software maker agree to the demands above:

__

Jake Levine, Software Maker of the future

====== fin ======

Related Posts

My first (and only) Pebble watch face

I was looking for that sometimes watch face when you need a break - and need to be reminded.

github - the time is now - I’d really like to be able to make this for the Apple Watch line. It was the reason I bought the first Apple Watch.

A picture is worth 1000 4 words:

The move to react native

The ENTIRE reason I initially pursued programming later in my career as a product manager was because I was frustrated with the time it took to get from the abstract concepts written in my verbose requirements documents to actual code that was living and breathing. I initially learned Rails because of the approachability of Ruby and the community and also because of some of the tooling that got messy stuff out of my way so I could get the basics done more rapidly. Progress a few years and I’ve launched an iOS app using Swift…then had hired a contract dev to build the android app. This was my first venture as developer or product into the mobile app world and it was enormously frustrating to have feature disparity between platforms. Inevitably, iOS would have the features before Android because I was at the helm and the Android users didn’t appreciate that. So I started looking for options and I had seen a few things about React Native. I immediately started absorbing as much as I could by reading everything, took a Udemy class, and then embarked on rebuilding my Swift/Java app in React Native. I have a week or two of coding left and it will be in both app stores. Efficient, effective, easy to use, intelligent…it’s fair to say I love React Native and would really welcome coding in it full time. I am using Facebook (login and sharing), Parse Server, (entire data system) Redux, OneSignal for notifications, Ad Mob, Google Analytics, and React Native Router Flux.

Stop Skynet

Start early, start now.

Say please and thank you to ChatGPT and any other conversational AI.

Don’t be a jackass.