RideMemo helps you discover, save, compare, and share cycling routes. This policy explains how information is handled when you use ridememo.com.
Information we collect
- Google sign-in: your Google account identifier, verified email address, name, and profile picture when provided by Google. RideMemo does not receive your Google password or request access to your Gmail, contacts, or Google Drive.
- Your account: profile details you enter, account permissions, saved rides, collections, and sign-in session records.
- Route content: GPX tracks, coordinates, activity timestamps when present, route descriptions, notes, photographs you upload as route content, and import details. Routes can reveal places you visit, including a home or work address.
- Optional connected services: if you connect Strava, we store its account identifier, connection status, granted permissions, and encrypted access and refresh tokens. We retrieve route or activity information when you use connected features. Imports from other services process the links, files, and metadata you supply.
- Technical information: our hosting and service providers may process IP addresses, request URLs, browser information, and operational or security logs when they serve requests.
How we use information
We use information to sign you in, manage your account, save and display rides, process route imports, calculate route information, provide maps, enforce permissions, maintain security, respond to requests, and operate the service.
If AI route suggestions are enabled and requested, route measurements, location labels, notes, and source metadata may be sent to OpenAI to generate proposed descriptions. Do not include sensitive personal information in notes submitted for this feature. Google sign-in credentials are not sent for AI suggestions.
What other people can see
Published route guides, their route geometry, notes, images, and displayed author information are public. Drafts and submissions are restricted according to account permissions. Editors can review content submitted for publication.
Collections are shared through links. Anyone with a collection link can view the collection's shared information and published rides; recipients may forward that link. Do not treat a shared collection link as confidential. Review tracks, timestamps, photographs, and descriptions before uploading or publishing them.
Cookies and information stored on your device
RideMemo uses essential cookies to complete Google sign-in and keep you signed in. The temporary sign-in cookie lasts up to 10 minutes; the RideMemo session cookie lasts up to 30 days. Signing out revokes that session. These cookies are managed by RideMemo, not Supabase Auth.
Your browser also stores display preferences and, if you download routes, offline route data and map tiles. You can remove these by clearing site data in your browser or using available offline controls.
Photos you select for a flyover are processed locally in your browser. Reduced copies and placement information may be stored on that device with a one-day expiry and are cleared when the app next checks that expiry. This differs from photographs you explicitly upload as route content, which are stored on our servers. Exported files remain wherever you save them.
If you enable location features and grant browser permission, your location is used to show your position on the map. We do not store a continuous location history for this feature. Map providers can infer the area you view from requested map tiles.
Service providers and disclosures
We use Google for authentication, Vercel for hosting, and Supabase for database and file storage. Maps, terrain, and geographic lookups use providers such as OpenFreeMap, OpenStreetMap/Nominatim, AWS-hosted terrain data, and MapTiler when configured. These providers receive the information needed to answer requests, such as IP addresses, map areas, or lookup coordinates. Optional imports and AI features involve the providers described above.
We do not sell personal information or share it for targeted advertising. We may disclose information when required by law, to protect rights and security, or to service providers helping us operate RideMemo. Providers may process data outside your country under their own applicable policies and safeguards.
Retention and security
We retain account and route information while it is needed to provide the service, and may retain limited records for security, legal obligations, or resolving disputes. Sessions expire after 30 days; expired session records are removed during subsequent account registration or sign-in processing. Backups and provider logs may retain copies for their normal retention periods.
We use HTTPS, restricted database permissions, opaque session tokens stored as hashes, and encryption for stored connected-service tokens. No system can guarantee absolute security.
Your choices and requests
You can edit available profile fields, manage your collections, sign out, and disconnect Strava from your account. Disconnecting stops use of the saved connection; it does not automatically delete routes you already imported. You can also revoke app access through the provider's account settings.
You may request access to, correction of, or deletion of your personal information and account. Subject to applicable law, you may also have rights to portability, restriction, objection, withdrawal of consent, or a complaint to your local data protection authority. We may verify ownership before acting on a request.
Removing an account may leave public route guides in place with the account association removed. Tell us if your request also concerns personal information in a published guide. Copies saved or shared by other people may remain outside our control.
For questions about these policies, privacy requests, or account deletion, emailsupport@ridememo.com. Include the email address used for your RideMemo account; we may ask you to verify ownership.
Children
RideMemo is not intended for children under 13, or below the age at which they can consent to this service under applicable law. We do not knowingly collect their personal information. Contact us if you believe a child has provided information.
Changes to this policy
We may update this policy as the service changes. The effective date identifies the current version. We will provide additional notice of material changes when required by law.
See also our Terms of Service.