TIGER Funding Radar

Privacy Policy

Version 1.0 · Effective September 25, 2026 · Applies to TIGER Funding Radar v2.2.86

This policy describes the privacy model of TIGER Funding Radar and the static download website distributed with version 2.2.86. TIGER is designed primarily as a local desktop application that opens its interface in your web browser.

1. Local application data

TIGER stores its portable application state locally beside the executable in its data directory. TIGER does not require a TIGER account and does not provide a central TIGER cloud account service for storing your application state.

2. Network requests

Some features require an internet connection because they query external funding, scholarly, or public-data sources. Network access may occur when you actively refresh supported sources, update scholarly evidence, update NSF/NIH award data, or enable a background update feature. Those external services receive ordinary network-request information and are governed by their own privacy policies and terms.

3. Research ideas and built-in neural AI

TIGER's built-in Idea Match uses the compact TIGER MiniLM-L6-v2 INT8 neural model locally in the browser inside the desktop application. The model performs local semantic inference and, in built-in mode, the pasted research idea is not sent to an AI provider. The model/runtime may require a one-time download before local use. Users should still avoid entering information they are not authorized to process or store on the device.

4. LSU SPA data

No LSU SPA Excel workbook is included in the public TIGER distribution. If you are authorized to use SPA data, you import the workbook manually. You are responsible for safeguarding institutional data, following applicable LSU policies, and avoiding unauthorized redistribution of the workbook or derived confidential information.

5. API keys and credentials

If you configure credentials for a supported external source, treat the local TIGER data directory as sensitive. Do not publish or share local configuration files that contain credentials.

6. Website privacy

The live TIGER website is a static Cloudflare Pages site and does not require a TIGER user account. It is configured to use GoatCounter under the site code tigerfunding for aggregate page-visit statistics and explicitly tagged download-button events. GoatCounter receives the tracked path or event plus ordinary network-request information under GoatCounter's own service terms; TIGER does not use advertising pixels or behavioral advertising trackers. The homepage can display the aggregate homepage-visit count when public counters are enabled. The About section also loads the creator's public faculty photo from LSU.edu when online, which creates an ordinary image request to LSU. Cloudflare Pages may maintain routine hosting or operational logs under its own policies.

7. Data you download

Download packages, the user manual, and the demonstration video are static files. TIGER does not receive a notification merely because you open a locally packaged copy of this website. If optional download metrics are enabled by the site operator, clicks on the download buttons can be counted as aggregate events. A hosting provider may also record file requests in its server logs.

8. Security and responsibility

TIGER is a research and decision-support tool, not a security boundary. You are responsible for maintaining operating-system security, controlling access to local data, validating imported files, protecting credentials, and complying with applicable policies and laws.

9. Changes

This policy may be updated in later TIGER releases. The policy packaged with a release applies to that distributed version unless an updated policy is expressly provided.

10. Questions

Questions about privacy or permitted use should be directed to the software creator through the channel from which you obtained TIGER.

Plain-language notice: This policy is intended to accurately describe TIGER’s current local-first design. Organizations with formal legal, privacy, or records-management requirements should perform their own review before deployment.