Cookie Policy
Provider: MiRide Technology (Private) Limited · 7 Tweed Road, Eastlea, Harare, Zimbabwe · Effective: 13 May 2026 · Last updated: 28 August 2026
1. What are cookies?
Cookies are small text files that a website places on your device when you visit. They are stored by your browser and sent back to the website on subsequent visits. Cookies can remember your preferences, keep you signed in, and help website owners understand how their site is being used.
Related technologies include local storage and session storage, which work similarly but are managed differently by the browser. This policy covers cookies and these related browser storage mechanisms as a group.
Cookies and browser storage are a concept specific to websites running in a browser. The MiRide mobile app does not use browser cookies. It uses secure on device token storage instead. We explain this separately in Section 3.
2. How MiRide uses cookies on this website
The MiRide public website (miride.app) is a static site built with Astro. It contains no login, no user accounts, and no personalisation features. As a result, it uses very few cookies.
We do not currently deploy analytics scripts, tracking pixels, or advertising networks on this website. No cookies are set by MiRide Technology (Private) Limited directly for analytics or marketing purposes.
One page makes a connection to a third party service that may set its own cookies: the live trip tracking page draws its map with Google Maps. Every other page is served entirely from miride.app, typefaces included. Section 4 sets out the detail.
Cookie categories used on this website
| Category | Used? | Details |
|---|---|---|
| Strictly necessary | No | The website has no login or account features, so no session cookies are required for authentication. |
| Functionality | No | No language preference or personalisation cookies are currently stored by this site. |
| Analytics | No | No analytics platform (e.g. Google Analytics, Mixpanel) is currently installed on this website. |
| Advertising | No | No advertising networks or retargeting pixels are active on this website. |
| Third party | On one page | The live trip tracking page loads a Google map, which may set cookies under Google's own domains. No other page loads a third party resource. See Section 4. |
3. How MiRide uses tokens in the mobile app
The primary MiRide product is a mobile app available on iOS and Android. Mobile apps run natively on your device and do not use a web browser, so browser cookies do not apply to the MiRide app.
Instead, the app uses industry standard, token based mechanisms stored securely on your device:
- JWT access token — a short-lived token (typically 15 minutes) that authenticates your requests to MiRide's servers. Stored in the device's secure storage (iOS Keychain / Android Keystore), not accessible by other apps.
- JWT refresh token — a longer-lived token used to obtain a new access token without requiring you to log in again. Stored with the same device level security as the access token.
- Firebase Cloud Messaging (FCM) token — a device registration token provided by Google Firebase that allows us to send you push notifications (trip updates, driver arrival, delivery status). This token is stored in MiRide's database and associated with your account. It is not a cookie.
These tokens are not shared across apps, are not accessible via a browser, and do not persist beyond your session or device without your explicit action (such as choosing "stay signed in"). You can revoke them at any time by signing out of the app.
App token summary
| Token / Mechanism | Purpose | Duration | Storage |
|---|---|---|---|
| JWT access token | Authenticates API requests | ~15 minutes | Device secure storage (Keychain / Keystore) |
| JWT refresh token | Renews access token without re-login | 30 days (or until sign-out) | Device secure storage (Keychain / Keystore) |
| FCM device token | Enables push notifications | Until token rotation or sign-out | MiRide server side database; device managed by Firebase |
| App preferences | Stores local settings (e.g. language, map type) | Until app uninstall or reset | Device local storage (not transmitted to MiRide servers) |
4. Third party services and their cookies
This website is deliberately light on third parties. Its typefaces are served by us, and there are no embedded widgets, players, or trackers on any page. One page loads a map from Google, and that is the whole list. Where an external service is used, it operates under its own privacy and cookie policy, and MiRide Technology (Private) Limited does not control what data it collects.
Typefaces are served by us, not by Google
The typeface used across this site is served from miride.app itself. Your browser makes no request to fonts.googleapis.com or fonts.gstatic.com, and Google receives nothing when a page loads.
Until 28 August 2026 this section said the opposite: that the site loaded typefaces from Google Fonts and that Google received your IP address as a result. That was never true of this website. We have corrected it rather than leave a claim here that overstated what we share.
Google Maps (live trip tracking page only)
When someone shares a MiRide trip with you, the link opens a live tracking page that shows the vehicle moving on a map. That map is drawn with the Google Maps JavaScript API (maps.googleapis.com, maps.gstatic.com). While it loads, Google receives your IP address, the address of the page, and your browser headers, and may set or read cookies under its own domains.
This is the only page on the website that loads anything from Google. In particular, the coverage map on the home page is not a Google map: it is an image drawn by us from public boundary data, and it makes no external request.
If you would rather not load it, blocking third party scripts or cookies will stop the map appearing. The trip details on that page — the status, the driver, and the estimated arrival time — are rendered by us and will still be shown.
Google's privacy policy: policies.google.com/privacy
Links that lead to other companies
Some pages link out to Google Maps for directions to our office, and to the Apple App Store and Google Play to download the app. These are ordinary links, not embeds. Nothing is requested from those companies until you click one, and from that point their own policies apply.
Cloudflare (hosting)
This website is hosted and delivered by Cloudflare, Inc. As our host, Cloudflare processes your IP address and request headers in order to serve pages to you and to protect the site from abuse. It acts on our instructions as a processor rather than as an independent tracker, and we have not observed it setting any cookie on this site.
Third party service summary
| Service | Purpose | Loaded on | Cookies set? | Set by |
|---|---|---|---|---|
| Google Maps JavaScript API | Draws the map on a shared live trip | The live trip tracking page only | Possibly, under Google's own domains | Google LLC |
| Cloudflare | Hosting, delivery, and protection of this website | Every page | None observed | Cloudflare, Inc., as our processor |
| Google Fonts | Not used — typefaces are served from miride.app | Nowhere | No | — |
5. How to manage cookies
This website sets no cookies of its own, so on most pages there is nothing here to manage. The one control that matters is over the Google map on the live trip tracking page (see Section 4 above).
Browser settings
All modern browsers let you view, block, and delete cookies. Instructions for the most common browsers:
- Google Chrome — Settings → Privacy and security → Cookies and other site data
- Mozilla Firefox — Settings → Privacy & Security → Cookies and Site Data
- Apple Safari — Settings → Privacy → Manage Website Data
- Microsoft Edge — Settings → Cookies and site permissions → Manage and delete cookies and site data
Blocking third party cookies or scripts will prevent the map from loading on the live trip tracking page. The trip details on that page still appear, and the rest of the website is unaffected: it loads nothing from anyone else.
Google's own opt-out tools
These apply to your Google account generally, not only to the map on our tracking page. You can opt out of Google's interest based advertising at adssettings.google.com. For broader Google data controls, visit myaccount.google.com.
Mobile app tokens
To revoke the JWT tokens stored by the MiRide app, simply sign out of the app. Your refresh token will be invalidated on our servers and removed from your device. To stop receiving push notifications, you can disable notifications for the MiRide app in your device's system settings (iOS: Settings → Notifications → MiRide; Android: Settings → Apps → MiRide → Notifications).
6. Changes to this policy
MiRide Technology (Private) Limited may update this Cookie Policy as the website or app evolves. For example, if we introduce analytics tooling or a cookie consent mechanism in the future, we will update this page before those tools go live and, where required by law, seek your consent at that time.
Material changes will be noted at the top of this page with a revised effective date. We encourage you to review this policy periodically. Continued use of the website after a material change constitutes acceptance of the revised policy.
Current effective date: 13 May 2026
7. Contact
If you have questions about this Cookie Policy or how MiRide Technology (Private) Limited handles your data, please contact us:
MiRide Technology (Private) Limited
7 Tweed Road, Eastlea
Harare, Zimbabwe
Email: [email protected]
This policy applies to the MiRide website at miride.app and the MiRide mobile app. It does not cover the MiRide admin portal, which operates on a separate subdomain and is accessible only to authorised staff.