Privacy Policy

CookieSensei is the education brand operated by CookieSensei Labs Private Limited, an Indian private limited company. In this policy, “we”, “us” and “our” mean the company responsible for the personal information described here.

This policy covers cookiesensei.com, its learning services and connected CookieSensei apps, workshops, guided cohorts, Community, Jobs, support contributions, virtual classrooms and Cloud Labs. Independent services you visit through links have their own privacy policies.

1. What we collect and why

• Enquiries: your name, email, phone if supplied, and message, so we can answer your question and maintain correspondence.
• Workshops: your name, email, phone, selected event and registration status; paid workshops may also require your GitHub username and payment references. Free college registration does not require a payment or GitHub account. Authorized administrators can export registration details for workshop coordination.
• Guided cohorts: application answers about your background, goals and availability, contact details, selected batch, scholarship requests, agreed fees and payment schedule. We keep application history, approval decisions and administrative records to deliver the agreed service and resolve questions.
• Voluntary support: your name, email, phone, contribution amount and payment references, used to process a contribution, provide its receipt and investigate payment questions.
• Accounts and access: email or connected-account identifiers, verification links, session records and access eligibility, used to sign you in and protect your account.
• Technical and security information: network information such as IP addresses, browser/device information, request times, errors and abuse-prevention identifiers may be processed to operate the service, investigate faults and prevent misuse. Some features use hashed identifiers; hashing does not make them fully anonymous.

Providing optional information is your choice. Without information necessary for a registration, payment or sign-in, we may be unable to provide that feature. Published free lessons remain available without creating an account.

2. Learning progress and connected apps

Signed-out website progress is stored in your browser. If you choose email sign-in, we store your verified email, lesson completion choices and update times so you can continue across devices. Learn and Community share that email identity; your email is not shown on public posts. Existing browser progress is imported only when you choose to import it.

Email sign-in links for Learn and Community expire after 15 minutes and can be used once. Their essential, HTTP-only session cookies last up to 30 days. Signing out ends the shared browser sign-in, but does not delete saved server progress. Student, administrator, Jobs and mobile sessions are separate.

When you use a connected CookieSensei app, the service may also process app sign-in and device/session identifiers and the learning progress you choose to sync. Removing the app or clearing browser storage does not automatically delete information held on our servers. Contact us to request account or progress deletion.

3. Community contributions

Approved questions, answers, display names and screenshots are public. Avoid posting private information, credentials or other people’s details. Posting as an anonymous learner hides your name from readers; moderators can still associate contributions with an internal identity. An anonymous browser cookie helps you manage your posts. Clearing it may remove your ability to find or delete those posts yourself.

We process posts, images, reports, moderation decisions and account or browser identifiers to operate and moderate Community. Removing a post hides it from public pages; retained moderation records and copies held by others may remain. See the Community guidelines for removal, image retention and appeals.

4. Graduate profiles and employer connections

Jobs processes account email, graduate profiles, project evidence, employer details, jobs, applications and introduction decisions. Private completion evidence is reviewed by administrators. With your opt-in and approval, your graduate name, biography, city, LinkedIn link and approved projects become public.

Your account email is not public. Applying to a role shares it with that employer; accepting an introduction shares contact details between the parties. Hiding a profile or withdrawing stops further sharing through the relevant feature but cannot recall information already copied. See the Jobs guidelines.

5. Classrooms, recordings and Cloud Labs

Live classrooms process participant identity, attendance/access details, audio, camera video and shared-screen content according to the features you use. Recorded sessions may include shared screens and participant audio; camera capture depends on the session’s recording mode. Read the recording notice before participating and avoid sharing confidential information.

Eligible participants can access replays within the seven-day window described in our Recording Policy. Online access expires at the displayed deadline. Deletion of expired server files depends on the retention service running; outages can delay physical removal. A downloaded copy remains on its recipient’s device.

Cloud Labs use self-hosted Coder software. Account and GitHub identity, workspace metadata, authentication information, source code, files and projects may be stored on the infrastructure operating your lab. Authorized administrators may access this information for support, security or service operation. Keep your own project backups and avoid unnecessary secrets or sensitive data.

6. Payments

Online payments are processed through Cashfree Payments. We process payer contact details, order and transaction references, amounts, payment status, refunds and reconciliation records. Where we expressly arrange an offline payment, we retain the receipt, method, reference and verification information.

We do not ask you to send card security codes, UPI PINs, banking passwords or one-time payment codes to us. We do not intentionally store complete card numbers or those credentials in the website database. The payment provider processes payment information under its own policies and legal obligations.

7. Service messages and marketing choices

We use Resend and our email infrastructure for sign-in links, registration messages, workshop joining and recording links, payment-related correspondence and support. Email providers process recipient details, message content and delivery information. If you contact us on WhatsApp, that conversation also uses WhatsApp’s service.

A workshop registration or service enquiry is not permission for unrelated marketing. We do not sell learner data to data brokers or supply registration lists for another organization’s independent marketing. You can ask us to stop optional promotional messages; necessary account, payment and service messages may still be sent.

8. Who receives information and where it is processed

Access is limited to people and providers who need information for the purposes described here: authorized company staff and administrators, hosting and database services including Hostinger, Cashfree, Resend, GitHub integrations, and the infrastructure running classrooms and Cloud Labs. Coder and LiveKit are software used in our infrastructure; their use alone does not mean all learner data is sent to their vendors.

Website and registration records are stored in PostgreSQL on our hosting infrastructure. Workspace and recording data are held on the systems providing those services. Providers and their infrastructure may process information in India or other countries. We do not promise that every copy stays in India, and apply legally required safeguards and transfer restrictions.

We may disclose relevant information to comply with a lawful request, enforce our terms, investigate fraud or protect people and systems. If a business transfer affects personal information, applicable notice and legal requirements still apply.

9. Cookies and browser storage

We use cookies and similar storage for sign-in, account security, registration continuity, display preferences and learning progress. Read our Cookie Policy for the feature-specific purposes and your controls.

If non-essential analytics or advertising technologies are introduced, we will explain them and obtain consent where required before enabling them.

10. Retention and security

We retain information for the purpose it was collected, including active learning services, support, accounting, disputes, fraud prevention and legal obligations. Different records have different retention needs: expiring sign-in links and recordings are not governed by the same period as payment receipts or moderation history.

When retention is no longer necessary, information should be deleted or anonymized through our operational processes. Deletion requests may leave records we must retain by law, restricted security/dispute records and copies in backup rotation. We will explain relevant limits when responding. Signing out or hiding a public item is not the same as deleting every retained record.

We use access controls and reasonable technical and organizational safeguards. No system is completely secure. Report a suspected account or data incident to the contact below without sending passwords or private sign-in links.

11. Children and guardian involvement

If you are under 18, involve a parent or legal guardian before providing personal information, registering for a live service, making a payment or publishing a public contribution. Contact us first so we can discuss eligibility and any consent or verification required by applicable law. Do not submit a child’s identity documents through a public post.

A parent or guardian can contact us about a child’s information. Where required consent is missing, we may restrict the relevant feature and arrange removal, subject to lawful retention requirements.

12. Requests, choices and grievances

Email ashish@cookiesensei.com to request access, correction or deletion, withdraw consent for consent-based processing, or raise a privacy grievance. Include the affected feature and account email or public post link. We may verify your identity proportionately; never send a password or sign-in token.

Withdrawal does not invalidate earlier lawful processing and may prevent us from continuing a feature that needs that information. Some records must be retained for legal obligations or disputes. Your statutory rights and available escalation routes depend on the law in force and applicable to the processing. This policy does not restrict those rights.

Our company and grievance page explains how to raise concerns. We update this policy as services and applicable requirements change, and provide additional notice or seek consent where required.

Contact the company