Privacy Policy

1. Scope and who this policy covers

This Privacy Policy explains how the KRISHN-O-LOGY service collects and uses personal data when you browse the website, create an account, purchase a membership, use interactive products, contact support or participate in a launch or competition feature. KRISHN-O-LOGY is the digital service described on this website and is created by Indushekhar Patra. Contact and privacy requests can be submitted through the Contact & Support page; a public support email is also displayed there when configured.

2. Personal data we may collect

• Account data: name, email address, password hash when email/password sign-in is used, verified-email status, Google account identifier when Google Sign-In is chosen, membership plan, account timestamps, legal-policy acceptance record and optional marketing-email preference.
• Purchase and membership data: Razorpay order/payment references, amount, plan, payment status, Founding 108 number, promotional allocation and entitlement history.
• Product-use data: saved Workbook entries, 21-Day Challenge progress, Decision Arena progress, Archetype results and WWKD decision/reflection data when account sync is used.
• Support data: information you submit through the Contact page and related support communications.
• Technical/security data: limited server and security information that may be generated when you use the service, such as request timestamps and information needed to prevent abuse.

3. Payment information

Payments are processed through Razorpay. KRISHN-O-LOGY does not intentionally store your full card number, CVV, UPI PIN or internet-banking password on its own server. Razorpay may independently collect and process payment, transaction and technical information under its own privacy notices and legal obligations.

Read Razorpay's Buyer Privacy Notice.

4. Why we use personal data

• to create and secure your account;
• to provide Free Explorer, Experience or Founder access;
• to verify payments and prevent duplicate or fraudulent fulfilment;
• to allocate and preserve Founding 108 membership numbers and launch benefits;
• to save your product progress when account sync is enabled;
• to send transactional messages such as welcome, password-reset, support receipt, payment-success and Founding 108 confirmation emails;
• to send optional product or future-launch updates only when you have separately opted in to those communications;
• to answer support/privacy requests and resolve technical problems;
• to protect the service, enforce the Terms and meet applicable legal obligations.

5. WWKD and optional AI processing

WWKD can operate with the built-in adaptive engine. If an external AI provider is enabled, the text needed to generate the requested response may be sent from the KRISHN-O-LOGY server to that provider. The website should clearly indicate when AI enhancement is enabled. Do not enter passwords, payment credentials, government identifiers or other unnecessary highly sensitive information into WWKD.

6. Who data may be shared with

Data may be shared only as reasonably necessary with service providers used to operate KRISHN-O-LOGY, such as Razorpay for payments, Google when you choose Google Sign-In, an email-delivery provider for transactional email, an AI provider when AI enhancement is enabled, hosting/security providers, and professional or governmental recipients where disclosure is required by applicable law. When Google Sign-In is used, KRISHN-O-LOGY receives the verified identity information returned by Google that is needed to create, link or sign in to your account; KRISHN-O-LOGY does not receive your Google password. KRISHN-O-LOGY does not claim to sell your personal data to advertisers.

7. Cookies and local storage

The service uses an HttpOnly session cookie for account login; in production it is restricted to HTTPS and configured with additional browser cookie protections. Authentication tokens are not intentionally stored in browser local storage. Some product modules may use browser local storage only as an offline/cache layer for non-credential product state. Signed-in account progress stored on the server is intended to be the durable copy where that module supports sync. Clearing browser storage can remove local-only data.

8. Retention

Account and entitlement records are kept while reasonably necessary to provide the service and maintain purchase/Founding history. Transaction records may be retained for accounting, fraud prevention, dispute handling and legal obligations. Support messages are normally retained only as long as reasonably necessary for the request and operational recordkeeping. Data may be retained longer where required by law or a legitimate dispute/security need.

9. Your choices and requests

You may use the Contact page to request access, correction or deletion of account data, withdraw consent where consent is the applicable basis, change optional marketing preferences, or raise a privacy grievance. Some records may need to be retained where required or permitted by applicable law, including transaction, fraud-prevention or dispute records. Withdrawing or deleting data needed to operate an account may make some account features unavailable.

10. Security

Passwords are stored as password hashes rather than plain-text passwords. Google identity credentials are verified by the server before an account is created, linked or signed in. Paid checkout requires a verified account email. Production sessions use protected cookies rather than browser-readable authentication tokens. The service also uses server-side authorization, payment-signature/webhook verification, rate limits, origin checks and browser security headers. Payment secrets and provider credentials belong only in server environment configuration. No internet service can promise absolute security, so users should use a unique password and report suspected unauthorized access promptly.

11. Age requirement

The current KRISHN-O-LOGY commercial account and interactive-data system is intended for adults aged 18 or older. Users under 18 should not create an account or submit personal data through the current account system. A future minor-access model, if offered, would require separate age-appropriate and parental-consent safeguards before launch.

12. Changes to this policy

If this policy materially changes, the effective date/version will be updated and an appropriate notice will be provided through the website, account or email where required.

13. Contact and grievance requests

Use the Contact & Support page and select Privacy / Data Request. The support form creates a reference number for follow-up. The configured support address is the designated contact point for privacy and grievance requests; additional legally required operator details will be kept current on the public Contact page when applicable.