Everything in one place, written to help you navigate your learning journey.
Our approach to privacy
Code with Jamshed is a learning platform for courses, practice, projects and developer resources. This policy explains the kinds of information involved when you visit or use these features.
The information involved depends on the features you choose. For questions about this policy or your information, please use the contact details below.
Information you provide
You may provide information directly when you create an account, update a profile, save a resume draft or send us a message.
- Account and profile details, such as your name and email address.
- Content you choose to enter, such as resume details, practice responses or messages.
- Learning information, such as completed lessons, saved items and test attempts, where a feature records them.
Browser storage and technical information
The platform uses browser storage and may use a session cookie to support functions such as sign-in, preferences and a secure social-login flow. Some learning progress or saved choices may be stored on your device or saved to your account when the feature supports it.
Your browser and network send technical information when they connect to a website, such as an IP address, browser type and requested page. Technical records may be used to operate, troubleshoot and protect the service.
How information is used
Information associated with the features you use helps us operate the learning experience.
- Create and maintain accounts and support authentication.
- Provide courses, practice, saved progress and other requested features.
- Respond to messages and support requests.
- Investigate errors, maintain security and improve the service.
Third-party services and sharing
When you use social sign-in or follow an external link, you interact with the relevant third-party service. Its own policies explain how it processes information.
Our pages may load Google Fonts, an embedded Google Map, resources from content delivery networks and, where enabled, a Norby chat widget. These services may receive connection details such as your IP address; the chat provider may also receive information you enter into the widget.
Service providers used to operate the platform, such as hosting or technical infrastructure providers, may process information for those services. Information may also be disclosed where required by applicable law or to protect the platform and its users.
How long information is kept
Information is kept for as long as reasonably needed to provide the relevant feature, respond to requests, maintain security or meet applicable obligations. Retention can differ by type of information and the service used.
You can contact us for more information about a specific record or to request its deletion.
Your choices and requests
You may contact us to ask about access to, correction of or deletion of information associated with your account. We may need to verify your identity and assess the request against applicable obligations.
You can also manage your browser storage and the permissions given to a social sign-in provider through that provider’s settings. Clearing browser storage may sign you out or remove progress saved only on that device.
Keeping information safer
We use security measures intended to help protect the platform and account information. No online system can be guaranteed completely secure. Keep your account credentials private and contact us if you suspect unauthorized access.
Updates and contact
We may update this policy as the platform or its practices change. The updated version will be posted on this page. For privacy questions or requests, contact Code with Jamshed using the email link below.
Social sign-in
If you choose a sign-in provider such as Google, GitHub or Facebook, that provider handles your sign-in and may share a unique account identifier, name or email address with us, depending on the permissions and information available. Google sign-in requests basic identity information, including profile and email.
We use the information received to identify your account and support sign-in. Your provider password is entered with the provider, not in our sign-in form. The provider’s own privacy policy also applies.