Your logistics data stays under your control.

LogicCalc uses an essential authentication cookie to keep signed-in users securely logged in. Browser storage is also used for language preferences, the current unsaved workspace, temporary calculation results and interface settings. LogicCalc does not use advertising cookies or cross-site tracking pixels.

When you create an account, LogicCalc stores the account email, authentication and security data required by ASP.NET Core Identity. Routes that you explicitly save are stored on the LogicCalc server in your private Archive and are linked to your account.

Addresses, cargo details, rates, costs, margins, client prices and company information are processed to create your calculation. The current unsaved workspace may remain in browser storage. It is added to the server Archive only when you explicitly save a route.

When you search for an address or calculate a route, the required search text, coordinates and routing options may be sent to the configured geocoding, map or routing service. Only the data needed to return suggestions, coordinates or route geometry is sent.

AI Autofill runs only after you actively submit order text or attach a supported file. The source content is sent through the LogicCalc server to the paid Gemini API to extract structured loading, delivery, cargo and weight fields.

Under the paid Gemini API terms, submitted prompts, files and responses are not used to improve Google's products. Limited provider logging or retention may still apply for service security, abuse prevention, technical operation and legal obligations.

LogicCalcPro uses first-party product telemetry to understand how the interface is used and where users encounter friction. Detailed interaction telemetry uses a random page-session key that exists only in memory and is not linked to an account. Separate aggregate and advertising analytics may use a temporary sessionStorage key and a fixed campaign bucket; signed-in aggregate events may be associated with the account for personal activity analytics. No persistent cross-session browser identifier is used.

Detailed telemetry records event names, timing and only a limited error category such as validation, geocoding, routing, network, timeout or unknown. It does not record entered route addresses, coordinates, free text, cargo, customer or company names, prices, rates, costs, margins, AI prompts or files, exact user-agent strings, browser fingerprints or cross-site activity.

Passwords are handled through ASP.NET Core Identity and are not stored as readable text. Access to account routes and settings requires authentication. Users should protect access to their device, browser and email account and avoid entering unnecessary sensitive information.

Clearing LogicCalc site data in the browser removes the locally stored workspace, temporary results and local preferences from that browser. Saved routes must be deleted separately from the Archive. Requests concerning account data can be sent to the contact address below.

Raw detailed Product Telemetry events are automatically deleted after 30 days. Aggregate usage counters may be retained longer. Account information, Workspace data and saved routes are retained while required to provide the service or until deleted through available controls, subject to security and legal obligations.

LogicCalc does not sell route, rate, cargo, client-price or company data and does not use that information to build advertising audiences or shared market-rate benchmarks.