Privacy policy
Last updated:
Accounts and guest access
You can browse, search and navigate without an account. Posting public contributions and saving places to an account require sign-in. Creating or completing an account requires an Iraqi mobile number and a nickname. An account stores these details, your email, display name and a password hash, not your original password. Your account phone number is private and is not included in public driver markers or shared links. We do not currently verify phone ownership by SMS. We also store submitted reports, votes, place details, fuel prices and saved places. Install identifiers and IP addresses support abuse limits and session security.
Your location
GPS shows your position and supports navigation and nearby results. Active guidance can continue with the screen off or another app open through a foreground location service with a notification, including Android Auto. Route calculation sends start and destination coordinates to our server and the routing service. A report includes the location you choose to submit; a private issue includes location only when you opt to attach it.
Sharing your ETA
Sharing is optional. A shared trip stores its latest position, direction, speed, destination and ETA on our server. While sharing is active, anyone with the link can see your nickname, position, remaining route, destination and arrival information. The link stops revealing these details when sharing is stopped, you arrive or the eight-hour sharing period expires. Stored trip data is removed by the cleanup process described below.
What is public
Reports and road features appear on the map without your account name. Showing yourself to other drivers is off by default and requires an explicit choice. When enabled, Mashi users whose app reports a position within 5 km of you can see your nickname, latest position and direction; drivers farther away cannot. Public visibility expires 90 seconds after the last update; switching it off removes your presence. Your account phone number is not shown. Published business contact details and photos are public. Fuel-price reports can show your display name, and leaderboards and competition results can show your name and points.
Invitations, points and competitions
Each account gets an invite code. When someone signs up with your code, we record that you invited them; small points they earn can also give a point to you and to the driver who invited you. Your app shows your code and how many drivers you invited, not their details. Points, levels and categories are calculated from your contributions and stored with your account. To keep competitions fair we compare devices, timing and voting patterns, and we may withhold or remove points.
Private support messages
Website messages store the name, email, selected topic and text you submit. In-app support requests store your description, category and app version, plus contact and location only if supplied. Signed-in requests are linked to your account; you can read their status and exchange replies with the support team inside the app. Authorized support staff can review, reply to and assign requests in a separate support panel. These conversations are private and do not appear on the public map. Guest submissions remain available, but guests cannot read or receive in-app replies. Guest and website messages are not automatically linked to an account for deletion.
Staff access
Authorized administrators and moderators can view the account details needed to run and protect the service and to answer you: name, nickname, email, phone number, language, sign-up and last-seen times, invitations, signed-in device names, contributions, points and moderation history. Staff accounts are limited by role, and moderation actions are logged.
Services we rely on
Our map tiles and map fonts come from our server and use OpenStreetMap data. Routing and some address searches use configured external services, receiving route coordinates or search text to answer the request. To draw a reported jam along its road, our server sends the report location and direction to the routing service, without account details. Weather is a MET Norway model forecast: our server sends a rounded location cell of roughly 5 km, without your account token or phone IP, and asks the OpenStreetMap geocoder for the name of the city in that cell. Search and forecast responses are cached. Opening Google Maps or another external link is your choice and uses that service's privacy policy. The website loads text fonts from Google Fonts.
Website and API delivery
We use Cloudflare to protect and deliver our website and app API. Cloudflare processes your IP address and request details, including URLs, headers and any data sent in a request, which may include account, support or location information. HTTPS encrypts traffic between your device and Cloudflare and between Cloudflare and our server. Cloudflare ends the first encrypted connection, can read the request at its proxy, and forwards it over the encrypted connection to our server. We cache only approved public static files there. Account, support and shared-trip responses, API responses and other dynamic pages bypass its shared cache. Cache bypass does not prevent processing or security logging by Cloudflare.
Retention and cleanup
Expired live reports leave the active map. Routine cleanup removes reports expired for over 30 days, tokens inactive for 180 days, trips expired for over two days, fuel prices over one year old and shared search/forecast cache entries over 30 days old. Cleanup runs periodically, so removal is not immediate at each cutoff. IP/install rate-limit counters become eligible for cleanup after 24 hours and can remain longer when the service is idle. Support messages have no automatic age-based deletion; staff can remove them. Hosting and provider logs or backups may have separate retention, including request IPs and coordinates.
Deleting your account
In the app, open your account, choose Delete account and confirm your password. This removes the account, saved places, sessions, votes, points, linked private issues and account-linked shared trips. Public reports, place details and fuel prices may remain with their account association removed. Uploaded listing photos are detached and queued for deletion; a file still used by another listing is retained. Public business details or information written inside public content are not automatically erased. Contact us about that content or a guest/website message.
Security and your phone
The production app uses HTTPS, and passwords are hashed on the server. Private account email and phone numbers, support content and replies, saved-place details and shared-trip details are encrypted in server storage using authenticated AES-256-GCM with a key kept separately from the database. The server decrypts this information for authorized access, including support staff access to support conversations. This is not end-to-end encryption: authorized server code and staff with the relevant permissions can read the information. Public map data and hosting or provider logs are not encrypted by this field-encryption system. On Android, credentials, cached account/saved-location data and search history use authenticated AES-256-GCM encryption with an Android Keystore key. Private app data is excluded from Android backup.
Children and 18+ voices
Mashi is made for drivers and is not directed to children under 13. Voices marked 18+ are for adults only: the app asks you to confirm your age before playing or downloading them and keeps that answer only on your phone.
Contact
Questions, retained-content or deletion requests: use the contact form on our website ([email protected]). Do not send passwords or sign-in codes.