Keys : When you first onboard your @sign, the phone will cut the keys for you (that is accessible only by you), and allow you the option to back up a copy of the file (your .atKeys file). This is the file you would use to onboard your @sign to other apps. You should backup this file to another device to ensure you can continue to use your @sign in the event you lose your phone.

As for the keys file on your lost phone, it is dependent on the phone that you are using. iPhone storage is encrypted by default, and Android’s encrypted storage was introduced in 2016. However, if your phone has no password, none of this matters as the individual in possession of your phone will be able to access your data regardless. Both Android and iPhone have options to remotely wipe your data.

Pricing : ​​In our model, people don't really incur any costs for using the apps built on the @platform. They could choose to use FREE @ signs or they can pay to buy custom/vanity @ signs depending on their preference. That is the only cost from their standpoint but that is totally up to them. There is no cost based on server storage or usage - we cover all of that.

See https://atsign.com/pricing/

Secondary Servers: When it comes to the ownership of the secondary, there are two options for hosting. However in both cases, you can ensure that you are the owner of the data. As mentioned above, the keys get cut on your device, and you are the only one in possession of them.

Option 1: We host your secondary on our infrastructure - everything is encrypted and we don’t have the keys! We can’t nor want to do anything with your data.

Option 2: Host your own secondary server with dess - this gives you additional control over where the secondary server lives. See https://atsign.dev/docs/get-started/dess/.