Orderafy privacy policy

The data controller is AZIMUTHA LLC, with registered address at 7623 Canterchase Ct APT 1C, Fort Wayne, IN 46804, Estados Unidos. Orderafy (the “Platform”) is a B2B vehicle-transfer management platform serving transport companies (“Clients” or “tenants”).

Personal data processed for operations in Mexico is handled under the Mexican Federal Law on the Protection of Personal Data Held by Private Parties (LFPDPPP) and its Regulations.

Data is hosted and processed on servers located in the United States (Microsoft Azure), so it may be transferred to and processed outside Mexico; processing is carried out with the security measures described in section 13.

The “Orderafy Driver” mobile app is used by our Clients' operators (drivers). Regarding them, the Platform collects and processes:

• Identification and contact data: full name, email and phone (users table). Purpose: account creation, authentication and operational contact.
• Driver's license and validity: license number and expiry date (drivers table). Purpose: prove eligibility to drive, required by transport operations.
• Compliance document file (driver_documents table): federal/CDL license, medical certificate, drug test result, motor vehicle record (MVR), FMCSA Clearinghouse query, background/previous employment check, insurance policy, tax status certificate (RFC) and signed agreement. Purpose: regulatory compliance and document validation.
• Sensitive data (health / toxicology): the medical certificate and the drug test result are sensitive personal data. They are stored only with the operator's explicit, current consent (document_types.sensitive and driver_consents tables).
• Bank data for payment: bank, account holder, account number / CLABE / routing number (driver_payout_accounts table). Purpose: paying the operator. Stored encrypted at rest (AES-256-GCM); reads are restricted to a specific permission and logged in an access journal; users without the permission only see the masked version (last 4 digits).
• Profile photo (optional): if the operator uploads a profile photo from the app, the file is stored in the service's filesystem and its reference is stored in the `avatar_url` column of the `drivers` table. It is only uploaded with their explicit consent. Purpose: operator identification in the interface. The operator can delete it at any time with the “Delete photo” button in the app itself: the photo is removed from the application and from the backups generated after this change; earlier backups may retain it until they expire. For requests about already-deleted data or earlier backups, email privacidad@azimutha.com (ARCO rights, section 11).

The Platform requires verifiable photographic evidence to close a receipt or delivery order. Photographs of the receipt, delivery, damage checklist and signed order are captured (order_photos table, kind receipt | delivery | incident).

Each photograph is stored with its SHA-256 hash (integrity lock) and, optionally, location metadata (latitude, longitude, accuracy and source) and EXIF metadata. If the operator did not accept the location block, the photo is stored without coordinates (geo_source = 'none'); capture is never blocked by missing location.

Photographs and documents are stored in the service's file system and backed up off-site with encryption at rest by the storage provider.

The mobile app records the operator's route during their shift. This constitutes tracking of a person's position while they work, and is described here precisely.

What is collected: geographic position (latitude and longitude), speed, heading, accuracy and signal source (GPS, network or background). Points are sent by default every 20 seconds, adaptively (≈15 seconds moving, ≈30 seconds stopped). Driving events (hard braking, hard acceleration, sharp curves and speeding) are also detected using the phone's sensors and GPS.

When it is collected: from when the operator signs in until they sign out, or until they revoke the location consent. Collection continues even without an active order (to estimate the arrival time to the origin) and, in the native app, also with the app in the background or the screen off, via a service with a persistent visible notification. It does not continue if the operator force-closes the app.

Why it is used: to give visibility of operations to the transport company employing the operator, to estimate arrival times (ETA), to produce the driving score and for training.

Retention: route points and events are kept for 90 days by default (configurable per Client).

Consent: collecting location, driving behavior and usage analytics requires the operator's consent, which can be granted or revoked per block at any time (Settings → Privacy). Revocation stops collection immediately.

The app records usage events (visited screens, time per step, camera and sync errors, and GPS state transitions) to improve the capture flow. These events contain no free text from the operator and the device is identified with an anonymous identifier (UUID) without personal data.

Public sites (azimutha.com and orderafy.app): we use aggregate, cookieless web analytics with no personal identifiers to understand page views and performance. We do not record email, phone, name, order folio, VIN, coordinates or device identifiers, and we do not send such data to third parties.

We monitor site availability with our own automated probes; they record check results (up or down), not people's activity.

When signing up, the Client provides: email, administrator name, phone (optional), password (stored as a hash, never in plain text), company legal name, RFC, fiscal address and chosen plan. The payment method is captured with the payment provider's form (Stripe Elements): the full card number never reaches our servers; we only receive a token and the last 4 digits.

From each Client's staff using the portal we collect name, email, phone and role.

A half-completed signup draft is kept for up to 30 days.

If the Client enables WhatsApp reception, the Platform stores inbound messages to the business number (sender number, profile name and content) for handling from the app's inbox.

We process personal data based on: (a) the data subject's consent (explicit and in writing for sensitive data and for location/telemetry); (b) compliance with legal and regulatory obligations (licenses, tax status certificates, electronic invoicing/CFDI, accounting retention); and (c) the performance of the contractual relationship with the Client.

We do not sell personal data. We share data only for the purposes described and with the following recipients:

• The transport company (Client) employing the operator: the operator's data —including their live location— is shared with their employer for the operation the Platform manages.
• Microsoft Azure: infrastructure (servers and database) hosting the Platform.
• Cloudflare: edge/CDN network, off-site encrypted backup storage and aggregate web analytics for the public sites (cookieless, with no personal identifiers).
• Meta (WhatsApp Cloud API): receiving inbound WhatsApp messages.
• Twilio: sending SMS and WhatsApp notifications (phone number).
• Stripe: card payment processing (receives the token, not the full number).
• Conekta: bank transfer (SPEI) payments — CLABE issuance and payment reconciliation.
• Facturapi (authorized certification provider / PAC): electronic tax invoice (CFDI) stamping, which requires the Client's RFC and tax data.
• Zoho: sending transactional email.
• Apple (APNs) and Google (Firebase Cloud Messaging): delivering push notifications in the native apps (device token).
• Telegram (optional): notification channel only if the Client configures it.
• OpenStreetMap / Nominatim: geocoding (converting an order's origin and destination address into coordinates).
• OSRM routing service (self-hosted instance and, as fallback, the public demo server): computing routes and arrival times from coordinates.

We retain personal data only as long as necessary for the described purposes and for the applicable legal periods. Cost evidence is kept for at least 60 months (article 30 of the Mexican Federal Tax Code); the driver file (DOT Driver Qualification File) is kept for at least 36 months after the end of the relationship; telemetry is kept for 90 days by default.

Data subjects may exercise their rights of Access, Rectification, Cancellation and Opposition (ARCO), as well as consent revocation, by sending a request to the contact address in section 12. The request must identify the data subject and describe what is asked; we will respond within the applicable legal periods.

Revocation of location and telemetry consent can be done directly in the app (Settings → Privacy), without writing to us.

Deletion does not apply when the law requires retention (e.g. accounting and tax documentation); in that case the data is blocked and kept only for the legal purpose that requires it.

To exercise ARCO rights or ask about this policy, write to privacidad@azimutha.com.

We apply technical and organizational security measures, including: encryption at rest of bank data (AES-256-GCM), passwords stored as hashes, SHA-256 hash of photographic evidence (preventing undetected alteration), a sensitive-data access journal and role-based access control.

The Platform is not directed at minors and does not intentionally collect personal data from minors.

When we change this policy we will update the effective date and, in the case of consents, request acceptance of the current version again.