Who is responsible
TribeOut is operated by Andrius Krivicius, an individual operating in the United Kingdom and the data controller. TribeOut is the website and trading name, not a registered company name claimed here.
Contact support@tribeout.co.uk for support, privacy questions or a data request. You do not need a TribeOut account to email a request. Signed-in members can also use Help & requests.
Information we use
- Account information: name, email, verified sign-in identifier, account status and permissions. Passwords pass through the secure server to Supabase Auth; they are not stored in your saved account content. TribeOut does not receive your ChatGPT password or chat history.
- Personal organisation: saved places, plans, journals, collections, preferences and files you choose to save. Booking and expense records are personal notes; TribeOut does not process payments.
- Community: chosen profile details, friends, groups, messages, invitations, meetup responses, reviews and contributions.
- Support and safety: requests, reports, appeals, moderation decisions and limited access/security records.
- Technical data: connection and device information used by hosting and sign-in providers; optional usage events only when you allow analytics.
Information comes from you, service providers and people who interact with or report content concerning you. Do not post identity documents, health records or unnecessary sensitive personal information. A dietary option is not a declaration about your religion or health, and we do not use it to infer those characteristics.
Why we use information
- Account and requested features — contract
- Provide sign-in, saved content, messages and sharing you request under the terms of use. These features need the relevant identity and content to work.
- Service protection and support — legitimate interests
- Keep the service reliable, prevent misuse, respond to enquiries and reports, moderate submissions and maintain proportionate accountability records. These interests are balanced against privacy, with limited access, minimisation, review and objection routes.
- Optional analytics — consent
- Measure opted-in usage, banner engagement and combined place popularity. You can decline or withdraw without losing ordinary features.
- Binding legal requirements — legal obligation
- Use or disclose only the information necessary to meet a legal requirement that applies to us.
No marketing email programme is enabled. The membership declaration is self-declaration, not identity-document verification; its date and policy version are recorded, not date of birth.
Providers and overseas processing
Cloudflare Workers, D1 database and private R2 storage host the website and its content. Supabase Auth handles sign-in; the selected project region is London. Resend delivers authentication emails, and Zoho Mail handles the support inbox. Cloudflare Access protects restricted deployments separately from the TribeOut account login.
These providers and their subprocessors may process information outside the United Kingdom. A London project or European email-sending region does not mean all processing remains there: Resend states that its stored data is in the United States. Provider data-processing terms describe contractual transfer safeguards, including UK transfer provisions where applicable. Ask support for information about the arrangements relevant to your request.
Maps load OpenStreetMap tiles and some images load from Unsplash, exposing connection details such as your IP address to those services. Requested transport searches send journey points, date/time and access options to Transport for London. External venue and booking links lead to providers with their own privacy practices.
Your choices and browser storage
Near me asks for browser location permission to sort nearby places or show a position. You can refuse and search by area instead. Precise coordinates are not included in optional analytics.
A necessary Secure, HttpOnly session cookie keeps you signed in. Provider tokens are encrypted on the server, not held in browser storage. A separate short-lived cookie binds confirmation and reset links to the requesting browser. Hosting/access services also use necessary session technology. The offline helper caches a generic offline page and icon, not private account content. Demonstration data and older favourites may use browser storage; unsent chat drafts stay in the current tab.
Optional analytics are off until an eligible signed-in member chooses to allow them. They use a pseudonymous identifier and limited event types, not raw searches, emails, IP addresses or precise locations in the analytics event table. The owner sees combined reports. No analytics cookies are used by this feature. Necessary provider logs are separate.
Choose Decline / withdraw and erase my analytics in the footer to stop optional collection and remove your events. Withdrawal does not undo earlier lawful processing.
Retention and deletion
Saved content normally remains until you remove it or delete your site account. Leaving a group or ending a friendship does not remove all previous contributions. Deleted messages may leave a placeholder. Copies held by recipients may remain outside our control.
Site-account deletion removes the main account content, associated messages and owned groups through the deletion workflow. It does not delete your Supabase Auth identity. Contact support for coordinated full-account removal, including if you cannot sign in. Separate identity records, justified restriction records and shared-file references require operator handling; the dashboard does not provide a one-click complete erasure of every service.
Normal sessions expire after seven days, recovery sessions after 15 minutes, pending confirmation/reset requests after 30 minutes and rate-limit buckets after 15 minutes. Bounded cleanup is configured every 15 minutes; expiry is not a promise of immediate removal of every physical copy.
Optional analytics have a 180-day window. Older events are removed when analytics processing runs, not by a guaranteed daily job; withdrawal or site-account deletion removes your events.
The selected retention target is three calendar months after closure for support requests, after final resolution including appeals for reports, and after creation for routine site-controlled security records. Case deletion is not currently automatic: the operator must review and carry out justified removals. Open cases and documented legal or investigation holds may need longer retention, with a reason and review date. Active access restrictions are reviewed separately and are not erased merely because an account is deleted.
Files follow their owning content and surviving shared references. Provider backups and logs have separate retention windows; deletion from the working service does not immediately erase all backups. Restored data must be reconciled with earlier deletion requests. Contact support for the retention information relevant to your data.
Requests and rights
Depending on the circumstances, you may request access, correction, erasure, restricted processing or portable information. You can object to processing based on legitimate interests and withdraw optional analytics consent. Email support or use Help & requests. We may ask for proportionate identity confirmation, never your password or reset link.
Account exports are useful snapshots, not necessarily every record or uploaded file. Contact us for a fuller request. Legal exceptions may apply and should be explained. You may complain directly to the Information Commissioner’s Office or another applicable authority.
Support and updates
Andrius Krivicius personally checks support@tribeout.co.uk and the owner dashboard every day. Support hours: every day, 08:00–18:00 UK time (GMT or BST as applicable).
We aim to respond within four working hours during these hours, not to resolve every issue within that time. Some issues may take longer to resolve. There is no backup support cover; replies may take longer when Andrius is unavailable. This is manual support and moderation, not continuous monitoring.
TribeOut is not an emergency-response service. If someone is in immediate danger, contact local emergency services rather than waiting for a TribeOut reply.
Material changes to this notice will be explained where appropriate, with a new choice if consent is required. Reading it is not consent to optional analytics.