HCESL · Privacy

Privacy policy

Last updated:

This policy explains how HCESL collects, uses, shares, stores, and deletes personal information when you visit the website, contact us, or use a learner account.

1. Scope and operator

This policy applies to the HCESL website at hcesl.notsolazy.dev, its learner workspace, and messages sent to the HCESL support and privacy mailbox. Arnab Sarkar, an individual operator in India, decides how HCESL uses this information and is the privacy grievance contact. Reach him at arnabsarkar0132@gmail.com.

Links to other websites, including research sources, are governed by those websites' own privacy practices once you leave HCESL. This policy does not cover them.

2. Information we collect and where it comes from

We receive information directly from you, from your browser when it contacts the site, and from records created as you use a learner account. We do not ask for a legal name, government identity document, precise location, or payment card on the current site.

Information, source, and use
SourceInformationUse
Your visitIP address, browser and device request details, requested page, time, and similar technical data available to the host.Deliver pages, protect the service, and investigate errors or misuse.
Your accountVerified sign-up email; credential and session verifiers, issue and expiry times, and credential labels. HCESL stores verifiers rather than the raw access token used to sign in.Identify your account, authenticate access, and manage sessions and recovery.
Your learning activityTopics and other text you submit, courses, lessons, practice answers, assessment results, progress, and source references associated with your account. Free-text entries can contain personal information if you put it there.Build and save the learning experience you request and show your progress.
Your messagesSupport tickets entered in your account and direct emails sent to our mailbox, including your address, message, and any attachment or other detail you choose to include.Answer support, privacy, and security requests and retain the conversation.

We do not obtain profile data from social sign-in, advertising networks, or data brokers. Please avoid putting access tokens, identity documents, or another person's private information into a support message or course topic.

3. How we use information

  • Run and secure the website: use technical request data to deliver pages, maintain availability, enforce rate limits, and investigate failures or misuse.
  • Provide an account and saved learning: use your email and account records to control access, and your course activity to save lessons, answers, and progress.
  • Respond to you: use tickets and email to answer support, privacy, and security requests and keep a record of the conversation.
  • Meet a legal obligation: use or disclose limited information if required by applicable law or a valid legal process.

You can browse public pages without an account. An email address and issued credential are needed to use an account; without them, we cannot provide private courses or recovery. Course text is optional in the sense that you choose what to submit, but HCESL needs it to create and save that particular course. You do not need to provide payment or marketing information to use the current site.

This policy is information about processing; reading it or merely visiting the site is not treated as consent to an optional use. Where a future feature requires consent, HCESL will request it separately before that processing begins. We do not use your account information for targeted advertising or sell it.

4. When we share information

Arnab Sarkar can access information needed to operate HCESL and answer requests. The following services handle information on HCESL's behalf or receive it when you contact us directly:

Services used by HCESL
ServiceInformation and role
VercelWebsite hosting and processing of page and API requests, including technical request information.
SupabaseProduction database and separate storage for account encryption keys.
Google / GmailDelivery and storage of messages you send directly to the HCESL support and privacy mailbox.

We may disclose information if a valid legal requirement applies, limited to what is required. HCESL does not share account data with advertisers or data brokers. Public enrollment email, the app's Gmail connection, AI generation through OpenRouter, and live web and paper research are currently off. The site does not send your learning text to those inactive integrations. We will update this policy before activating a new recipient or materially different use.

5. Processing outside India

The services named above may store or process information outside India. HCESL does not claim that all information remains in India, and the exact location may vary with a provider's infrastructure and your use of the service. Their linked notices describe their own practices. If a future feature changes where or to whom learner information is sent, we will update this policy before activating it.

6. Cookies and local token files

After sign-in, HCESL sets an essential hcesl_session cookie so your browser can access your account. The cookie lasts up to one hour; signing out revokes the session. It is HttpOnly and SameSite Strict, and is marked Secure on HTTPS. You can block it in your browser, but account sign-in will not work. HCESL's website code does not set advertising or analytics cookies.

If you choose a token file, your browser reads it locally and sends only the extracted access token for sign-in. The file and its path stay on your device. Treat the token like a password; anyone holding it may be able to access your account.

7. Retention and deletion

We keep account information while the account is active, unless you request deletion. We do not delete an account merely because it has not been used. Different records have different lifetimes:

How long information remains
RecordCurrent period or criterion
Verification or recovery linkUsable for 30 minutes after issue. The database record may remain until it is consumed or cleaned up; link expiry alone is not record deletion. Issuance is currently disabled.
Sign-in sessionUsable for up to one hour or until sign-out or revocation. Expired records may remain until cleanup.
Account and learning dataKept while the account exists. An authenticated deletion request revokes access immediately and schedules private-record and account-key erasure 30 days after the request. The request cannot be cancelled.
Encrypted database backups, if madeMay outlast live records. A fixed archive period has not yet been set. Account keys are kept separately from database backups and are destroyed as part of account erasure.
Direct email and hosting logsMailbox conversations and provider-managed request logs do not yet have a single HCESL retention period. Ask us about a particular message; the providers also apply their own retention practices.

We will set and publish the missing periods before opening public enrollment. A specific legal obligation or dispute may require a record to remain longer; we will explain that if it applies to your request.

8. Your rights, choices, and grievances

You can ask what personal information HCESL holds about you, request a copy or correction, seek deletion, withdraw a consent you gave for a particular use, or complain about how your information was handled. Email your request to arnabsarkar0132@gmail.com with the subject “HCESL privacy request.” Arnab Sarkar is the contact responsible for reviewing it.

Use your verified sign-up email if you have an account. Tell us what you want us to review, but do not send an access token or government identity document. We may need to confirm that you control the account before disclosing or changing private records. Responses concerning an account will go to its verified sign-up email. If your request cannot be fulfilled in full, we will explain why.

An account holder who can sign in can use the deletion control to revoke access immediately and schedule erasure after 30 days. If you cannot sign in, contact us at the address above. Withdrawing consent may prevent us from providing a feature that depends on it, but does not undo processing already completed. If a complaint remains unresolved, you may pursue a regulator or other complaint route available under applicable law.

9. How we protect information

HCESL uses HTTPS, restricted account and operator access, one-way credential verifiers, and account-specific encryption for private learner content and support tickets. Account keys are stored separately from database backups. We limit operator access to the admin support panel. These safeguards reduce risk, but no online service can guarantee absolute security. Please report a suspected account compromise or privacy incident to arnabsarkar0132@gmail.com; do not include a token in the message.

10. Changes and contact

We will update this policy when the information collected, purposes, recipients, or retention practices change. The date at the top identifies the current version. We will give appropriate notice before starting a materially different use of learner information. For questions, requests, or grievances, email arnabsarkar0132@gmail.com or visit Contact & help.