Your principles might be explored further in the context of an architecture of devolution. Data collection for service efficiency can occur by centralizing or by devolving and federating decision-making. Your goals of transparency and security serve architectures that devolve power, thus enhancing rather than only protecting autonomy. The operating system of the city should be modular and decentralized.

This also raises the other design principle you could use to supplement this excellent thinking you've already done: studying outflows as well as inflows of data. How the city makes available data it collects and derives, optimized for the activities of particular people, determines productivity in the entire economy. Taxi drivers, retailers in particular neighborhoods, light industry trying to schedule deliveries and shipments, culture workers trying to keep abreast of materials—the city knows when it is smart, but its intelligence lies in its ability to teach in real time. Think of several hundred thousand RSS feeds that each business or worker could subscribe to, containing exactly the information best estimated by that person to give her or him a way to be more productive, to have a better life. That information flow (prices, markets, conditions, offers) becomes the life's blood of commerce, enabled by a smart city that teaches smartly. Kerla Planning Commission thought about this as early as any government I know of. No one is doing it right yet.