Klymb.ai · legal
Privacy Policy
How we collect, use, share and protect your personal data: written around what this product actually does, and India's Digital Personal Data Protection Act, 2023.
Version 2026-11-05 · Effective 5 November 2026
1.Who we are
In plain English: Klymb.ai is run by Creators Enterprises Private Limited. We decide why and how your data is used, which makes us the Data Fiduciary. Our Grievance Officer, below, is the person to contact.
| Brand | Klymb.ai |
|---|---|
| Registered entity | Creators Enterprises Private Limited |
| Entity type | Private Limited Company |
| Corporate Identification Number (CIN) | U72900UP2016PTC086187 |
| Date of incorporation | 06 September 2016 |
| Registered with | Registrar of Companies, Kanpur |
| Directors | Tarun Kumar Singh, Gayatri Singh |
| Registered office | 1605, Tower 3, Panchsheel Wellington, Crossing Republik, Ghaziabad, Uttar Pradesh 201016, India |
Grievance Officer
| Name | Tarun Kumar Singh |
|---|---|
| Designation | Director and Grievance Officer |
| team@klymb.ai | |
| Address | 1605, Tower 3, Panchsheel Wellington, Crossing Republik, Ghaziabad, Uttar Pradesh 201016, India |
We acknowledge grievances within 24 hours and aim to resolve them within 15 days. If our response does not satisfy you, you may escalate to the Data Protection Board of India.
2.What we collect
In plain English: What you type into the registration form, what Google tells us when you sign in, the coursework you submit, and, only if you allow cookies, aggregate analytics.
| Registration | Name, email, phone, chosen track, current role, years of experience, optional LinkedIn URL, and your consent to be contacted |
|---|---|
| Account | Your Google account email, name and profile image, through Google sign-in |
| Evidence accounts | The GitHub username and LinkedIn profile you declare, so submitted links can be checked as yours |
| Coursework | Daily submissions, deliverable links, your notes, knowledge-check answers, checkpoint LinkedIn post links, assessment scores and reviewer feedback |
| LinkedIn posting (optional) | Only if you connect LinkedIn to post in one tap: an access token that lets us publish posts you confirm, your LinkedIn member ID and display name, and when that permission expires. The token and ID are stored encrypted. We never read your feed, connections, messages or email, and nothing is posted unless you tap Post |
| Payments | For System Design: what you paid, when, Razorpay's order and payment IDs, the campaign link you came from, and any refund. Card, UPI and bank details go to Razorpay and never reach us |
| Referrals | Your referral code, whose code you used when you bought System Design, and how many people bought with yours. People who open your link see your first name. Your browser keeps a code from a link for 14 days, so it still applies if you come back later. We never tell anyone who bought |
| Technical logs | IP address, request time, path, status and browser type, processed by our hosting provider to serve pages and keep the service secure |
| Analytics | Aggregate usage measured with Google Analytics 4, on by default and switchable off at /cookies; cookieless page-view and page-speed counts from Vercel |
We never ask for, and you should never submit, sensitive data such as government ID numbers, financial account details or health information. Do not put employer-confidential material in your coursework.
3.Why we use it
In plain English: To run the cohort you signed up for, to contact you about it, and to review your work.
- Creating and running your account, and signing you in
- Reserving your cohort place and giving you access to the daily programme
- Storing your submissions so reviewers can score them and give feedback
- Checking that submitted GitHub and LinkedIn links belong to the account you declared
- If you connect LinkedIn: publishing a lesson or badge post to your own feed when you tap Post, after you have seen its image and text
- Emailing or calling you about your registration, your cohort and your results
- Keeping the service secure, and preventing abuse of the registration form
- Understanding, in aggregate, how the site is used, unless you have turned analytics off
4.Our lawful basis
In plain English: Some things we do because you asked us to provide the programme; optional things, like analytics cookies and marketing contact, we do only with your consent.
Necessary to provide the service you asked for: creating your account, reserving your place, storing and reviewing your submissions, verifying evidence, issuing results, and keeping the service secure. Without this processing we cannot run the cohort.
Consent: the contact permission you give on the registration form. You can withdraw it at any time: see section 8. Withdrawal does not undo processing already lawfully carried out.
Analytics: aggregate measurement runs by default and is not tied to your identity: we never send your name, email, phone or submissions to Google. You can switch it off at any time at /cookies.
5.Who we share it with
In plain English: Only the services that run the product. We do not sell your data.
| Vercel | Website hosting, technical logs, and cookieless web analytics and speed insights: United States and global edge network |
|---|---|
| Neon | Database holding registrations, learner records, submissions, lesson results and payment records: United States |
| Razorpay | Taking payments and issuing refunds: India |
| Brevo | Sending receipts and course emails: European Union |
| Amazon SES | Sending course emails, through our mail service: Global |
| Cloudflare | Storing and delivering course videos: Global |
| Supabase | Live messages that sign a second device out, holding no personal records: Tokyo, Japan |
| Sign-in (OAuth) and Google Analytics 4: Global | |
| Publishing the posts you confirm, with their image, to your own LinkedIn feed, only if you connect it: Global |
Reviewers and administrators of Klymb.ai see your submissions and evidence links in order to score your work. Nobody else can see another learner's submissions: access is enforced in the database itself, not only in the interface.
We do not sell personal data, and we do not use advertising or cross-site tracking networks.
6.International transfers
In plain English: Some of our providers store data outside India: mainly the United States and Japan.
Our database is hosted in Tokyo, Japan, and our hosting and sign-in providers operate globally, including in the United States. By using the service you understand that your data may be processed in those countries. We use established providers and rely on their contractual protections.
7.How long we keep it
In plain English: Registrations and coursework stay while your cohort runs and for a period afterwards, so your record and certificate remain verifiable. Ask us to delete it and we will.
- Registrations that do not enroll: kept for 24 months, so we can tell you when a track opens, then deleted.
- Learner records and submissions: kept for 24 months after the cohort ends, so results and feedback remain available to you.
- LinkedIn connection: kept until you disconnect it or LinkedIn's 60-day permission runs out, then deleted. Posts you published stay on LinkedIn, under your control there.
- Technical logs: kept for the short period our hosting provider retains them.
- Records we must keep: consent records, kept as long as needed for tax, accounting or a dispute.
8.Your rights
In plain English: Get a copy of your data, correct it, delete it, withdraw consent, complain, or nominate someone to act for you.
- Access: ask for a copy of the personal data we hold about you.
- Correction: have inaccurate or incomplete data corrected.
- Erasure: ask us to delete your account and data, subject to records we must keep.
- Withdraw consent: stop marketing contact, or turn analytics cookies off at any time.
- Disconnect LinkedIn: tap Disconnect in the Post to LinkedIn step and we delete the token straight away. To remove Klymb.ai from your LinkedIn account as well, use LinkedIn's permitted services settings.
- Grievance: complain to our Grievance Officer, whatever else you have done. We acknowledge in 24 hours and aim to resolve in 15 days, and you may escalate to the Data Protection Board of India.
- Nomination: nominate someone to exercise these rights if you die or become incapacitated.
Email team@klymb.ai and we will respond within 30 days. We may need to verify who you are first.
9.Security
In plain English: HTTPS everywhere, access rules enforced in the database, and secrets kept server-side. No system is perfectly secure.
- The site is served over HTTPS.
- Access rules live in the database: a learner can only read their own record, and the public can only add a registration, never read one.
- Administrative access is limited to an allowlist of email addresses, checked on every request.
- Keys and secrets are stored as server configuration, never in the browser.
- A LinkedIn connection is encrypted before it is stored, and the token never reaches the browser.
If a personal data breach occurs, we will notify the Data Protection Board of India and affected users as required by the DPDP Act.
10.Children
In plain English: This is an 18+ service.
Klymb.ai is for adults. We do not knowingly collect data from anyone under 18. If you believe a minor has registered, contact us and we will delete the account.
11.Cookies
In plain English: What is needed to sign you in, plus analytics you can switch off.
See the Cookie Policy for what each cookie does, and for the switch that turns analytics off.
12.Changes
In plain English: If we change something material, we will post a new version and tell you.
The version and effective date are at the top of this page. Material changes to what we collect or how we use it will be signalled with a new version, and where we reasonably can we will email the address on your account. Your enrolment is governed by the version in force when you registered, unless you accept a newer one.
13.Contact
In plain English: One address for everything.
Privacy questions, data rights requests and grievances: team@klymb.ai. Entity and grievance details are also published at /contact.