Transparency
Operational disclosures for the services behind Jungle Grid
This page summarizes the external services, public embeds, and operational integrations presently visible in or referenced by the Jungle Grid website and browser product surfaces.
This page covers external services referenced in the current frontend and public docs.
Identity, analytics, billing rails, email delivery, public embeds, and user-directed callbacks.
Reflects the current shipped repo state rather than future roadmap assumptions.
Policy details
Identity and authentication disclosures
Jungle Grid currently supports Google-based sign-in or account-linking flows and browser-based email/password authentication with email OTP verification. These identity flows may involve Google and backend identity services that support account creation, account linking, and device/browser confirmation flows.
If you choose to use Google authentication or account linking, relevant account and identity information may be processed as part of that flow.
Analytics and measurement disclosures
The public site currently records page-view activity through PostHog to help Jungle Grid measure website and product usage, navigation patterns, and onboarding performance.
Analytics may capture page URLs, event timing, and related usage context needed to understand product engagement and diagnose issues.
Billing and payment disclosures
Jungle Grid’s current billing surfaces include Paystack-backed wallet topup flows in USD, balance and history views, and related billing verification behavior reflected in the portal and docs.
Provider payout profile and payout-related surfaces are also present in the product, although the public docs and UI state indicate that some payout operations may be temporarily unavailable while the platform standardizes on USD.
Email and operational messaging disclosures
The public docs state that transactional emails in the account lifecycle are sent through ZeptoMail. This includes flows such as signup verification and related account communications.
Jungle Grid may also send operational, billing, security, or service-related messages needed to administer accounts and product usage.
Browser storage and workflow continuity disclosures
The frontend uses local storage and session storage for themes, signed-in sessions, onboarding continuity, guest inference resume state, and selected UI memory. These are described in more detail on the Cookies and Local Storage page.
Jungle Grid may also store promotional tokens or temporary flow state in the browser to complete signup or landing-page experiences.
User-directed outbound destinations
Some Jungle Grid features let users configure external callback or webhook destinations. Those outbound requests are sent to the user-selected endpoint and may include status or correlation information based on the configured integration.
Users remain responsible for the destinations they configure and for the data practices of those external services or endpoints.
Public embeds, badges, and outbound links
The public site currently includes links or badge embeds from third-party directories and launch platforms in the footer and marketing surfaces. Examples visible in the current frontend include Fazier, ScrollLaunch, Better Launch, FoundrList, Findly.tools, Turbo0, Wired Business, Startup Fame, FrogDR, Twelve Tools, and X.
When you interact with those links or embedded assets, the third-party service may receive technical request information such as your browser request, IP address, referrer, or other standard web metadata according to that third party’s own practices.
Changes and contact
We may update these disclosures when Jungle Grid changes vendors, analytics tools, billing rails, public embeds, or product integrations.
For questions about these disclosures, contact legal@junglegrid.dev.
Related pages
Related legal pages
Use the adjacent page when your question is narrower than the policy you started with.