TribeLines Privacy Policy

We do not import your phone address book, calendar, SMS or call logs. In-app Kin connections and private messages are stored separately. We do not request health records or biometric scans. Optional matching fields and user content may include sensitive information. Registration tokens and session identifiers are used; referring website URLs may be recorded.

To run the app: placing and showing pins, moving a Tribe beacon while you run one, delivering media and chat to your Kin, publishing your profile and articles, sending in-app notifications, generating optional AI text, answering your feedback, and measuring product usage so we can improve the beta.

TribeLines uses first-party usage measurement, not an advertising SDK. This does not mean all service-provider logging is absent. Partner use must be assessed separately before making an App Store tracking declaration.

The services below process data to provide app features. Authorised partner exports and API access may also provide PullingStrings with pseudonymised public check-in, venue, event and artist insights. Names, usernames, email addresses and media are excluded; stable coded identifiers, timestamps and venue coordinates rounded to three decimal places can still link activity across records. Pseudonymisation is not a guarantee of anonymity. Partner downstream use and retention require a separate agreement.

Content you choose to make public — your profile page, articles, and any Tribe you drop publicly — is visible to anyone with the link. All data is encrypted in transit (HTTPS/TLS) between the app, our backend, storage, and the services above.

• Tribes are ephemeral: live pins leave the active map at expiry or when the Chief disperses the Tribe. Map expiry is not immediate deletion of associated records; check-in, membership and analytics records may remain.
• Moving-beacon trails and last-known location records may remain after a beacon ends. No fixed automatic deletion period is currently established for these records.
• Media access depends on its type and audience. Private media uses access controls and signed or proxied delivery; profile images and public content may be visible publicly. A link expiring does not itself delete the file.
• Bug screenshots live in a separate private bucket readable only by admins through signed links, and are only created when you attach one.
• Profile details, articles, messages and your social graph are kept until you change or delete them, or until your account is deleted.
• Analytics, walkthrough and bug-report records do not yet have a fixed retention window in the beta. The owner is finalising these windows and a scheduled purge before public launch; until then you can switch analytics and the diagnostic trail off, and ask us to delete your records.

Access to every table is restricted by row-level security, and admin permissions are checked server-side against a dedicated roles table — never a client-side flag.

Use Delete my account on My Profile to remove your application content and close your login. The app runs an account-content purge before deleting the authentication account. This does not establish immediate deletion of every storage object, backup, processor record or export already received by a partner; contact us for questions about those records. Deleting an account should not be assumed to cancel a separately managed subscription.

You can also remove things individually at any time: delete a post or media item, end a Tribe early, clear any profile field, delete an article, block a Kin, or clear the diagnostic activity trail on your device.

Account deletion and requests, use Delete my account on My Profile, or send a deletion request through the feedback form below.

• Location: granted or revoked in your device settings; the app asks at the moment of use.
• Moving Tribes: opt-in per pin, and you can stop the beacon at any time.
• Camera, microphone and photo library: only used when you choose to post media.
• Product analytics: opt out on the Privacy & permissions screen.
• Diagnostic activity trail: switch off or clear on the same screen; nothing is sent unless you submit a report.
• Notifications and walkthrough alerts: opt-in, and can be turned off in your profile.

TribeLines is not directed at children, and the store launch is intended for adults aged 18 and over. The current signup does not establish verified age; contact us about an underage account.

Reach us about privacy, deletion or a safety concern through the feedback form, which goes to the same inbox as bug reports.

You can request access, correction, deletion or a copy of your personal information through feedback, subject to applicable law and identity verification. Fixed retention windows, backup deletion coverage and partner downstream-use agreements are not yet established here; we do not promise an unverified deletion deadline. You may raise a concern with your local data-protection authority.