TribeLines Privacy Policy

We do not collect contacts or address book, calendar, SMS, call logs, health or fitness data, financial or payment data (payments are not part of this beta), advertising identifiers, device IDs, browsing history outside the app, biometrics, or data on race, ethnicity, religion, politics or sexual orientation.

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.

We do not use any data for tracking or advertising. There are no ad SDKs, attribution SDKs or data brokers in this app, and we do not link your activity to other companies' apps or websites.

We do not sell your data and we do not share it with third parties for their own purposes. The services below process data on our behalf, only to deliver a function you asked for:

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: each pin expires at its set time — one hour by default, extendable by your chosen duration or streak rewards. Expired pins stop being served.
• A moving Tribe's breadcrumb trail exists only while that beacon runs and is discarded with the pin.
• Media lives in a private bucket and is served only through short-lived signed links. Downloads are gated by the pin's download permission and brand usage flags.
• 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.

Deleting your account removes your auth user, and that cascades to your profile, pins, media rows, messages, memberships and reactions.

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.

To request deletion during the beta, send a deletion request through the feedback form below and we will delete your account and content. A self-serve in-app "Delete my account" control and a public deletion-request URL are being added before store submission.

• 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 accounts are intended for users aged 13 and over.

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

Still to be finalised by the app owner before public launch, and deliberately not stated here until they are: the registered legal entity and address of the data controller, a dedicated privacy contact address, fixed retention windows for analytics and support records, and region-specific commitments such as a UK/EU representative and CCPA disclosures.