Extension Privacy Policy

This Extension Privacy Policy explains what the ClerqLegal EOIR Calendar Sync browser extension (the "Extension") does with information, and what it does not do. ClerqLegal ("ClerqLegal," "we," "us," or "our") publishes the Extension.

How this policy fits with our other policies. The Extension is part of the ClerqLegal Services. Our Privacy Policy and Terms of Service apply to your use of the Extension and to everything that happens to your data once it reaches ClerqLegal. This policy adds the details that are specific to the Extension itself: what it reads in your browser, where it sends it, and what it keeps. If this policy and the Privacy Policy ever conflict about the Extension, this policy controls for the Extension.

The short version. The Extension is a relay. When you click "Import & Sync" on a ClerqLegal page, it reads your hearing schedule from the EOIR portal using the EOIR session you already have open, hands that data to ClerqLegal, and shows you a progress message. It stores nothing, tracks nothing, and talks to no one but EOIR and ClerqLegal.

1. What the Extension does

The Extension has a single purpose: to import the hearing schedule of a signed-in EOIR portal user into that user's ClerqLegal account so the hearings can be written to their calendar. It runs only on clerqlegal.com pages, and only when you, or a ClerqLegal page you have opened, ask it to run a sync or to check whether you are signed in to EOIR. It has no settings, no background activity between syncs, and no user interface beyond a small progress message on the ClerqLegal page and a toolbar popup that links to the EOIR portal.

2. Information the Extension accesses

From the EOIR portal (case-access.eoir.justice.gov), using your own session. During a sync the Extension makes read-only requests to EOIR and relays EOIR's responses to ClerqLegal exactly as received. Those responses contain:

• The EOIR hearings page as EOIR serves it to you. ClerqLegal uses this page to identify which EOIR account is signed in. It includes whatever EOIR shows on that page, which typically includes your name, your email address, and your EOIR identifier.
• Your hearing schedule from EOIR's case API. This includes hearing dates and times, hearing locations and courts, the assigned immigration judge, the hearing type, and the respondent information EOIR attaches to each hearing, such as the respondent's name and alien registration number.
• For hearings whose respondent name is missing from the schedule, the individual case record that EOIR returns for that hearing.

Because the Extension relays EOIR's responses without reading or filtering them, the exact contents are determined by EOIR. If EOIR adds or removes fields, the Extension relays whatever EOIR returns. ClerqLegal extracts only the fields it needs, on its own servers.

From the ClerqLegal page. The page tells the Extension which attorney profile you selected in ClerqLegal, as an internal identifier, so ClerqLegal can confirm the EOIR account belongs to that attorney. On some deployments the page also tells the Extension which part of the site to save to. Requests to ClerqLegal are made by the page itself, so they carry the ClerqLegal session you are already signed in with. The Extension does not read that session.

Nothing else. The Extension does not read any other web page, tab, or window. It does not read your browsing history, bookmarks, downloads, clipboard, keystrokes, or files. It does not run on any site other than clerqlegal.com.

3. Information the Extension does not collect

• Your EOIR username or password. The Extension never asks for, sees, or stores EOIR credentials. Chrome attaches your existing EOIR sign-in cookies to the Extension's requests in the same way it does when you open the portal yourself. The Extension cannot read those cookies.
• Your ClerqLegal password or session. Requests to ClerqLegal are made by the ClerqLegal page, not by the Extension.
• Anything stored on your device. The Extension uses no local storage, no extension storage, no cookies of its own, and no cache. Data exists in memory only for the seconds a sync takes.
• Usage analytics or identifiers. There is no analytics library, no crash reporting, no advertising identifier, and no telemetry of any kind.
• Data from other websites. The Extension requests access to exactly two sites, clerqlegal.com and case-access.eoir.justice.gov, and refuses to contact any other.

4. How the information is used

The Extension uses the information described in Section 2 for one thing: to deliver your EOIR hearing schedule to your ClerqLegal account. Concretely, during a sync it:

• sends the EOIR hearings page to ClerqLegal so ClerqLegal can identify the signed-in EOIR account and confirm it matches the attorney you selected;
• sends your hearing schedule to ClerqLegal so ClerqLegal can store the hearings and write them to the calendar you connected in ClerqLegal;
• sends individual case records to ClerqLegal only for hearings that ClerqLegal reports are still missing a respondent name.

Once the data reaches ClerqLegal it is Firm Data, and ClerqLegal processes it on your firm's behalf as described in the Privacy Policy and the Terms of Service. As the Privacy Policy states, ClerqLegal does not use Firm Data for advertising, does not sell it, and does not use it to train artificial intelligence models shared with other customers except in de-identified form.

5. Where the information goes

The Extension sends data to exactly one destination: the ClerqLegal server that serves the page on which you clicked "Import & Sync" (for example, clerqlegal.com or a ClerqLegal application subdomain). It does not send data to any other party, and it sends nothing to EOIR beyond the read-only requests needed to fetch your schedule.

ClerqLegal in turn shares hearing data only as described in the Privacy Policy, principally with the calendar provider you connected to ClerqLegal (such as Google Calendar) so that your hearings appear on your calendar, and with the infrastructure providers that host the Services.

Chrome Web Store limited use disclosure. The Extension's use of information obtained through Chrome, including information from the EOIR portal, is limited to providing and improving the single purpose described in Section 1. We do not sell that information. We do not transfer it to third parties except to provide that single purpose, to comply with law, or as part of a merger or acquisition in which the recipient is bound by this policy. We do not use it for advertising, for determining creditworthiness, or for any lending purpose. People at ClerqLegal read it only for security purposes, to fix a problem at your request, or as required by law.

6. Storage and retention

In the Extension: nothing. The Extension does not write anything to disk or to browser storage. When a sync finishes, or the page is closed, the data it was relaying is gone from the browser.

At ClerqLegal. Hearings imported through the Extension are stored in your firm's ClerqLegal account as Firm Data, and calendar events created from them are stored by your calendar provider. Retention follows the Privacy Policy: Firm Data stays available while your subscription is active, can be exported for 30 days after it ends, and is deleted after that except for copies we are required by law to keep. You can delete individual hearings inside ClerqLegal at any time.

7. How the Extension protects information

• All connections to EOIR and to ClerqLegal use HTTPS, and the Extension runs only on HTTPS ClerqLegal pages.
• The component that talks to EOIR is a fixed allowlist, not a general-purpose fetcher. It accepts only read-only (GET) requests to case-access.eoir.justice.gov and refuses everything else, so a script on a web page cannot use the Extension to reach any other site with your credentials.
• Every value that could end up in a web address is validated before use, in both the page component and the background component.
• The Extension requests no Chrome permissions beyond access to the two sites named above. It cannot read tabs, history, cookies, or storage.
• All code ships inside the extension package. The Extension loads no remote code and no third-party scripts.
• Diagnostic messages written to the browser console contain step names, status codes, and counts only. They never contain your name, email address, EOIR identifier, or hearing data unless a developer deliberately enables a debug flag in a local copy of the code.

8. Your choices

• Run a sync only when you want one. The Extension acts only when you click "Import & Sync" or open ClerqLegal's dedicated EOIR sync page. Signing out of the EOIR portal prevents any sync from reading your schedule.
• Uninstall at any time from the chrome://extensions page. Uninstalling removes the Extension completely. It does not remove hearings already saved in ClerqLegal or events already written to your calendar; manage those inside ClerqLegal or your calendar.
• Access, correct, or delete your information by using the tools inside ClerqLegal or by contacting us at the address below. The rights described in the Privacy Policy, including the California privacy rights, apply to information handled through the Extension.

9. Children's privacy

The Extension is intended for law firms and their authorized staff, not for children, and we do not knowingly collect information from children through it. Hearing data relayed by the Extension may describe respondents who are minors, as recorded by EOIR; ClerqLegal processes that data only as Firm Data on your firm's instructions.

10. Changes to this policy

We may update this policy when the Extension changes or the law requires. The "Last updated" date above shows when it last changed. Material changes will be announced through the Chrome Web Store listing, the ClerqLegal site, or a message to your firm. Each version of the Extension is governed by the policy in effect when that version was published.

11. Contact us

Questions about this policy or about the Extension can be sent to ghassan@clerqlegal.com or masaf@clerqlegal.com.