Privacy policy

Effective October 8, 2026. This policy covers the Knotty Logistics Android app, Web and Dispatch services.

Information we process and why

Accounts and companies. We process account identifiers, contact details, company membership, roles and profile information to authenticate users and control access. If you choose Google sign-in on Android, Google processes the selected sign-in and Knotty verifies the Google identity token for an existing Knotty account.

Business activity. We process assignments, vehicle and pre-trip information, job progress, pickup and drop details, tickets, submitted photos and documents, signatures, and billing/bookkeeping records so participating companies can perform and record their work.

Financial records. Android processes work rates, amounts owed and user-entered Paid/Received bookkeeping. It does not provide a payment checkout or ask for payment-card or bank-account credentials.

Location during Driver work. Before Android requests location permission, Knotty presents an in-app disclosure for you to acknowledge. Precise GPS location supports active Driver work, dispatch visibility and Job progress; authorized dispatch and Job participants can see truck position. Tracking starts after Pre-Trip. It may continue while the screen is off or the app is not visible, and a foreground-service notification remains visible while tracking is running. Tracking stops at valid ticket Sign-Off or Post-Trip on a no-ticket day. Knotty does not request Android's “Allow all the time” background-location permission. While you use the app, location also supports maps and local weather.

Notifications and operations. We process device notification tokens to deliver push notifications. We use operational and security records to protect accounts, diagnose failures and restore service.

Contacts and invitations. With your permission, Find Friends reads device contacts and matches phone numbers on your device against the Knotty directory. If you choose to invite someone, Knotty processes the selected account identifier or the name, email address or phone number you enter to prepare the invitation.

Local weather. While you use Knotty, location also supports local weather. Android, Web and Dispatch send your current or selected coordinates to the Knotty backend. Before requesting weather, the backend rounds the coordinates to a 0.05-degree area (about 5.6 km north/south; east/west size varies by latitude). Knotty sends that area query and forecast options to WeatherAPI.com over HTTPS. WeatherAPI.com also receives the Knotty server's network address and ordinary connection metadata. Knotty does not include your name, email, account identifier, company, Job, ticket, device identifier or raw tracking history in that weather request. Weather results are shared in an area-based cache for 15 minutes; during an outage a cached result may be used for up to 30 minutes. This weather processing is separate from the precise location used for active Driver work.

Access and service providers

Authorized company users and job participants can access relevant information according to their roles and job relationships. AWS hosts the application, database, files and backups. Google/Firebase provide selected sign-in, maps and push-notification services. WeatherAPI.com provides local conditions and forecasts through the Knotty backend. These providers process information needed to supply those functions.

Maps requests and SDK diagnostics

Google Maps receives map, address-search and route requests. Its Android SDK also collects device and SDK metadata, IP addresses, a Maps-specific pseudonymous identifier, crash metrics and map-interaction information, such as panning and zooming. Google uses this information to operate, maintain and improve its services. These SDK records are separate from Knotty's stored Driver GPS history. Firebase Cloud Messaging processes installation identifiers, push tokens, device/app metadata and notification content to deliver notifications.

Earlier Android releases still distributed through Google Play

The current P001 Android version 1.0.50 uses WeatherAPI.com through Knotty's backend as described above. Earlier versions 1.0 (version code 5) and 1.0.49 (version code 49) include direct weather requests to Open-Meteo that send location coordinates and expose the device's network address to that provider. Their weather display also contains OpenWeather icon requests. Those versions also use legacy document hosting operated by HOI; version code 5 additionally contains a Supabase-hosted update check that transmits application/platform/version and ordinary network metadata. These legacy services are not current P001 v50 integrations.

Protecting information in transit

We use encrypted connections (HTTPS/TLS) to protect data in transit between current Knotty apps and services, between our service components and database, and to current service providers. This is encryption in transit, not end-to-end encryption. We recommend using the latest app version.

Your controls

You can edit available profile settings, control device permissions, stop driver tracking using the app's controls, sign out, and request account deletion. Removing a permission may prevent a feature that depends on it. You can request account deletion both in the app and through the account-deletion page.

Retention and deletion

We aim to fulfill a valid account-deletion request within 30 days. We delete or anonymize personal profile and account data that is not required for legitimate business, security, legal, regulatory or financial-record purposes. Disabling access is the first step and is not confirmation that deletion has been completed.

Records affected by a legal hold, dispute, claim or investigation are retained until the matter is fully resolved, even if that exceeds the normal period. Where technically practical, retained historical records are de-linked or anonymized from the deleted account while preserving company transaction history, ticket and signature integrity, billing and accounting integrity, and audit integrity. Historical records do not justify retaining active authentication tokens, credentials or unnecessary profile data.

Backups are restricted to recovery use. Deletion and retention decisions must be reapplied if a backup is restored. We confirm fulfillment only after the deletion/anonymization work has been completed; we identify any records retained under the policy.

For privacy questions or account-deletion requests, contact office@knottylogistics.com.