Privacy Policy

1. General

The website explainx.ai ("Website"), including related subdomains such as newsletter.explainx.ai where applicable, and any future web or application interfaces (collectively, the "Platform"), is operated by AISOLO Technologies Private Limited ("AISOLO", "we", "us", "our"), a company incorporated under the laws of India, with its registered office at 1003, Kamdhenu Commerz, Sector 14, Kharghar, Navi Mumbai 410210, Maharashtra, India.

explainx.ai is a product of AISOLO. The Platform provides: the main Website and related Learn application; shared account access; courses, chapters, quizzes, learning progress, personalized paths, organization workspaces, and certificates; a public skills registry; directories of MCP servers, AI tools, agents, language models, and agent loops; an authenticated explainx.ai MCP service for compatible AI clients; Melo, the explainx.ai learning copilot, including file-aware chat and interactive learning modes; AI-assisted search, chat, evaluations, and research experiences; blogs and other educational content; a weekly AI newsletter; the Melo by Explainx browser extension ("Extension") distributed via the Chrome Web Store; the explainx.ai mobile app ("App", available or forthcoming on iOS and Android); instructor-led live Workshops; self-paced Courses; structured Bootcamps; AI certification Mock Tests; optional paid custom deliverables (such as custom DESIGN.md drafting); paid Membership plans (monthly, annual, lifetime) that grant access to premium features and workshop enrollment; paid skill access, corporate training inquiries, and related tools for learning about, discovering, and sharing AI resources (collectively, the "Services").

Public directory data. Information displayed about skills, MCP servers, repositories, install commands, descriptions, categories, and similar fields is generally intended to be publicly visible on the Website and may be indexed by search engines or provided through APIs. Much of this data is supplied by users for publication or derived from publicly available sources; it is not private account information. Do not submit secrets, credentials, or other sensitive data in fields meant for public listings. We do not claim that directory data is complete, accurate, or current; see our Terms of Service (including provisions on third-party offerings).

This privacy policy ("Privacy Policy") describes how we collect, use, disclose, store, and protect information relating to identified or identifiable individuals ("Personal Information") when you browse, register for an account, submit content, subscribe to communications, install or use the Extension, or otherwise use the Platform. It should be read together with our Terms of Service and our Data rights summary for exercising privacy requests.

This Privacy Policy is a notice about our data practices, not a request for blanket consent. By using the Platform, you acknowledge this notice. Where consent is legally required, we request it separately at the relevant collection or choice point. If you do not want your information processed as described, do not use the relevant Service.

This document is an electronic record under the Information Technology Act, 2000. India's Digital Personal Data Protection Act, 2023 ("DPDP Act") and Digital Personal Data Protection Rules, 2025 have phased commencement dates; we apply their requirements to the extent they are in force and applicable, and use their transparency principles more broadly where practicable.

2. Information we collect

Depending on how you use the Platform, we may collect:

2.1 Account and authentication

• Email address, display name, profile image and profile fields you choose to provide, and password (stored as a secure hash where password sign-in is used).
• Email verification status and related security tokens managed through our authentication system.
• Session identifiers required to keep you logged in securely.
• Supported identity-provider account identifiers and OAuth tokens or scopes when you choose Google, GitHub, or another supported sign-in or repository connection.

Shared identity across explainx.ai and Learn.The main Website and Learn may keep separate operational user records linked through a canonical user identifier and normalized email. We synchronize the minimum identity, verification, role, session, and entitlement information needed to provide shared sign-in and consistent access. Activity inside Learn remains in Learn's learning systems unless needed by another Platform feature, support, security, or a disclosed integration.

2.2 Platform, learning, and organization activity

• Information you submit when publishing or managing skills (e.g. repository metadata, descriptions, categories, and similar fields required by the submission flow).
• Metadata relating to MCP servers or other directory listings that you submit or that we index for display on the Platform, to the extent such fields identify you as an individual (e.g. in an account context); purely public listing text is treated as described in Section 1.
• Reviews, ratings, comments, questions, answers, votes, saved items, content flags, and other community or directory interactions.
• Learn enrollments, purchases, assigned courses, chapter and video progress, last access, completion, quiz answers and scores, certificates, learning-path choices, notifications, and course enrollment requests. A display name and learning score may appear on a Learn leaderboard where that feature is enabled.
• Learner profile inputs such as role, experience, goals, interests, existing knowledge, preferred learning style, time commitment, focus areas, and topics you choose to skip.
• Organization workspace data including membership, role, invitations, assigned courses, due dates, seat and license use, completion status, and security/audit records. Audit records may include the acting user, action, affected record, IP address, user agent, and timestamp.
• Seller and buyer information for paid skills, including payout email, repository connection, purchase email, GitHub username, entitlement and fulfillment status, and transaction identifiers.
• Usage data such as pages viewed and interactions, to operate and improve the Platform.

2.3 Newsletter and marketing

• If you opt in (e.g. at registration or on your profile), your email address and preferences may be used to send the explainx.ai AI newsletter or similar product updates. You can withdraw consent via unsubscribe links in emails or by updating preferences in your account where available.
• Where enabled, we maintain journey state and send history—such as signup source, a related blog or pathway, scheduled step, delivery, open/click, bounce, complaint, and suppression status—to pace educational or product messages, prevent duplicate sends, and honor unsubscribes.

2.4 Technical and analytics data

• Log data, device/browser type, approximate location derived from IP, and similar technical data for security and reliability. Requests to explainx.ai, including Extension calls to /api/ask-explainx, may appear in HTTPS access logs and routine server diagnostics.
• Analytics and product analytics events (e.g. via PostHog, Google Analytics, or similar services) to understand feature usage and diagnose issues, subject to applicable cookie and privacy rules.
• Website analytics used for B2B and sales intelligence (e.g. Apollo.io website visitor tracking) where enabled, which may process technical and usage signals to help us understand organization-level interest in the Services.
• Advertising or conversion signals (for example, Meta Pixel where enabled), embedded-media events, and referral parameters used to measure campaigns, subject to consent or opt-out requirements that apply in your location.
• Anti-abuse and human-verification results (for example, Cloudflare Turnstile), rate-limit keys, hashed network identifiers, failed-login counts, and security events. Providers may receive IP, browser, and request data needed to perform these checks.

2.5 Melo by Explainx browser extension (Chrome)

The Extension runs in your browser. Its productivity-tracking and focus features work without an account and keep signals on-device in Chrome storage as described below. Its Melo sidebar — chat, teach, ELI5, quiz, practice, explain-back, flashcards, interview, and web search, matching the skills at /dashboard/learn — requires connecting your explainx.ai account and is described separately below and in Section 2.9.

• Productivity summaries (local).Per-hostname aggregates such as approximate active time, navigation counts, click and scroll aggregates, and a bounded list of pathnames on each host may be computed and retained locally to populate the in- Extension analytics UI. These metrics are tied to browsing activity on pages where the Extension is injected; they are not sold and are processed for the Extension's productivity features.
• Focus shield (local behavior). When you start an active focus timer, configured distracting sites may have their main-document navigation redirected to an HTML page bundled with the Extension until the timer ends. This blocking is enforced in the browser; it does not transmit those navigations to AISOLO for blocking purposes.
• Appearance and Extension settings. Theme preference and focus-related settings you configure (duration, hostname blocklist stored in Extension storage).
• Account connection. To use the Melo sidebar, you sign in to explainx.ai through an OAuth 2.0 + PKCE flow and approve the connection on explainx.ai. The resulting access token is stored in background-only Extension storage (not exposed to the pages you visit) and is sent as a Bearer token with each Melo request so it can be attributed to your account and its usage allowance. You can review or revoke this connection at any time from explainx.ai/dashboard/extension or by disconnecting from the Extension itself.
• Optional archived sidebar chats (local). A transcript keyed by page URL, including the Melo skill/mode last used on that page, may be stored locally so you can return to a thread; it resides in Extension storage unless you clear it or uninstall.
• Melo sidebar requests. When you message Melo from the Extension, it sends an HTTPS request to explainx.ai (/api/learn) carrying your message, the selected skill/mode, recent turns from that conversation, and — on the first message for a page — the page's title, URL, and extracted text sent as an attachment, the same way a file upload works in Melo on the web (see Section 2.9). That request counts against your account's Melo usage allowance and is processed the same way as a Melo conversation started at /dashboard/learn. Do not use Melo on pages containing highly sensitive Personal Information unless you accept that such content could be transmitted and processed under this flow.
• Executable code. The downloadable Extension bundles the code that performs these features and does not load remote JavaScript/WebAssembly for execution; replies from our API are data (JSON / text).

2.6 Paid custom DESIGN.md service

If you purchase a custom DESIGN.md through the Platform (paid checkout), we collect and process:

• The email address you provide for delivery and receipts, and the website URL you ask us to document.
• Payment data handled by our payment processor (currently Stripe), such as charge amount, currency, and transaction identifiers. We do not receive or store your full payment card number.
• Internal order records (e.g. linked to the Stripe checkout session) to fulfill the service, provide support, and meet accounting and legal obligations.

We may contact you at the email you provide with clarification questions about your product or site when reasonably needed to deliver a high-quality result. Custom deliverables are not published in our public DESIGN.md registry as part of that purchase unless we tell you otherwise in writing for a specific program. Starting checkout after affirming agreement on the order form constitutes acceptance of our Terms of Service and this Privacy Policy for that transaction.

2.7 Bootcamps

The Platform lists bootcamp programs at /bootcamp. Some are operated directly by AISOLO; others are operated by third-party brands and listed for discovery only. For Third-Party Bootcamps, any Personal Information you share during enrollment or payment is governed by that brand's own privacy policy — AISOLO does not collect or process it.

For AISOLO-operated Bootcamps (such as the Complete AI Builder Bootcamp), we collect and process:

• The name and email address you provide at enrollment, used to confirm registration, deliver session access links, and communicate schedule or instructor changes.
• Payment data handled by our payment processor (currently Stripe). We do not receive or store full payment card numbers.
• Internal enrollment records (linked to the Stripe checkout session) to manage access, provide support, and meet accounting and legal obligations.
• Attendance or engagement signals (e.g. session joins, completion status) where technically collected, used solely for program administration and improvement.

AISOLO Bootcamp dates, times, and instructors may change at AISOLO's discretion. We will use the email you provide to notify you of material changes. Starting checkout constitutes acceptance of our Terms of Service (including Bootcamp-specific terms) and this Privacy Policy.

2.8 Membership plans

We offer paid Membership plans (monthly, annual, and lifetime) ("Membership") that provide access to premium features, premium content, workshop enrollments at no additional charge, and other benefits described on our pricing page. For Members, we collect and process:

• Account and billing information — email address, subscription status, subscription tier, and billing cycle, linked to your account record.
• Payment data handled by our payment processor (currently Stripe). We receive a subscription identifier, payment status, and renewal dates. We do not store your full payment card number.
• Access and usage records — which gated features or content you access during your subscription, used for account management, support, and product improvement.

Membership access is to content and features curated and selected by explainx.ai. Material changes to included content will be communicated via email. Cancellation takes effect at the end of the current billing period. For refunds, see our Refund Policy. For billing disputes or questions, contact support@explainx.ai.

2.9 Melo learning copilot and uploaded files

When you use Melo, we process your prompt, up to a limited number of recent conversation turns, Melo mode, relevant learner-profile fields, explainx.ai sources you select, and the generated response. Interactive learning activity may also include quiz or interview answers, scores, feedback, flashcards, and practice requests. This context is sent to our AI inference provider (currently OpenAI) to generate the requested response.

If you attach a file, the browser sends its name, type, and contents to explainx.ai and then to the AI inference provider for that request. Uploaded file contents are not intentionally saved in your Melo chat history or reusable file library; you may need to attach the file again after reopening a conversation. The saved conversation may include your prompt, Melo's response, learning mode, quiz interaction, selected explainx.ai source references, and the uploaded file name. Do not upload secrets, regulated data, or personal information about another person unless you have authority and a lawful reason to do so.

Where server-side chat history is available, we currently retain up to 30 saved Melo conversations for up to 90 days after the most recent save, unless you delete a conversation sooner. Ordinary security, abuse-prevention, provider, and infrastructure logs may follow separate limited retention schedules. Deleting a saved conversation removes it from active Melo history but may not immediately remove copies from short-lived backups or a provider's systems where lawful retention applies.

2.10 Live Workshops

When you enroll in an instructor-led Workshop via the Platform (paid or free via annual Membership), we collect and process:

• Name and email address provided at enrollment, used to confirm your place, deliver session access links, and communicate changes.
• Payment data processed by Stripe for paid enrollments. We do not store your full payment card number.
• Enrollment records — run ID, enrollment status, amount paid, currency — retained for account management, access control, and accounting.
• Attendance or session engagement signals (e.g. session joins) where applicable, used for program administration and completion records.
• Class and recording data — if a session is recorded, the recording may capture participant display names, voice, video, screen shares, chat, questions, and other contributions. We provide recording notice and use recordings to provide enrolled access, support learning and completion, review quality, train facilitators, or create future educational material as described at the session or in the Workshop Terms.

Corporate training, facilitator, brochure, and similar inquiry forms may also collect name, work email, company, phone, budget range, role, program interest, and free-text details so we can respond and prepare an appropriate proposal. Workshop chat may retain a session identifier, optional name and email, messages with the AI assistant or human team, status, and timestamps.

2.11 Learn, organizations, and personalized learning

Learn processes the learning and organization information described in Section 2.2 to deliver courses, track progress, issue certificates, support discussions, recommend next steps, and operate team learning. If you belong to an organization, authorized organization owners, administrators, billing users, instructors, or other permitted roles may see member identity, assignments, requests, progress, completion, and organization audit information. The organization may separately control or direct some processing under its agreement with you or AISOLO.

Course instructors and authorized support staff may see learner name, email, enrollment, questions, progress, completion, and viewing-time estimates where needed to teach, support, or administer a course. Other learners may see the name attached to discussion posts, ratings, and leaderboard entries.

When you request a personalized path, your goals, prior knowledge, focus areas, preferences, course activity, and relevant course metadata may be sent to an AI provider. We may store the resulting chapter order, recommendations, skipped topics, estimated completion time, explanation, confidence, model and version metadata so the path can be displayed and refreshed. You can use standard course order where available instead of relying on AI personalization.

2.12 Mock Tests

We offer AI certification practice tests ("Mock Tests") purchasable on the Platform. For Mock Test purchases, we collect and process:

• Email address provided at checkout for order confirmation and access delivery.
• Payment data processed by Stripe. We do not store card numbers.
• Test attempt records — scores, responses, timestamps — used to display your results and improve test quality. These are linked to your account where applicable.

Mock Tests are digital content delivered immediately upon purchase. Please review our Refund Policy before purchasing.

2.13 Other AI features, evaluations, chats, and research

• AI search and chat. Prompts, current page or content context, recent conversation, retrieved Platform records, and responses may be processed to answer a request. Some chats are stored as conversation threads; others are transient, as indicated by the feature and ordinary server logs.
• AI evaluation. Evaluation answers are scored before email claim where practicable. If you claim or save a result, we store the email, score, level, answers, recommendation, optional linked user, timestamp, and a hashed IP-derived abuse-prevention value.
• State of AI research. The response table is intentionally designed without account, email, IP address, user agent, or a cross-question visitor identifier. It stores the question, a yes, no, or skip answer, and submission time. Local browser storage may reduce repeat prompts, and transient security processing may still occur before the response is accepted. Aggregated findings may be published publicly.

2.14 MCP service and connected clients

When you connect a compatible AI client to the explainx.ai MCP service, we process registered-client metadata (such as client name and redirect URIs), authorization requests, consent, scopes, hashed or otherwise protected authorization credentials, expiry and revocation state, security/rate-limit data, and MCP tool requests. Tool requests may include search text, slugs, identifiers, pagination, and protocol metadata sent by the connected client. We return relevant public or account-authorized Platform data. The connected client independently processes your prompts, conversation, and returned results under its own privacy terms; disconnect or revoke the integration in that client when you no longer want access.

2.15 Mobile app

The explainx.ai mobile app (available or forthcoming on iOS and Android) may collect and process data broadly consistent with this Privacy Policy, including: account authentication information, usage and analytics events, push notification tokens (where you grant permission), and app-specific interaction data. App-specific privacy disclosures will be provided in the respective app store listings and within the app. If you have questions about mobile data practices, contact support@explainx.ai.

3. How we use information

We use Personal Information to:

• Provide, secure, and improve the Services (including accounts, submissions, the registry, and Extension features such as summaries and side-panel assistance).
• Authenticate users, prevent abuse, and enforce our Terms.
• Fulfill paid custom deliverables (for example, a custom DESIGN.md), including emailing you the output, sending transactional notices, and asking clarification questions when reasonably needed to improve quality or scope.
• Administer Bootcamp enrollments, including delivering session access, communicating schedule or instructor changes, and providing participant support.
• Operate Learn, synchronize shared identity, enroll learners, personalize course paths, track progress, administer quizzes and certificates, and provide organization learning and audit features.
• Provide AI search, chat, evaluation, summaries, recommendations, MCP tools, and aggregated research.
• Communicate transactional messages (e.g. verification, password reset, security notices).
• Send marketing communications where you have opted in, or as otherwise permitted by law.
• Comply with legal obligations and respond to lawful requests.
• Analyze aggregated or de-identified usage and research findings to improve and report on the product experience.

4. Legal bases and consent

Where the GDPR applies, our legal bases may include performance of a contract (providing the Services you request), legitimate interests (such as proportionate security, analytics, and product improvement), compliance with law, and consent for processing that requires it. Where the DPDP Act applies, we process personal data based on consent or a specific "certain legitimate use" identified by that Act, to the extent the relevant provisions are in force. You may withdraw consent for processing that depends on it; withdrawal may limit the associated feature, such as marketing emails or an optional upload.

AI scores, recommendations, content ranking, fraud controls, and personalized paths assist product delivery and moderation. We do not use them to make solely automated decisions that produce legal or similarly significant effects about you. Where applicable law grants rights concerning such decisions, you may request human review or object through the contact method below.

5. Sharing and subprocessors

We do not sell your Personal Information for money. Some privacy laws define disclosures for targeted advertising or cross-context measurement as a “sale” or “sharing” even without payment; where those laws apply, you may exercise the relevant opt-out rights by contacting us. We may share information with service providers who assist us under contract, such as:

• Hosting and infrastructure providers.
• Email delivery and newsletter services (including AWS SES and Resend where configured).
• AI inference providers processing Melo, Extension, evaluation, and other Website requests routed through explainx.ai APIs (currently OpenAI for these features). Depending on the feature, the provider may receive prompts, recent conversation, selected source context, uploaded file contents, learner-profile context, and technical request metadata.
• Analytics providers (e.g. PostHog and Google Analytics).
• Sales and marketing intelligence providers (e.g. Apollo.io) for website visitor insights.
• Advertising and campaign measurement providers (e.g. Meta) where enabled.
• Security and human-verification providers (e.g. Cloudflare Turnstile).
• Authentication and repository providers you choose to connect (e.g. Google or GitHub).
• Video, storage, course-content, and embedded-media providers used to deliver learning materials (for example, Bunny.net, AWS storage, and YouTube where used).
• Payment processors (e.g. Stripe) to process purchases, prevent fraud, and deliver payment receipts where applicable.
• Newsletter and CRM providers when you subscribe to marketing communications (e.g. services connected to newsletter.explainx.ai or integrated mailing lists).

We may also share information at your direction or as part of the feature you use: public submissions with Website visitors and search engines; buyer details needed for a skill author to fulfill access; organization-scoped identity and learning records with authorized organization administrators; and MCP results with the connected client you authorized. Other users may see your name and content when you post in public or course discussion areas.

These providers may process data in accordance with our instructions and applicable agreements. We may also disclose information if required by law, to protect rights and safety, or in connection with a business transfer (e.g. merger) subject to applicable requirements.

6. Cookies and similar technologies

We use cookies and similar technologies for essential operation (e.g. sessions, security), preferences (e.g. theme), and analytics where enabled. You can control cookies through your browser settings; blocking certain cookies may affect functionality.

Embedded videos, social content, analytics, advertising pixels, and connected third-party widgets may set or read their own cookies or receive device and page information when loaded. You may use browser controls and provider opt-outs; applicable law may also give you consent or opt-out rights, which you can exercise through available Platform controls or by contacting us.

7. International transfers

Our primary operations are in India. If we or our subprocessors process data in other countries, we take steps consistent with applicable law (including appropriate safeguards where required).

8. Security

We implement reasonable technical and organizational measures to protect Personal Information. No method of transmission or storage is 100% secure; we cannot guarantee absolute security.

9. Retention

We retain Personal Information for as long as necessary to provide the Services, comply with law, resolve disputes, and enforce agreements. After account deletion, we may retain certain data for a limited period where required for backups, legal obligations, or legitimate interests (e.g. fraud prevention), then delete or anonymize it in line with our practices.

Retention depends on the record: account, learning progress, certificates, entitlements, and organization records generally remain while needed to provide access; saved Melo conversations currently expire up to 90 days after their most recent save and uploaded file contents are not intentionally stored in that saved history; Workshop recordings and attendance records remain while needed to deliver the applicable run, learning access, certificates, support, or other disclosed educational uses; OAuth codes and security credentials expire or are revoked on shorter schedules; marketing suppression records may be retained to honor opt-outs; and transaction, tax, dispute, fraud, and audit records may be retained for legally required or reasonably necessary periods. Public submissions and de-identified or aggregated statistics may remain after account deletion. Because anonymous State of AI responses are not linked back to a person, we generally cannot identify one for individual deletion after submission.

10. Your rights

Depending on applicable law, you may have rights to access, correct, update, or delete your Personal Information, withdraw consent, or object to certain processing. You may exercise rights by contacting us (see below). You may also delete your account from your profile where the feature is available, and you may delete individual Melo conversations from its history, subject to the retention and backup limits above. A concise overview of how to exercise rights and grievances is on our Data rights page.

A request concerning a shared explainx.ai account may require us to search both the main Website and Learn systems. Organization-controlled records may also require coordination with the relevant organization. You can unsubscribe from marketing through any email's unsubscribe link and revoke connected OAuth or MCP clients through the applicable product or client controls where available.

11. Children

The Platform is not directed at individuals under 18 (or the age of majority in your jurisdiction). We do not knowingly collect Personal Information from children. If you believe we have, contact us and we will take appropriate steps to delete it.

12. Third-party sites

The Platform may link to third-party websites, repositories, MCP servers, package registries, or tools. Their privacy practices are governed by their own policies; we do not control how they process data and we are not responsible for them. If you install or connect third-party software discovered through the Platform—including browser extensions—or direct us to summarize third-party web content, that interaction may cause data to leave your device in line with Sections 2 and 5.

13. Changes

We may update this Privacy Policy periodically. Material changes may be communicated through the Platform or by email where appropriate. Please review this page regularly.

14. Contact and grievance

For questions about this Privacy Policy or your Personal Information, contact us at support@explainx.ai.

For grievances under applicable Indian law, you may also write to the Grievance Officer at the same email, with "Privacy grievance" in the subject line. We will address complaints in line with applicable timelines and rules.

Registered office: AISOLO Technologies Private Limited, 1003, Kamdhenu Commerz, Sector 14, Kharghar, Navi Mumbai 410210, Maharashtra, India.