It is simple like this.

SPUtility.GetSPField('City').Hide();

Please refer this question to show how to apply it.

Edit:

As far as you are concerned not only on the displaying and having high security concerns over the security of data, you better try something like creating another list with a one-to-one mapping. Then add a lookup column from first list to the second list and move the secured column from first list to second list. Then you can give a restricted permission on the second list. This will be the option as you cannot use SPD or even InfoPath.

It is simple like this.

SPUtility.GetSPField('City').Hide();

Please refer this question to show how to apply it.

Edit:

As far as you are concerned not only on the displaying and having high security concerns over the security of data, you better try something like creating another list with a one-to-one mapping. Then add a lookup column from first list to the second list and move the secured column from first list to second list. Then you can give a restricted permission on the second list. This will be the option as you cannot use SPD or even InfoPath.

It is simple like this.

SPUtility.GetSPField('City').Hide();

Please refer this question to show how to apply it.

It is simple like this.

SPUtility.GetSPField('City').Hide();

Please refer this question to show how to apply it.

Edit:

As far as you are concerned not only on the displaying and having high security concerns over the security of data, you better try something like creating another list with a one-to-one mapping. Then add a lookup column from first list to the second list and move the secured column from first list to second list. Then you can give a restricted permission on the second list. This will be the option as you cannot use SPD or even InfoPath.