- Profile object itself can be considered as non-private/public.
- Every file embed into the Profile object also can be considered as non-private/public (cause embed attachments adds the encryption key to the object where it has been embed)
- Other objects, that were linked from the profile page remains private
We mention private instead of encrypted because technically everything is encrypted, the only thing is that the key for the profile object is derived from the accountid — so in the future people will be able to read profile of each other. The rest linked objects are depend on sharing options that will be introduced later.