---
title: "Comment by Hrithwik Bharadwaj on \"Getting Started with Next Auth\" | Hashnode"
description: "I am super new to next-auth and trying it for my new side project . I have few questions How can I get custom data which is stored in the DB for the user like u"
url: "https://hashnode.com/posts/getting-started-with-next-auth/64a832418dee05a5f82599b6/comment/64aa4368395b682e51ab682f"
---

[Discussion](https://hashnode.com/posts/getting-started-with-next-auth/64a832418dee05a5f82599b6)

Comment [Getting Started with Next Auth](https://hashnode.com/posts/getting-started-with-next-auth/64a832418dee05a5f82599b6)

[Hrithwik Bharadwaj](https://hashnode.com/@hrithwik)

[Jul 9, 2023](https://hashnode.com/posts/getting-started-with-next-auth/64a832418dee05a5f82599b6/comment/64aa4368395b682e51ab682f)

I am super new to next-auth and trying it for my new [side project](https://prepwithai.vercel.app/) .

I have few questions

-   How can I get custom data which is stored in the DB for the user like userId. (Should I use the session hook and whenever the use session is called , it makes a DB call)
    
-   How can I stop making a session API call everytime the tab is switched ?
    

[Arjun](https://hashnode.com/@dotarjun)

[Jul 9, 2023](https://hashnode.com/posts/getting-started-with-next-auth/64a832418dee05a5f82599b6/comment/64aa4368395b682e51ab682f#reply-64aa7156a25b1020144627a6)

1.  Yes, using the NextAuth session hook is a good option to fetch custom user data.
    
2.  For that use case, you should store the user data in cache on the client side. You can use sessionStorage to do that. This way you only make the API call once, and on subsequent tab switches you read from the cache.
