Privacy Policy

Effective August 28, 2026 · Version privacy-2026-08-28

Information we collect

GigLogging stores the work records and settings you create, including events, batches and orders, earnings, stores, times, mileage or odometer information, notes, edits, exports, and preferences. Location may be collected when you request location-assisted store matching or weather and may be saved with a related work entry.

Google sign-in may provide an account identifier, email address, name, and profile image. GigLogging does not receive or store your Google password. GigLogging may also infer and save a coarse city, region, and country from network/request information during sign-up.

If you connect a supported gig account, Argyle or another authorized provider may supply work history such as platform and connection identifiers, batch times, earnings, tips when available, mileage, order counts, stores, pickup or delivery details, and related timestamps. GigLogging does not receive or store passwords entered through the connection provider.

If you purchase GigLogging+, Stripe processes your payment information. GigLogging does not receive your full card number. We may store plan, price, billing cadence, subscription/payment status, Stripe identifiers, cancellation status, accepted checkout disclosure and policy version, timestamp, IP address, and browser/device information.

We may also collect technical and security information such as browser/device type, page URL and title, referrer, app version, error details, IP address, sign-in events, policy acceptance, and feature usage. Public-page analytics honor the browser's Do Not Track setting when available.

AI and weather

When you request an AI Daily Glance, a compact summary of relevant optimizer calculations, historical work patterns, stores, notable historical orders, schedule preferences, and available weather context is sent to OpenAI. GigLogging stores the report, compact input context, model and token-usage information, and generation date so the same report can be reused rather than regenerated.

Weather requests use latitude and longitude needed for a forecast and are sent from your browser to Open-Meteo. Forecasts and related settings may be cached in browser storage.

How information is used and shared

We use information to provide accounts, manual tracking, connected imports, dashboards, calendars, statistics, exports, subscriptions, support, security, backups, weather-informed guidance, AI reports, and Daily and Weekly optimizer features. We may use aggregated, de-identified, or anonymized information for product improvement and generalized analytics.

GigLogging does not sell personal information or individual identifiable work logs. Service providers currently may include Cloudflare for hosting, functions, databases, and security; Google for authentication; Argyle for authorized connected accounts; Stripe for billing; OpenAI for requested AI reports; and Open-Meteo for weather. They process information under their own terms and privacy practices as needed to provide their services.

Your choices, deletion, and retention

You can edit records, use available exports, control browser location permission, and request account deletion through the app. Some features will not work without the relevant permission or connected account.

Deletion removes your sign-in and active profile data. GigLogging may retain billing, consent, security, dispute, backup, and legal/audit records as reasonably necessary. If a deleted account has work history, GigLogging may retain a de-identified or pseudonymized snapshot for aggregate analytics and legitimate business records. Direct account identifiers are removed or hashed, but that snapshot may include dates, stores, earnings, and approximate or precise locations previously saved with entries.

Account and work-history information is generally kept while the account is active or as needed to provide the service. Browser storage is used for sessions, preferences, temporary caches, staging/test state, and interface settings.

Security, children, and changes

No system is perfectly secure, but GigLogging uses reasonable safeguards including account authentication, server-side storage, access controls, and operational logging. GigLogging is intended for adults and is not directed to children under 18. Information may be processed in the United States and other places where our providers operate.

We may update this policy as the product changes. Material updates may require acceptance of a new version before continuing.