♛ NAUKARI CROWN

Effective 13 October 2026

Privacy Policy

This policy explains the verified data practices of the Naukari Crown education website and, separately, the private YouTube AI tool used by the Naukari Crown channel owner.

Who we are. Naukari Crown is the operating brand covered by this policy. No registered legal entity name or postal address is asserted because those details have not been confirmed.

Privacy questions and deletion requests: naukaricrown@gmail.com.

1. Scope and important distinction

This policy covers two different services:

  1. The Naukari Crown education website, including course information, student sign-in, enrolments, online tests and the administrator panel.
  2. The YouTube AI tool, a separate owner-operated application used to research, analyse and manage the Naukari Crown YouTube channel. Website visitors and students do not sign in to this tool.

The website does not give students or the public access to the YouTube AI tool. More detail is available on the YouTube AI transparency page.

2. Education website: information handled

Public browsing

You can view public course and batch information without creating an account. The current website source does not include an advertising network, behavioural analytics SDK or a payment gateway.

Student authentication and course access

If you choose “Sign in with ChatGPT”, the hosting authentication service provides the website with a user identifier, email address and, when available, full name. These details are used to authenticate you, display your dashboard and match your email address to course enrolments. Authentication may use strictly necessary cookies managed by the hosting sign-in service; the application source does not set advertising or analytics cookies.

Tests, enrolments and administration

The website database can store enrolment email addresses and online-test records, including user ID, email address, test answers, questions marked for review, score, start time, save time and submission time. It also stores course, batch, question-bank and website-content records. Administrator uploads and related metadata can be stored in site file storage.

Payments

The reviewed source does not collect card, bank or UPI details and contains no integrated payment processor. Course enquiries currently link to WhatsApp or telephone. If a payment process is added later, this policy must be updated before that collection begins.

3. Education website: third-party services

  • ChatGPT-hosted authentication supplies the verified sign-in identity described above.
  • Google Fonts is loaded by the public and test-page stylesheets. A visitor’s browser may send ordinary request information, such as IP address and browser details, to Google. See the Google Privacy Policy.
  • jsDelivr provides pinned PDF.js files used on the administrator PDF-import screen. This is an admin-only workflow; the selected PDF is processed in the browser before extracted content is imported.
  • WhatsApp, Telegram and telephone links open services outside this website. Their own terms and privacy practices apply after you follow a link.

The source review found no website integration with Google Analytics, an advertising network, Stripe, Razorpay or PayPal. This is a statement about the reviewed software, not an unverified assurance about any offline advertising or business data-sharing practice.

4. YouTube AI tool and Google authorization

The YouTube AI tool uses YouTube API Services. The Google OAuth application is currently configured as External / Testing and is intended only for the Naukari Crown channel owner. Other people do not have an account or sign-in flow for this tool.

The full-access configuration can request:

  • youtube.readonly — view the authorised channel, videos and comments;
  • yt-analytics.readonly — view channel analytics reports;
  • youtube.upload — upload a video after a specific owner confirmation; and
  • youtube.force-ssl — make owner-approved title or description changes and post an owner-approved comment reply.

A separate read-only configuration requests only youtube.readonly and yt-analytics.readonly. Publishing automation is disabled. Available write commands require explicit confirmation and must not be understood as automatic publishing.

5. YouTube data accessed and purposes

With the channel owner’s Google authorization, the tool can access channel ID, name and statistics; recent upload titles, IDs and dates; video views, likes, comment counts and duration; analytics such as views, watch time, average view duration and percentage, subscribers gained and lost, traffic sources and audience retention; and top-level comments when requested.

This information is used to prepare performance reports, research and plan content, and—only following a specific owner confirmation—to perform an available write action. The reviewed tool code does not contain advertising, tracking or data-selling functionality.

6. YouTube AI storage and processors

  • Google OAuth tokens are stored as local JSON files on the owner’s Windows computer. They are not protected with file-level encryption.
  • YouTube API results may be retained as working files in the local project and Claude Code temporary folders.
  • Anthropic Claude Code processes information shown during AI sessions to prepare reports and plans. Some channel analytics reports have also been stored as private documents in the owner’s Claude account. Anthropic retention depends on the owner’s account and plan and has not been independently confirmed here. See the Anthropic Privacy Center.
  • TranscriptAPI may receive its service API key, search terms, and public channel or video identifiers for transcript research. The implementation does not send Google OAuth tokens or private YouTube Analytics data to TranscriptAPI. Its retention and method of obtaining YouTube data have not been verified by Naukari Crown. See the TranscriptAPI Privacy Policy.

7. Retention, manual deletion and revocation

YouTube’s storage rules require non-analytics authorised data and non-authorised API data to be deleted or refreshed no later than 30 calendar days after collection. YouTube Analytics data and API statistics may be retained longer only while needed for the authorised purpose, provided the tool reconfirms at least every 30 days that authorization remains valid and the underlying data has not been deleted. OAuth tokens are retained only while the tool is in use.

These are retention requirements, not automatic controls in the current tool. A report can identify expired data, but the owner must review and execute deletion manually. An authorization-status checker exists, but no scheduled 30-day check is currently running.

To request deletion, email naukaricrown@gmail.com with enough information to identify the relevant account or record. The request is logged, its scope is confirmed by the owner, and the owner manually deletes and verifies the relevant locally held data. Under the YouTube API Services Developer Policies, stored user data covered by the request must be deleted as soon as possible and within 7 calendar days. Deleting data held by this tool does not delete data held by YouTube. Provider-held data must be addressed through Anthropic’s or TranscriptAPI’s applicable process.

The channel owner can revoke access through Google Account third-party access settings. Related API data must then be deleted as soon as possible and within 30 calendar days. The website project has not verified that the separate local Claude Code application implements programmatic Google token revocation, so this policy does not claim that it does. Because deletion is manual and authorization checks are not scheduled, meeting the applicable deadlines requires an owner-confirmed manual check, deletion and verification.

8. Google authorization and policy acceptance

The tool has no public user registration. Google displays the requested OAuth scopes, and the owner chooses whether to grant those permissions. That Google OAuth action authorises the displayed scopes only; it is not a separate acceptance of this Privacy Policy.

No checkbox, “I agree” control, or recorded policy-acceptance event is currently implemented in the local Claude Code application, and the website does not implement that acceptance on its behalf. A separate affirmative owner-acceptance mechanism must be implemented and recorded before continued use of the YouTube API Client. The Privacy Policy and YouTube AI page should also be linked from the Google OAuth consent-screen configuration so they can be reviewed before authorization. Declining or revoking Google authorization prevents further authorised API access.

9. YouTube terms and external policies

Use of the YouTube AI API Client is subject to the YouTube Terms of Service. By accessing or using the API Client, the channel owner agrees to be bound by the YouTube Terms of Service. This Terms of Service statement is separate from acceptance of this Privacy Policy.

10. Changes and contact

This policy may be updated when the website, YouTube AI tool, service providers or verified practices change. The effective date at the top identifies this version. Questions, complaints and deletion requests should be sent to naukaricrown@gmail.com.