Home Privacy Master Privacy Policy
Master Data Protection Version 4.2 • Updated: 2026

Master Privacy Policy

How MD Technologies transparently collects, processes, encrypts, and safeguards personal data, source code, and commercial records across the global MD Colab ecosystem.

1. Zero Data-Selling Commitment & Core Principles

Zero Data-Selling Guarantee: MD Colab does NOT sell, rent, monetize, or trade your personal data, developer source code, or private project databases with advertisers or external data brokers.

At MD Technologies, privacy is treated as a fundamental architectural requirement. This Master Privacy Policy outlines the comprehensive protocols governing how your personal data, developer credentials, and commercial identities are managed across all MD Colab platforms.


2. Scope Across MD Colab Ecosystem

This privacy policy applies to all interactions across our interconnected platform services:

MD Workspace & IDE

Browser Monaco editor sandboxes, multiplayer room state, live preview sessions, and repository tokens.

TalentX Creator Directory

Public creator listings, skill endorsements, OrangeTick verification data, and direct message communications.

MD Business & KYC

Corporate registration records, GSTIN certificates, authorized signatory records, and Razorpay Route accounts.

MD DropShip & Supplier

Order routing, buyer shipping details, wholesale SKU pricing, and Razorpay Route settlement payouts.

MD Invoice

GST business identifiers, line item tax calculations, and WhatsApp transaction snapshots.

MD Plus & Cloud Services

High-tier compute allocations, priority bandwidth, cloud storage quotas, and encrypted session archives.


3. Information We Collect Directly from Users

  • Account Credentials: First name, last name, registered email address, securely salted/hashed passwords, date of birth, and avatar images.
  • Portfolio & Professional Footprint: Claimed username (e.g. /@username), professional role, biography, skill keywords, GitHub/LinkedIn links, and public showcase projects.
  • Commercial Tax Data (MD Business): Registered business name, GSTIN number, PAN identifier, business address, and linked Razorpay Route account ID.
  • Support Inquiries: Ticket transcripts, bug reports, and diagnostic logs submitted via our Support Desk.

4. Automated Telemetry & System Logs

When interacting with our browser sandboxes and APIs, we collect minimal technical telemetry:

  • IP addresses (used transiently for geolocation and DDoS rate-limiting).
  • Browser client fingerprints, user agent strings, and viewport dimensions for IDE rendering compatibility.
  • Client-side JavaScript console error traces and WebContainer build diagnostics.

5. Lawful Bases & Purposes of Processing


6. Authorized Cloud Infrastructure & Sub-Processors

MD Colab relies on enterprise-grade infrastructure providers adhering to SOC-2 and ISO-27001 standards:

  • Google Cloud Platform (Firebase Firestore): Real-time database hosting, authentication, and secure document storage (Asia-South1 Mumbai region).
  • Razorpay Software Pvt. Ltd.: Payment gateway and automated Razorpay Route split settlement engine (RBI-regulated).
  • Cloudinary Ltd.: Secure image CDN hosting for invoice WhatsApp snapshots and portfolio assets.
  • Vercel Inc. & Netlify: Edge network hosting, serverless functions, and static CDN asset caching.
  • Google Gemini API (Google Cloud): Large language model inference for Zainin AI and code co-pilot.

7. Cryptographic Standards & Data Security

We employ defense-in-depth protection across all layers:

  • In-Transit Encryption: All traffic is enforced over TLS 1.3 with HSTS headers and strong cipher suites.
  • At-Rest Encryption: Cloud databases and snapshot backups are encrypted using AES-256.
  • Granular Firestore Rules: Server-side security rules ensure users can only access authorized documents and projects.

8. International Data Transfers

While our primary database clusters reside within India (Mumbai region), certain global CDN edge caches or third-party APIs may process data across international server nodes under Standard Contractual Clauses (SCCs).


9. 72-Hour Security Breach Notification SLA

In the unlikely event of a confirmed security incident affecting personal user data, MD Colab will notify affected users and relevant statutory authorities within 72 hours of confirmation, accompanied by technical impact assessments and remediation steps.

Link copied to clipboard!