Privacy Policy | Glide Rentals

Scope

This Privacy Policy explains how Glide Rentals Pvt. Ltd. collects and uses information through the Glide Rentals website, dashboard, mobile app, backend API and related rider, driver and support workflows.

This page is based on the current production code paths for the backend, mobile app and dashboard. It is intended to be understandable and accurate, but it is not a substitute for legal advice.

Information We Collect

Account and authentication data

Name, email address, phone number, city, account role, account status, account creation date and profile photo URL.
Password credentials are processed at sign-up and login. The backend stores a password hash, not the plaintext password.
Authentication tokens identify the signed-in user. Mobile tokens are stored in secure device storage; dashboard tokens are stored in a browser cookie.

Profile and driver verification data

Driver license-front image path, driver selfie image path, review status, review timestamps, reviewer IDs and rejection reasons.
Vehicle class, license plate, make, model, color, seat count, vehicle photo paths, vehicle review status and rejection reasons.
Admin review actions, suspension/reactivation reasons and before/after driver review state.

Ride and booking data

Pickup and drop-off labels and coordinates, city, requested vehicle class, trip type, scheduled time, return time, daily rental days and ride status.
Driver assignment, offer/session IDs, dispatch attempt IDs, timestamps for acceptance, arrival, start, completion and cancellation.
Command idempotency keys, command request bodies, ride events, outbox events and response records used to make ride actions reliable.

Location and route data

Drivers who are signed in and active can send foreground location updates including latitude, longitude, accuracy, heading, speed, recorded time and received time.
The backend stores a current driver location and minute-bucket location snapshots for dispatch, live ride tracking, fleet monitoring and support.
Rider pickup/drop-off coordinates and route coordinates are used to request and render trip routes.

Communications and notifications

APNs and Firebase Cloud Messaging device tokens, platform, APNs environment, notification enabled preference and push delivery status.
Push delivery rows may include notification title, body, collapse ID, ride ID, ride version and delivery errors.
WebSocket connections carry real-time refresh hints and may include ride, offer, user or driver-location update payloads.

Ratings, feedback and support context

Ride rating score, rating tags, optional feedback text and rating prompt dismissals.
Admin dashboard views may show driver names, emails, phone numbers, documents, vehicle records, latest location, ride history, ratings and audit history.
If you contact us by phone or email, we collect the details you choose to provide so we can respond.

Website and dashboard data

The public site uses Umami analytics to understand site traffic and page usage.
The dashboard uses a cookie for the admin session token and localStorage for dashboard theme preference.
The dashboard live map loads Leaflet and OpenStreetMap map tiles to display fleet location.

How We Use Information

Create and maintain rider, driver and admin accounts.
Authenticate users, protect sessions and prevent unauthorized dashboard or API access.
Match riders with eligible drivers and vehicles, create durable offers and run dispatch waves.
Provide foreground driver location for dispatch, rider trip tracking, admin fleet monitoring and operational support.
Review driver documents, selfies and vehicles before allowing drivers to accept trips.
Send ride alerts, dispatch requests, cancellation notices and status notifications.
Maintain ride history, ratings, support context, audit trails and operational reliability records.
Improve the website and app, diagnose errors, prevent abuse and comply with legal obligations.

App Store Privacy Summary

For Apple App Store privacy disclosures, Glide may collect data that is linked to your account or device and used for app functionality, safety, support and operations. We do not use this data for cross-app advertising tracking.

Contact info: name, email address and phone number.
Identifiers: user/account ID and APNs or Firebase device token for ride alerts.
Location: precise foreground driver location and rider pickup/drop-off coordinates.
User content: profile photos, driver license images, selfies, vehicle photos, ratings, feedback and support details you provide.
Sensitive or verification information: driver identity, license, selfie and vehicle review materials.
Usage and transaction context: ride requests, accepted rides, dispatch offers, trip status, payment/charge records where applicable and operational interaction records.

Location Data

The mobile app requests foreground location permission for drivers. The current implementation reports driver location only when the user is signed in as a driver, the app is active, and the driver location bridge is running. It does not request background location permission in the current app configuration.

Driver location is used for dispatch eligibility, live rider tracking after assignment, admin fleet visibility and support. Rider pickup and drop-off coordinates are shared with drivers who receive a ride offer so they can decide whether to accept the trip.

Photos and Uploaded Files

The app may request photo-library permission for profile, license and vehicle uploads, and camera permission for driver selfies. Uploaded images are stored in S3-compatible object storage under account-specific paths.

Profile avatars may be visible in account experiences. Driver verification and vehicle images are used for onboarding, review, safety and support, and are visible to authorized administrators.

How We Share Information

We do not sell personal information and we do not use app data for cross-app advertising tracking. We share information only as needed to provide, operate, protect and improve the service.

With riders and drivers: trip details, driver name, assigned vehicle details, selected pickup/drop-off information, ride status and live driver location during an active ride.
With offered drivers: limited trip request details such as pickup/drop-off labels, coordinates, vehicle class, schedule and offer expiration.
With administrators and support: account, driver, vehicle, ride, location, rating and audit data needed to operate and support the platform.
With service providers: backend hosting, PostgreSQL database, S3-compatible storage, Apple Maps, APNs, Firebase Cloud Messaging, OSRM route service, Cloudflare, Umami analytics, Leaflet/OpenStreetMap assets and similar infrastructure providers.
With authorities or other parties if required by law, to enforce our terms, to protect users, or to investigate fraud, safety incidents or security issues.

Retention

We keep account, driver, vehicle, ride, rating, audit and operational records for as long as reasonably needed to provide the service, resolve disputes, meet legal obligations, improve reliability and protect users.

When you delete your account in the app, we remove active device tokens, close live driver sessions, mark the account deleted and anonymize direct account identifiers. Some ride, command, event, delivery, driver verification and audit records are retained for legal, safety, payment, reliability, replay protection and operational traceability.

Device tokens are removed when you disable notifications, sign out, or delete your account if the unregister/delete request succeeds, and invalid APNs/FCM tokens are pruned when rejected by the push provider.

Your Choices

You can update your name, phone number, city and avatar in the app.
Ride alerts are opt-in. You can enable or disable app notifications in the app or in system settings. If unregistering a token fails because of connectivity, the app retries when it is opened again.
Drivers can deny foreground location permission, but some driver dispatch and ride-tracking features may not work.
You can delete your account from Profile in the app. Deletion may be blocked until active or unsettled rides are completed or cancelled.
You can contact us to request access, correction or data handling assistance, subject to legal, safety, fraud-prevention and operational retention needs.

Security

We use authenticated API access, role checks, password hashing, idempotency controls, review gates and limited admin routes to protect service data. No system is perfectly secure, so you should keep your password and devices safe and tell us quickly if you suspect unauthorized access.

Children

Glide Rentals is not intended for children. Users must be old enough to form a binding agreement and, for drivers, legally permitted to drive and provide passenger transport services where applicable.

Changes and Contact

We may update this Privacy Policy as the product, backend or app changes. If the changes are material, we will take reasonable steps to notify users through the site, app or account channels.

For privacy questions or requests, contact Glide Rentals at nischal1024@gmail.com or +977 97444405504.