Anonymous

My feedback

  1. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  2. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    I'd prefer the app to require a 8 numeric digit (minimum) keypad entry to unlock the app running in the back ground. I use a 32 character long upper, lower, alpah numeric, special character password so having to use keypass repeatedly to open would provide a level of quick entry protection while on the fly. It also provides protection in the event of losing your phone while logged in. I do however log out when not being used repeatedly. Therefore, the ability to log out if you want to close as currently held in my view is sufficient.

  3. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  4. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  5. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  6. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  7. 392 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    25 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    A real must guy's. If you want businesses (paying customers and I'm one of those potentially), this is another critical aspect. It makes total sense to enable the client to download their emails in a secure manner. It shouldn't take that much to do it either. Further as suggested below, it will assist in resource management for yourselves.

    I have a need to have all emails kept on my server with my client specific info (all one place) and not some here, there and everywhere as would be the case using Tutanota and others. Hence my reluctance to get fully on board.

  8. 42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    The metadata can be encrypted provided it remains within Tutanota (sender and receiver). So that's the starting point. The question of non Tuanota is another story. I appreciate the difficulties this presents but if you could. :) :) :).

  9. 283 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  18 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    256bit AES with 4096bit RSA is essential..... I'll gladly contribute to the cause but won't subscribe until it is provided. For those that want a lower level of security for speed/mobile device purposes, they should have the option. Flexibility guy's, then you satisfy all. :)

Feedback and Knowledge Base