On registration, password-reset and confirmation forms, do not check account existence synchronously. Schedule a Sidekiq job that either sends a 'reset your password' email if the account exists or a 'confirm your account' email if it doesn't. The HTTP response takes constant time, defeating timing-based enumeration attacks. Doesn't work for login — use rate limiting there.