Privacy Policy

Effective: August 10, 2026  ·  Last updated: August 10, 2026

 

Applies to juggertech.com, the juggerECO browser extension, and the juggerAUTH app.

jugger Technologies, LLC ("juggerTECH," "we," "us") builds software that IT service providers use to manage their clients — including the juggerECO platform, the juggerECO for Chrome extension, and the juggerAUTH authentication app.

​

This policy explains what information those products handle, why, and where it goes.

​

1. Who this policy covers

​

juggerTECH sells software to managed service providers (MSPs) and IT departments ("organizations"), who use our products to manage their own users, clients, and devices. That creates two different relationships, and this policy addresses both:

 

• When you visit juggertech.com or contact our team, juggerTECH is responsible for the limited information you provide (Section 2).

• When you use the juggerECO extension or the juggerAUTH app, an organization gave you access. That organization runs its own juggerECO workspace and decides what data is stored in it — it is the controller of that data, and juggerTECH is its software provider. The extension and app send information only to the juggerECO services your organization configures, not to juggerTECH as a separate destination (Sections 3–4).

 

Deployment matters. A juggerECO workspace is either self-hosted by your organization on its own infrastructure, or hosted by juggerTECH as a managed juggerECO SaaS service on your organization's behalf. Either way the data belongs to your organization. If your organization self-hosts, juggerTECH never receives extension or app data at all. If it uses juggerECO SaaS, we process that data solely to run the service under our agreement with the organization — never for our own purposes.

 

2. The juggerTECH website

​

When you browse juggertech.com or contact us, we collect only what we need to respond and keep the site working.

 

• Information you give us. If you submit a contact or demo-request form, we collect the details you provide — typically your name, email, phone, company, and message — and use them to reply, schedule demos, and follow up about our products.

• ​

• Information collected automatically. We log standard technical data (IP address, browser and device type, referring pages, pages visited) and use cookies and similar technologies to keep the site working and to understand aggregate traffic. We use Google Analytics for traffic measurement under Google's terms. You can block cookies in your browser or opt out of Google Analytics with Google's browser add-on.

• ​

• How we use it. To respond to enquiries and provide requested information/demos; to operate, secure, and improve the site; to send product information you've requested (unsubscribe anytime); and to detect and address technical or security issues.

 

3. juggerECO for Chrome (browser extension)

​

The juggerECO extension is a workspace tool for technicians. Its single purpose is to let an authorized user securely reach their organization's juggerECO workspace from the browser — shared password vaults, knowledge base, tickets, and device information — and to help capture credentials, passkeys, and screenshots into that workspace.

 

Signing in. You sign in with your organization's juggerECO identity provider (an OAuth 2.0 / OpenID Connect flow to your organization's Keycloak). The extension stores the resulting access and refresh tokens locally in the browser's extension storage (chrome.storage.local) so you stay signed in, and refreshes them automatically. Your organization can set how often re-login is required. The extension never stores your password, and juggerTECH never receives your sign-in credentials.

​

What the extension handles — and where it goes. Everything below is transmitted only to the juggerECO endpoints your organization configures, over HTTPS, from the extension's background service worker. None of it is sent to juggerTECH as a separate party, used for advertising, or sold.

 

• Login credentials — only when you choose to save one (manually, or via the "Save this login?" prompt). Stored in your organization's juggerVAULT, encrypted at rest.

• Login-form detection — on pages where you submit a username and password, so the extension can offer to save a new login. Detection happens locally in the page; nothing leaves your browser unless you click Save. You can dismiss a site permanently.

• Passkey metadata — when you register or use a passkey and choose to record it, to keep an inventory of where passkeys exist (relying party, account, credential ID, public key). Stored in juggerVAULT. The passkey private key is never accessed or transmitted.

• Screenshots — only when you trigger a capture of the visible tab, to attach to a knowledge-base article or ticket note. Stored in your organization's juggerDOCS or juggerPSA.

• Workspace content you view — vault entries, articles, tickets, and read-only device details are read from your organization's services to display them; they aren't copied out.

• Sign-in tokens and settings — kept locally in chrome.storage.local on your device to keep you signed in and remember which endpoints to use.

​

Permissions the extension requests, and why.

 

• Access to websites you visit (host access for http/https): required so the extension can autofill a saved login into a page's form on your command, and so the "Save this login?" prompt can detect a submission on the site you're on. The extension does not read, collect, or transmit page content for any other purpose, and does not track your browsing.

• Active tab / scripting: to capture a screenshot of the visible tab when you ask, and to fill login fields on the current page.

• Extension storage: to hold your session tokens and preferences on your device.

• Access to your configured juggerECO hosts: to call your organization's identity, vault, knowledge-base, ticketing, and device services.

​

Chrome Web Store — Limited Use. juggerTECH's handling of information received through the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data the extension accesses is used only to provide and improve the user-facing features described above, is transmitted only to your organization's juggerECO services, and is never sold, used for advertising or profiling, or transferred to third parties except as needed to operate those features or where required by law.

 

4. juggerAUTH app (web app and future mobile app)

​

juggerAUTH is an authentication companion for people whose identities are managed in juggerECO. It runs today as an installable web app (PWA); a native mobile app is planned, and this section covers both. Its purpose is identity verification and multi-factor authentication — approving help-desk requests and sign-ins — plus an aut and a personal vault.

 

Enrolling a device. When your administrator enrolls you, the app receives a device credential (a devic to your identity, which it uses to authenticate to your organization's juggerECO service. juggerTECHdoes not receive this credential.

What the app handles — and where it goes.

 

• Verification & MFA requests — to show you Approve/Deny requests (e.g. before a password reset or sign-in) and record your response. Stored in your organization's juggerECO service.

• Push notification token — to deliver approval requests promptly (if you decline notifications, the ald by your organization's juggerECO service and the platform push service (Apple/Google/browser).

• Your own authenticator codes (TOTP) — to generate rotating one-time codes for services you add yourself. Stored on your device only; these secrets are never sent to juggerECO or juggerTECH.

• Personal vault items — logins, cards, notes, and keys you save. Stored in your organization's juggert and scoped to your identity.

• Camera image (QR scan) — only if you scan a QR code to add an authenticator account; processed on your device to read the code, and not uploaded.

• Permissions the app requests, and why.

• Notifications: to alert you to verification and sign-in requests. Optional — the app works without them.

• Camera: only when you choose to scan a QR code to add an authenticator account. Nothing is recorded

• Device biometrics / screen lock (native app): if enabled, used locally to protect access to the app. juggerTECH never receives your biometric data.

​

When we publish the native mobile app, its app-store listing will carry data-safety details consistent with this section.

​

5. Sharing, and what we never do

​

We never sell your data. No advertising or profiling. No data brokering. Vault secrets are encrypted at rest.

​

We do not sell personal information and do not share it for cross-context behavioral advertising. We disclose information only in these limited cases:

• Your organization. Data you create in the extension or app lives in your organization's juggerECO workspace and is available to its authorized administrators under its own policies.

• Service providers. Vendors that help us operate — for example website analytics, and (where your org) our hosting and infrastructure providers — may process data on our behalf under contracts limitingthem to that purpose.

• Legal and safety. When required by law, or to protect the rights, safety, and security of our users,

• Business transfers. In connection with a merger, acquisition, or sale of assets, subject to this policy.

​

6. Storage and security

​

We take reasonable technical and organizational measures to protect information. Sensitive workspace data — vault credentials, notes, and personal-vault items — is encrypted at rest with AES-256-GCM using per-tenant keys, and traffic
between the extension or app and juggerECO services travels over TLS. Sign-in uses standard OAuth 2.0 rd is never handled by the extension or stored by juggerTECH, and passkey private keys are neveraccessed. Access to workspace data is governed by your organization's roles and permissions. No method of transmission or storage is ever completely secure, so we cannot guarantee absolute security — but we work continuously to protect
your information and address vulnerabilities.

​

7. How long we keep information

​

• Website: we keep enquiry and analytics data only as long as needed for the purposes above, then dele

• Extension & app: data you create lives in your organization's juggerECO workspace and is retained according to your organization's settings and retention policies. Locally held items — session tokens, on-device authenticator secrets,

• and per-site preferences — remain on your device until you sign out, remove them, or uninstall.

​

8. Your privacy rights

​

Depending on where you live, you may have rights to access, correct, delete, or port your personal infrestrict certain processing.

• For website information (enquiries, analytics), contact us using Section 11 and we'll respond as the

• For data in a juggerECO workspace (extension and app), your organization controls that data — direct access or deletion requests to your organization's administrator; where juggerTECH hosts the workspace, we assist that organization in fulfilling your request.

​

We will not discriminate against you for exercising your rights.

​

9. Children

 

Our products are business tools intended for use by adults in a workplace. They are not directed to chly collect personal information from anyone under 18. If you believe a child has provided usinformation, contact us and we will delete it.

​

10. Changes to this policy

​

We may update this policy as our products or the law evolve. When we do, we'll revise the "Last updated" date above and, for material changes, provide a more prominent notice. Your continued use of our products after an update means
you accept the revised policy.

​

11. Contact us

​

jugger Technologies, LLC
Email: info@juggertech.com
Phone: 855-734-5662
Web: http://www.juggertech.com