iOS 1Password rated for everyone

blockorange
blockorange
Community Member

Would you be able to modify 1Password for iOS so that that isn't rated 17+ (which is due to the built in browser)? I created a shared vault for my child's passwords, but they didn't have access to it on their iOS device due to app restrictions. I now have to choose between allowing 17+ apps and 1Password or neither. Could you tie enabling of the browser to the app restrictions setting on the iOS device (or one of the other restriction settings)? Hopefully one of these solutions would allow you to change the rating of the app for iOS. If not, maybe you could create a child's version without the browser. Thanks.

Comments

  • prime
    prime
    Community Member

    Now this is wha I did for my daughter (who's 16 now). I went on her Apple ID
    https://appleid.apple.com
    I changed my daughters birthday so it shows she 17. It doesn't ask to comfirm it or anything, and then I added this info in my 1Password so I knew what birthday I used.
    my daughter is old enough and knows better too, but not all kids are the same.

  • Could you tie enabling of the browser to the app restrictions setting on the iOS device

    I don't believe that is technically possible, but I will pass the feedback along to our development team. Thanks!

  • prime
    prime
    Community Member

    I get the parent restrictions, but this is a great tool
    to start teaching kid about on-line security and using different passwords for everything. I got my daughter this when she just turned 16 and she loves it. When we realized the restrictions, I just changed her brithday. She uses it all the time and shows me how much she added to it.

    How hard would it be just to have 2 versions? One with the browser and one without? The one without could be used for all ages.

  • How hard would it be just to have 2 versions? One with the browser and one without?

    Probably not feasible to maintain two distinct apps just for this purpose. I'll pass the suggestion on to our developers though.

This discussion has been closed.