Thank you for your quick reply. So actually this is a feature in newer version :)
I used the function suggested by you to find the usable area rect.
OS.get_window_safe_area() returns (0, 0, 1080, 2257) in v3.2.3 whereas it returns (0, 83, 1080, 2257) in v3.3. So moving my score panel to rect.y in script solved my problem, thanks.
I noticed that returned Y position is more than actual. Because, in case of v3.2.3 the panel is just below the camera notch whereas in v3.3 it is much lowered. (i.e. physically it is not on the same location in both cases). Anyway, after getting the usable rectangle, if Y position is not zero I can subtract some pixels to achieve the required results.