1. Information We Collect
Meandly may process account information, such as email, login provider, and authentication tokens; profile information, such as nickname, photo, Bio, profile flag, and visited-country context; content you create, such as routes, photos, notes, comments, community posts, saves, likes, messages, and reports; location-related information, such as selected browsing region, route coordinates, start and end points, place search results, map center, or current location when permission is granted. When you explicitly start recording a walk, location processing may continue in the background until you pause, finish, or discard the recording; device and app information, such as push tokens, app version, language, permission status, error and usage state; subscription status; and support communications.
2. Sensitive Data
Walking routes and location records can reveal routines, frequently visited places, and movement patterns. Signed-in completed walk GPS routes, timestamps, distance, estimated steps and calories, and day-goal history are stored privately under your account for sync and restore. Offline records may queue on your device. Existing records that belong only to a device are imported to your account only when you choose that action. These private records are not automatically published to the feed or used for public rankings. When you delete a record or account, Meandly removes the private record content while keeping minimal deletion markers when needed to prevent deleted records from syncing back from another signed-in device.
3. How We Use Information
We use information to create and secure accounts, show profiles, save walks, draw and match routes to roads, power maps and place search, deliver local feeds, community features and messages, manage follows, blocks and reports, send notifications, verify subscription entitlement, provide support, protect against abuse, improve service quality, and comply with legal obligations. When you enable optional settings, we may also use information for personalized suggestions and usage analytics.
4. Sharing and Service Providers
Your public profile and public content may be shown to other users. We may share information with service providers that help operate Meandly, including cloud hosting, databases, file and image storage, map, geocoding and road-matching providers, push notification providers, app stores, billing and subscription partners, email or support tools, and analytics or error-diagnostics tools. For example, coordinates or search terms may be sent to providers such as Google or Geoapify for map, route, or road-matching features, and push tokens may be processed by notification providers. Meandly does not sell personal information or use it for cross-app behavioral advertising.
5. Retention and Deletion
Account and content data is generally kept while you use the service. When you delete content or request account deletion, Meandly will try to delete or anonymize related data within a reasonable time. Some information may be retained for limited periods when needed for security logs, fraud and abuse prevention, billing and tax records, reports or disputes, legal obligations, or backup recovery windows.
6. Your Choices and Controls
You can manage profile details, Bio, profile flag, visited-country context, browsing region, public or private account state, follow requests, blocked accounts, notifications, location permissions, health-data connections, personalized suggestions, and usage analytics in the app or device settings. You can revoke location, notification, photo, and health permissions through your operating system. Some features may stop working if a required permission is turned off.
7. Security
Meandly aims to protect information with access controls, authentication, permission checks, secure transmission, limited operational access, monitoring, and backups. No app or network can guarantee perfect security, so you should also protect your account and be careful with public location content.
8. Children
Meandly is not directed to children under 13. If we learn that we collected personal information from a child without required parental consent, we will take reasonable steps to delete it.
9. International Processing
Meandly may rely on global service providers and cloud infrastructure, so information may be processed or stored outside your country of residence. When that happens, we aim to protect information according to this Policy and applicable law.
10. Changes and Contact
We may update this Privacy Policy when features, providers, laws, or operations change. Material changes may be communicated in the app or through official channels. To request access, correction, deletion, consent withdrawal, account deletion, or help with privacy questions, contact support@meandly.com.
11. Advertising and Privacy Choices
Free-plan users may see clearly labeled Google Mobile Ads and may choose an optional rewarded ad for a non-transferable Road pass. Pro users do not receive passive ad requests. The Google Mobile Ads SDK may collect and share an IP address used to estimate approximate location, ad and product interactions, diagnostic and performance information, and device, app, or account identifiers for advertising, analytics, and fraud prevention. Meandly does not request iOS tracking permission and removes Android advertising-ID and ad-services permissions in the current build, so it does not use cross-app behavioral tracking. Where required, Google's consent form is shown before ads can be requested, and privacy choices can be revisited in Settings. If consent or ad eligibility cannot be resolved, no ad is requested.
12. Usage Analytics and Record Sync
When the usage analytics setting is enabled, Meandly may send first-party product analytics events to Meandly servers and to PostHog, a usage analytics provider with United States infrastructure. These events use pseudonymous identifiers such as user, session, visit, workflow, screen, content, and event identifiers, and may include screen views, content impressions, active-time buckets, scroll depth, button or control interactions, feature outcomes, permission-result buckets, and coarse Record buckets such as distance, duration, steps, route-point count, mode, visibility, media presence, and route presence. Product analytics are designed not to include raw GPS traces, precise coordinates, full private routes, place names, search query text, post or message bodies, media URLs, callback arguments, or raw error text. Search quality events may be processed separately for search operation and improvement, so this analytics limit should not be read as a statement that search-related data is never processed. Private Record cloud sync is separate from analytics: signed-in recorded walks, steps, goals, and deletion markers are stored under your account for sync and restore, and private Record routes are not exported to PostHog as raw route data.