Privacy & permissions

What TribeLines collects, and what you can switch off

This page is maintained by the TribeLines team to answer, in plain English, what the app collects while you're using it. It describes the controls in the app today — it isn't a certification or an audit.

The five things we handle

Location

What: Location for pins, routes, proximity check-ins, moving beacons and the public or connected-Kin sharing you enable.
Why: Placing a pin on the map and letting Kin find it. Moving Tribes exist for run clubs and mobile Clans.
How long: Pins leave the active map at expiry or dispersal. Trails and check-in records may remain; map expiry is not database deletion. Updates depend on enabled features, permissions and device support.
Opt out: Deny or revoke the location permission in your device settings. Stop a moving Tribe from its card and switch off location sharing; ending a pin removes it from the active map, not necessarily every associated record.

Photos, video and audio

What: Media you post to TribeLines, profiles, galleries, articles, hotspots or private messages.
Why: It's the content your Kin came to see. Download permission is set by you per Tribe.
How long: Retention depends on content type and deletion. Expiring a pin or signed link does not automatically delete a stored file.
Opt out: Don't post, or delete a post to remove it. Turn off downloads for a Tribe so Kin can view but not save. Report anything that shouldn't be there and it goes to moderation.

Messages and profile

What: Tribe and private Kin messages, profile and matching fields (including optional sensitive identity preferences), music, films, hotspots, social connections and articles.
Why: Running the chat and your public profile page.
How long: Profile and message records may remain until edited or deleted. Public content is visible to others; private messages and member content have separate access controls.
Opt out: Edit or clear any profile field, delete articles, block a Kin, or ask us to delete your account and everything attached to it.

Product analytics

What: Events, page paths, referrers, searches, interactions, walkthrough progress, user and session identifiers.
Why: Product measurement and authorised pseudonymised partner insights. Stable partner identifiers may link records; they are not guaranteed anonymous.
How long: There is no fixed retention period established for all usage records; request access or deletion through feedback.
Opt out: The switch below stops product events on this device. Walkthrough events are separate and are not currently disabled by that switch.

Diagnostics and bug reports

What: Device type, app version, the last 30 screens/errors on this device, and a screenshot only if you attach one.
Why: Reproducing what broke when you tap the bug button.
How long: Only sent when you submit a report; screenshots go to a private, admin-only store.
Opt out: Switch the activity trail off below, or clear it. Don't submit a report and nothing is sent.

Your controls

Location permission

Held by your phone, not by us. Change it in your browser or OS settings for TribeLines — the app keeps working, you just can't drop or move a Tribe until it's allowed again.

Unknown

Product analytics

Counts like sign-ups, pins dropped and shares — used to size the beta. No message or media content, ever.

Diagnostic activity trail

The last 30 screens and errors on this device, attached only when you send a bug report. Never leaves the device otherwise.

Questions, deletion or a concern

Use Delete my account on My Profile, or send a deletion request or privacy concern through feedback. See the full policy for processor, partner and retention limitations.

Contact the team Read the full privacy policy