Legal
Privacy for a workload platform that stores only what it needs to operate
This policy explains what Jungle Grid collects from visitors, account holders, workload operators, and providers, how that information is used, and how to contact us about privacy questions or requests.
These pages describe the public website and product surfaces under the Jungle Grid brand.
Use this email for privacy questions, access requests, and data-handling concerns.
This version reflects the current website, auth, portal, and billing behavior shipped in this repository.
Policy details
What this policy covers
This Privacy Policy applies to the Jungle Grid marketing website, signup and login flows, browser-based portal, billing surfaces, provider account tools, and related browser flows that interact with Jungle Grid APIs.
It covers information you give us directly, information generated when you use the service, and limited browser-side data used to keep the site working correctly.
Information we collect
We collect contact, identity, and account information when you register or manage an account. Depending on the flow, this can include your email address, password, account role, referral code, first name, last name, country code, signup source details, and Google-linked identity details.
We also collect service and operational data generated when you use Jungle Grid. That can include workload and job metadata, node or provider details, billing and payout profile information, registry credential metadata, API key metadata, webhook configuration metadata, audit history, and account role state.
- Browser auth flows use tab-scoped session storage for signed-in sessions.
- Theme and certain interface preferences are stored in local storage.
- The landing experience can store guest inference draft state in local storage before signup.
- The homepage can request and store promotional signup tokens tied to credit offers.
How we use information
We use information to provide, secure, and improve Jungle Grid, including creating and verifying accounts, routing workloads, managing provider participation, operating billing flows, enforcing product rules, supporting users, and maintaining auditability across account actions.
We also use information to measure product usage and page activity, detect abuse or failures, communicate account or billing events, and keep the website and portal functioning across sessions and devices.
When we share information
We share information only when it is reasonably necessary to operate the service, complete a transaction, deliver communications, support sign-in, measure product usage, or comply with legal obligations.
Examples in the current product include payment processing, email delivery, analytics, Google authentication, and user-directed outbound webhook or callback destinations configured inside the product.
Cookies, local storage, and browser-side identifiers
Jungle Grid uses a mix of browser storage and third-party telemetry rather than relying only on classic cookies. The site stores theme preferences in local storage, account sessions in session storage, and certain temporary workflow state such as guest inference drafts or dismissed promotional UI state in local storage.
Analytics and promotional flows may generate identifiers or event data that help us understand usage, attribution, and onboarding effectiveness. More detail appears in the Cookies and Local Storage page.
Billing, payout, and transaction information
If you use wallet funding or provider billing surfaces, Jungle Grid processes transaction-related information needed to initialize, verify, record, or reconcile credits and payout readiness. The current product includes Paystack-backed wallet funding flows in USD and provider payout profile surfaces.
We do not publish full card data in the frontend codebase. Payment handling and settlement events are processed through payment rails and related backend services, with status reflected in Jungle Grid account and billing views.
Security, retention, and account controls
We use reasonable administrative, technical, and product controls to protect account and operational data, including authenticated API access, scoped account tools, verification flows, and product-level controls for secrets such as webhook signing material and registry credentials.
We retain information for as long as needed to operate Jungle Grid, maintain account history, resolve disputes, meet security and compliance needs, and enforce product rules. Different categories of data may be retained for different periods based on those purposes.
Your choices and rights
You can contact Jungle Grid to request access, correction, or deletion assistance, to ask about how your information is used, or to raise privacy concerns. We may need to verify your identity before acting on a request.
Depending on the request and the context, we may retain certain data that is necessary for security, billing records, fraud prevention, legal obligations, or core service history. Request instructions are described on the Data Requests page.
Changes and contact
We may update this Privacy Policy when the product, billing rails, identity flows, or operational practices change. When we do, we will update the effective date on this page.
For privacy questions or requests, contact legal@junglegrid.dev.
Related pages
Related legal pages
Use the adjacent page when your question is narrower than the policy you started with.