Last updated: August 24, 2026 Effective date: June 30, 2026
Roamily is an iOS app that helps parents and caregivers find family- and toddler-friendly activities and places in the Denver area. This policy explains what data the app collects, how it is used, and the choices you have.
Roamily is operated by Luapine LLC (Colorado). You can reach us at [email protected].
No account. No sign-up. No forms. We never ask for your name, email, or phone number.
If you email us — for example with the "Report an issue" button — we'll see the address you sent from and what you wrote, because that's how email works. We use it to answer you and fix the listing. Nothing else.
The app can ask to use your location for the map, and for sorting and filtering by distance. We never receive it — drive-time estimates go to Apple Maps, not to us.
We use a privacy-respecting analytics tool (PostHog) to count how the app is used. It records an anonymous device identifier — not you.
We don't sell your data. We don't show ads. We don't share data with advertisers.
Roamily has no accounts and does not request names, phone numbers, or other personally identifying information. The one exception: if you choose to email us (for example via "Report an issue"), we receive your email address and message — see "When you email us a report or feedback" below.
We use PostHog to understand which parts of the app are useful. PostHog generates an anonymous device identifier (a random string) the first time you open the app. We do not associate that identifier with your real identity — we never call PostHog's identify function.
The events we record are:
| Event | What it tells us |
|---|---|
| App opens, installs, and background events | How often the app is used (auto-captured by PostHog) |
activity_viewed |
Which activity you opened, its type, whether it was cancelled, and whether it had a registration link |
place_viewed |
Which place you opened, its category, and its activity type |
date_filter_applied |
Whether you filtered to a specific day, and how you got there — the date strip or the calendar. For a calendar pick, how many months ahead it was ("2 months out"), never the date itself |
setting_filter_applied |
Whether you filtered by indoor/outdoor |
place_filter_applied |
Which Places filter (category, indoor/outdoor, or cost) you tapped |
amenity_filter_applied |
Which amenity filter you toggled (e.g. restrooms) and whether it's on or off |
age_filter_applied |
Only whether a child-age filter is set — never the age itself, which stays on your device |
outbound_link_tapped |
When you tapped "Get Directions," "Learn More," or a website link, and to which activity/place |
add_to_calendar_tapped |
When you tapped "Add to Calendar" on an activity |
weekend_surface_viewed |
That you viewed the This Weekend reel, and how many picks it had |
weekend_highlight_tapped |
When you tapped a This Weekend pick, and its curated reason |
item_saved |
When you fave or un-fave an event or place. The collection itself never leaves your device — we only count that it happened |
places_view_toggled |
Whether you switched the Places tab between the list and the map |
report_issue_opened |
When you tapped "Report an issue," and which listing it was about — never anything about you |
card_impression |
Which activity or place cards actually scrolled into view, and on which screen — so we can tell "nobody tapped it" from "nobody saw it" |
photo_carousel_swiped |
That you swiped through a listing's photos, which listing, and how far through you got |
tab_selected |
Which tab you switched to |
place_sort_selected |
Which sort order you chose on the Places tab |
activity_sort_selected |
Which sort order you chose on the Events tab — soonest or nearest |
distance_filter_applied |
Which distance you picked (for example "within 10 miles"). Never where you are |
time_of_day_filter_applied |
Which times of day you filtered to — morning, afternoon, evening |
empty_results_shown |
That a screen came up empty, and how many filters were on — so we can tell "your filters were too tight" from "that week was genuinely quiet" |
share_initiated |
That you opened the iOS share sheet for a listing, and which listing |
share_completed |
That you went through with a share. We never see who you sent it to, or what you wrote |
share_cancelled |
That you opened the share sheet and backed out |
location_permission_resolved |
Whether you allowed or declined the location prompt. Only the answer — never a coordinate |
feedback_form_opened |
That you opened the feedback form. Nothing else — this event carries no details at all |
feed_load_failed |
That one of our data feeds failed to load, and why. Nothing about you |
app_session_ended |
How long a session lasted, how many tabs you visited, and which number session it was on this device |
PostHog also automatically collects technical context that comes with any mobile app usage: device model, iOS version, app version, and language/region. PostHog never receives your device's GPS location — see "When you use the map and distance features" for how location is handled.