Privacy policy (draft)

1. Scope and operator

AixNew LLC operates aixtrack. This draft describes data flows in the current code. It does not mean the service is live, third parties are enabled, or compliance certification is complete. Specific legal roles, processing grounds, applicable regions and agreements must be determined after legal review.

2. Accounts and sessions

Registration stores email, password hash, verification status, account identifier and timestamps. Passwords are not stored in plain text. Verification and password recovery tokens are stored only as digests with expiry dates; emails contain one-time links. Login uses an HttpOnly session cookie. Signing out or resetting a password can revoke old sessions. The frontend also stores language or theme preferences.

3. Shipments and tracking data

Tracking numbers, carriers and optional destination countries supplied by signed-in users are linked to their accounts. The system may store statuses, times, locations, descriptions and source events returned by authorized carriers, and raw incoming tracking webhooks, for queries, synchronization, anomaly checks and evidence exports. PDFs are snapshots of stored records and are managed by the downloader after download.

When the tracking data source is enabled, tracking numbers and carrier information are sent to authorized carrier services for tracking queries. Account email and payment information are not proactively sent for tracking queries. Its contractual role, DPA, subprocessors and cross-border transfer arrangements must be confirmed before launch.

4. Anonymous queries, IP addresses and logs

Anonymous queries are disabled by default. When enabled, IP addresses are converted into keyed HMAC digests and stored for rate limits and shared quotas. These digests remain linkable pseudonymous identifiers and must not be treated as irreversible anonymization. The service may encounter raw IP addresses when receiving requests; authentication rate limiting also briefly uses IP addresses in process memory. Proxy, host and error logs may separately contain IP addresses and request context. Actual log settings must be reviewed before launch.

Anonymous tracking numbers are used only to read upstream tracking history. They are not written to account shipment tables or analytics events and do not appear in query page URLs. Public responses do not display detailed addresses or free-text scan descriptions. Upstream providers and infrastructure may still process queries under their own arrangements.

5. Subscriptions, email and analytics

Web SaaS subscriptions support Stripe TEST and LIVE modes; development defaults to TEST. When subscriptions are enabled, email, internal user identifier, selected price and callback URLs will be sent to Stripe. Customer/subscription IDs, status, plan, validity period and necessary event IDs are stored; this site does not store payment card numbers. Stripe may have an independent legal role in some circumstances; see the Stripe privacy policy. This draft does not mean real payments are available.

When Resend is configured, recipient email addresses and verification/reset email content are passed to Resend for processing. A configured SMTP fallback may be used on failure. Development mode writes emails and links to local application logs, so logs also require confidentiality. See the Resend privacy policy; the operator must confirm the SMTP provider and its terms.

The database records basic analytics events such as registrations, tracking queries and paid-plan upgrades, including time, internal user ID or anonymous IP digest, restricted source markers and necessary plan status. Events do not record email addresses, raw IP addresses, tracking numbers or payment card data. Daily exports contain only dates and aggregate metrics. Current MRR is a simulated monthly amount from test-mode subscriptions, not actual revenue. No third-party advertising analytics scripts have been installed for this feature.

DHL data retention (draft)

DHL (including DHL Paket) tracking data is deleted from the live database 30 days after delivery. Database backups are retained for at most 30 days, so the maximum retention of this data is approximately 60 days after delivery. Files exported by users (such as dispute evidence PDFs and CSVs) are outside our control after download.

6. Retention, security and individual requests

Except for the DHL data and database backup rules described below, the current code has no complete retention policy for automatically clearing accounts, other tracking histories, rate-limit history or analytics events, and no complete self-service deletion/data rights process. Fixed deletion deadlines or “zero logs” cannot yet be promised for other data. Before launch, the operator must determine necessary retention periods, backup cycles, access permissions, request handling procedures and cross-border arrangements. Security measures cannot guarantee absolute freedom from risk.

Access, correction, deletion and other applicable rights and exceptions must be handled under the reviewed policy. No public privacy contact address is currently provided. Before launch, AixNew LLC must publish a valid contact channel, necessary company information and applicable processing grounds, then publish a final version. This draft must not be presented as an effective privacy commitment.