This Privacy Policy describes how QuickMove (“we,” “us,” or “our”) handles information when you use our mobile application (the “App”) and related services that connect to our backend API.
By using the App, you agree to this policy. If you do not agree, please do not use the App.
1. Introduction
QuickMove is a transport and logistics application. It lets users with different roles (such as clients, transporters, and administrators) create and manage transport requests, bids, shipments, messages, ratings, return-load offers, and related features.
We process personal information only as needed to provide these services, as described below. We do not sell your personal information.
2. Information We Collect
2.1 Account and profile information
When you register or use the App, we may collect and store:
- Email address (used as your login identifier)
- Password (stored in hashed form on our servers; we do not store your plain-text password)
- Account role (for example: client, transporter, or admin)
- Name (first and last name, if you provide them)
- Phone number (if you provide it)
- Profile image (if you upload one; stored as a file on our servers with a URL reference in your profile)
2.2 Transporter (driver) and verification information
If you use the App as a transporter, we may collect and store:
- Vehicle details (such as type, brand, model, year, license plate)
- Operating zones (for example, region names you select)
- Vehicle photos (uploaded images)
- Identity and vehicle documents for verification, including file names, file types, URLs on our servers, and optional expiry dates where applicable
- Verification status, rejection reasons, admin review notes, and related metadata
- Account balance in Moroccan Dirhams (MAD), used in the App for transporter features
- Location while providing services
2.3 Transport jobs, bids, shipments, and return loads
Depending on how you use the App, we may collect and store:
- Pickup and delivery locations, including addresses and latitude/longitude
- Cargo details such as weight, optional volume, category, description, number of helpers, and uploaded photos
- Preferred dates and status of requests and shipments
- Pricing-related information such as estimates, breakdowns, and amounts you or the system set
- Bids, including prices, optional messages, acceptance information, and shipment progress status
- Completion location for a delivery, including address and coordinates where that feature is used
- Return trip listings and offers, including routes, timing, cargo details, photos, prices, and messages between parties
2.4 Location information
- The App may request foreground location access on your device to show maps, suggest or set locations, filter or browse offers, and support live tracking during deliveries
- Device location may be read using the device’s location services when you grant permission
- For transporters, latitude, longitude, and a timestamp may be stored on our servers as current location so clients and the service can show tracking and nearby matching where those features apply
2.5 Messages and ratings
- Chat messages you send through the App, including content, sender and recipient identifiers, and read or delivery-related flags where implemented
- Ratings and optional comments you submit about completed jobs, linked to the relevant bid, transport request, client, and transporter
2.6 Push notifications
- If you enable notifications, the App may obtain a push token from the notification platform and send that token to our servers so we can deliver push notifications
- You can control notification categories through in-app notification preferences where those settings are available
2.7 Photos, files, and device permissions
- The App may request access to your camera, photo library, and on some Android versions, storage, so you can upload images and documents
- Uploaded files are stored on our servers, and we may keep metadata such as file URLs, names, sizes, and MIME types where our system records them
2.8 Technical and usage data
- The App connects to our backend API
- Authentication tokens and a cached copy of your user profile may be stored locally on your device so you stay signed in
- Language and display preferences such as dark mode may be stored locally on your device
- Our servers may log technical information for operation and troubleshooting, such as IP address and request paths in server logs
- We do not integrate third-party analytics SDKs such as Firebase Analytics in the App’s dependencies as shipped in this project
3. How We Use Information
We use the information above to:
- Create and manage accounts and sign-in
- Provide core features such as transport requests, bids, shipments, return trips, maps, routing views, and live tracking
- Verify transporter accounts and documents, and show relevant status to you and authorized administrators
- Send push notifications according to your token and preferences
- Calculate and display prices and balances as implemented in the App
- Enable in-app messaging between users
- Record ratings and improve trust and quality within the platform
- Operate, secure, and improve our services, including debugging and fraud prevention where applicable
4. Third-Party Services
When you use the App, these third parties may receive or process data as part of their normal operation:
| Service | Role | Typical data involved |
|---|---|---|
| Google Maps Platform | Map display and, when configured, Directions API requests from the App | Coordinates or place-related parameters needed to show maps and routes |
| Expo / Apple / Google push infrastructure | Delivering push notifications | Push token and notification payloads |
| 2Checkout (Verifone) | Transporter balance top-up through a hosted payment page in the browser | Amount, currency (MAD), and order identifiers used to initiate checkout. Payment card and billing details are handled by 2Checkout |
| EAS (Expo Application Services) | Build and project configuration services | Project metadata used for Expo-related services |
5. Data Storage & Security
- Server-side data is stored in a MongoDB database and in files on our servers
- Passwords are stored using one-way hashing (bcrypt) on the server
- API access is protected with JWT access and refresh tokens
- Local device storage may hold session tokens and UI preferences so the App works more smoothly
No method of transmission or storage is completely secure. We take reasonable steps to protect information, but we cannot guarantee absolute security.
6. User Rights (Access, Correction, Deletion)
Depending on your location, privacy laws may give you rights to access, correct, export, or delete your personal information, or to object to or restrict certain processing.
What the App supports today:
- You can view and update much of your profile and preferences through the App
- You may be able to delete certain content you created where the App exposes delete actions, subject to business rules and permissions
Account deletion: The current public user API in this project does not expose a self-service “delete my entire account” button for all data. To request deletion of your account or personal data, or to exercise other rights, contact us using the details below.
7. Children’s Privacy
QuickMove is not intended for children under 13, or the minimum age required in your country. We do not knowingly collect personal information from children. If you believe a child has provided us personal information, please contact us and we will take appropriate steps.
8. Changes to This Policy
We may update this Privacy Policy from time to time. We will post the new version in the App or on our website and update the “Last updated” date. Continued use of the App after changes means you accept the updated policy, unless a stricter rule applies under your local law.
9. Contact Information
For privacy questions, requests about your data, or to ask for account or data deletion:
- Email: ayoub.berouijel10@gmail.com