Privacy policy

1. Scope and operator details

SwiftShip is the trading name shown by this service. It provides software for shipper-entered shipment records and is not represented as a carrier, customs broker, warehouse, or bank. The operator has not supplied a registered entity number or public street address, so this site does not invent one. Privacy and business enquiries can be sent to swiftshipdeliverys@gmail.com.

2. Data collected

• Account data: name, email, optional company, password hash, role, consent timestamps, and account creation time.
• Shipment data entered by shippers: recipient name, optional contact details, route, shipper-reported location, package description, status, notes, charge, and timeline.
• Manual-payment data: payer name, sender bank, transfer reference, date, note, approval status, and the shipment credit it funds. Never enter card numbers, PINs, passwords, or one-time codes.
• Security data: necessary session cookie, rate-limit records held in memory, and ordinary server request information such as IP address.
• Email preferences: a one-way hash used to remember an unsubscribe choice.

SwiftShip does not use advertising cookies, analytics SDKs, remote fonts, or browser fingerprinting.

3. Why data is used

• To provide accounts, dashboards, worldwide delivery records, and tracking-code access.
• To approve manual payments and apply one approved credit to one shipment.
• To protect accounts, prevent replay and abuse, and investigate incidents where the operator has a legitimate security interest.
• To send requested records and operational administrator alerts.
• To comply with valid legal obligations.

The operator determines how account, security, payment, and service-administration data is handled. Account holders separately decide what recipient and shipment data they upload and must have authority and a lawful basis to do so. Do not place sensitive medical, financial, child, identity-document, or authentication data in free-text fields.

4. Who receives data

• Authorized administrators can access users, payment requests, and shipments for support, security, and payment approval.
• Resend or the configured SMTP provider processes recipient addresses and email content when an email is sent.
• OpenStreetMap tile services receive requested tile coordinates through the server. Production place search uses a local city list unless the operator explicitly configures a contracted geocoding provider; do not submit confidential addresses to map search.
• Anyone with a valid tracking code can see the route, status, shipper-reported location and timeline, and can open a shipment record containing recipient name, package description, weight, shipper-entered charge, and payment status.

SwiftShip includes no advertising integration or data-sale feature.

5. Retention, transfers, and deletion

Account and shipment data remains in the active database until the account holder deletes a shipment or closes the account. Payment records remain while the account is active; deletion is blocked until unused approved credits are refunded. A non-reversible payment-reference hash may remain to prevent replay. Email suppression hashes remain after unsubscribe unless support verifies and restores the address.

Rate-limit records remain in memory only until their window expires or the server restarts. Application errors are written to the server console; the hosting operator controls any external log retention. No automated backup-retention schedule has been configured, so the operator must protect and delete manual backups. Delivered emails, downloaded files, bank records, and copies held by recipients cannot be recalled.

Resend, SMTP, or a configured map provider may process data in another country under its own terms and safeguards. The operator must assess and document the transfer mechanism appropriate to the people served.

Authenticated users can export or delete their active account data from Account and data. Exports contain recipient and delivery information and must be protected. Requests from recipients or people unable to sign in can be sent to the privacy contact.

6. Security

Passwords are salted and hashed with versioned scrypt. Sessions use signed, HTTP-only cookies. Access checks, rate limits, restrictive browser headers, input limits, and long random tracking codes are used. No service can guarantee absolute security; report suspected misuse promptly.

7. Your choices and rights

Depending on applicable law, you may request access, correction, export, deletion, restriction, or objection. You may also complain to your local data-protection authority. Email preference links are included in SwiftShip emails. Transactional messages requested by a shipper are separate from marketing; SwiftShip currently sends no marketing email.

8. Children

Accounts are for adults aged 18 or older acting for themselves or an organization. SwiftShip does not knowingly create accounts for children and does not ask for dates of birth. Do not add unnecessary information about children to shipment descriptions or notes. A parent or guardian may request deletion through the privacy contact.

9. Contact and updates

Contact swiftshipdeliverys@gmail.com for privacy requests. Material changes will be dated on this page. The current policy version is 2026-11-08.