1. Information you provide
Depending on the features you use, you may provide:
- Name, display name, username, email address, phone number, date of birth, biography, travel preferences, and profile photo
- Emergency-contact name and phone number
- Additional verified email addresses used for itinerary import
- Trips, destinations, dates, schedules, itinerary items, reservation details, notes, and locations
- Trip expenses, amounts, descriptions, payer information, and cost-sharing details
- Packing lists and presets
- Journals and journal entries
- Invitations and attendance or RSVP responses
- Trip chat messages
- Imported itinerary information
- Forwarded-email content used for itinerary import
Some profile fields and features are optional. An email address, username, and account identifier are required to create and operate a RambleWise account.
2. Email and pasted-text import
You may voluntarily forward travel emails or paste travel text so RambleWise can extract itinerary details. Forwarded email data may include the sender, recipients, subject, plain text, HTML, attachment count, and extracted itinerary information.
Raw forwarded-email content may remain stored while an import awaits review, fails processing, or remains unreviewed. After a successful import, raw email content is removed from the inbox record. Discarding an inbox item deletes that item, and deleting an account removes pending imported-email content associated with the account.
Email attachment bytes may reach the inbound processing function, but they are streamed and are not intentionally stored as files. Pasted travel text is processed to create structured itinerary suggestions and is not intentionally stored as raw text by RambleWise after processing. Pasted or forwarded travel text may be sent to OpenAI for extraction.
3. Location information
Local location use
You may grant approximate or precise location access. Your current location may be used locally to center the map or show your position. This local-only map positioning is not intentionally stored by RambleWise unless you enable live location sharing or a search request includes your location.
Live location sharing
Live location sharing is optional and controlled by you. When it is enabled, the latest latitude, longitude, timestamps, and limited profile information may be stored in Firebase Realtime Database. Your user ID and the trip ID are associated with the database path, and your live location is visible to permitted trip participants.
RambleWise stores the latest reported location rather than a historical movement trail. Live-location records are removed when sharing stops, expires, disconnects, becomes stale, the trip is deleted, or the account is deleted, subject to normal service operation.
4. Search and map services
RambleWise uses search terms, destinations, place identifiers, and optional coordinates to provide city, airport, destination, and place-search features. Active or potentially active services include:
- Google Places
- Google Geocoding
- Typesense
- Mapbox Geocoding as a configured fallback when enabled
- OpenStreetMap map tiles
- Wikipedia and Wikimedia content and images
RambleWise does not provide a persistent in-app search-history feature. External providers may process and retain search requests according to their own terms and requirements.
5. Account, device, and technical information
RambleWise may process:
- Firebase user ID, authentication status, and email-verification status
- Push-notification token, platform, and token creation and last-seen timestamps
- App Check and Play Integrity security signals
- Active, background, or offline presence state
- Current app route, trip, or chat context used for app functionality and notification behavior
- Server request, response, error, trace, and diagnostic metadata
- IP address or device-related information processed automatically by service providers
RambleWise does not currently use Firebase Analytics or Firebase Crashlytics. RambleWise may still maintain operational server logs and diagnostic metadata for reliability, troubleshooting, security, and abuse prevention.
6. Photos, files, and attachments
You may upload a profile photo. Profile photos are stored in Firebase Storage in multiple resized versions.
RambleWise does not currently offer a general user document-upload feature. Trip-chat “attachments” are structured references or snapshots of planned and suggested places rather than uploaded files. Forwarded email attachment bytes may pass through the inbound processing service but are not intentionally stored as files.
7. Financial information
You may voluntarily enter trip expenses, amounts, descriptions, payer information, and cost-sharing details. This information is used only for trip planning and expense functionality.
RambleWise does not currently collect payment-card numbers, bank-account information, credit scores, Google Play Billing purchase data, subscription data, or in-app payment credentials. User-entered trip expenses are not payments made through RambleWise.
8. How information is used
RambleWise uses information to:
- Create and manage accounts
- Authenticate users, verify email addresses, and reset passwords
- Provide trips, itineraries, maps, expenses, packing, journals, invitations, attendance, chat, imports, search, and live-location features
- Deliver notifications
- Personalize profile and travel-related app experiences
- Protect the service using authentication, authorization, App Check, and abuse-prevention controls
- Maintain reliability, investigate errors, and troubleshoot service failures
- Respond to support, privacy, and deletion requests
- Comply with legal obligations
10. Data retention
- Account and profile data generally remain while your account is active unless you edit or delete them.
- Trips, itinerary items, expenses, packing lists, journals, chat, invitations, attendance records, and other user-generated content remain until deleted, cleaned up, or the account is deleted, subject to shared-content rules.
- Trips with no remaining members may be retained temporarily for cleanup before permanent deletion.
- Forwarded-email content may remain while pending, failed, or unreviewed. Raw forwarded-email content is removed after successful import.
- Live location stores the latest coordinate and is removed through stop, expiry, disconnect, stale cleanup, trip deletion, or account deletion mechanisms.
- Search queries are not stored as a persistent RambleWise search-history feature, though providers may process them under their own terms.
- Operational logs and provider-held information may remain according to provider, security, legal, and operational requirements.
11. Account and data deletion
You can delete your account in the RambleWise app through the ellipsis menu and “Delete Account.” If you cannot access the app, email support@ramblewise.com from the email address associated with your account. For detailed instructions, visit the account deletion page.
Once confirmed, the RambleWise account and private account data are deleted immediately after the deletion process completes. Account deletion is permanent and cannot be undone.
Shared itinerary items, shared expenses, attendance records, and trip chat messages may remain for other trip participants. Trips with no remaining members may be retained temporarily for cleanup. Service-provider data may be subject to separate operational, security, or legal retention.
12. Security
RambleWise uses HTTPS/TLS for app-controlled network communications, and Typesense is accessed through HTTPS. Firebase security rules, authentication, authorization, and App Check are used to restrict access and protect requests. Sensitive credentials are stored outside client source code where applicable.
No method of transmission or storage is completely risk-free.
13. Children and age
RambleWise is intended for users aged 18 and older. RambleWise is not designed for children, and we do not knowingly seek to collect personal information from children. If you have concerns involving a minor’s information, contact support@ramblewise.com.
14. International processing
Information may be processed in the United States and other locations where RambleWise’s service providers operate, subject to applicable safeguards and law.
15. Policy changes
RambleWise may update this Privacy Policy as the service or legal requirements change. When updates are made, the effective date at the top of this page will be changed.
16. Contact
RambleWise
support@ramblewise.com