M2M Network

Privacy Policy

Last updated: April 4, 2026

This Privacy Policy describes how M2M Network (“M2M,” “we,” “us,” or “our”) handles information when you use our web application, protocol interfaces, and related services (collectively, the “Services”). By using the Services, you acknowledge this policy.

1. Scope

M2M is a Decentralized Physical Infrastructure Network (DePIN) that connects electric vehicle (EV) drivers with charging capacity. Some processing occurs on public blockchains and through third-party infrastructure; those systems have their own privacy practices.

2. Information we collect

2.1 Wallet and on-chain data

When you connect a Solana wallet, we process your public wallet address and may display it in the interface. On-chain transactions, balances, and program interactions are recorded on Solana public ledgers and are not controlled by M2M.

2.2 Account and authentication (Supabase)

If you sign up with email, OAuth (e.g. Google or Apple), or similar methods, our authentication provider (Supabase Auth) processes identifiers such as your email address, authentication provider metadata, and session tokens as needed to operate login, password reset, and account security. We use this data to maintain your profile and sync it with application data stored in our database.

2.3 Vehicle and charging telemetry

To operate sessions, reconciliation, and safety features, we may process data such as vehicle model or identifiers you provide, energy-related readings from integrated vehicle APIs where you grant access, and charger-reported status (including plug state, session energy, and hardware identifiers) received through charging hardware integrations (e.g. OCPP-aligned flows). The categories processed depend on your actions and integrations enabled in your jurisdiction.

2.4 Location and map usage

When you use map features, we may process approximate or precise location as provided by your browser or device and by our mapping provider (e.g. Mapbox) to show chargers and routes. You can control location permissions in your device or browser settings.

2.5 Technical and usage data

We may collect logs, device and browser type, IP address, and usage events to secure the Services, debug issues, and understand aggregate usage patterns.

3. Oracle and infrastructure providers

M2M’s Dual-Verification Oracle and related services may process telemetry from chargers and vehicles to reconcile energy delivery. That processing is limited to operating the protocol, displaying session status, and settling flows described in our documentation. Third-party APIs, indexers, and node operators may process data according to their own terms.

4. How we use information

We use the information above to:

  • Provide, maintain, and improve the Services;
  • Authenticate users and link wallets to profiles where applicable;
  • Facilitate charging sessions, QR verification, and escrow-related flows;
  • Communicate about security, support, and important notices;
  • Comply with law and enforce our terms.

5. Sharing

We may share data with service providers (e.g. hosting, database, authentication, mapping, analytics) under contractual safeguards. Blockchain data is inherently public. We may disclose information if required by law or to protect rights and safety.

6. Retention

We retain information as long as needed for the purposes above and as required by law. On-chain records may persist permanently on Solana.

7. Security

We implement reasonable technical and organizational measures. No method of transmission or storage is 100% secure; you use the Services at your own risk.

8. Your rights

Depending on your location, you may have rights to access, correct, delete, or restrict processing of personal data, or to object or port data. Contact us to exercise applicable rights.

9. International users

If you access the Services from outside the United States, your information may be processed in the United States or other countries where we or our providers operate.

10. Changes

We may update this Privacy Policy from time to time. The “Last updated” date reflects the current version. Continued use after changes constitutes acceptance of the updated policy.

11. Contact

For privacy-related questions, contact the M2M team through the official M2M Network repository or project site.