このページは英語版のみご利用いただけます。 英語版が正式な内容となります。
法務
Privacy Policy
最終更新日:2026年11月5日
What information MZGrid Labs collects when you use the website, coordinator API and provider agent, why, how long we keep it, and the choices you have. On-chain data is public and outside our control.
This Privacy Policy explains how MZGrid Labs ("MZGrid Labs", "we", "us") collects, uses and shares information when you use the MZGrid website, dashboards, coordinator API, SDK and provider agent (the "Services"). It should be read together with our Terms of Service.
We have designed the Services to collect as little personal information as practical. We do not ask for your name, email address or government identification to rent or provide compute, and we do not run advertising trackers.
1. Public blockchain data
MZGrid runs on the Base network. When you fund a Job, accept a Job, receive a settlement, lock or withdraw MZG, or are slashed, the transaction — including your wallet address, amounts, timestamps and Job identifiers — is recorded permanently on a public blockchain.
This data is public by design. Anyone can read it, and it cannot be modified or deleted by us or anyone else. The Services also display on-chain data (for example, provider addresses, settlement amounts and slashing events) on the network dashboard and marketplace. If a wallet address can be linked to you, your on-chain activity can be linked to you as well. Consider using a dedicated wallet for MZGrid if this concerns you.
2. Information we collect
Account and authentication
- Wallet address. When you sign in, you sign a message with your wallet. We store your address and issue a session token.
- API keys. If you create API keys, we store a name you choose, creation and last-used timestamps, and a cryptographic hash of the key. We never store API keys in plain text and cannot show a key again after creation.
Customer Job data
When you create a Job, the coordinator stores Job metadata: template, GPU model, provider, region, price, maximum duration, deposit, status, timestamps, used seconds, settlement amounts and transaction hashes, as well as the configuration you submit (for example, model name, container image, ports and arguments).
Environment variables you mark as secrets are passed to the Provider's container and are not retained by the coordinator after the Job ends. The contents of your requests to a Job endpoint (prompts, files, audio, outputs) go directly to the Provider's machine; the coordinator does not store them.
Job logs
Container logs streamed by the provider agent are stored by the coordinator so you can view them in the dashboard and through the API. Logs are retained for 30 days after a Job ends and then deleted. Logs may contain whatever your workload prints, so avoid logging sensitive data.
Provider data
If you operate a Provider, we collect: your wallet address and provider name; region; machine specifications (GPU models and UUIDs, driver versions, CPU cores, RAM, disk, bandwidth); benchmark results; heartbeats (GPU utilisation, memory use and temperature, sent every 30 seconds); usage samples for running Jobs; and the endpoint address your machine exposes for Jobs, which necessarily includes its IP address or hostname. Offer details, reliability scores and aggregate statistics are displayed publicly on the Services.
Raw heartbeat data is kept for 90 days; after that we retain only daily aggregates used for reliability and uptime scores.
Technical and security data
When you access the Services, our servers receive your IP address, user agent, request paths and timestamps. We use this for security, abuse prevention and rate limiting. Request logs containing IP addresses are retained for 14 days, except where needed longer to investigate a specific security incident.
Support communications
If you email us, we keep the correspondence and the email address you used to respond and keep a record of the issue, for up to 24 months after the issue is closed.
3. Cookies and local storage
The website does not use advertising cookies, third-party or cross-site tracking cookies or tracking pixels, and we do not sell or share data for targeted advertising. Our Cookie Policy lists every cookie and browser storage item we set, with its purpose, duration and category. In summary:
- Consent record. A first-party cookie (
mzg_consent) stores your cookie choice for 12 months. - Language preference. If you consent to Preferences, a first-party cookie (
NEXT_LOCALE) remembers the language you selected. It is deleted when you withdraw that consent. - Session token. After you sign in with your wallet, your session token, wallet address, session expiry and accepted terms version are kept in your browser's local storage so you stay signed in. They are removed when you sign out or the session expires.
- Provider dashboard. A short-lived signed authentication header is kept in session storage and cleared when you close the tab.
- Wallet connection. Your wallet extension may store its own data; that is governed by the wallet provider's policies.
No analytics cookies or scripts are currently set. Privacy-friendly, aggregate page-view statistics would only ever be enabled after you opt in, and the Cookie Policy will be updated first. You can change your choice at any time through "Cookie settings" in the site footer, and clear cookies and local storage through your browser settings.
4. How we use information
We use the information above to:
- operate the Services: authenticate you, schedule and dispatch Jobs, show logs and status, settle Jobs on-chain;
- verify Providers and apply the reputation and slashing rules described in the documentation;
- keep the Services secure: detect abuse, enforce rate limits, investigate incidents and enforce our Terms;
- publish aggregate network statistics;
- respond to support requests; and
- comply with legal obligations, including sanctions compliance.
Where data protection laws require a legal basis, we rely on performance of our contract with you, our legitimate interests in operating a secure and reliable service, and compliance with legal obligations.
5. How information is shared
- Providers and Customers. To run a Job, the Provider receives the Job configuration and your requests to the endpoint. Customers see Provider names, regions, specifications and reliability scores.
- Service providers. We use processors that help us run the Services, such as cloud hosting and storage providers, blockchain RPC node providers, and email providers for support correspondence. They process data on our instructions and under contractual confidentiality and security obligations.
- RPC providers. Calls your browser makes to the blockchain through your wallet go to the RPC endpoint your wallet is configured to use, which will see your IP address and wallet address.
- Legal reasons. We may disclose information if required by law, or if we believe in good faith that disclosure is needed to protect the rights, property or safety of users, MZGrid Labs or the public.
- Business transfers. If the Services are transferred to another operator, information may be transferred as part of that transaction, subject to this Policy.
We do not sell personal information.
6. Retention summary
| Data | Retention |
|---|---|
| On-chain transactions | Permanent (public blockchain, outside our control) |
| Job metadata and settlement records | While your account is active and up to 6 years for accounting and dispute purposes |
| Job container logs | 30 days after the Job ends |
| Provider heartbeats (raw) | 90 days, then daily aggregates |
| Server request logs with IP addresses | 14 days, unless needed for an active security investigation |
| API key hashes | Until the key is revoked, then 30 days |
| Support correspondence | Up to 24 months after the issue is closed |
7. Security
We protect information with access controls, encryption in transit, hashing of API keys and least-privilege access for our staff. No system is perfectly secure. If you find a vulnerability, please report it to [email protected].
Data you send to a Job is processed on a Provider's hardware, which we do not control. MZGrid is not confidential computing; see the Risk Disclosure.
8. Your rights
Depending on where you live, you may have rights to access, correct, delete or export personal information we hold about you, to object to or restrict certain processing, and to complain to a data protection authority.
To exercise these rights, email [email protected]. Because most of our records are keyed to wallet addresses, we may ask you to sign a message with the relevant wallet to verify the request. We cannot delete or alter on-chain data, and we may retain some information where required by law or to resolve disputes.
9. International transfers
We and our service providers may process information in countries other than the one you live in, which may have different data protection laws. Where required, we use appropriate safeguards for such transfers, such as standard contractual clauses.
10. Children
The Services are not intended for anyone under 18. We do not knowingly collect information from children. If you believe a child has used the Services, contact [email protected] and we will take appropriate steps.
11. Changes
We may update this Policy. We will post the new version here with an updated date and, for material changes, give notice through the Services or our blog.
12. Contact
Privacy questions and requests: [email protected]. Other enquiries: [email protected].