Updated: April 17, 2026
This Privacy Policy explains how Eigen Labs, Inc., operating the Darkbloom platform ("Eigen Labs," "Darkbloom," "we," "us," or "our") collects, uses, discloses, and otherwise processes personal information in connection with Darkbloom's websites, console, APIs, software, provider applications, hosted services, and related products and features (collectively, the "Services").
Standalone Document. This Privacy Policy is a standalone document governing the Darkbloom Services only. It is separate from and does not incorporate the Eigen Labs Privacy Policy or other privacy notices governing EigenLayer, EigenCloud, EigenDA, EigenCompute, or other Eigen Labs products. Your use of those products is governed solely by their respective privacy notices. This Privacy Policy is designed for the Darkbloom product, including consumer-facing API and console features and provider-facing node software. It does not apply to third-party services we do not control, even if they interoperate with the Services.
This Privacy Policy applies when you:
Additional notices may apply to specific products, integrations, or enterprise relationships.
The categories of personal information we collect depend on how you use the Services.
2.1 Account and identity information. We may collect:
2.2 Payment, transaction, and billing information. We may collect:
We generally do not receive full payment card numbers from Stripe or similar payment processors.
2.3 Usage and service metadata. We collect service usage information such as:
2.4 Content you submit and receive. Depending on the feature you use, we may process:
We refer to this material as "Content."
2.5 Provider and device information. If you run provider software or use provider-related features, we may collect:
Further, provider Macs enrolled in the platform are subject to periodic automated SecurityInfo queries sent via Apple's MDM protocol through Apple's Push Notification service (APNs). These queries request SIP status, Secure Boot level, and Authenticated Root Volume integrity from the device's OS MDM client and not from Darkbloom software. This querying occurs on an ongoing basis throughout the provider's participation in the platform.
MDM enrollment is configured for security verification. Darkbloom requests only the minimum MDM permissions necessary to verify your device's security posture, specifically the ability to query device information and security status. We have deliberately not requested MDM permissions that would allow us to erase, lock, install or remove applications, or access user content or application data.
2.6 Technical and log information. When you use the Services, we may automatically collect:
2.7 Communications and support information. If you contact us, we collect the contents of your message, attachments, and related contact details.
We collect personal information:
We use personal information to:
Because Darkbloom is an inference platform, Content handling is central to how the Services work. The following disclosures are intended to be precise and conservative.
5.1 Transit and relay. Content sent to the Services is transmitted to our coordinator over TLS. Depending on the service path and provider capabilities, we may also encrypt request bodies before relaying them to a selected provider.
5.2 Coordinator access. The current service architecture requires our coordinator to process request payloads in plaintext on a transient basis for routing, compatibility, metering, and operation of the Services. You should not treat the current architecture as guaranteeing that the coordinator is technically incapable of accessing request payloads in every service path.
5.3 Logging. Our coordinator code is designed not to log prompt content in ordinary request logs. However, we do log operational metadata such as request path, status, duration, and remote address. Content may also be disclosed to us if you intentionally provide it in support requests, bug reports, or other communications.
5.4 Selected providers. To fulfill inference requests, we disclose relevant Content to the provider selected to process the request. If you operate provider software, that means customer requests may be routed to your device subject to the Services' security and attestation controls.
5.5 Images and uploads. Generated images may be temporarily stored in service memory pending retrieval and delivery to the requesting user. These in-memory image uploads are removed after retrieval, but no system can guarantee perfect deletion or eliminate all risk.
5.6 Training. This Privacy Policy does not grant us a right to use your Content for general-purpose model training. If we decide to do so in the future, we will update this Privacy Policy and any related contractual terms before doing so, to the extent required by law.
We may disclose personal information:
Some information may also be public by design:
We do not sell personal information for money. We also do not share personal information for cross-context behavioral advertising as those terms are used in certain U.S. privacy laws.
If and to the extent a legal basis is required for our processing, we rely on:
We retain personal information for as long as reasonably necessary for the purposes described in this Privacy Policy, including to:
Retention periods may vary by data type. For example:
Depending on where you live, you may have rights to:
We may need to verify your identity before fulfilling a request. We may deny or limit requests where permitted by law, including where we cannot verify identity, where the request is legally exempt, or where retention is necessary for security, billing, compliance, or dispute purposes.
To submit a privacy request, contact us at notices@eigenlabs.org.
Authorized agents may submit requests on your behalf where permitted by law, subject to verification.
California residents may have rights described in the California Consumer Privacy Act, including rights to know, delete, correct, and opt out, subject to applicable exceptions.
We and our partners may use cookies, local storage, SDK storage, or similar technologies to:
You can control some browser storage through your browser settings, but disabling these features may impair the Services.
Our websites and apps are not currently designed to respond to browser "Do Not Track" signals.
The Services may link to third-party websites, repositories, social channels, wallet providers, identity providers, and payment services. If you follow those links or use those services, your information will be governed by the applicable third party's terms and privacy practices, not ours.
This includes services used for authentication and embedded wallet flows:
We are not responsible for the privacy, security, availability, or accuracy of third-party services we do not control.
We use administrative, technical, and organizational safeguards designed to protect personal information appropriate to the nature of the data and the Services. These may include authentication controls, TLS, integrity checks, attestation workflows, access restrictions, and logging.
No security program is perfect, and we cannot guarantee absolute security.
We may process personal information in the United States and other jurisdictions where we or our service providers operate. Those jurisdictions may not provide the same level of data protection as your home jurisdiction. Where required by applicable law, we rely on appropriate legal mechanisms for international transfers of personal information, which may include Standard Contractual Clauses approved by the European Commission or other lawful transfer mechanisms. For more information about the transfer mechanisms we use, contact us at notices@eigenlabs.org.
The Services are not directed to children under 13, and we do not knowingly collect personal information from children under 13. We also do not permit users under 18 to use the Services under our Terms of Service.
If you believe a child has provided personal information to us in violation of this Privacy Policy, contact us so we can take appropriate steps.
We may update this Privacy Policy from time to time. If we make material changes, we will post the updated version, update the effective date, and take any additional steps required by law.
For questions or requests about this Privacy Policy, contact: notices@eigenlabs.org