Back to Home
Juice Tools Privacy Policy

Last updated: July 7, 2026

1. Introduction

Welcome to Juice Tools ("Juice Tools", "we", "our", or "us"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our web application (the "Service").

You can use many features of the Service without creating an account. If you choose to log in with Discord, we store a cloud copy of your gameplay data so you can access it across browsers and devices. You may also choose to make individual profiles public via shareable links.

By accessing or using the Service, you agree to the collection and use of information in accordance with this Privacy Policy. If you log in, you also acknowledge our Terms of Service. If you do not agree, please do not access or use the Service.

Juice Tools is operated by an individual based in California, United States.

2. Information We Collect

2.1 Gameplay and session data you provide

When you use Juice Tools, you may enter or generate information such as:

  • Session data (map runs, waystone configurations, tablet data, map type, party type, outcomes)
  • Currency drops and item information
  • Session notes and other session metadata
  • Profile names and character rarity modifiers
  • League selection, loadout preferences, and related in-app settings

This data is stored locally in your browser (for example, in localStorage) so the Service stays fast and usable. If you log in with Discord, we also store a copy of this gameplay data on our servers to provide cloud sync (see Section 5).

If you export data (for example, to JSON or CSV) and share that file elsewhere, that export is outside the scope of this Policy.

2.2 Account information (Discord login)

If you choose to log in with Discord, we receive information from Discord through our authentication provider, Supabase, such as:

  • Discord username and avatar URL
  • Email address associated with your Discord account
  • A unique account identifier used to associate your cloud data with your login

We store an account record with this information so you can sign in and access your cloud-saved data. You may opt in or out of product-update emails in Settings; we do not send marketing emails unless you enable that preference.

Authentication uses HTTP-only cookies managed by Supabase to keep you signed in. You can sign out at any time from the app.

2.3 Public profile sharing (opt-in)

Profiles are private by default. If you turn on public sharing for a profile in Settings, anyone with the link may view a read-onlyversion of that profile's analytics and session history for cloud-synced sessions.

When a profile is public, viewers may see information such as:

  • Your Discord username and avatar on your account hub page
  • Profile name, league, and summary statistics
  • Session history, drops, waystones, tablets, durations, and related analytics filters
  • Map type, party type, player count, and session outcomes

Session notes are never shown on public pages. Logging in does not make your data public; only the explicit per-profile toggle in Settings enables sharing.

Public pages are intended for link sharing, not a searchable directory. We may record approximate profile page view counts; owners viewing their own public page do not increase the count.

2.4 Automatically collected information

When you visit or use the Service, certain information is collected automatically:

  • Usage data: Information about how you interact with the Service, such as pages visited and actions taken. This is collected via Google Analytics and PostHog.
  • Device information: Browser type, operating system, screen resolution, and similar technical data.
  • Location data (approximate): General geographic location (for example, country or region) derived from your IP address. We do not use this to determine your precise location.
  • Cookies and similar technologies: Including authentication cookies (when logged in), analytics cookies, and advertising cookies. These may be used to keep you signed in, remember preferences, analyze usage, and serve or measure ads.
  • Security and abuse prevention: We may process IP addresses and request metadata to rate-limit public endpoints and protect the Service.

You can control many cookies through your browser settings and, in some cases, through third-party opt-out tools (see Sections 4.3, 4.4, and 4.5).

3. How We Use Your Information

We use the information we collect for purposes such as:

  • Providing, operating, and maintaining the Service
  • Storing and syncing your gameplay data when you use a Discord account
  • Displaying public profile pages when you opt in to sharing
  • Improving and optimizing the application and user experience
  • Analyzing usage patterns to understand how the Service is used
  • Displaying advertisements and personalized ads (via Google AdSense, where applicable)
  • Sending product-update emails if you opt in
  • Providing customer support and responding to inquiries
  • Detecting, preventing, and addressing technical, security, or abuse issues
  • Complying with legal obligations where applicable

We do not sell your gameplay or session data. Ads and analytics rely on cookies and identifiers handled primarily by third-party providers (see Section 4).

4. Third-Party Services

We use third-party services that may collect and process information in connection with your use of the Service. Their handling of data is governed by their own policies.

4.1 Supabase

We use Supabase for user authentication and cloud database storage. When you log in, Supabase processes your authentication session and stores account-linked gameplay data on our behalf. See the Supabase Privacy Policy.

4.2 Discord

Discord provides OAuth login. When you sign in, Discord shares account information with us as described in Section 2.2. See the Discord Privacy Policy.

4.3 Google Analytics

We use Google Analytics to understand how users interact with the Service. Google Analytics collects information such as how often users visit and what pages they visit.

Google's ability to use and share information collected by Google Analytics about your visits is governed by the Google Analytics Terms of Service and the Google Privacy Policy.

You can opt out of Google Analytics using browser add-ons or settings provided by Google or third parties.

4.4 PostHog

We use PostHog to understand product usage (for example, which features are used and how often). PostHog may collect page views, selected in-app actions, and a user identifier when you are signed in. We do not enable PostHog session replay or autocapture of clicks and form inputs.

PostHog's processing of this information is governed by the PostHog Privacy Policy.

4.5 Google AdSense

We use Google AdSense to display advertisements. AdSense uses cookies and similar technologies to:

  • Serve ads based on your prior visits to our site and other sites
  • Measure ad performance
  • Support interest-based (personalized) advertising where enabled

You can manage or opt out of personalized advertising by visiting Google's Ads Settings and other industry opt-out tools where available.

4.6 Market economy APIs

We use third-party Path of Exile 2 economy APIs (primarily poe.ninja, with a secondary fallback provider) to fetch currency exchange rates, listing volume, and item price data. When you use features that require this data, our servers make API calls to those providers.

We do notsend your personal information or session history to these economy providers as part of these requests. Each provider's handling of request data is governed by its own terms and privacy policy.

5. Data Storage and Retention

5.1 Local storage (browser)

The Service stores gameplay data, loadouts, and preferences in your browser (for example, localStorage) for performance and offline-style use on your device.

  • Clearing your browser data for this site may delete local copies of your sessions and loadouts.
  • If you have previously signed in with Discord and then sign out, local data may remain on your device but be hidden from the app until you sign in again.

5.2 Cloud storage (Discord account)

When you log in with Discord, we store profiles, sessions, tablets, and related account preferences on our servers (via Supabase) so you can access them from other browsers or devices and recover data after clearing local storage.

  • Cloud sync is optional; you are not required to create an account to use core tracking features locally.
  • Deleting local browser data does not delete your cloud data while your account remains active.
  • You can upload local changes to your cloud account from Settings.

5.3 Public profiles

Public profile pages read from your cloud-synced data only. If a profile is public but has no synced sessions, the public page may appear empty. Turning public sharing off stops new public access; we do not operate a searchable public directory of players.

5.4 Import and export

You may export session history as JSON or CSV from Session History. JSON can be re-imported; CSV is for viewing or external use and cannot be re-imported.

Importing a JSON file updates your local session history for the imported data. If you are logged in, imported sessions may also be uploaded to your cloud account.

Retention: We retain cloud account data while your account is active. When you delete your account in Settings, we delete your authentication record and associated cloud data within a reasonable period, subject to legal obligations and backup cycles. Local browser copies may remain until you clear site data.

6. Your Rights and Choices

Depending on your location and applicable law, you may have certain rights regarding your information. Regardless of location, the following controls are available today:

  • Access: View your gameplay data in the app. If logged in, your cloud-saved data is associated with your Discord account.
  • Correction: Edit sessions, profiles, and related details in the app.
  • Deletion: Delete individual sessions or profiles in the app. To permanently delete your account and all cloud data associated with it, use Settings → Delete Account. Clearing local browser data removes local copies on your device but does not delete cloud data while your account is active.
  • Export: Download session history as JSON (recommended backup) or CSV from Session History.
  • Public sharing: Enable or disable public sharing per profile in Settings. Profiles are private unless you turn sharing on.
  • Product update emails: Toggle in Settings.
  • Analytics and ads controls: Use browser privacy tools, Google Analytics opt-outs, PostHog blocking via browser extensions or cookie settings, and Google's Ads Settings.

California residents

If you are a California resident, you may have additional rights under the California Consumer Privacy Act (CCPA), including the right to know what personal information we collect, request deletion, and not be discriminated against for exercising these rights. You can delete your account in Settings or contact us at the email in Section 10. We do not sell personal information as defined under the CCPA.

7. Data Security

We implement reasonable technical and organizational measures to help protect information related to the Service, including HTTPS, authenticated API access, and database access controls for account-linked data. However, no method of transmission over the Internet or electronic storage is 100% secure, and we cannot guarantee absolute security.

You also play a role in security by:

  • Using a secure, up-to-date browser
  • Protecting your device and Discord account from unauthorized access
  • Being cautious when installing extensions or software that can access your browser data
  • Understanding that anyone with a public profile link can view the data you have chosen to share

8. Children's Privacy

The Service is not intended for children under the age of 13, and we do not knowingly collect personal information from children under 13.

If you are a parent or guardian and believe that a child under 13 has provided personal information in connection with the Service, please contact us so that we can take appropriate steps to delete such information.

9. Changes to This Privacy Policy

We may update this Privacy Policy from time to time.

When we make changes, we will:

  • Post the updated Privacy Policy on this page, and
  • Update the "Last updated" date at the top of the Policy.

We encourage you to review this Privacy Policy periodically. Your continued use of the Service after an updated Policy has been posted constitutes your acceptance of the changes, except where additional consent is required by law.

10. Contact Us

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