Legal · RideCost
RideCost Privacy Policy
Effective date: August 14, 2026 · Last updated: August 14, 2026
1. Introduction
RideCost is a motorcycle fuel and trip cost estimator for Philippine riders, published by Freymwork ("we", "us", or "our") — the same team behind Waypoint. This policy covers the RideCost mobile app and the backend services it talks to.
This policy is specific to RideCost. Waypoint has its own policy at wypnt.app/privacy. The two apps share one account system, so if you sign in to RideCost with a Waypoint account, both policies describe parts of the same account.
You can produce a full cost estimate without an account and without granting any permission. Everything in Section 2.1 below applies only if you choose to create an account.
Questions: [email protected].
2. Information We Collect
2.1 Information You Provide Directly
Account details — if you create one: your email address and name. If you sign up with an email and password, the password is stored only as a hash. If you sign in with Apple or Google, we receive your name and email address from that provider and never see your password. Apple's Hide My Email is supported and works normally.
Your bike: the motorcycle model you select from our catalog, or a custom entry (label, engine displacement, km/L, and preferred fuel grade). This is what makes an estimate specific to you rather than generic.
Trip inputs: the start and destination you enter for an estimate, plus any intermediate stops.
Gas price alert preference: whether the weekly alert is on, and the peso threshold you set for it. This is a setting, not a subscription — we do not build a marketing list from it.
2.2 Information Collected Automatically
Device identifier: on first launch the app generates a random UUID and stores it in the device keychain. It is not your advertising ID, not your hardware serial, and not derived from anything about your device — it is a fresh random value with no meaning outside RideCost. It exists so the estimates you make before signing up are still there after you sign up. If you create an account, this identifier becomes associated with it.
Estimate history: each estimate you run is stored with its origin, destination, distance, terrain profile, the bike and fuel grade used, and the resulting peso figure — this is what the History list on the You tab reads from.
Usage analytics: the app sends batched event records (app version, platform, event name, and the estimate an event relates to) to our own server so we can see which parts of the app are used and which are not. These events go to us and nowhere else. There is no third-party analytics SDK, no advertising SDK, and no crash-reporting SDK in RideCost.
The app does not use cookies and performs no cross-app or cross-site tracking.
2.3 Location Information
Optional, foreground only, one reading at a time. If you grant location permission, RideCost takes a single coarse-to-moderate accuracy reading to prefill the starting point of an estimate, so you do not have to type where you already are. That coordinate is sent to our server to be resolved into a place and routed from.
RideCost does not track your ride, does not record a route trace, and never requests or uses background location. There is no "Always Allow" mode, and closing the app ends any location access entirely.
If you decline location permission, nothing breaks — you type the starting point instead, and every feature continues to work.
2.4 Photos
RideCost requests add-only access to your photo library, and only at the moment you tap Save on an estimate share card. It writes that one image and never reads your library. The broader read/write photo permission is deliberately not requested, so the app is technically incapable of seeing your existing photos.
3. Summary of Data Collected
This table mirrors the App Privacy disclosure on RideCost's App Store product page. None of it is used for tracking as Apple defines the term.
| Data | Why | Linked to your account |
|---|---|---|
| Name | Account creation and display | Yes |
| Email address | Account creation, sign-in, and support | Yes |
| Precise location | One-time prefill of an estimate's starting point (optional) | Yes |
| Trip and estimate history | Showing your past estimates on the You tab | Yes |
| User ID | Identifying your account across requests | Yes |
| Device ID | Carrying pre-sign-up estimates into a new account; usage analytics | Yes |
| Product interaction | First-party analytics — which features get used | Yes |
4. How We Use Your Information
• Produce the estimate — resolve the places you typed, route between them, read the elevation profile along that route, and combine it with your bike's km/L and today's pump price. • Keep your estimates — so the History list and the "your first estimates are still here" behaviour work after you sign up. • Authenticate and secure your account — issuing session tokens and detecting abuse. • Send the weekly gas price alert — only if you turned it on, and only about fuel prices. • Improve the app — using our own aggregate usage events to decide what to build and what to remove.
We do not use any of it to build advertising profiles, and we do not sell it.
5. Third-Party Services
Producing an estimate requires calling services we do not operate. What each one receives is listed below.
| Service | What it receives | Purpose |
|---|---|---|
| Google Maps Platform | The start, destination, and stops of an estimate as place text or coordinates | Geocoding, routing, and elevation along the route |
| Mapbox | The computed route shape, to render a static map image | The route map on the Results screen |
| OpenWeather | Coordinates of points along the route | Weather along your route |
| Apple / Google Sign-In | Handled by Apple or Google; we receive your name and email | Sign-in, if you choose those options |
6. What RideCost Does Not Do
Stated plainly, because the absence of these is a design decision and not an oversight:
• No advertising, no ad networks, and no ad identifiers. • No tracking across other apps or websites, and no sharing with data brokers. • No selling of personal information. • No background location and no ride tracking. • No reading of your photo library. • No third-party analytics or crash-reporting SDKs. • No in-app purchases or subscriptions — RideCost is free. • No contacts, microphone, health, or payment data of any kind.
8. Data Retention
Account data and estimate history are kept while your account is active. Anonymous estimates tied only to a device identifier are retained so they can be claimed if you later sign up on that device.
When you delete your account, your account record, saved bike, alert preference, and estimate history are deleted. Aggregate usage counts that cannot identify you may remain.
9. Your Rights and Choices
Permissions: location, notifications, and photo-add access are each optional, requested in context, and revocable at any time in your device settings. Revoking any of them leaves the core estimate working.
Access and correction: your account details and saved bike are editable in the app's You tab.
Deletion: you can delete your account and its data from the You tab, or by writing to [email protected]. See wypnt.app/account-deletion for the full procedure.
Philippine Data Privacy Act: if you are in the Philippines, you have rights of access, correction, erasure, objection, and data portability under RA 10173, and the right to complain to the National Privacy Commission. Write to [email protected] to exercise any of them.
10. Children
RideCost is rated 4+ for content but is not directed at children, and we do not knowingly collect personal data from anyone under 13. If you believe a child has given us personal data, contact [email protected] and we will delete it.
11. Security
Traffic between the app and our servers is encrypted in transit. The device identifier and your session token are held in the device's secure keychain rather than ordinary app storage. Passwords are stored only as hashes.
No system is perfectly secure, and we cannot guarantee absolute security — but we do not store what we do not need, which is the most effective protection available.
12. Changes to This Policy
We may update this policy as RideCost changes. The "last updated" date at the top will always reflect the current version, and material changes will be surfaced in the app.
13. Contact
Questions, requests, or complaints about this policy or your data: [email protected].