Last updated: October 9, 2026
1. Who is responsible for your data
TRIBL ("TRIBL", "we", "us") is operated by Tribl AB, a Swedish company (company number 559427-1511), Kungsgatan 10, 111 43 Stockholm, Sweden. Tribl AB is the data controller for the personal data described in this notice.
For any privacy question or to exercise your rights, email info@tribl.app. For help with your account, you can also write to support@tribl.app.
This notice explains what personal data we process when you visit tribl.app (including our blog), create a Creator account, support a Creator as a Fan, book a session with a Creator, fill in a form on a Creator's page, join a waitlist, or contact us; why we do it; which service providers help us; and what rights you have. It should be read together with our Terms & Conditions and Cookie Notice. Words such as "personal data" and "processor" are explained in section 15.
2. The personal data we process, in short
Creators (people with a TRIBL account):
- Account data: username, email address, phone number, password (stored only as a secure hash), sign-in method (email, Google or Apple), country, currency and account settings.
- Profile data you choose to publish: name, profile and cover photos, bio, links, social media handles, memberships, gift-card blocks, media kit and other page content.
- Identity verification data, needed before you can receive payouts: name, date of birth, nationality, address and proof of address, ID document details and images, a selfie and liveness check, and the result of sanctions and politically exposed person (PEP) screening. For Creators in the USA, the Social Security Number our payment provider requires, which we pass to the payment provider and do not keep.
- Payout data: bank account details (account holder, IBAN, SWIFT/BIC, account number), crypto wallet addresses, and your account ID with our payment provider.
- Transaction data: tips, memberships, gift cards and other payments you receive, our fees, payouts and balances.
- Emails you send to your Fans through TRIBL and the templates you design.
- Booking data, if you offer sessions: what you offer (description, images, price, length and where it takes place, such as a meeting link), your available hours and time zone, the automatic messages you set, and the bookings Fans make with you.
- Connected calendar data, if you connect Google Calendar or Microsoft Outlook: the email address of the account you connect, the calendars you choose, the times you are busy on them (only when each starts and ends), and the events we add to your calendar for your bookings (see section 3.18).
- Connected video data, if you connect Zoom: the email address, user and account IDs and plan of the Zoom account you connect, and the meetings we create for your bookings (see section 3.18).
- Calendly data, if you connect Calendly: the email address of your Calendly account, the times you are busy in Calendly, and your upcoming Calendly bookings (what was booked, when, and the name and email address of who booked it), shown to you in Bookings and not stored (see section 3.18).
- Activity data: when you last used your account (signing in, receiving payments, payouts), so we can apply the retention rules in section 9.
Fans (people who tip, join a membership, buy a gift card or book a session):
- Name, email address and, where needed for the payment, phone number, billing address and date of birth.
- Transaction data: what you paid, to which Creator, when and how. Card details are entered directly with our payment provider; TRIBL never sees or stores your full card number.
- The IP address, approximate location and device type used at checkout, for fraud prevention.
- For gift cards: the name you give as the sender.
- For bookings: the session and time you chose, your time zone, your answers to the Creator's questions and, if the Creator asks for it, your billing address. If the Creator has connected Google Calendar or Microsoft Outlook, your name and email address, the session and its time are added to the event in the Creator's own calendar (see section 3.18).
- In some cases, identity verification data (as above) when it is required for a payment.
- Emails a Creator you support sends you through TRIBL, which the Creator can personalise with the details you gave at checkout (such as your name).
Everyone who visits tribl.app:
- Technical data: IP address, approximate location (country and city derived from the IP address), browser and device type, and the pages you visit.
- When you view a Creator's page or click one of their links, an anonymous event with the country, city and device type, so the Creator can see statistics about their audience (see section 3.7).
- Cookie and similar data, as described in our Cookie Notice. Analytics and marketing tools are only used if you consent.
People who fill in a form on a Creator's page: the answers you give, which are whatever the Creator asks for (often your name, email address, phone number or a message); whether you ticked a box to hear from the Creator, and the exact words you agreed to; when you sent the form; and your device type (see section 3.16).
People who buy a digital product from a Creator: your name and email address, your answers to the Creator's checkout questions, what you bought and what you paid, your confirmation that you want access straight away and lose your right of withdrawal (with the time and the exact wording), your device type, and how often you opened your link and downloaded (see section 3.17).
People who join a waitlist: your email address, the list you joined, whether you are a creator or a brand (Dealroom), the idea you type for our AI builder if you choose to, the page you signed up on, and when you joined (see section 3.14).
Anyone who contacts us: your message, your contact details and our reply.
We do not ask for special categories of data (such as health, religion or sexual orientation). Identity verification involves comparing your face with your ID document; see sections 3.3 and 5.
3. How and why we process your data, service by service
Below, our processing is grouped by purpose. Under each purpose we list every service provider involved, what it does, the personal data it handles, the legal basis, and where the data is processed. Open a purpose to see the details. Unless we say otherwise, providers act as our processors: they may only use the data on our instructions, under a data processing agreement. Providers marked as independent controllers decide themselves how they use the data, under their own privacy policy.
3.1 Registration and sign-inTRIBL account · Sign in with Google · Sign in with Apple · Google reCAPTCHA
We create and secure your account, verify your email address and phone number with one-time codes (sent as described in section 3.6), and keep you signed in.
TRIBL account
- Provider
- Tribl AB (stored with the hosting providers in section 3.5)
- What it does
- Creates your account, checks your password or one-time code, and keeps you signed in for up to 24 hours at a time.
- Personal data
- Username, email address, phone number, password hash, sign-in method, one-time codes, and the IP address used at signup.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU
Sign in with Google
- Provider
- Google Ireland Limited, Ireland (independent controller)
- What it does
- Lets you sign up or sign in with your Google account. You are sent to Google’s sign-in page and Google tells us who you are.
- Personal data
- Your name, email address, profile picture and Google account ID. Google also sees that you are signing in to TRIBL.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU and USA
- Privacy policy
- policies.google.com/privacy
Sign in with Apple
- Provider
- Apple Distribution International Ltd., Ireland (independent controller)
- What it does
- Lets you sign up or sign in with your Apple Account. You are sent to Apple’s sign-in page and Apple tells us who you are.
- Personal data
- Your name, email address (or an Apple relay address if you choose to hide it) and Apple account ID.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU and USA
- Privacy policy
- www.apple.com/legal/privacy/
Google reCAPTCHA v3
- Provider
- Google Ireland Limited, Ireland
- What it does
- Runs on the Creator signup page and scores whether the visitor is a human or a bot, to block automated signups.
- Personal data
- IP address, browser and device information, mouse and keyboard interaction on the page, and Google cookies.
- Legal basis
- Our legitimate interest in preventing fake and automated accounts (Art. 6(1)(f)).
- Place of processing
- EU and USA
- Privacy policy
- policies.google.com/privacy
3.2 Payments and payoutsStripe · IBAN API · Zippopotam.us
We use payment providers to take payments from Fans and to pay Creators. The providers below may change as we develop TRIBL; we will update this section before a new payment method goes live.
Stripe
- Provider
- Stripe Payments Europe, Limited, Ireland. Stripe acts as our processor for payment processing and as an independent controller for its own legal duties (such as anti-money-laundering checks, fraud prevention and verifying Creators who receive payouts through Stripe Connect).
- What it does
- Card and wallet payments (including Apple Pay and Google Pay), recurring membership payments, the gift-shop checkout, Creator payout accounts, bank payouts, refunds and referral rewards. Stripe’s script is loaded on Creator pages, the gift checkout and the Creator earnings pages, where it collects device signals to detect fraud.
- Personal data
- Fans: name, email address, card details (entered directly with Stripe), amount, IP address and device data. Creators: name, date of birth, address, email address, phone number, the IP address used to accept Stripe’s terms, bank account details, ID document images and, for Creators in the USA, the Social Security Number, as Stripe requires to open a payout account; balances and payouts.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)). For Stripe's own checks: Compliance with a legal obligation (Art. 6(1)(c)).
- Place of processing
- EU and USA
- Privacy policy
- stripe.com/privacy
IBAN API
- Provider
- IBAN API (ibanapi.com)
- What it does
- Checks that a bank account number (IBAN) you add for payouts is valid and looks up the bank.
- Personal data
- The IBAN you enter.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- Not stated by the provider
- Privacy policy
- www.ibanapi.com
Zippopotam.us
- Provider
- Zippopotam.us
- What it does
- Looks up the city and state for a US ZIP code when a Creator in the USA adds a payout address.
- Personal data
- The ZIP code.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- USA
3.3 Identity verification and anti-money-laundering screeningDidit · Stripe
Before a Creator can receive a payout, and in some cases before a Fan can make a payment, we must confirm who they are and check them against sanctions and politically exposed person (PEP) lists.
Didit
- Provider
- Didit Identity Spain, S.L., Barcelona, Spain
- What it does
- Runs the identity check on Didit’s own page: you photograph your ID document and proof of address and take a selfie; Didit checks the document is genuine, compares your face with the document photo, checks that you are a live person, and screens you against sanctions and PEP lists. Didit may email you about your verification, and sends us the result.
- Personal data
- Your account ID and email address; ID document images and details (name, date of birth, nationality, document type and number, issuing country, expiry date); proof-of-address document and address; selfie and liveness images or video; the face comparison result; sanctions and PEP screening results; IP address and device data.
- Legal basis
- Compliance with a legal obligation (Art. 6(1)(c)). Where anti-money-laundering rules do not apply to us directly, our legitimate interest in preventing fraud, impersonation and financial crime, and meeting the requirements of our payment providers (art. 6(1)(f)).
- Place of processing
- EU
- Privacy policy
- didit.me/terms/privacy-policy
Stripe (verification data)
- Provider
- Stripe Payments Europe, Limited, Ireland (independent controller for its own checks)
- What it does
- To open a Creator’s payout account, we pass Stripe the verified identity details and copy the ID document images from Didit to Stripe, as Stripe requires by law. We do not do this for Fans.
- Personal data
- Name, date of birth, address, ID document images and details, verification status.
- Legal basis
- Compliance with a legal obligation (Art. 6(1)(c)).
- Place of processing
- EU and USA
- Privacy policy
- stripe.com/privacy
3.4 Content moderation and platform safetyOpenAI · Amazon Rekognition · TRIBL team review
Content published on TRIBL is checked automatically before it goes live, to stop illegal, explicit or harmful content, scams and impersonation. See section 5 for how these checks affect you.
OpenAI moderation
- Provider
- OpenAI Ireland Ltd, Ireland
- What it does
- Screens text entered on TRIBL with OpenAI’s moderation model, and checks web addresses with an OpenAI language model, to detect explicit, harmful or fraudulent content. This covers what Creators publish (username, name, bio, links, memberships, media kit, emails to Fans) and what is typed into forms (such as the username and email address at registration, the name, email address and address a Fan gives at checkout, and the payout address and wallet addresses a Creator adds). OpenAI does not use data sent through its business API to train its models.
- Personal data
- The text being checked, which can include names, usernames, email addresses, postal addresses and wallet addresses.
- Legal basis
- Our legitimate interest in keeping TRIBL safe and lawful (Art. 6(1)(f)).
- Place of processing
- USA
- Privacy policy
- openai.com/policies/eu-privacy-policy
Amazon Rekognition
- Provider
- Amazon Web Services EMEA SARL, Luxembourg
- What it does
- Screens images Creators upload (such as profile and cover photos and link images) for explicit content. Images that pass are also compared, by face, with Amazon’s index of well-known public figures, to help detect people impersonating celebrities. A match is sent to our team for review; it is not used to identify you.
- Personal data
- The uploaded image, including any face in it. For a celebrity match: the public figure’s name, the confidence of the match and the position and features of the face in the image.
- Legal basis
- Our legitimate interest in preventing explicit content and impersonation (Art. 6(1)(f)).
- Place of processing
- EU
- Privacy policy
- aws.amazon.com/privacy/
TRIBL team review
- Provider
- Tribl AB
- What it does
- Our team reviews flagged content and celebrity matches, and decides whether to remove content or restrict an account.
- Personal data
- The flagged content or image, the automated result, your username and email address, and earlier flagged content on the same account.
- Legal basis
- Our legitimate interest in keeping TRIBL safe and lawful (Art. 6(1)(f)).
- Place of processing
- EU
3.5 Hosting and infrastructureAmazon Web Services · MongoDB Atlas · Vercel · Content loaded from other sites
These providers run the servers, database and network that TRIBL is built on. They store or transmit all the data described in section 2, but do not use it for their own purposes.
Amazon Web Services (Elastic Beanstalk, S3, Systems Manager)
- Provider
- Amazon Web Services EMEA SARL, Luxembourg
- What it does
- Runs our application servers and their logs, stores uploaded images and videos and payment receipts, and delivers them to your browser.
- Personal data
- All data described in section 2, including uploaded files and receipts; the IP address of anyone loading images from TRIBL.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU (Germany and Sweden)
- Privacy policy
- aws.amazon.com/privacy/
MongoDB Atlas
- Provider
- MongoDB
- What it does
- Hosts our database.
- Personal data
- All account, profile, transaction, verification and waitlist data described in section 2.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU
- Privacy policy
- www.mongodb.com/legal/privacy/privacy-policy
Vercel
- Provider
- Vercel Inc., USA
- What it does
- Hosts and delivers the tribl.app website. Vercel’s network tells us which country a request comes from, which we use to block access to parts of TRIBL from countries where we do not offer the service.
- Personal data
- IP address, country derived from it, browser information and the pages requested.
- Legal basis
- Our legitimate interest in running a fast and secure website and complying with sanctions and local law (Art. 6(1)(f)).
- Place of processing
- Global edge network, USA
- Privacy policy
- vercel.com/legal/privacy-policy
Content loaded from other sites
- Provider
- jsDelivr, flagcdn.com, GitHub Pages, Wikimedia, Reloadly, Instagram (Meta), TikTok and YouTube (Google)
- What it does
- Some images are loaded by your browser directly from other companies’ servers: emoji images in the Creator dashboard (jsDelivr); country flags (flagcdn.com, GitHub Pages, Wikimedia); gift-card images (Reloadly); and, on media kits, thumbnails of a Creator’s posts (Instagram, TikTok and YouTube). These companies receive your IP address, as with any web request; they do not set cookies on tribl.app.
- Personal data
- IP address and browser information sent with the image request.
- Legal basis
- Our legitimate interest in showing the page correctly (Art. 6(1)(f)).
- Place of processing
- Global content networks, including the USA
3.6 Email and SMSAmazon SES · Amazon SNS · Beefree
Amazon Simple Email Service (SES)
- Provider
- Amazon Web Services EMEA SARL, Luxembourg
- What it does
- Sends our emails: verification codes, receipts, membership and payment notices, gift-card codes, security and service messages, internal notices to our team (for example about new signups, payout requests and blocked accounts), and the emails Creators write to their Fans through TRIBL, which can be sent straight away, scheduled, or triggered automatically (for example when a Fan tips or joins a membership).
- Personal data
- Recipient email address and name, the content of the email (for internal notices, for example payout bank details), and delivery status.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)). Emails a Creator sends to their Fans are written and sent at the Creator's choice; we send them on the Creator's behalf.
- Place of processing
- EU
- Privacy policy
- aws.amazon.com/privacy/
Amazon Simple Notification Service (SNS)
- Provider
- Amazon Web Services EMEA SARL, Luxembourg
- What it does
- Sends one-time verification codes by SMS.
- Personal data
- Phone number and the code.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU
- Privacy policy
- aws.amazon.com/privacy/
Beefree email editor
- Provider
- BEE Content Design, Inc., USA (independent controller for the technical data it collects)
- What it does
- The drag-and-drop editor Creators use to design emails to their Fans. It runs in a frame from Beefree inside the Creator settings.
- Personal data
- The email design and content you edit (which can contain placeholders for Fan details, not the details themselves), and your IP address.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- USA
- Privacy policy
- beefree.io/privacy
3.7 Location lookups and Creator audience statisticsIPinfo · ipify · jsonip.com
When you open a Creator's page, your browser looks up the approximate location of your IP address. We store an event with the country, city and device type (no IP address, name or account) so the Creator can see where their visitors and link clicks come from. We use the same lookups to pre-fill your country in forms, to show the gift cards available in your country, to work out which payout fees apply, and, at checkout, to help detect fraud.
IPinfo
- Provider
- IPinfo Inc., USA
- What it does
- Turns an IP address into an approximate location (country, region and city).
- Personal data
- IP address.
- Legal basis
- Our legitimate interest in giving Creators audience insights, showing you the right country settings, and preventing payment fraud (Art. 6(1)(f)).
- Place of processing
- USA
- Privacy policy
- ipinfo.io/privacy-policy
ipify and jsonip.com
- Provider
- ipify; jsonip.com
- What it does
- Tell the browser its own public IP address, which is then passed to the location lookup or stored with a payment for fraud prevention and accounting.
- Personal data
- IP address.
- Legal basis
- Our legitimate interest in preventing payment fraud and giving Creators audience insights (Art. 6(1)(f)).
- Place of processing
- USA
3.8 Media kitTRIBL · Phyllo (previously)
Media kit
- Provider
- Tribl AB
- What it does
- Creators can publish a media kit with their audience statistics, collaborations and selected posts. You enter the statistics yourself. If you add a brand you have worked with, our server fetches that brand’s logo from its website.
- Personal data
- The statistics, brands and posts you add.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU
Phyllo (no longer used to collect data)
- Provider
- Phyllo
- What it does
- Earlier, Creators could connect Instagram, TikTok or YouTube through Phyllo to import statistics and posts. We have stopped fetching new data through Phyllo. Statistics and posts imported before then stay in your media kit until you remove them or delete your account.
- Personal data
- Your Phyllo user ID, and the profile statistics, aggregated audience data (such as follower counts and audience country or gender split) and posts imported earlier.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- Stored by TRIBL in the EU
3.9 Gift cardsReloadly
Reloadly
- Provider
- Reloadly Inc., USA
- What it does
- Supplies the digital gift cards that Fans (or Creators themselves) buy, which are delivered to the Creator by email.
- Personal data
- The sender name given at checkout, the receiving Creator’s email address, and the gift card, country, amount and order details.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- USA
- Privacy policy
- reloadly.com/privacy-policy
3.10 Customer supportEmail
Email support
- Provider
- Tribl AB
- What it does
- When you write to support@tribl.app or info@tribl.app, we use your message to answer you and keep it in case you contact us again.
- Personal data
- Your name, email address, message and anything you choose to include.
- Legal basis
- Our legitimate interest in answering your questions and handling complaints (Art. 6(1)(f)).
- Place of processing
- EU
3.11 Internal operations and monitoringMicrosoft Teams · New Relic · TRIBL logs
Microsoft Teams alerts
- Provider
- Microsoft Ireland Operations Limited, Ireland
- What it does
- Our systems post automatic alerts to our team’s Teams channels about new signups, flagged content and celebrity matches, payout requests and technical errors, so we can act on them.
- Personal data
- Name and username, email address, the flagged content or a link to the image, and for payout requests the account holder name, IBAN, SWIFT/BIC and amount.
- Legal basis
- Our legitimate interest in running and supervising the platform (Art. 6(1)(f)).
- Place of processing
- EU and USA
- Privacy policy
- privacy.microsoft.com/privacystatement
New Relic
- Provider
- New Relic, Inc., USA
- What it does
- Monitors the performance and errors of our servers, when switched on.
- Personal data
- Technical data about requests to our servers, which can include IP addresses and account IDs.
- Legal basis
- Our legitimate interest in keeping TRIBL fast and reliable (Art. 6(1)(f)).
- Place of processing
- USA
- Privacy policy
- newrelic.com/termsandconditions/privacy
TRIBL logs
- Provider
- Tribl AB
- What it does
- We log requests to TRIBL, errors, and the calls we make to our service providers, to investigate problems, abuse and security incidents.
- Personal data
- IP address, account ID, the request and response, and timestamps.
- Legal basis
- Our legitimate interest in security and troubleshooting (Art. 6(1)(f)).
- Place of processing
- EU
3.12 AnalyticsOnly with your consentGoogle Tag Manager · Google Analytics 4 · Microsoft Clarity
These tools only run if you accept cookies. Because our Google Tag Manager container also holds advertising tags, it is currently only loaded when you accept both analytics and marketing.
Google Tag ManagerOnly with your consent
- Provider
- Google Ireland Limited, Ireland
- What it does
- Loads our analytics and advertising tools. It does not set cookies itself.
- Personal data
- IP address and browser information.
- Legal basis
- Your consent (Art. 6(1)(a)), which you can withdraw at any time in .
- Place of processing
- EU and USA
- Privacy policy
- policies.google.com/privacy
Google Analytics 4Only with your consent
- Provider
- Google Ireland Limited, Ireland
- What it does
- Measures how visitors use the site: pages viewed, time on site, where visitors came from, and the device and approximate location. We use two Analytics properties.
- Personal data
- Cookie identifiers, pages visited and interactions, device and browser data, approximate location. Google Analytics 4 uses your IP address to estimate your location but does not store it.
- Legal basis
- Your consent (Art. 6(1)(a)), which you can withdraw at any time in .
- Place of processing
- EU and USA
- Privacy policy
- policies.google.com/privacy
Microsoft ClarityOnly with your consent
- Provider
- Microsoft Ireland Operations Limited, Ireland
- What it does
- Records how pages are used (clicks, taps, scrolling and mouse movement) and produces heatmaps and session replays. Text typed into forms is masked.
- Personal data
- Cookie identifiers, interactions with the page, device and browser data, approximate location.
- Legal basis
- Your consent (Art. 6(1)(a)), which you can withdraw at any time in .
- Place of processing
- USA
- Privacy policy
- privacy.microsoft.com/privacystatement
3.13 Advertising and remarketingOnly with your consentMeta Pixel · TikTok Pixel · Google Ads · X Pixel · Quora Pixel
These tools measure which of our ads lead people to TRIBL and let us show TRIBL ads to people who have visited the site. They only run if you accept marketing cookies (Google Ads, TikTok, X and Quora only if you also accept analytics). For the collection of data on our site and its transfer to Meta, TikTok, X or Quora, we and that company are joint controllers; each company is then the controller of what it does with the data on its own platform.
Meta PixelOnly with your consent
- Provider
- Meta Platforms Ireland Limited, Ireland (joint controller for collection)
- What it does
- Reports visits and actions on TRIBL to Meta so we can measure and target ads on Facebook and Instagram.
- Personal data
- Cookie identifiers, pages visited and actions taken, IP address, browser and device data, and the ad you clicked.
- Legal basis
- Your consent (Art. 6(1)(a)), which you can withdraw at any time in .
- Place of processing
- EU and USA
- Privacy policy
- www.facebook.com/privacy/policy
TikTok PixelOnly with your consent
- Provider
- TikTok Technology Limited, Ireland (joint controller for collection)
- What it does
- Reports visits and actions on TRIBL to TikTok so we can measure and target ads on TikTok. We use three TikTok Pixels.
- Personal data
- Cookie identifiers, pages visited and actions taken, IP address, browser and device data, and the ad you clicked.
- Legal basis
- Your consent (Art. 6(1)(a)), which you can withdraw at any time in .
- Place of processing
- EU, USA, Singapore and other countries where TikTok operates
- Privacy policy
- www.tiktok.com/legal/page/eea/privacy-policy/en
Google Ads conversion tracking and remarketingOnly with your consent
- Provider
- Google Ireland Limited, Ireland
- What it does
- Measures which Google ads lead to visits and signups, and lets us show ads to people who visited TRIBL.
- Personal data
- Cookie identifiers, pages visited and actions taken, IP address, browser and device data, and the ad you clicked.
- Legal basis
- Your consent (Art. 6(1)(a)), which you can withdraw at any time in .
- Place of processing
- EU and USA
- Privacy policy
- policies.google.com/privacy
X (Twitter) PixelOnly with your consent
- Provider
- X Internet Unlimited Company, Ireland, for users in the EU, EEA and UK; X Corp., USA, elsewhere (joint controller for collection)
- What it does
- Reports visits and signups on TRIBL to X so we can measure and target ads on X. Loaded on every page, with extra events on the signup steps.
- Personal data
- Cookie identifiers, pages visited and actions taken (such as completing signup), IP address, browser and device data, and the ad you clicked.
- Legal basis
- Your consent (Art. 6(1)(a)), which you can withdraw at any time in .
- Place of processing
- EU and USA
- Privacy policy
- x.com/en/privacy
Quora PixelOnly with your consent
- Provider
- Quora, Inc., USA (EU representative: VeraSafe) (joint controller for collection)
- What it does
- Reports visits on TRIBL to Quora so we can measure and target ads on Quora.
- Personal data
- Pages visited, IP address, browser and device data, and identifiers stored by Quora on its own domain.
- Legal basis
- Your consent (Art. 6(1)(a)), which you can withdraw at any time in .
- Place of processing
- USA
- Privacy policy
- www.quora.com/about/privacy
3.14 Waitlists and early accessOnly with your consentTRIBL waitlists
Before a new product opens, you can join its waitlist on tribl.app. There are two today: Dealroom (on the Dealroom page) and early access to our AI page builder (on the home page). We only add you if you send the form. A waitlist entry is separate from a TRIBL account.
TRIBL waitlistsOnly with your consent
- Provider
- Tribl AB (stored with the hosting providers in section 3.5)
- What it does
- Keeps your place on the list and tells you when it is your turn. We use your email address only for the product you signed up for: for Dealroom, to tell you when your invite is ready; for AI early access, to email you about your early access. We don't add you to a newsletter, send you other marketing or share your address. For AI early access you can also tell us what you would ask TRIBL to build. We read these ideas to decide what the AI builder should do first, and may use the text of an idea, without your email address, as an example when we design and test it. We don't publish ideas or use them to contact you. Please don't put sensitive personal details in the idea field.
- Personal data
- Your email address; the list you joined; for Dealroom, whether you are a creator or a brand or agency; for AI early access, the idea you typed, if any (up to 280 characters); the page the form was on; when you joined, which is when you gave your consent; and, later, when we sent your invite. If you join the same list twice, we keep one entry and your first sign-up time. We don’t store your IP address with the entry.
- Legal basis
- Your consent (Art. 6(1)(a)), given when you send the form. You can withdraw it at any time by emailing info@tribl.app, and we will delete your entry.
- Place of processing
- EU
3.15 BookingsTRIBL bookings
Creators can offer sessions, such as calls or coaching, that Fans book from the Creator's page. You don't need a TRIBL account to book. Paid sessions are paid through Stripe (section 3.2).
TRIBL bookings
- Provider
- Tribl AB (stored with the hosting providers in section 3.5; emails sent with Amazon SES, section 3.6)
- What it does
- Shows the Creator's free times in your time zone, holds the time you pick while you pay, confirms the booking and sends you the confirmation (with a calendar file and a link to manage your booking), reminders 24 hours and 1 hour before the session if the Creator keeps them on, notices if the booking is moved or cancelled, and a follow-up message if the Creator writes one. You can move or cancel a free booking with your link; a paid booking is cancelled by the Creator, which refunds you in full. We share your name, email address, answers and, if asked, billing address with the Creator you book, who needs them to hold the session and is responsible for how they use them. The meeting link or address is only sent to you once you have booked.
- Personal data
- Your name, email address, time zone, the session and time you chose, your answers to the Creator’s questions, your billing address if the Creator asks for it, the price and any discount, the booking reference and status, when it was moved or cancelled and why (if a reason was given), and which reminders were sent. For Creators: the sessions you offer, your available hours and time zone, where sessions take place, and your automatic messages.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU
3.16 Forms on Creators' pagesTRIBL forms · Apps a Creator connects · AI assistance (form drafting)
Creators can add a form to their page, for example to take enquiries, booking requests or feedback. The Creator decides what the form asks and what the answers are used for, so the Creator is the controller of your answers. TRIBL stores and delivers them for the Creator, as their processor. Please only share what the form asks for, and don't put sensitive personal details in a form.
TRIBL forms
- Provider
- Tribl AB (stored with the hosting providers in section 3.5), on the Creator's behalf
- What it does
- Stores your answers and shows them to the Creator in their dashboard. If the Creator asked for it, we email them a copy of each response. The Creator can download the answers. If the form gives you something when you send it (such as a link or a code), we show it to you straight away. If you tick the box to hear from the Creator, we record when you did and the exact words you agreed to, so the Creator can show your consent; that consent is given to the Creator, not to TRIBL. We don't use your answers for our own marketing and don't share them with anyone except the Creator and the apps they connect. To stop spam, we limit how often a form can be sent and ignore forms filled in by bots. We also count how many people viewed, opened and sent each form, without storing who.
- Personal data
- Your answers; when you sent the form; your device type (such as iOS or Android); and whether you ticked the box to hear from the Creator, with the time and wording.
- Legal basis
- The Creator decides the legal basis for the answers they collect. TRIBL processes them to perform our contract with the Creator (Art. 6(1)(b)) and, for spam protection and the anonymous counts, on our legitimate interest in a safe platform (Art. 6(1)(f)).
- Place of processing
- EU
Apps a Creator connects
- Provider
- The service the Creator chooses (for example Zapier, Make or their own system)
- What it does
- A Creator can ask us to send each new response to another app they use, such as a spreadsheet or an email tool. We send your answers there as soon as you send the form. The Creator chooses that app and is responsible for it.
- Personal data
- Your answers, when you sent them, and whether you ticked the box to hear from the Creator.
- Legal basis
- As decided by the Creator, who instructs us to send the answers.
- Place of processing
- Depends on the app the Creator chooses
AI assistance (form drafting)
- Provider
- AI service providers that we engage as our processors
- What it does
- When a Creator asks TRIBL to draft a form, we send the description they type to an AI service provider, whose model suggests a title and questions. The Creator reviews and edits the draft before anything is published, and fans' answers are never sent for drafting. We choose these providers and models, and may change them from time to time, for example when a model is retired or a better one becomes available, without changing the purpose described here. Whichever provider we use acts only on our instructions under a data processing agreement, may not use the data to train its own models, and is subject to the transfer safeguards in section 8. You can ask us which provider we currently use.
- Personal data
- The description the Creator types.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- In the EU, or outside the EU/EEA under the safeguards in section 8
3.17 Digital productsTRIBL digital products
Creators can sell digital products, such as e-books, templates, files or links, from their page. You don't need a TRIBL account to buy one. Paid products are paid through Stripe (section 3.2). The Creator is the seller.
TRIBL digital products
- Provider
- Tribl AB (stored with the hosting providers in section 3.5; emails sent with Amazon SES, section 3.6)
- What it does
- Takes your order and, for a paid product, delivers it once Stripe confirms your payment. We email you a personal link to your purchase and show you the same link on screen. The link is private: we only store a scrambled (hashed) version of it, and each download uses an address that expires after 5 minutes. Before you pay, you confirm that you want access straight away and understand that you lose your 14-day right of withdrawal once delivery starts; we record that you did, when, and the exact wording, and confirm it in the email (see section 11.3 of our Terms). We share your name, email address, your answers to the Creator's checkout questions, what you bought and how many times you downloaded it with the Creator who sells the product, who needs them to deal with your purchase and is responsible for how they use them. We count how often you open your link and download, to help with support questions. If you lose your link, the Creator can ask us to email you a new one (up to three times a day); the Creator never sees the link itself.
- Personal data
- Your name, email address, answers to the Creator’s checkout questions, the product, quantity, price and any discount, when you paid, your confirmation about the right of withdrawal (time and wording), your device type (such as iOS or Android), how many times you downloaded, when you last opened your link and when a Creator asked us to resend it. For Creators: the products you sell, their files, images and descriptions, and your sales.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)). Keeping proof of your confirmation about the right of withdrawal is our legitimate interest in being able to show it was given (Art. 6(1)(f)).
- Place of processing
- EU
3.18 Calendar and video connectionsCalendar invites and feed · Google Calendar and Google Meet · Microsoft Outlook and Microsoft Teams · Zoom · Calendly
Creators can see their bookings in their own calendar, and can connect Google Calendar or Microsoft Outlook (one at a time) so busy times are blocked and each booking is added to their calendar, with a Google Meet or Microsoft Teams link if they choose. They can also connect Zoom, so each booking gets a Zoom meeting, and Calendly, so times they're busy in Calendly are blocked and their Calendly bookings show up in Tribl. Fans booked into the same group session share one meeting link. Connecting is optional, and a Creator can disconnect at any time in Bookings → Calendar and video.
Calendar invites and feed
- Provider
- Tribl AB (stored with the hosting providers in section 3.5; emails sent with Amazon SES, section 3.6)
- What it does
- Attaches a calendar invite to booking emails for the Fan and the Creator, and updates or cancels it when the booking changes. A Creator can turn off their own invites. Creators can also subscribe to a private calendar feed of their own bookings; the feed link is secret, and the Creator can replace it at any time, which stops the old link working.
- Personal data
- The session, date, time and place or meeting link; the Fan’s name and email address; the Creator’s name.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU
Google Calendar and Google Meet
- Provider
- Google Ireland Limited, Ireland, the Creator’s calendar provider, acting as an independent controller for the Creator’s Google account
- What it does
- If a Creator connects Google Calendar, we read the list of their calendars so they can choose which ones count, and the start and end times of busy periods on those calendars, so Fans are only offered times the Creator is free. We never read the titles, descriptions or guests of their events, and we never change events we didn't create. When a Fan books, we add an event to the Creator's main calendar with the session, the Fan's name and email address, and where it takes place (for a phone call, the number to call). If the booking uses Google Meet, Google makes a Meet link for it, which we send to the Fan in their confirmation. We move the event if the booking is rescheduled and delete it if the booking is cancelled. The Fan is not added as a guest, so Google doesn't send them an invitation and they never see the Creator's email address. Busy times are kept in memory for up to 30 minutes and are not stored. The access Google gives us is stored encrypted and is never shown in your browser; when a Creator disconnects, we revoke it at Google and delete it. Events already added stay in the Creator's calendar, under the Creator's control.
- Personal data
- For Creators: the email address of the connected Google account, the calendars they choose (names and IDs), busy start and end times, the IDs of events we created and the encrypted access. For Fans: name, email address, the session and its time, and, for phone sessions, the phone number they gave, which are added to the Creator’s calendar event.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU and the USA (safeguards in section 8)
- Privacy policy
- policies.google.com/privacy
Microsoft Outlook and Microsoft Teams
- Provider
- Microsoft Ireland Operations Limited, Ireland, the Creator’s calendar provider, acting as an independent controller for the Creator’s Microsoft account
- What it does
- If a Creator connects their Microsoft account (work, school or personal), we read the list of their calendars so they can choose which ones count, and, for each event on those calendars, only its start and end time and whether it shows the Creator as busy, so Fans are only offered times the Creator is free. We never read the titles, descriptions or attendees of their events, and we never change events we didn't create. When a Fan books, we add an event to the Creator's default calendar with the session, the Fan's name and email address, and where it takes place (for a phone call, the number to call). If the booking uses Microsoft Teams and the Creator's account is a work or school account, Microsoft makes a Teams link for it, which we send to the Fan in their confirmation. We move the event if the booking is rescheduled and delete it if the booking is cancelled. The Fan is not added as an attendee, so Microsoft doesn't send them an invitation and they never see the Creator's email address. Busy times are kept in memory for up to 30 minutes and are not stored. The access Microsoft gives us is stored encrypted and is never shown in your browser; when a Creator disconnects, we delete it. Microsoft doesn't let apps revoke that access themselves, so a Creator can also remove Tribl from the apps in their Microsoft account. Events already added stay in the Creator's calendar, under the Creator's control.
- Personal data
- For Creators: the email address of the connected Microsoft account, whether it is a work, school or personal account, the calendars they choose (names and IDs), busy start and end times, the IDs of events we created and the encrypted access. For Fans: name, email address, the session and its time, and, for phone sessions, the phone number they gave, which are added to the Creator’s calendar event.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- EU and the USA (safeguards in section 8)
- Privacy policy
- privacy.microsoft.com/privacystatement
Zoom
- Provider
- Zoom Communications, Inc., USA, the Creator’s video provider, acting as an independent controller for the Creator’s Zoom account
- What it does
- If a Creator connects Zoom, we read their Zoom user and account IDs, email address and plan (so we can warn them that free Zoom meetings end after 40 minutes). When a Fan books a session that uses Zoom, we create a scheduled meeting in the Creator's Zoom account with the session's name, time and booking reference, and send the Fan the link in their confirmation. We don't send the Fan's name or email address to Zoom, and Zoom doesn't email them. Fans booked into the same group session share one meeting. We move the meeting if the booking is rescheduled and delete it when the last Fan booked into it cancels. We never read the Creator's other meetings, recordings or contacts, and we never keep the host's start link. The access Zoom gives us is stored encrypted and is never shown in your browser; when a Creator disconnects, we revoke it at Zoom and delete it. When a Fan joins the meeting, Zoom handles the call under its own privacy statement.
- Personal data
- For Creators: the email address, user and account IDs and plan of the connected Zoom account, the IDs and links of meetings we created and the encrypted access. For Fans: none is sent to Zoom by us; the session’s name, time and booking reference are in the meeting.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- USA (safeguards in section 8)
- Privacy policy
- www.zoom.com/en/trust/privacy/privacy-statement/
Calendly
- Provider
- Calendly LLC, USA, the Creator’s scheduling provider, acting as an independent controller for the Creator’s Calendly account
- What it does
- If a Creator connects Calendly, we read the times they are busy in Calendly (Calendly bookings and the calendars Calendly checks), so Fans can't book those times on Tribl, and their upcoming Calendly bookings, which we show only to the Creator in Bookings. We read busy times as start and end only. Busy times are kept in memory for up to 30 minutes and bookings for a few minutes; neither is stored. We never change anything in Calendly or contact the people who book the Creator there. Tribl bookings reach Calendly only through the Creator's own calendar. The access Calendly gives us is stored encrypted and is never shown in your browser; when a Creator disconnects, we revoke it at Calendly and delete it.
- Personal data
- For Creators: the email address of the connected Calendly account, busy start and end times, and their upcoming Calendly bookings (event name, time, place). For people who booked the Creator in Calendly: name and email address, shown to the Creator and not stored.
- Legal basis
- Performance of our contract with you (GDPR Art. 6(1)(b)).
- Place of processing
- USA (safeguards in section 8)
- Privacy policy
- calendly.com/privacy
Google user data, Limited Use. Tribl's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace APIs will adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements. In plain words: we only use Google data to provide the calendar features you see in Tribl. We don't sell it, use it for advertising, or use it to train AI or machine-learning models, and nobody at Tribl reads it unless you ask us to for support, it's needed for security, or the law requires it.
Microsoft data. The same applies to data we receive from Microsoft: we only use it to provide the calendar features you see in Tribl, we don't sell it, use it for advertising, or use it to train AI or machine-learning models, and nobody at Tribl reads it unless you ask us to for support, it's needed for security, or the law requires it.
4. Legal bases at a glance
| Purpose | Legal basis (GDPR) |
|---|---|
| Running your account and Creator page, and the features you use (sections 3.1, 3.5, 3.6, 3.8). | Performance of contract (Art. 6(1)(b)). |
| Taking payments, paying out Creators, gift cards, receipts and transaction emails (3.2, 3.9). | Performance of contract (Art. 6(1)(b)). |
| Verifying identity and screening against sanctions and PEP lists (3.3). | Legal obligation (Art. 6(1)(c)) where anti-money-laundering or payment rules apply, otherwise legitimate interest in preventing fraud and financial crime (Art. 6(1)(f)). |
| Keeping accounting records. | Legal obligation under the Swedish Accounting Act (Art. 6(1)(c)). |
| Keeping VAT records of the fees TRIBL charges Creators, including evidence of where the Creator is located. | Legal obligation under Swedish and EU VAT rules (Art. 6(1)(c)). |
| Preventing fraud, spam, abuse and account takeover, and moderating content (3.1, 3.4, 3.7, 3.11). | Legitimate interest in a safe and lawful platform (Art. 6(1)(f)). |
| Showing Creators anonymous statistics about their visitors (3.7). | Legitimate interest in giving Creators audience insights (Art. 6(1)(f)). |
| Analytics and advertising (3.12, 3.13). | Consent (Art. 6(1)(a)), which you can withdraw at any time. |
| Waitlists: telling you when a product opens, and reading the ideas you send us for our AI builder (3.14). | Consent (Art. 6(1)(a)), which you can withdraw at any time. |
| Bookings: showing free times, holding and confirming the session, sharing your details with the Creator you book, and sending confirmations, reminders and follow-ups (3.15). | Performance of contract (Art. 6(1)(b)). |
| Forms on Creators' pages: storing and delivering your answers for the Creator (3.16). | The Creator decides the legal basis for what they collect. TRIBL acts for the Creator under our contract with them (Art. 6(1)(b)), and on legitimate interest for spam protection (Art. 6(1)(f)). |
| Digital products: taking and delivering your order, sharing your details with the Creator who sells it, and keeping your confirmation about the right of withdrawal (3.17). | Performance of contract (Art. 6(1)(b)), and legitimate interest in being able to show your confirmation was given (Art. 6(1)(f)). |
| Calendar invites, the calendar feed and connected calendars: blocking busy times and keeping the Creator’s calendar in step with their bookings (3.18). | Performance of contract (Art. 6(1)(b)). |
| Service messages such as security alerts and changes to our terms. | Performance of contract and legitimate interest (Art. 6(1)(b) and (f)). |
| Answering questions and complaints, and establishing or defending legal claims. | Legitimate interest (Art. 6(1)(f)). |
When we rely on legitimate interest, we have weighed our interest against your rights and expectations. You can object at any time (see section 10). If you do not give us the data we need for a contract or a legal obligation, such as identity details for a payout, we cannot provide that part of the service.
5. Automated checks and profiling
We use the automated checks described in section 3.4 to keep TRIBL safe:
- Text and links are screened by OpenAI's models. Content that is flagged is not saved, and you are asked to change it. Flagged content is recorded for our team.
- Images are screened for explicit content by Amazon Rekognition. Explicit images are rejected and recorded, and our team is alerted. After three rejected images, the account is blocked automatically until our team has reviewed it.
- Celebrity matching: images that pass are compared, by face, with Amazon's index of well-known public figures. A strong match (a confidence above 95%) does not block the upload: it is sent to our team, who check whether someone may be impersonating that person. The comparison is only against public figures in Amazon's index; we do not use it to identify you or to build a profile of your face.
- Identity verification and screening: Didit compares your ID document with your selfie and screens you against sanctions and PEP lists. If the screening finds a possible sanctions or PEP match, or the name or date of birth on your document does not match your account, your account is put on hold automatically and payouts are paused until our team has reviewed the case.
These automatic steps are temporary safety measures; final decisions to remove content, close an account or refuse a payout are taken by a person. If you disagree with the outcome of a check, you can ask for a human review, give your point of view and contest the decision by emailing info@tribl.app.
With your consent, our advertising partners (section 3.13) may use data about your visit to build interest profiles for ad targeting on their platforms.
6. Where the data comes from
- Directly from you, when you sign up, join a waitlist, fill in a form, edit your page, pay or contact us.
- From Google or Apple, if you sign in with them (name, email address and account ID).
- From our identity verification and payment providers (the outcome of checks and the status of payments and payouts).
- Earlier, from Instagram, TikTok or YouTube through Phyllo, if you connected them to your media kit (see section 3.8).
- From Google, if a Creator connects Google Calendar: the email address of the connected account, their calendar list and busy times (see section 3.18).
- From Microsoft, if a Creator connects Microsoft Outlook: the email address of the connected account, whether it is a work, school or personal account, their calendar list and busy times (see section 3.18).
- From Zoom, if a Creator connects Zoom: the email address, user and account IDs and plan of the connected account (see section 3.18).
- From Calendly, if a Creator connects Calendly: the email address of the connected account, the times they are busy, and their upcoming Calendly bookings, including the name and email address of the person who booked (see section 3.18).
- From your browser and device, as described above.
7. Who we share it with
We do not sell your personal data. We share it only with:
- The public: your Creator page and media kit are visible to anyone, and Creators see the name and message of Fans who support them, and the details Fans give when they book a session (section 3.15).
- The Creator whose form you fill in, who receives your answers, and any app that Creator has connected to the form (section 3.16).
- The Creator whose digital product you buy, who receives your name, email address, checkout answers, what you bought and how many times you downloaded it (section 3.17).
- The Creator's calendar provider, if the Creator you book has connected Google Calendar or Microsoft Outlook: the booking is added to the Creator's own calendar with your name and email address (section 3.18).
- Service providers acting as our processors, listed in section 3.
- Independent controllers listed in section 3: Stripe for its own legal duties, Google and Apple for sign-in, Beefree for the technical data it collects, and (with your consent) Meta, TikTok, Google, X and Quora for advertising.
- Authorities, courts and advisers, where the law requires it or it is needed to establish, exercise or defend legal claims, for example the police, the tax authority or our auditors.
- A buyer or successor, if all or part of TRIBL is sold or merged, under the same protections.
8. Transfers outside the EU/EEA
Some providers in section 3 are based in, or access data from, countries outside the EU/EEA, mainly the USA. We only allow this when the transfer is protected: either the recipient is certified under the EU–US Data Privacy Framework (for example Google, Microsoft, Meta, Amazon and Stripe), the European Commission has decided the country gives adequate protection, or we use the European Commission's Standard Contractual Clauses together with additional safeguards where needed. You can ask us for a copy of the relevant safeguards at info@tribl.app.
9. How long we keep it
- Account and profile data: for as long as your account exists. When you delete your account we delete your profile, published content, uploaded images, payout details, connected social accounts and statistics. We keep only the records described below, and remove from them what we no longer need (such as addresses, phone numbers and device details).
- Transaction and accounting records: 7 years after the end of the financial year, as required by the Swedish Accounting Act. We keep the name, email address, country and IP address of the person who paid, and the amounts.
- Records of the fees TRIBL charges Creators, and the evidence of where the Creator is located (country of residence, bank account country and the IP address used at sign-up): 10 years after the end of the year, as required for VAT records under EU rules.
- Identity verification and screening records: for as long as your account is active, and then for one more year, after which we and our verification provider delete them. Your account stops being active when you delete it, or when it has not been used for 6 months after your verification. Using it means signing in, receiving or making a payment, a payout, a transfer to your account or a top-up. These are the same events our payment provider, Stripe, uses to decide whether an account is active. If you come back after your records were deleted, you will need to verify again.
- Payout account with our payment provider: when we delete the verification records of an inactive Creator, we also close their Stripe account, once any balance has been paid out. We never close it while money is owed to you.
- Anonymous page-view and click statistics: for as long as the Creator's account exists.
- Security and technical logs: 90 days for logs of requests to TRIBL, and 180 days for error logs and logs of calls to our service providers. One-time verification codes: 1 hour.
- Waitlist entries: until 6 months after we send your invite, then we delete them. If we have not invited you within 2 years of joining, for example because the product has not opened, we delete your entry then. We delete it straight away if you withdraw your consent, ask us to, or delete a TRIBL account that uses the same email address. We may keep counts of what people asked our AI builder to do (such as how many asked for memberships), which do not identify anyone.
- Bookings: for as long as the Creator's account exists, so the Creator keeps a record of their sessions. A time held for a payment that was never completed is deleted 7 days after the hold ran out. If you delete your Fan account or ask us to erase your data, we remove your name, email address, answers and billing address from your bookings. The payment record is kept as described above for transaction records.
- Answers sent through a form on a Creator's page: they belong to the Creator, so we keep them for the Creator until the Creator deletes them or deletes their account. We don't delete them on a schedule. Deleting your own TRIBL account doesn't delete answers you sent to a Creator; see section 10 to ask for that.
- Digital product orders: for as long as the Creator's account exists, so you can keep downloading what you bought and the Creator keeps a record of their sales. A checkout that was never paid is deleted after 30 days. If you ask us to erase your data, we remove your name, email address, answers and link from your orders, and the link stops working. The payment record and your confirmation about the right of withdrawal are kept as described above for transaction records.
- Connected calendars and video accounts: the connection and its encrypted access are kept until the Creator disconnects or deletes their TRIBL account. If the Creator removes Tribl in their Google, Microsoft or Calendly account instead, the access stops working and the connection is kept, marked for reconnecting, until they disconnect; if they remove Tribl in Zoom, Zoom tells us and we delete the connection. Zoom meetings already created stay in the Creator's Zoom account. Busy times are not stored (we keep them in memory for up to 30 minutes). Events already added to a Creator's calendar stay there, under the Creator's control; a Creator's data export lists their connections without the access itself.
- Support messages: for as long as needed to handle your request and any follow-up.
- Cookies: see the durations in our Cookie Notice.
Providers acting as independent controllers (such as Stripe) keep data for the periods set out in their own policies.
10. Your rights
Under the GDPR you have the right to:
- get a copy of the personal data we hold about you (access);
- have inaccurate data corrected (rectification);
- have your data deleted (erasure), unless we must keep it by law;
- have our use of your data restricted;
- receive the data you gave us in a machine-readable format (portability);
- object to processing based on legitimate interest, including profiling, and to direct marketing at any time;
- not be subject to a decision based solely on automated processing that significantly affects you (see section 5);
- withdraw your consent at any time, without affecting what we did before. For cookies, use . To leave a waitlist, email info@tribl.app.
Creators and Fans can edit most data and delete their account in their account settings. If you are on a waitlist, email us from the address you signed up with to see, change or delete your entry, or to leave the list. For answers you sent through a form on a Creator's page, the Creator is responsible: contact them directly, or email us and we will pass your request on and help the Creator respond. To get a copy of your data, or for anything else, email info@tribl.app. We will reply within one month, and may need to confirm your identity first.
If you are unhappy with how we handle your data, you can complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY), www.imy.se, or the data protection authority where you live or work. We'd appreciate the chance to sort it out with you first.
11. Age
TRIBL is for people aged 18 and over. We do not knowingly collect data from anyone under 18. If you believe a minor has given us personal data, contact us and we will delete it.
12. Security
We use technical and organisational measures to protect your data, including encryption in transit (HTTPS), hashed passwords, access controls, restricted access to verification data, and hosting with established providers. No system is completely secure; if a breach is likely to affect you, we will tell you and the authorities as the law requires.
13. Links to other sites
Creator pages link to other websites and social networks. When you follow such a link, the other site's own privacy policy applies.
14. Changes to this notice
We may update this notice when our services, our providers or the law change. We will change the "Last updated" date and, for significant changes, tell you by email or on the site before they take effect.
15. Definitions
- Personal data: any information that relates to an identified or identifiable person.
- Processing: anything done with personal data, such as collecting, storing, using, sharing or deleting it.
- Controller: the organisation that decides why and how personal data is processed. Joint controllers decide this together.
- Processor: a provider that processes personal data on a controller's behalf and instructions.
- Creator and Fan: as defined in our Terms & Conditions.
- GDPR: the EU General Data Protection Regulation (EU) 2016/679.