Jupiter Meta Labs Foundation & JMDT Blockchain Infrastructure
Effective Date: [Date] Last Updated: [Date]
Version: 1.0
1. INTRODUCTION AND SCOPE
1.1 Overview
Jupiter Meta Labs Foundation ("Foundation", "we", "us", or
"our") is committed to protecting the privacy and security of users interacting with the JMDT
Chain platform ("Platform") and JMDT utility tokens ("Tokens").
This Privacy Policy explains our approach to data collection, use, storage, and protection in connection with
the Platform, Tokens, Platform-related services and communications, and validator node operations and
participation.
1.2 Privacy-by-Design Approach
- Minimal Data Collection: We collect only essential technical data
- No Personal Data: We do not collect personal information or identity verification data
- Blockchain Native: User interactions occur via blockchain transactions
- Decentralized Architecture: Minimal centralized data storage
1.3 Applicability
- General users interacting with JMDT tokens
- Enterprise users building on the Platform
- Validator node operators
- Website visitors and documentation users
2. DATA COLLECTION PRACTICES
2.1 Personal Data Collection
We DO NOT collect personal data, including names, contact information, government IDs,
biometrics, payment details, demographics, preferences, or similar data.
2.2 Blockchain Data Collection
We DO NOT actively collect or store wallet addresses, transaction histories, token holdings,
smart contract interaction data, or profiling data.
2.3 Technical Data Collection
2.3.1 Network Operations Data
- IP Addresses: Temporarily processed for routing and security (not stored)
- Connection Data: Basic connectivity information
- Protocol Data: Technical blockchain protocol communications
- Node Communications: Validator synchronization data
2.3.2 Platform Interaction Data
- Transaction Broadcasts: Processed but not attributed to individuals
- Network Participation: Anonymous validator performance metrics
- Error Logs: Anonymized maintenance data
2.4 Voluntary Communications
User-initiated contact only: support requests, enterprise inquiries, community interactions, bug reports.
3. PURPOSE AND LAWFUL BASIS FOR DATA PROCESSING
3.1 Legitimate Interests
3.1.1 Platform Operations
- Network security and anti-abuse
- Technical maintenance and performance
- Protocol development and efficiency
- Infrastructure management
3.1.2 Legal Compliance
- Regulatory requirements and security obligations
- Judicial cooperation when required by law
3.2 No Marketing or Advertising
We DO NOT conduct targeted advertising, profiling, data sales, personalization, or business
analytics.
3.3 No Third-Party Analytics
We DO NOT use Google Analytics or similar tracking services, pixels, or third-party marketing
platforms.
4. DATA SHARING AND DISCLOSURE
4.1 No Commercial Data Sharing
We DO NOT share data with advertisers, brokers, analytics firms, or partners for commercial
purposes.
4.2 Infrastructure Providers
Limited technical data may be processed by cloud providers (e.g., GCP USA), network providers, and security
services under strict agreements.
4.3 Legal and Regulatory Disclosure
- Disclosures only under valid legal process
- Minimum necessary data; legal review; user notice where permitted
- Transparency reports (if any)
4.4 Emergency Situations
Limited data may be shared to address imminent threats with legal review.
5. DATA STORAGE AND SECURITY
5.1 Data Storage Infrastructure
- GCP (USA), redundancy, SOC 2 / ISO 27001
5.2 Security Measures
5.2.1 Encryption
- AES-256 at rest; TLS 1.3 in transit; HSM key storage
5.2.2 Access Control
- MFA, RBAC (least privilege), audit logs, quarterly access reviews
5.2.3 Zero-Knowledge Architecture
- Client-side crypto; minimal server knowledge; ZK proofs where applicable
5.3 Security Monitoring
- 24/7 monitoring, penetration tests, vulnerability management, incident response
5.4 Data Minimization
- Automatic log purging after 30 days; anonymization; quarterly audits
6. BLOCKCHAIN TECHNOLOGY AND IMMUTABILITY
6.1 Characteristics
- Immutability, public visibility, distributed storage, no central control
6.2 User Control
- Private key security; user-decided transactions; no deletion rights on-chain
6.3 Smart Contract Data
- Automated execution; no personal data; transparent and decentralized processing
7. USER RIGHTS AND LIMITATIONS
7.1 Limitations
- No personal profile to access; on-chain data is public; technical logs are transient
7.2 Controls
- Wallet and transaction control; cease use anytime; voluntary communications
7.3 Grievance and Contact
- Data Protection Officer: Yashaswini — [DPO Email Address] (response within 30 days)
- Legal Team: [Legal Email Address], [Foundation Legal Address]
- Complaint Process: contact → investigation → resolution → external appeals
8. INTERNATIONAL DATA TRANSFERS
- Processing in USA (GCP); global validator nodes
- Encryption, contractual protections, legal compliance
9. CHILDREN'S PRIVACY
- No targeting children; delete any discovered data; COPPA compliance
10. COOKIES AND TRACKING TECHNOLOGIES
- Essential cookies only (session/security/load balancing); no third‑party cookies
11. THIRD-PARTY LINKS AND SERVICES
External links (explorers, exchanges, docs, community). Separate policies apply.
12. DATA BREACH NOTIFICATION
- Assessment, containment, investigation, remediation
- User and regulatory notification; documentation
13. BUSINESS TRANSFERS
- Privacy obligations transfer; notice of significant changes
14. CHANGES TO THIS PRIVACY POLICY
- Annual review; legal/tech updates; notice for material changes
15. JURISDICTION-SPECIFIC RIGHTS
Jurisdiction-specific rights (e.g., GDPR, CCPA/CPRA) acknowledged in a minimal data context.
16. TRANSPARENCY AND ACCOUNTABILITY
- Privacy by design, audits, continuous improvement
17. CONCLUSION
- Minimal data, strong security, transparency, user control, compliance
← Back to Home