Client allows unauthenticated access to pages which should require login

The only page which seems to require login at the moment is the dashboard (home page `/`).

For example, visiting:

- `/add-new-profile`
- `/profiles/1`

will both show the respective pages even though a user should have to log in first,

Start by locating the client-side routing and authentication checks for `/`, `/add-new-profile`, and `/profiles/1`. Verify how unauthenticated access is handled for the dashboard, then ensure the other listed pages require login and confirm their behavior while logged out.

Written by the indexing model from the issue text.