1Purpose
This Policy describes DIVE2CORE account and authentication security, India-only access enforcement, protected-content controls, watermarking, content-misuse reports, Report Issue, security actions and learner support.
2Server-authoritative model
Frontend validation is for user experience only. The server decides, and its decision is final, for:
- Account identity and state.
- Email verification and account creation.
- Geographic eligibility.
- Session ownership and token validity.
- 15-day free-access validity.
- Paid-pack state and expiry.
- Course and resource entitlement.
- Progress and completion.
- Test Yourself answer checking.
- Saved positions.
- Referral qualification.
- Career Support entitlement and service states.
- Payment state.
3Password security
Passwords meet the password-strength requirements shown at Sign Up and are protected with secure one-way hashing. DIVE2CORE does not store or display plain-text passwords.
4Sign-up verification code
The sign-up email code is tied to the email address entered, has a limited lifetime (currently 20 minutes), allows a limited number of resends and wrong attempts, and cannot be used again once it has been accepted. No account is created for an email address until its code has been entered correctly.
To protect inboxes from misuse, the number of codes that can be requested for one address, and the number of requests from one connection, are limited.
5Password-reset OTP
A password-reset OTP is specific to password reset and cannot be used for sign-up verification, nor the other way round.
Password recovery follows OTP verification and then requires the learner to create a new password. It does not use a clickable reset link and does not automatically log the learner in after reset. Setting a new password ends every session that was signed in with the old password.
6Login lockout
Five wrong password attempts on one account lock that account's sign-in for 15 minutes, regardless of which device or connection the attempts came from. A correct sign-in resets the count. This protects the account even against attempts spread across many devices or connections.
7One active authenticated session
One learner account may have one active authenticated session at a time. A new valid Sign In ends the previous session.
A session also expires after a maximum lifetime (currently 30 days) regardless of activity, requiring the learner to sign in again.
Protected requests are checked against the current active session rather than trusting stale browser state.
Security · India-only accessAuthenticated/account services are India-only. Public informational pages may be available outside India, but account and protected features are not.
8Devices and the two-device limit
DIVE2CORE records each device an account signs in from, so that the limit of two different devices per account in the Terms can be applied. For each device it keeps the browser, operating system and device type, a random device identifier stored in the browser, the sign-in address, the first and latest sign-in times and the number of sign-ins. It also keeps a history of each sign-in (time, address and browser) for 12 months, so that an administrator can see how an account has been used.
A sign-in from a third, unregistered device/browser combination is refused automatically, at the moment of sign-in and before any session is created, even with the correct email, password and one-time code. The refusal does not register the device, replace a registered device, use up a device slot or end the legitimate learner's current session, and it does not by itself suspend the account or cancel an active pack; the learner is shown a message asking them to continue from a registered device or to contact Support about a device change. A device change, where supported, goes through a verified and audited process rather than automatically removing a registered device. This check runs on the server and does not depend on anything the browser reports about itself.
These records are read only by authorised DIVE2CORE administrators, and each time an administrator opens a learner's device or sign-in records it is recorded in the audit log. The place an address is in is looked up when the record is viewed and is not stored. Separately from the automatic refusal above, an account whose device history suggests it is being shared may still be reviewed and, where warranted, deactivated. That decision is made by a person, not automatically, and the administrator's reason is kept in the audit log.
The device identifier is not a password and not a credential. Clearing the browser's site data creates a new one at the next sign-in, so a changed device is looked at in context before any action is taken.
9India-only protected access
Authenticated/account services are India-only. Public informational pages may be available outside India, but account and protected features are not.
The server checks geographic and security eligibility before Sign Up, email verification and other sensitive account operations, and on authenticated and protected requests.
Access is denied from outside India and where the location cannot be determined reliably. It may also be denied where prohibited masking, proxy, hosting or Tor conditions are detected.
10VPN, proxy, Tor and location masking
VPNs, proxies, Tor and similar technologies must not be used to bypass DIVE2CORE's India-only rule.
DIVE2CORE may use third-party or internal IP/network intelligence, hosting/datacenter detection, Tor intelligence and other security signals.
DIVE2CORE does not promise perfect detection of every sophisticated VPN or proxy.
1115-day free-access authorization
Free learning resources are accessible only while the server confirms:
- the account is successfully verified;
- the request satisfies India-only and security rules;
- the current time is within the active free-access window, unless an active paid entitlement exists; and
- the requested resource is part of the designated free-access scope.
Free-content completion and free-access validity are separate.
Important · Protected contentProtected DIVE2CORE learning content is for the learner’s personal educational use. Unauthorized resale, credential sharing, systematic extraction or bulk copying is prohibited.
12Paid-access authorization
Paid learning, preparation and project resources are accessible only when the server confirms an active applicable paid entitlement. Payment activation and expiry are never inferred from what the screen shows.
13Protected-content usage
Protected DIVE2CORE learning content is for the learner's personal educational use under the applicable account and access rights.
Unauthorized resale, credential sharing, systematic extraction, bulk copying, mirroring or substantial redistribution is prohibited.
This Policy does not limit any right or exception that cannot legally be excluded.
14Content delivery controls
Protected course figures and diagrams are delivered through short-lived signed links, so a copied link stops working. Test Yourself answers are checked on the server and are not sent to the browser before a question is attempted, and the number of attempts is limited. Requests are rate-limited to protect the service.
15Technical limits of content protection
DIVE2CORE uses browser and interface controls, session controls, watermarking and monitoring to discourage misuse, but cannot guarantee prevention of operating-system screenshots, external-camera capture, screen recording, OCR, developer tools or every method of copying displayed content.
16Watermark placement
Protected course learning uses exactly three watermark positions:
- Default: Top-left + Center + Bottom-right.
- Alternate: Top-right + Center + Bottom-left.
Watermarks are low opacity, not tiled, do not obscure important educational content and remain visible in fullscreen.
Example: DIVE2CORE · D2C-IND-001003 · 28-Sep-2026 11:18 AM IST.
17Watermark privacy
The watermark uses a pseudonymous learner reference and a timestamp. It does not show the learner's name, email, mobile, password, OTP or authentication token.
18Watermark evidence principle
A watermark/account correlation may support investigation but does not automatically prove intentional misuse by the account holder.
DIVE2CORE considers context, ownership, possible account compromise, onward sharing and other available evidence before taking an account action.
19Reporting suspected unauthorized content
A report may include the URL or platform, a description of the suspected content, an optional screenshot or other evidence and a contact method if needed.
Reports should not include passwords, OTPs or session tokens.
Evidence provided by a reporter is handled carefully, and unnecessary personal information is redacted or minimised where practicable.
20Review of misuse reports
Authorized staff verify that DIVE2CORE has the relevant rights, preserve appropriate evidence, consider possible lawful exceptions, assess whether an account correlation is reliable and review the possibility of account compromise or onward sharing.
A report does not automatically remove content or penalize an account.
21Proportionate security/content actions
Depending on verified evidence and severity, actions may include:
- requesting verification;
- ending sessions;
- restricting, suspending or deactivating the account where unauthorised sharing, an attempt to bypass the device limit or other misuse is confirmed (a refused third-device sign-in alone is not such a case, and one account's misuse does not deactivate other accounts, including other students of the same college);
- requiring a password or security reset;
- warning the learner;
- temporary restriction;
- requesting removal from an external platform;
- legal review for serious or repeated misuse;
- other proportionate action permitted by the applicable terms and law.
22Report Issue inside learning
Report Issue applies to Module Introduction, Understand, LiveFlow, Common Issues and Test Yourself.
The system may automatically capture Domain · Module · Chapter · Tab · Scenario · Step.
Issue categories include Visual Diagram · Theory · Flow/Step error · Null/Wrong data.
23Support scope
Support may assist with:
- Sign Up, verification and Sign In.
- Password recovery.
- India-only access and security issues.
- Session and account issues.
- Payment, pack activation and expiry.
- Learning access and saved position.
- Progress and activity questions.
- Technical problems.
- Content, visual and flow issues.
- Referral.
- Career Support.
- Feedback and testimonial questions.
- Policy and account-deletion requests.
- Security and content-protection reports.
24Support contact
Support email: support@dive2core.com. DIVE2CORE does not promise fixed support hours or a fixed response time.
Account emails (verification codes, password recovery, receipts and notices) come from noreply@dive2core.com; replies to them reach support.
25Identity verification for sensitive support actions
DIVE2CORE may require reasonable account verification before changing sensitive account details, assisting with account deletion, handling certain payment or access disputes or disclosing account-specific information.
Support never asks for the learner's password or OTP.
26Security incidents
DIVE2CORE may end sessions, force password resets, temporarily restrict access or take other protective action when there is reasonable evidence of compromise or elevated risk.
If a security incident affects personal data, DIVE2CORE takes steps to contain it and notifies affected learners and authorities where the law requires.
27Appeals and review
A learner can contact support to ask for a review of a security or content-related restriction, or of a support response they are not satisfied with. DIVE2CORE keeps enough internal audit information to understand the decision being reviewed.
