0G Private Computer

Zero Gravity Labs, Inc., a Delaware corporation ("Company," "we," "us," or "our"), is committed to protecting your privacy and providing you with information on our use of your personal data in accordance with applicable data privacy laws. This Privacy Policy describes how we collect, use, process, and share personal information in connection with 0G Private Computer, available at https://pc.0g.ai, including the associated web console and Playground, the 0G Compute Router API at https://router-api.0g.ai, the TypeScript SDK and CLI, documentation, and related tools and features (collectively, the "Service"), as well as your choices and rights regarding such information. The Service is a decentralized AI inference network: your requests are routed to model providers on the 0G Compute Network, which include official model-company channels and independent operators, including individuals, who join the network permissionlessly.

This Privacy Policy is incorporated into and forms part of our Terms of Service, available at pc.0g.ai/terms (the "Terms"). Capitalized terms used but not defined in this Privacy Policy have the meanings given to them in the Terms. This Privacy Policy applies only to the Service. Our other websites and services are governed by the privacy policies posted on those websites. This Privacy Policy does not govern the data practices of model providers, node operators, wallet providers, or other third parties described below, each of which is an independent party responsible for its own privacy practices.

Before accessing or using the Service, please read this Privacy Policy carefully. By accessing or using the Service, you acknowledge that you have read and understood this Privacy Policy. Where we rely on consent as a legal basis for processing, we will obtain such consent separately and in accordance with applicable law. If you do not agree to this Privacy Policy, please do not access or use the Service.

Section 1Personal Information We Collect

The categories of personal information we collect depend on how you interact with the Service. We collect information that you provide to us, information we collect automatically, and information from third-party sources.

1.1Information You Provide to Us

aWallet and Account Information. There is no email-and-password registration. You sign in either by connecting an Ethereum-compatible digital wallet (for example, MetaMask or WalletConnect) and signing a login message, or through a social login provided by Privy, Inc. ("Privy"), which generates a managed wallet for you. Your wallet address is your account identifier; one wallet address corresponds to one account. We store your wallet address and your Privy user ID. We do not collect, have access to, or store your private keys or seed phrases. When you sign in through Privy, your browser receives from Privy the wallet type and, for social logins, the basic public profile of the social account (such as username and avatar); our servers do not store that profile information. Privy processes the information it collects under its own privacy policy at https://www.privy.io/privacy-policy.

bEmail Address. We automatically retrieve the email address associated with your Privy account, and if none exists you may add one in the console (which also records it to your Privy account). We store your email address and use it to send balance and other service notifications and, unless you opt out, marketing messages. See Section 7.4.

cPayment Information. The Service offers two billing modes. In Default mode, you may fund your account (i) through Stripe, using a payment card or a supported payment method such as Apple Pay or WeChat Pay, in which case the amount is converted to and held in U.S. dollars in our Stripe account in the United States, or (ii) with digital assets, in which case supported tokens are bridged and, where necessary, swapped through the third-party service Khalani into a stablecoin held in our finance wallet. In either case our internal payment system credits the resulting balance to your account, denominated in U.S. dollars. In On-chain mode, you fund your account only with digital assets, by transaction to the on-chain payment layer. We record balances, credits granted to you (including the one-time welcome credit), and the transaction references necessary to reconcile your deposits. Stripe collects your payment card and billing information directly and processes it under its own privacy policy at https://stripe.com/privacy; we do not receive or store your full payment card number, and receive only payment confirmation, the amount, a transaction identifier, and related billing metadata. Where you fund a balance with digital assets, the underlying blockchain transfer is recorded on the applicable public blockchain; your Default-mode balance itself is maintained off-chain in our systems. See Section 5.

dPrompts, Inputs, and Outputs. When you submit a prompt, message, tool definition, file, image, or audio to a model through the API or the Playground, and when a model returns a response, including text, images, or other generated media (together, "Content"), that Content is transmitted through the Service to the provider that serves your request. Content may contain personal information if you choose to include it. Section 3 describes how Content is handled and who can access it.

eFine-Tuning Datasets. If you use the optional fine-tuning feature, you upload your own datasets and the resulting models are stored as described in Section 3.5.

fCommunications and Feedback. If you contact us for support, submit feedback or a model request, or otherwise communicate with us, we collect the information you provide, such as your name, email address or handle, wallet address, and the content of your communications. If you register as a Partner to route your own users' traffic through the Service, we collect the contact email address you provide.

1.2Information Collected Automatically

aUsage Metadata. For each inference request we record the model and provider that served it, the trust tier, token counts, cost, timestamps, the API key used, and any referring site or application identifier supplied with the request (such as an HTTP Referer, X-Title, or Partner source header) ("Usage Metadata"). Usage Metadata does not contain the content of your prompts or outputs. Per-request details are retained for ninety (90) days and then aggregated into daily usage summaries that are retained permanently. For management keys, we also record the source IP address of each use for security auditing.

bDevice, Network, and Log Data. Our gateway records your full IP address and browser or client user agent for security auditing, together with request timestamps and error information, in logs retained for seven (7) to thirty (30) days. Your user agent is forwarded with your request to the upstream model provider that serves it. We maintain your session through a session cookie.

cCredentials. We store API keys only as irreversible one-way hashes; the full key is displayed to you once at creation. Revoking a key takes effect immediately, but usage records associated with the key are retained as described in Section 9.

dAnalytics and Error Monitoring. We use PostHog (hosted in the United States) to collect page views and product events, using your wallet address as the analytics identifier; session recording and automatic capture of interactions are disabled. We use Google Analytics to measure website traffic and usage. We use Sentry to collect error traces.

eInformation Stored in Your Browser. Your Playground chat history, your API keys, and your preferences are stored in your own browser (for example, in IndexedDB or local storage), unencrypted and without expiry. This information is not uploaded to our servers, and clearing your browser data deletes it. See Section 10.

1.3Information from Third-Party Sources

aBlockchain Data. We collect information that is publicly available on applicable blockchain networks, including wallet addresses, deposit, allocation, and settlement transactions, token balances, and smart contract interactions associated with your wallet address.

bAuthentication, Security, and Attestation Providers. We receive from Privy or your wallet provider the information necessary to authenticate you; bot-verification results from Cloudflare (Turnstile), which protects the welcome credit and other features; and hardware attestation reports from trusted execution environment attestation services (currently Phala Network and Alibaba Cloud), which verify the authenticity of provider enclaves and never receive your Content.

Section 2How We Use Your Information

2.1Provide the Service

We use your information to fulfill our contract with you and provide the Service, including to authenticate you and maintain your account; route your inference requests to providers in accordance with the trust mode, price ceilings, failover settings, and provider selections you configure, and return responses, cost traces, and cryptographic signatures to you; meter usage, maintain and deduct from your balance, apply credits and per-key spending limits, and settle consumed amounts on-chain; issue and manage API keys and management keys; deliver fine-tuning and Partner program features you elect to use; send balance and other service notifications to your email address; and respond to your support requests.

2.2Administrative Purposes

We use your information for our legitimate interests or to comply with legal obligations, including to enforce rate limits and detect and prevent fraud, abuse, automated traffic, and security incidents; measure and improve the performance, reliability, and user experience of the console, Playground, API, and SDK; diagnose and repair errors; attribute and settle Partner traffic; verify identities in connection with privacy rights requests; enforce our Terms and policies; and comply with applicable laws, regulations, legal process, and governmental requests. We may also create de-identified or aggregated information, including the network-level statistics displayed on the Service, that cannot reasonably be used to identify you, and may use and disclose it for any purpose.

2.3Marketing Communications

We may use your email address to send you marketing messages about the Service, including promotions and new models. You may opt out at any time using the marketing toggle in the console or the unsubscribe instructions in any marketing email. Opting out does not affect service notifications, such as balance alerts and security or policy notices, which we will continue to send while you hold an account.

2.4No Training on Your Content and No Human Review

We do not use your Content or fine-tuning datasets to train, fine-tune, evaluate, or otherwise improve artificial intelligence models, other than fine-tuning you initiate on your own datasets for your own use, and we do not use personal information collected through the Service for those purposes without your explicit consent. We do not conduct human review of your Content. Because Content is end-to-end encrypted and our routing layer sees only ciphertext, we are technically unable to read or reuse it, subject to the exception for asynchronous jobs described in Section 3.4. This commitment applies to us only; providers that receive plaintext Content, as described in Section 3, may have different practices.

2.5Other Purposes

We may use personal information for other purposes that are clearly disclosed to you at the time of collection or with your consent.

Section 3How Your Prompts and Outputs Are Handled

3.1End-to-End Encryption

Content in your requests and responses is end-to-end encrypted by default under the HPKE standard (RFC 9180), using a one-time key for each request that is never written to disk. Our routing layer handles only ciphertext in every trust mode and reads only the metadata needed for routing, such as the model name and sampling parameters. Content is decrypted and processed only by the provider that serves your request. As a result, we cannot read your requests or responses, except for asynchronous jobs as described in Section 3.4. Whether any other party can read your Content depends on the type of provider that serves your request, which in turn depends on the trust mode you select.

3.2Provider Types and Trust Modes

Providers on the network are of four types. TeeML providers run the model inside a hardware-isolated trusted execution environment ("TEE"); Content is decrypted only inside the enclave and cannot be read by anyone, including the provider's operator. TeeTLS providers forward your request through a TEE-verified encrypted channel to a model company's official first-party API; the TEE proxy cannot inspect the request, but the model company receives your Content in plaintext and processes it under its own privacy policy. Third-party resale providers call model companies' official APIs (for example, Anthropic or OpenAI) through our commercial accounts; the model company receives your Content in plaintext and processes it under its own privacy policy. SPML providers run the model on ordinary GPUs without TEE hardware isolation; sampling verification confirms that the claimed model is running, but the provider's operator, who may be an independent individual, can read your Content in plaintext. Every provider in the marketplace carries a type badge.

You select a trust mode for each API key in the console (the "Private" toggle) or for each request using the X-0G-Provider-Trust-Mode header. The trust mode determines which provider types may serve the request:

Trust mode	Provider types that may serve your request	Who can read your Content
Private	TeeML only	No one. Content is processed only inside hardware-isolated enclaves; neither 0G nor the provider's operator can read it.
Verified	TeeML and TeeTLS	TeeML: no one. TeeTLS: the upstream model company, under its own privacy policy.
Standarddefault	All live provider types, including third-party resale and SPML	Depending on the provider that serves the request: no one (TeeML); the upstream model company (TeeTLS or resale); or the SPML provider's operator, who can read plaintext. A request sent without a trust mode is served in Standard mode and may reach an SPML operator or a model company.

If you require that no operator or model company can read your Content, use Private mode.

If no provider satisfying your selected trust mode is available, the request fails rather than being served at a weaker tier; the trust tier is never silently downgraded, including during automatic failover to another provider. Every response includes a cost trace identifying the provider and trust tier that actually served it. In Advanced mode, you bypass our routing layer, allocate funds to providers you choose, and call them directly; we never handle your requests in that mode, and the provider you select processes your Content under its own terms and provider type.

3.3Limits of Trusted Execution Environments

TEE protections depend on hardware, firmware, and attestation infrastructure supplied by third parties and, like all security technologies, may be affected by undiscovered vulnerabilities, side-channel attacks, or misconfiguration. We design the Service so that Content in Private mode is processed only inside attested enclaves and has no mechanism to read that Content, but we do not guarantee that a TEE cannot be compromised by a vulnerability outside its control.

3.4Audio, Image, Video, and Asynchronous Jobs

The Service supports speech-to-text transcription, image generation, and, depending on the models available, video and other media generation. Audio, images, and other media you submit, and media generated for you, are Content and are handled as described in this Section 3, with the following exception. Requests processed as asynchronous jobs, such as media generation, are not end-to-end encrypted in the current version of the Service: the request and its result are held on our infrastructure in unencrypted form for up to thirty (30) minutes so that you can retrieve the result, and are then automatically deleted. The statement in Section 3.1 that we cannot read your Content does not apply to asynchronous jobs during that period. A file-upload feature is not currently available on the Service; if we enable one, we will update this Privacy Policy before doing so. We do not extract voiceprints, faceprints, or other biometric identifiers from audio, images, or video, and do not use them to identify you. If you submit audio, images, or video containing another person's voice, image, or likeness, you are responsible for having the rights and any consents required to do so. Content of other inference requests is not retained on our servers.

3.5Fine-Tuning

If you use the fine-tuning feature, your datasets and the resulting models and adapters are encrypted (AES-256) and stored on 0G decentralized storage, with decryption keys delivered only to you as the task owner. We do not access or reuse your datasets or models. Fine-tuning artifacts are stored permanently on the decentralized network and cannot be deleted, including in response to a deletion request; do not include personal information in a fine-tuning dataset unless you are prepared for it to be retained indefinitely in encrypted form.

3.6Your Responsibilities

You are responsible for the Content you submit, including for having any authority or legal basis needed to submit personal information about other individuals. The Service does not filter or moderate inputs or outputs. We recommend that you do not submit sensitive personal information to any model, and in particular not in Standard mode. If you use the API or the Partner program to serve your own users, you are solely responsible for your own privacy notices and consents and for selecting a trust mode appropriate to the data your application processes.

Section 4How We Share Your Information

We do not sell your personal information, do not share it for cross-context behavioral advertising, and use no advertising trackers. We may share your personal information in the following circumstances:

4.1Model Providers

Your encrypted Content is transmitted to the provider that serves your request, together with your user agent, and is decrypted and processed by that provider as described in Section 3. Providers include model companies and aggregators (currently including Anthropic, OpenAI, and AthenaAI) and independent operators of TEE hardware or ordinary GPUs, including individuals. Providers are independent third parties, not our agents. Each provider handles your Content under its own publicly posted terms and privacy policy, which we do not control, and we encourage you to review them before sending Content outside Private mode. Providers do not receive your wallet address, email address, or API key from us in connection with a request.

4.2Service Providers

We share personal information with third-party service providers that assist us in operating the Service, including Privy (social login and managed wallets), Stripe (card and local payment processing), Khalani (digital-asset bridging and swaps), Google Cloud (databases and logs), Vercel (front-end hosting), Cloudflare (traffic and bot verification), PostHog, Google Analytics and Sentry (analytics and error monitoring), and trusted execution environment attestation services (Phala Network and Alibaba Cloud, which receive attestation reports only). Each of these providers processes personal information in accordance with its own terms and privacy policy.

4.3Affiliates

We may share personal information with our affiliates and with other entities within the 0G group, including 0G Foundation, for purposes consistent with this Privacy Policy, including operating and supporting the Service, security, and compliance. The on-chain payment layer is shared across 0G products.

4.4Blockchain Networks

Deposit, allocation, and settlement transactions are recorded on the applicable public blockchain and are visible to anyone. This is not a revocable form of sharing. See Section 5.

4.5Compliance and Legal Obligations

We may disclose your personal information to governmental authorities, regulators, law enforcement, or other third parties where we believe in good faith that such disclosure is necessary to (i) comply with applicable laws, regulations, legal processes, or governmental requests; (ii) enforce our Terms or other agreements; (iii) protect our rights, property, or safety or those of our users or the public; or (iv) detect, prevent, or address fraud, security, or technical issues. We review such requests and comply as required by applicable law. Because we do not hold your Content in readable form, we are generally unable to produce your prompts or outputs in response to such requests.

4.6Business Transfers

In the event of a merger, acquisition, reorganization, dissolution, or similar transaction, your personal information may be transferred as part of such transaction, subject to applicable data protection law. We will provide notice of any such transfer and any choices you may have.

4.7With Your Consent

We may share your personal information for other purposes with your consent or at your direction.

Section 5Blockchain Data and Public Information

The Service is built on the 0G Network and interacts with public blockchain networks. You acknowledge and agree that:

aWhen you fund your account with digital assets, allocate funds to providers in Advanced mode, or when we settle accumulated On-chain mode usage in periodic batches, the underlying transaction, including the sending wallet address, the amount, and the timestamp, is recorded on the applicable public blockchain. Balances funded through Stripe, and Default-mode balances generally, are maintained off-chain in our systems and are not recorded on a public blockchain. Individual requests, the models used, and Content are never written to the blockchain.

bOn-chain records are public, immutable, and permanent. We cannot modify or delete them, including in response to a deletion request, and they will remain on the blockchain after you cease using the Service. Fine-tuning artifacts stored on 0G decentralized storage are likewise permanent, although encrypted.

cThird parties, including blockchain analytics providers, may independently collect, aggregate, and analyze public blockchain data associated with your wallet address. We also display aggregate, network-level statistics on the Service that do not identify individual users.

Section 6Cookies and Tracking Technologies

6.1Technologies We Use

We use cookies, browser storage, and similar technologies to operate the Service and understand how it is used. Strictly necessary technologies include our session cookie, technologies used by Privy for authentication, Cloudflare for security and bot verification, and browser storage that retains your Playground history, API keys, and preferences on your device; these cannot be disabled without impairing the Service. Analytics and performance technologies include PostHog (page views and product events, keyed to your wallet address, with session recording and automatic interaction capture disabled), Google Analytics (website traffic measurement) and Sentry (error traces). We do not use advertising or behavioral targeting cookies or trackers.

6.2Your Cookie Choices

You can manage cookies and browser storage through your browser settings. Blocking strictly necessary technologies may prevent you from signing in or using the Service, and clearing browser storage deletes your locally stored chat history and API keys. Choices must be applied separately in each browser and on each device you use.

6.3Opt-Out Preference Signals and Do Not Track

Where required by applicable law, we treat a Global Privacy Control signal or other legally recognized opt-out preference signal as a valid request to opt out of any sale or sharing of personal information and of targeted advertising. Because we do not engage in those activities, honoring such a signal does not change how the Service functions. We do not respond to Do Not Track signals, for which no industry standard has been adopted.

Section 7Your Privacy Choices and Rights

7.1General Rights

Depending on your jurisdiction, you may have the right to access and obtain a copy of your personal information; correct inaccurate or incomplete personal information; request deletion of your personal information; restrict or object to certain processing; request portability; withdraw consent where processing is based on consent; and be informed of the purposes for which your personal information is collected and the classes of third parties to whom it may be disclosed. To exercise these rights, contact us at privacy@pc.0g.ai. Because your wallet address is your account identifier, we may verify your request by asking you to sign a message from the associated wallet or to authenticate through the console. We will process your request in accordance with applicable law and will not discriminate against you for exercising your rights.

7.2Limits on Deletion and Access

We cannot modify or delete information recorded on a public blockchain or fine-tuning artifacts stored on decentralized storage. Because we do not hold your Content in readable form, we cannot provide copies of, or delete, your prompts or outputs; where a model company or SPML operator received plaintext Content, you may need to contact that provider directly. We may retain information as required by law or as necessary to complete settlement, resolve disputes, and enforce our agreements, and we retain aggregated daily usage summaries that do not identify individual requests.

7.3Account Deletion and Data Export

The Service does not currently offer self-service account deletion or data export. You may revoke your API keys at any time in the console, and you may request deletion of your account information or a copy of your personal information by contacting us at privacy@pc.0g.ai; we will respond as required by applicable law, subject to the limits described in Section 7.2. Your on-chain balance is controlled by your wallet and is not affected by any deletion request. Deleting your account information does not delete your Privy account or managed wallet, which are governed by Privy's terms, and does not delete information stored in your own browser.

7.4Trust Mode and Communications

Your most important privacy choice on the Service is your trust mode; enable the Private toggle on any API key, or send the private trust-mode header, for any request for which you require that no party other than you can read your Content. You may opt out of marketing emails at any time as described in Section 2.3; service notifications relating to your balance, security, and changes to our terms and policies will continue while you hold an account.

Section 8International Data Transfers

We are established in the United States and operate globally. Our databases and logs are hosted on Google Cloud in the United States (us-central1), our front end is hosted by Vercel, our Stripe account is held in the United States, and our other service providers, including Privy, PostHog, Google Analytics and Sentry, process personal information in the United States. Model providers and operators may be located anywhere in the world; in Private mode, provider location does not affect the confidentiality of your Content because no party other than you can read it. If you access the Service from outside the United States, your personal information will be transferred to, stored, and processed in the United States and in other jurisdictions that may have data protection laws different from those where you live.

Where personal information is transferred from the European Economic Area, the United Kingdom, or Switzerland to a jurisdiction that does not provide an adequate level of protection under applicable data protection laws, we implement appropriate safeguards, including the EU Standard Contractual Clauses (June 2021 version) and the UK International Data Transfer Addendum where applicable. For more information, contact us at privacy@pc.0g.ai.

Section 9Retention of Personal Information

We retain your personal information for as long as reasonably necessary to fulfill the purposes for which it was collected, including to provide the Service, comply with legal obligations, resolve disputes, and enforce our agreements. In particular: Content of ordinary inference requests is not retained on our servers; asynchronous job records are deleted within thirty (30) minutes; gateway logs, including IP addresses and user agents, are retained for seven (7) to thirty (30) days; per-request Usage Metadata is retained for ninety (90) days and then aggregated into daily summaries that are retained permanently; your wallet address, Privy user ID, email address, API key hashes, balance, and credit records are retained for as long as you hold an account and thereafter as required for our records; Partner attribution records are retained permanently for settlement; and on-chain records and fine-tuning artifacts are permanent. Information held by Privy and our analytics providers is retained in accordance with their respective policies, and information stored in your own browser persists until you clear it. When personal information is no longer necessary, we delete or de-identify it or, where deletion is not possible, isolate it from further processing to the extent practicable.

Section 10Security of Your Information

We implement administrative, technical, and organizational safeguards designed to protect your personal information. All traffic is encrypted in transit using TLS; Content is end-to-end encrypted by default under the HPKE standard with a one-time key per request, subject to the exception for asynchronous jobs described in Section 3.4; API keys are stored only as one-way hashes; and inference on TEE-class providers runs inside hardware enclaves whose authenticity is verified through cryptographic attestation, with every response signed by a key held inside the enclave. However, no method of transmission over the Internet or electronic storage is completely secure, and we cannot guarantee absolute security. Your API keys and Playground chat history are stored unencrypted in your own browser, so you should secure your device and clear browser storage on shared computers. You are solely responsible for maintaining the security of your wallet, private keys, seed phrases, login credentials, API keys, and management keys; API keys grant access to your balance, so treat them as secrets and revoke any key you believe has been compromised. In the event of a security breach affecting your personal information, we will notify you and any applicable regulatory authorities as required by applicable law.

Section 11Minors' Information

The Service is not directed to individuals under the age of eighteen (18), or such higher age as required by applicable law, and under the Terms you must be at least eighteen (18) to use it. We do not knowingly collect personal information from minors. If you believe a minor has provided personal information through the Service, contact us at privacy@pc.0g.ai and we will take steps to delete it promptly.

Section 12Supplemental Notice for EU/UK Residents (GDPR)

This section applies only to individuals whose personal information is subject to the EU General Data Protection Regulation, the UK GDPR, or the Swiss Federal Act on Data Protection.

12.1Data Controller

Zero Gravity Labs, Inc. is the data controller responsible for personal information relating to your account, email, payments, usage, analytics, security, and communications. With respect to Content, we act as a conduit that routes end-to-end encrypted Content to the provider selected in accordance with your trust-mode instructions and do not access, store in readable form, or determine the purposes of processing that Content; providers that decrypt and process Content act as independent controllers of it. The Service is operated from the United States and is not specifically directed to individuals in the European Economic Area or the United Kingdom; this Section applies to the extent applicable law nonetheless applies to our processing.

12.2Legal Bases for Processing

We process your personal information on the basis of performance of a contract (to authenticate you, maintain your account and balance, route your requests, meter usage, settle amounts due, and send service notifications); legitimate interests (to secure the Service, prevent fraud and abuse, analyze and improve the Service, attribute Partner traffic, display aggregate statistics, and enforce our agreements, in each case balanced against your rights and freedoms); compliance with legal obligations (including tax and accounting requirements and lawful requests); and consent (for non-essential analytics where required, marketing communications, and any use of your Content to train or improve AI models, which we do not undertake without your explicit consent). You may withdraw consent at any time without affecting the lawfulness of prior processing.

12.3Your Rights Under GDPR

In addition to the rights described in Section 7, you have the right to object to processing based on legitimate interests, in which case we will cease processing unless we demonstrate compelling legitimate grounds that override your interests, rights, and freedoms; to request information about the safeguards used for international transfers; and to lodge a complaint with the supervisory authority where you reside, work, or believe a violation occurred. We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you; automated rate limiting and bot verification may temporarily limit access, and you may contact us to request human review.

Section 13Supplemental Notice for U.S. State Privacy Laws

This section applies to residents of U.S. states that have enacted comprehensive consumer privacy laws, including California, Colorado, Connecticut, Delaware, Texas, Virginia, and other states with applicable legislation, to the extent those laws apply to us. In the preceding twelve (12) months, we may have collected the following categories of personal information: identifiers (wallet addresses, Privy user IDs, email addresses, IP addresses, and API key identifiers); commercial information (deposits, balances, credits, usage charges, and settlement records); internet or electronic network activity information (console and Playground usage, product events, device and browser information, and error reports); geolocation data (approximate location that may be inferred from IP address); audio, electronic, or visual information (audio, images, or video you submit as Content, which is transmitted in encrypted form and held only briefly as described in Section 3.4); and the content of support communications. Prompts and outputs are transmitted through the Service in encrypted form and are not stored by us in readable form. Account login credentials are held by Privy, not by 0G, and we do not otherwise collect sensitive personal information except to the extent you include it in Content or fine-tuning datasets, which we do not access. We collect this information from the sources described in Section 1, use it for the purposes described in Section 2, and disclose it for business purposes to the categories of recipients described in Section 4.

We do not "sell" or "share" personal information as those terms are defined under applicable state privacy laws, do not process personal information for targeted advertising, do not engage in profiling in furtherance of decisions that produce legal or similarly significant effects, and do not use automated decision-making technology to make significant decisions about you. We honor opt-out preference signals as described in Section 6.3. You may exercise your rights under applicable state privacy laws, including the rights to know, access, correct, delete, and obtain a portable copy of your personal information, directly or through an authorized agent, by contacting us at privacy@pc.0g.ai. If we deny your request, you may appeal by contacting us at the same address with the subject line "Privacy Appeal"; if your appeal is denied, you may contact your state attorney general. We will not discriminate against you for exercising these rights.

Section 14Governing Law and Dispute Resolution

This Privacy Policy is governed by and construed in accordance with the laws of the State of Delaware, United States, without regard to its conflict of law principles. Any dispute, controversy, or claim arising out of or relating to this Privacy Policy is subject to the dispute resolution provisions of the Terms. Nothing in this Section prevents you from exercising any right to lodge a complaint with a data protection or consumer protection authority in your jurisdiction, where applicable.

Section 15Changes to This Privacy Policy

We may update this Privacy Policy from time to time in our sole discretion. When we make changes, we will update the "Last Updated" date at the top of this Privacy Policy and post the revised version on the Service. If we make material changes, including any change that would permit 0G to read, log, or store Content or that changes which parties can read Content in a given trust mode, we will provide prominent notice through the Service before the change takes effect and, where required by law, obtain your consent. Your continued access to or use of the Service after the posting of a revised Privacy Policy constitutes your acceptance of the revised Privacy Policy.

Section 16Contact Us

If you have any questions about this Privacy Policy, our data practices, or wish to exercise your privacy rights, please contact us at:

Zero Gravity Labs, Inc.

Email: support@pc.0g.ai