Privacy & Data

How Feedy V4.561 Production uses browser-local data, aggregate visits and operational logs.

1. No account is currently required

Nutrient Lookup, Batch Net Energy, Procurement Value and Formula Cost Trial work without signing in; the independent Formulation Design & Optimization module remains in development. Batch ingredients, prices, cost-trial plans and selected settings are stored locally in IndexedDB/localStorage.

Clearing site data, private browsing or changing devices can make local-only records unavailable. Keep exports of important records.

2. Business data is not currently uploaded

The current production environment does not enable accounts or cloud workspaces. Batch ingredients, calculation parameters and formula plans are not uploaded to Feedy merely by opening the page or running a calculation.

The page sends one request to a same-site aggregate visit counter; that endpoint does not receive formula or ingredient parameters.

3. Local device security

Protect the computer and browser used with Feedy. Shared computers and private-browsing sessions are not suitable for storing important business records.

4. Visit statistics and operational logs

Feedy may call a first-party visit counter for aggregate page views. Servers, reverse proxies and security systems may keep ordinary access logs such as time, request path, IP address and browser identifier for operations and security troubleshooting.

5. What Feedy does not proactively do

• No third-party advertising tracking is configured.
• User batch ingredients, formulas or company parameters are not automatically published as public database records.
• Feedy does not read or upload browser data unrelated to Feedy.

6. Deletion and contact

Local business data can be removed through browser site-data settings or the corresponding management controls in Feedy. For privacy questions, contact the email below.