TraqsIQ DG Logo
TraqsIQ DG FIELD COMPLIANCE DESK
Capabilities Support
Sign In Get Started
TraqsIQ platform

Privacy Policy

Content version 1.0 · Effective date: 7 September 2026 · Canonical URL: https://traqsiq.com.au/privacy

Final Version 1.0 — approved 1 September 2026 · effective/publication date: 7 September 2026. TraqsIQ and TraqsIQ DG are operated by Makin Traqs. Approved for and on behalf of Makin Traqs, trading as TraqsIQ, by Jacqueline Feher, Director, on 1 September 2026. External legal review is not claimed.

Scope. This policy describes the current TraqsIQ and TraqsIQ DG build. It is not a statement about features or data practices that have not been shipped.

What TraqsIQ handles

TraqsIQ may handle information needed to provide the platform and its products, including account identity, product access state, information you enter into a workflow, and technical information needed to operate a request. TraqsIQ DG can work with reference data and temporary drafts on the device.

Purposes of collection and use

TraqsIQ uses information to provide account access, authenticate users, apply product and entitlement state, operate dangerous-goods workflows, process user-requested connote or SDS extraction, return extracted information for review, maintain device-local onboarding and draft state, respond to support or privacy requests, and operate and troubleshoot the service using request diagnostics.

TraqsIQ DG-specific data flows

Account and authentication

When you create or use an account, Clerk provides identity and authentication services. The app uses the authenticated account to provide account features and to associate access where needed. The app's account deletion action calls the account provider's deletion capability.

Subscriptions and store transactions

When subscriptions are activated for a release, RevenueCat is used for entitlement handling and Apple or Google process the relevant store transaction. Store and provider billing records are controlled by those providers and may be retained under their own terms or legal obligations. The app does not claim that signing out or deleting a TraqsIQ account deletes provider billing records.

Device-local data

TraqsIQ DG uses local device storage for app state such as onboarding state, entitlement/reviewer cache where applicable, temporary load drafts and connote sessions. Confirmed account deletion clears the temporary load draft, connote sessions, applicable entitlement/reviewer cache and app server cache before the account is signed out. This does not claim to erase provider-controlled records.

Camera, photos and documents

The app may request camera or photo-library access for dangerous-goods label or SDS capture. It may also allow an SDS PDF to be selected. A connote or SDS may include customer, consignor, consignee, address, contact and commercially sensitive freight information. Only select and upload documents you are authorised to handle.

Server-side assisted extraction

Images and PDFs used for connote or SDS extraction are sent to the TraqsIQ server for processing and may be processed through Replit AI Integrations using OpenAI models and Replit-managed provider credentials. Replit lists OpenAI in the USA as an AI-model subprocessor, so submitted extraction content may be processed outside Australia. TraqsIQ does not claim Zero Data Retention, regional residency, Modified Abuse Monitoring, opt-in sharing status or another account-level OpenAI control unless written evidence becomes available.

SDS quarantine and review

An extracted SDS record is quarantined for qualified review. Uploading a document does not create an EIP or an authoritative result. A possible catalogue match requires explicit confirmation and does not silently assign identity.

Diagnostics and logs

The server records metadata-only operational request diagnostics needed to run and troubleshoot the service. Request bodies and authentication or cookie headers are excluded, and extraction routes do not write raw connote contents, image data, model output or filenames to application logs. These diagnostics are emitted to Replit production deployment logs, which Replit documents as retained for 30 days. This page does not claim that TraqsIQ uses advertising analytics or a crash-reporting service.

Third-party and service-provider disclosures

Clerk provides account identity and authentication. RevenueCat handles subscription entitlement processing when configured. Apple or Google process the relevant store transaction. Replit AI Integrations (OpenAI, Replit managed) may process images or extracted PDF text when a user requests extraction. Replit manages the provider credentials and lists OpenAI in the USA as an AI-model subprocessor. These providers may have their own terms, privacy notices, retention rules and deletion boundaries.

Likely overseas processing

The server and configured service providers may process information outside Australia. Replit's current subprocessor register lists OpenAI in the USA for AI models. OpenAI publishes an API subprocessor list covering providers in multiple countries, but this project cannot determine which downstream location handles a particular Replit-managed request. Processing is not represented as confined to Australia or the USA.

Access and correction requests

Email traqsIQDG@makintraqs.com to request access to or correction of personal information held in connection with TraqsIQ DG. Provide enough information to identify the relevant account or request, but do not send a password, secret or raw connote or SDS content. The request will be assessed against the information and service records available to the operator.

Privacy complaints

Email traqsIQDG@makintraqs.com to make a privacy complaint without attaching raw connote or SDS contents. The operator will acknowledge the complaint within 5 business days and provide a response or progress update within 30 calendar days. If the complaint remains unresolved, you may contact the Office of the Australian Information Commissioner (OAIC).

Retention and deletion boundaries

Account-owned structured SDS records are deleted from the active TraqsIQ application database when the verified in-app deletion request completes, and in any event within 30 days unless legally required for longer. Temporary local drafts and connote sessions are cleared as part of confirmed account deletion. Residual provider-managed backups may remain until removed through Replit's backup lifecycle, legal requirements or operational retention processes. TraqsIQ cannot directly erase an individual record from an immutable provider backup. If backup data is restored, it remains subject to the deletion record and must be deleted again where applicable. API diagnostic metadata is retained for 30 days under Replit's documented deployment-log period, and support and privacy correspondence is retained for 2 years. Apple, Google and RevenueCat records remain subject to provider-controlled retention and are not represented as deleted by this action. See account-deletion information for the candidate scope.

Reference-only limitations

TraqsIQ DG reference data, extraction output and decision-support drafts are not automatically authoritative. Provenance, identity and review status are shown where available. Ambiguous or unsupported situations remain subject to manual review and fail-closed behaviour.

Changes and contact

If approved, updates may be published at this canonical URL with a new content version or the actual live-publication date. For the current support path, see Support. Controlled inbound delivery and outbound sending have been verified for the listed mailbox.

© 2026 TraqsIQ · Content version 1.0 · Effective date: 7 September 2026
DG Privacy Terms Support Delete account