Privacy Policy

Google user data (Google sign-in and YouTube)

This section is for anyone who signs in to Tribue (tribue.io) with Google, or links a YouTube channel by signing in with YouTube. It says what Google user data we access, how we use it, who we share it with, how we protect it, and how long we keep it. The legal bases are those in Section 4A.2 (contract, and legitimate interests for fraud prevention).

What Google user data we access

• Google sign-in (permissions: openid, email, profile): your Google account ID, name, email address, whether that email is verified, and your profile picture. Google also gives us sign-in tokens, which we store encrypted but do not use to read anything else.
• YouTube, only if you choose to link a channel by signing in with YouTube (permission: youtube.readonly, which is read only): your channel's ID, name, handle, profile image and statistics (subscriber, video and view counts); the list of videos uploaded to that channel, including unlisted and private ones, which we show only to you so you can choose what to submit and do not store; and for the videos you submit, the title, description, thumbnail, publish date, duration and view, like and comment counts.
• The YouTube access and refresh tokens Google gives us, so we can keep reading the data above while your channel stays linked.
• We do not access your Gmail, contacts, Drive, watch history, YouTube Analytics, comments or messages. Read-only access means we cannot upload, edit, delete or comment on anything.

How we use Google user data

• To sign you in and keep your account secure.
• To confirm that you own the YouTube channel you link and submit videos from.
• To check that a video you submit to a campaign meets that campaign's requirements, and to count its views. Those numbers decide what you earn, and we show them to you so you can see why.
• To show the brand, agency or agency client running a campaign the videos you submitted to that campaign, their statistics, and your linked channel name, handle and follower count (Section 4A.4). They never see your other videos, your tokens or your Google account email.
• To count sign-ups: when you create an account with Google, one sign-up event with your name and email goes to our analytics provider (Section 8).
• We use Google user data only to provide and improve these features for you. We do not use it for advertising, and we do not use it to develop, improve or train generalized or non-personalized AI or machine learning models. We do not use Google user data or Google APIs to create, edit or generate images or videos of people with AI.

Who we share Google user data with

• The brand, agency or agency client running a campaign you submitted to, as described above, and visitors to campaign pages and showcases where Section 4A.4 says approved submissions are shown.
• Service providers that host and process data for us under contract, including our analytics provider for the sign-up event above (Section 8).
• Authorities, where the law requires it.
• We do not sell Google user data, and we do not give or transfer it to anyone else: not to advertisers, data brokers or information resellers, and not to decide creditworthiness or for lending.

How we protect Google user data

• Google access and refresh tokens are encrypted with AES-256 before we store them, and only our servers can decrypt them.
• All data travels between your browser, our servers and Google over encrypted connections (HTTPS).
• Our staff look at Google user data only to support you, to prevent fraud and abuse, to operate the service, or where the law requires it (Section 8.3). Section 10 describes our other security measures.
• Signing in stores cookies in your browser that keep you signed in. Our Cookie Policy lists them.

How long we keep Google user data, and how to delete it

• YouTube tokens are kept only while your channel is linked. Unlinking YouTube in your workspace settings (Linked accounts) deletes them straight away, and we stop using your Google access.
• Your Google sign-in data is kept until you delete your Tribue account. Deleting your account deletes it and any tokens, as described in Sections 9 and 11. If you have another way to sign in, removing Google as a sign-in method in your settings deletes the Google sign-in tokens straight away.
• The list of your channel's videos is never stored.
• Videos you submitted. Your channel name, handle, image and statistics, and the details of the videos you submitted, stay on your profile and on those submissions, because they are the record of what you were paid (Section 9). We keep refreshing the public statistics of those videos until 90 days after the campaign ends (Section 4A.3). Once your channel is unlinked we do that from public YouTube data with our own API key, not your Google access.
• Removing access in Google. You can remove Tribue's access at any time on Google's security settings page at security.google.com/settings/security/permissions. Our stored tokens stop working immediately, so we can no longer read anything with them. To have them deleted as well, unlink the channel in Tribue or email us.
• You can ask us to delete any of your Google user data at privacy@tribue.io.

Google API Services User Data Policy and YouTube

• Tribue'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.
• Tribue uses YouTube API Services. By linking a YouTube channel you agree to the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy.

1. Who we are and how to reach us

1.1 Tribue (formerly Klipped) is a platform where brands and agencies fund marketing campaigns and creators get paid for content. This policy covers the web app at tribue.io (formerly klipped.io) and its subdomains, and our related sites. "We", "us" and "our" mean Tribue.

1.2 Controller: Tribue, a company established in the Republic of Cyprus.

1.3 Contacts.

• Privacy and data protection: privacy@tribue.io. Use this address for any request under this policy.
• General enquiries: hello@tribue.io.
• Support, complaints and appeals: support@tribue.io.
• Billing: billing@tribue.io.
• Legal notices: legal@tribue.io.

1.4 Supervisory authority: our lead authority is the Commissioner for Personal Data Protection, Cyprus (www.dataprotection.gov.cy).

1.5 Who this policy covers. Everyone whose personal data we handle. Section 4 has a part for each group:

• 4A: creators;
• 4B: brand and agency users;
• 4C: agency clients and CLIENT workspace users;
• 4D: shoppers on merchants' online stores;
• 4E: people who are not users but whose public social posts or profiles we look up;
• 4F: website visitors and waitlist sign-ups;
• 4H: merchants who use our Shopify app;
• Google user data: anyone who signs in with Google or links a YouTube channel.

The rest of the policy applies to everyone.

2. The short version

• What we use. Most of the data we hold is needed to verify submissions, calculate earnings and move money.
• Who handles money. We do not hold your card or bank details. Whop, our payment provider, handles payments, identity checks (KYC) and withdrawals, as a separate controller.
• Social data. We read public data about social posts and profiles to check that a submitted post is yours and to count its views.
• Google and YouTube. If you sign in with Google or link a YouTube channel (read only), we use that data to sign you in, confirm the channel is yours, check and count the views on the videos you submit, and show those videos and their stats to the brand running the campaign. When you sign up with Google, a sign-up event with your name and email goes to our analytics provider. We never post, edit or delete anything on YouTube, and we do not sell Google user data, use it for advertising, use it to train AI models or use it to create images or videos of people with AI. Google user data, at the top of this policy, has the details.
• Automated rules. Fixed rules can refuse a submission, reject pending submissions when a campaign ends or its budget runs out, and flag unusual views for our team. Section 6 explains each rule and how to get a person to review it. No score or flag stops a payout you have already earned.
• No selling. We do not sell personal data, and we run no advertising trackers on our own sites.
• Your rights. You can delete your account yourself in Settings. Records of money that moved are kept for legal reasons (Section 11).

3. Definitions

• Workspace: the account you act through on Tribue: CREATOR, BRAND, AGENCY or CLIENT (some older accounts are PERSONAL). A user can own several workspaces, and members are the users who can act for one.
• Submission: a social media post a creator submits to a campaign.
• Processor: a company that handles data for us, on our instructions.
• Independent controller: a company that decides for itself how to use the data it receives.

4. What we collect, why, and on what legal basis

Each part below says what we collect, where it comes from, why we use it, the legal basis and who receives it. Section 8 lists our service providers and Section 9 how long we keep data. We rely on these legal bases under the GDPR:

• Contract: needed to provide the service you signed up for.
• Legal obligation: for example, keeping accounting records.
• Legitimate interests: our interests, or a third party's, where your rights do not override them. You can object to this use (Section 11).
• Consent: you can withdraw it at any time.

4A. Creators

4A.1 What we collect

4A.2 Why we use it and on what basis

4A.3 How we read social media data

• Linking an account. For any platform, we give you a short code to put in your bio, then read your public profile to find it. This is how we verify Instagram, TikTok, YouTube, X, Threads and Facebook accounts. For YouTube and TikTok you can instead sign in with that platform and give us read-only access to your channel or profile and its videos. Section 4G explains exactly what we read from YouTube and how we use it.
• Reading posts. We read only submitted posts and linked accounts, one at a time, by post URL or handle. We do not crawl in bulk, and we do not collect follower lists or comment text.
• Who reads it for us. Our scraping providers: ScrapeCreators, SociaVault, Apify, Bright Data and RocketAPI.
• How often. While a campaign runs, every 10 minutes to 24 hours per submission. After it ends, weekly for 90 days.

4A.4 Who receives creator data

• Brands and agencies whose campaigns you join or apply to receive your submissions and their stats, your profile, linked handles, demographics screenshots and league badge, your application, and your messages to them. Each becomes an independent controller of what it receives, and our Terms limit its use to the campaign.
• CLIENT workspaces. If an agency runs a campaign for a client, the client can see its submissions, including your handle and videos (4C).
• The public. Approved submissions on campaign pages and showcases show your name, avatar, workspace handle, linked social handle and the video. Your public profile shows the fields you choose.
• Your referrer, if you joined through a referral link, sees that you signed up and your total realised earnings.
• Whop receives your email and workspace name when your Whop account is created, plus payout instructions. Whop collects your identity, tax and bank details itself, as an independent controller under its own privacy policy.
• Our service providers (Section 8) and authorities, where the law requires.

4B. Brand and agency users

4B.1 What we collect

4B.2 Why we use it and on what basis

The purposes and bases in 4A.2 apply where relevant, plus:

4B.3 Who receives it

• Creators who join or apply to your campaigns see your brand profile and the campaign details.
• Whop processes your payments as an independent controller, and as merchant of record for card payments.
• Our service providers (Section 8).

4C. Agency clients and CLIENT workspace users

4C.1 When an agency adds you as a client

Agencies on Tribue can add their own clients, who may never sign up themselves. We store what the agency enters: your name, email and image; organisation and VAT numbers; city, postcode and country; and invoices issued to you, including line items, any management fee and CC email addresses. You may receive an invoice email, a payment link that opens a Whop checkout (you pay Whop directly), and an invitation to open a CLIENT workspace.

4C.2 If you open a CLIENT workspace

You sign in with the email the agency recorded, and we match your account to the agency's client records by that email. A CLIENT workspace is read-only. It shows the campaigns agencies run for you, including creators' handles and submitted videos, campaign stats and the agency's margin.

4C.3 Legal basis

• Invoicing and payment links: contract (between you and the agency), and our legal obligation to keep accounting records.
• The invitation and the CLIENT workspace: legitimate interests (letting you see the work bought for you). Once you open the workspace, contract.

4C.4 Retention

Invoices are accounting records and are kept for the statutory period (Section 9). If the agency's workspace is deleted, your name, email, organisation and VAT numbers and address are removed from the client record. The invoice stays.

4D. Shoppers on merchants' online stores

When a merchant connects their online store to Tribue, for example through our Shopify app, our pixel records how shoppers use that store. We use it to credit sales to the creators who sent the shoppers, and to show the store and its creators how their campaigns perform. We keep only what we need for that. Section 9 says how long we keep it.

• Store activity: pages and products viewed, searches, collections, items added to or removed from the cart, checkout steps and completed orders. For each event we keep the page address, the product or variant, the price, quantity, cart value and currency, and the time.
• Visit details: the creator link and click code, if the shopper came through one; the landing page and referring page; ad click IDs in the link; a random visitor ID and session ID; the browser's user agent; the country; your answer to the store's cookie banner; and a salted hash of the IP address. We do not keep the IP address with the visit, only that hash.
• On your device: a random visitor ID, kept until you clear your browser's storage; a session ID and the time of your last activity on the store, replaced after 30 minutes without activity; and the code of the creator link you came through, kept for up to 90 days. They are saved only if the store's privacy settings allow analytics (Cookie Policy).
• Orders: the order ID, amount, currency, refunded amount and date, and the creator link or code the sale is credited to.
• What we never keep: the shopper's name, email address, phone number, postal address or payment details. If the store sends any of them to us, we discard them without storing them.
• Your choice: we follow the store's privacy settings, which you set by accepting or refusing its cookie banner where it shows one. If you refuse analytics, nothing is saved in your browser's storage. The link code is still added to your cart, so the order carries it, and we keep only what we need to credit a sale to a creator: the link and click code, the landing and referring page, ad click IDs in the link, and the order. We keep no visitor ID, session ID, user agent, country or IP hash, and no other store activity. If you have not answered the banner yet, nothing is saved in your browser, but the visit details above, including the IP hash, user agent and country, are still recorded. If the store does not ask for consent, its settings allow analytics and everything above applies.
• Who sees it: the store sees its own data. Creators see their own sales and earnings, one line per order: the date of the sale and of the click, the amount, any refund and the country of the click. They never see a shopper's name, contact details, IP address, device or visitor ID. We do not sell this data, we do not send it to ad networks, and we do not use it to build profiles of shoppers, to target advertising, or to train or improve AI or machine learning models.
• Who is responsible: the store and Tribue are joint controllers for recording visits to the store and matching them to orders. The store is responsible for its cookie banner and its own privacy notice. Tribue alone decides how credited orders are used to pay creators and to keep the accounting records the law requires. You can contact either of us about your data.
• Legal basis: legitimate interests (the store's, the creators' and ours) in crediting each sale to the creator who sent the shopper, and in preventing attribution fraud. Saving or reading anything in your browser's storage is based on your consent through the store's cookie banner, where the law requires it. Keeping orders that produced a commission is a legal obligation (accounting records). You can object to the use based on legitimate interests (Section 11).
• Your rights: write to privacy@tribue.io, or ask the store. We hold no name or email for you, so we may ask for the order number and the store's name to find your data.

4E. People whose public social posts or profiles we look up

4E.1 When this happens

Even if you have never used Tribue, we may read public data about you when:

• a creator submits your post. We read the post's public data and the author's public profile details (4A.1) to check that the post belongs to the creator's verified account. If it is yours and not theirs, the submission is refused. We keep no record of you, apart from technical logs that hold only the post ID;
• someone enters your handle to link an account. We read your public bio to look for our verification code. If the code is not there, nothing is linked;
• you appear in a submitted video, or its caption mentions you. We keep copies of submitted videos and captions (4A.1);
• a user shares a link to your public page in a message. Our server fetches the page's title, description and image to show a preview;
• a user mentions your handle or content in their profile, onboarding answers (for example "brands I've worked with") or a waitlist handle reservation. We store the text as they entered it.

4E.2 Source

Public pages on TikTok, Instagram, YouTube, X, Threads and Facebook, read through the providers named in 4A.3, and what our users enter.

4E.3 Purpose and legal basis

We use this data to verify who made a post, to stop creators claiming other people's content, and to keep evidence of paid work. Our basis is the legitimate interests of Tribue, brands and creators in making sure payments go to the person who made the content. We look up single posts and profiles by URL or handle only. We do not build profiles of non-users, crawl in bulk, or collect follower lists or comments.

4E.4 Retention

We do not store data from refused look-ups. Data in accepted submissions, including videos you appear in, is kept with the submission (Section 9).

4E.5 Your rights

You can object at any time by sending the post or profile URL to privacy@tribue.io. If a submitted video shows you and you object, we will review it and delete our copy unless we have an overriding reason to keep it. Records of money paid for the post are kept, without the video.

4F. Website visitors and waitlist sign-ups

4F.1 Visitors to our sites

• Hosting. Our hosting provider, Vercel, processes your IP address and request data to serve each page.
• Analytics. We load PostHog in your browser only if you click "Accept" on our cookie banner (see our Cookie Policy).
• Error monitoring. Sentry records errors in your browser. By default it receives no IP address or cookies, and security tokens are removed from URLs.
• Referral links. If you open a referral or campaign share link, we set a referral cookie and record the click with a hashed IP address and your user agent (Cookie Policy), so the person who shared it can be credited if you sign up.
• Third-party files. Some pages load files from other services, which receive your IP address: emoji data from unpkg in the message composer, and Google Fonts on the masterclass page. Our masterclass and onboarding sites collect no other data.

4F.2 Waitlist

• Joining: your email, where you signed up, and whether you are a brand or a creator.
• Your waitlist profile: name, handle, date of birth (to check you are 18 or over), country, website, social handles and where you heard about us. Creators also give their niches. Brands and agencies also give a phone number and tell us whether they already work with creators: if so, roughly how many creators (and, for agencies, how many brands) and their monthly spend on them; if not, which marketing they run today.
• Resuming: a cookie lets you pick up where you left off for 24 hours.

4F.3 Legal bases

• Joining the waitlist and reserving your handle: contract (steps you ask us to take before signing up).
• Analytics: consent.
• Referral cookie and click record: legitimate interests (crediting the person who invited you).
• Marketing email: only with your consent.

4G. Google user data (Google sign-in and YouTube)

What we access, use, share, protect and keep when you sign in with Google or link a YouTube channel is set out in Google user data, at the top of this policy.

4H. Merchants who use our Shopify app

This part is for brands and agencies that connect a Shopify store to Tribue by installing the Tribue Shopify app. The app credits sales that came through a creator's link to that creator, so the creator can be paid the commission the campaign sets. What we record about the store's shoppers is in 4D.

4H.1 What we access from your store

• The connection: your shop address (for example your-store.myshopify.com) and the access credentials Shopify issues when you install the app. We store the credentials encrypted.
• Orders: the order ID, order number and name (for example #1001), total, currency, payment status, date, whether it is a test order, and the order's cart attributes. Of the cart attributes we keep only the creator's link code. Besides the notifications Shopify sends for new orders, we also read recent orders through Shopify's API, with their refunded amounts and cancellation dates, to catch any notification that was missed.
• Refunds: the refund ID, the order it belongs to, its date and its transactions. Of the transactions we keep only the refunded amounts.
• Cancellations: the order ID, the date and reason of the cancellation, the total and the currency.
• Storefront events from our web pixel, as listed in 4D.
• Permissions we ask Shopify for: reading orders, reading customer events, and reading and writing our own web pixel. We do not ask for access to your customers' names, email addresses, phone numbers, postal addresses or payment details, and we do not keep them.
• Uninstall and privacy requests: when you uninstall the app, Shopify sends us your shop's details, including the store owner's contact details. Shopify's privacy requests about a shopper can include that shopper's email address and phone number. We use these only to act on the uninstall or the request, and we do not keep them.

4H.2 How we use it, and on what basis

We use your store's data only to provide Tribue to you. We do not sell it, we do not use it to contact your customers, and we do not use it, even in anonymous or aggregated form, to train or improve AI or machine learning models.

4H.3 Who receives it

• Creators see their own credited sales, one line per order: the date of the sale and of the click, the amount, any refund and the country of the click. They never see your customers' details.
• Our service providers that host and store data for us, under contracts that limit their use of it to serving us (Section 8).
• Shopify, which sends us this data and receives our app's requests (8.2).
• Authorities, where the law requires it.

No one else receives your store's data.

4H.4 How long we keep it

When you uninstall the app or disconnect your store, we stop crediting new sales to creators and delete your store's data within 30 days. Two exceptions protect creators: orders that came through a creator's link before you disconnected are still credited and paid, and orders that produced a commission are kept as accounting records for the period the law requires. Section 9 has the details.

4H.5 Your rights and questions

You can ask for a copy of your store's data in a structured, machine-readable format, ask us to correct it, or ask any question about how we handle it, at privacy@tribue.io. We reply within one month. Your other rights are in Section 11.

5. Data you must give us

To create an account, you must give us your email address and date of birth. A creator workspace also needs a name, a handle and your country. To get paid, you must complete Whop's identity checks. Without this data we cannot provide the service. Everything marked optional is optional.

6. Automated decisions and profiling

6.1 Overview. Some decisions are made automatically by fixed rules we wrote. We do not use machine learning or an outside vendor for them. They are necessary for our contract with you (Art. 22(2)(a) GDPR): they are how we check that every submission meets its campaign's requirements. You can ask for a person to review any of them, give your view and contest the decision (6.8).

6.2 Refusals when you submit. A submission is refused straight away if:

• the post was published more than 30 minutes before you submit it;
• the post's author does not match the social account you verified with us;
• the video is shorter than the campaign's minimum length, or the post is on a platform the campaign does not accept;
• the post has already been submitted; or
• the campaign belongs to your own workspace.

The refusal message tells you which rule applied. If we cannot complete a check, for example because the publish time is unavailable or ownership cannot be confirmed, the post is not refused. It gets a warning tag and goes to a person for review, even on campaigns that otherwise approve automatically.

6.3 Automatic rejections of pending submissions. A submission still waiting for review is rejected automatically, with a reason from section 3.3 of our Content Moderation Policy, when:

• the campaign ends or is cancelled (approved submissions are paid in final settlement, not rejected);
• the campaign's budget is used up or fully allocated; or
• the campaign ends before the content reaches the minimum view requirement.

The brand can re-approve a rejected submission later.

6.4 Unusual-view checks. We automatically check submissions for signs of fake views, such as very low engagement for the number of views, sudden view spikes, or large view removals by the platform. A match is recorded on the submission and reviewed by our team. It does not change the submission's status, earnings or payout date. Only a person on our team can decide there was fraud, and any action that follows comes with a statement of reasons (see our Content Moderation Policy). The recorded result also counts in your creator trust score (6.5).

6.5 Trust scores. We calculate a score for each workspace from its history. Recent events count more and older ones fade (a half-life of about 270 days). A new account is "Unrated" until it has enough history.

• Scores decide nothing. No score approves or rejects submissions, changes payouts or limits access.
• Confirmed fraud. If our staff confirm fraud, the workspace's score is set to zero ("Suspended").
• Wider use. Before any score is shown to other users or used in a decision, we will update this policy and give at least 15 days' notice.

6.6 Leagues, XP and leaderboards. You earn XP for activity such as submissions, streaks, lessons and referrals. Leagues are XP bands: your league badge appears on your public profile, and brands see it when you apply to their campaigns. Each month, the top 10 creators by earnings get a leaderboard badge. None of these has cash value or decides anything automatically.

6.7 What is not automated. Bans, account suspensions and payout freezes are always decided by a person on our team. No automated process takes back money that has been paid out or forfeits earnings.

6.8 How to get a human review or contest a decision.

• Re-check. Use "Recheck" on the submission to read the post again.
• Contact us. Write to support@tribue.io with the submission and why you think the decision is wrong. A person on our team will review it, and if a rule wrongly refused a genuine post, we can accept it. The full process is in section 6 of our Content Moderation Policy.
• Data-protection requests about automated decisions go to privacy@tribue.io.

7. Transfers outside the EEA

7.1 Some of our service providers are in the United States or can access data from there. We transfer data to companies certified under the EU-US Data Privacy Framework, relying on the European Commission's adequacy decision, or otherwise under the Standard Contractual Clauses (Commission Decision 2021/914), with additional safeguards where needed. For UK data, we use the UK Extension to the Data Privacy Framework or the UK Addendum to the Standard Contractual Clauses.

7.2 You can ask for a copy of these safeguards at privacy@tribue.io.

8. Service providers and other recipients

8.1 Processors (they act on our instructions):

8.2 Independent controllers (they use the data under their own privacy policies):

• Whop: payments, identity checks (KYC), payouts and withdrawals, and card payments for invoices and top-ups. Whop's payout and identity-check components load in your browser (Cookie Policy).
• Stripe: records of older payments and payouts. Stripe payout accounts are closed when you delete your account.
• Google: sign-in, and YouTube data if you link a channel by signing in with YouTube (Section 4G).
• Shopify: for merchants who connect a Shopify store, Shopify sends us the store and order data in 4H, and receives the requests our app makes to the store.
• Discord: sign-in, our community and support server, and alerts to our team.
• unpkg and Google Fonts: your browser downloads files from them directly, so they receive your IP address. We send them nothing else.
• Brands, agencies and clients: what they receive about creators (4A.4).
• AI apps you connect: within the read-only permissions you approve, an AI app you connect to your workspace can read its campaigns, submissions, credits, transactions and notifications. You can revoke access at any time. The app's provider handles the data under its own terms.

8.3 Our staff. Our team can see account data in our admin tools, and every admin change is logged with the admin's IP address. Staff can also use an AI assistant with read-only access to admin data. Data from merchants' stores (4D, 4H) is not made available to it.

8.4 Authorities and legal claims. We share data where the law requires it, or where it is needed to establish, exercise or defend legal claims.

8.5 Business transfers. If our business is sold or merged, data may pass to the buyer under this policy.

8.6 Changes to this list. We update this list before we start sending personal data to a new provider, and when we replace one.

9. How long we keep data

10. Security

10.1 We protect your data with encryption in transit (HTTPS); encryption at rest for sign-in tokens, payment-provider tokens and two-factor secrets; hashed login and backup codes; passwordless sign-in with optional two-factor authentication; new-device alerts and the option to sign devices out; access-controlled messaging and private file storage with expiring links; rate limits; and admin access restricted to staff and logged. Our payment provider never gives us your card or bank details.

10.2 If a breach is likely to put you at risk, we will tell you and the regulator as the law requires.

11. Your rights

11.1 Your rights under the GDPR and UK GDPR. You can ask us to give you a copy of your data, correct it, delete it, restrict how we use it, or give it to you in a portable format. You can object where we rely on legitimate interests, and always to direct marketing. Where we rely on consent, you can withdraw it at any time. You can also ask for a person to review an automated decision (6.8).

11.2 How to exercise them.

• Delete your account: Settings → Account → Delete account.
• Change your profile: edit it in Settings.
• Anything else: email privacy@tribue.io from your account email address.

We reply within one month. For complex requests we may extend that by two months, and we will tell you if we do. We may ask you to confirm your identity.

11.3 Before you can delete your account. You cannot delete your account while you have a balance, an open obligation (such as an active campaign or an unpaid charge) or an unresolved withdrawal. The screen tells you what is outstanding. This protects money owed to you and to others.

11.4 What deletion does.

• Deleted: your user record, sign-in methods, devices and two-factor settings; onboarding answers; your public and owner profiles; linked social accounts; notifications, XP and streaks; billing details; connected AI app access; uploaded profile images; demographics screenshots; message attachments; and any Stripe payout account.
• Blanked: the text of your messages, in direct messages and groups. The conversation stays for the other people, without your words.
• Kept, without your name or contact details, because others rely on them or the law requires them:
  • submissions, their stats and copies of the videos, which are the brand's record of what it paid for. The full provider data and the screenshots are removed;
  • the credit ledger, payouts, withdrawals, top-ups and invoices, with client contact details removed from invoices;
  • referral earnings records;
  • the admin audit log, which records the deletion using a hashed form of your email.
• Held by Whop: your Whop account, identity checks and payout history. Whop is an independent controller, so contact Whop to delete them.

Deleting a workspace without deleting your account follows the same rules, after the 14-day period.

11.5 Complaints. You can complain to the Cyprus Commissioner for Personal Data Protection (1.4), or to the supervisory authority where you live or work. UK residents can complain to the ICO (ico.org.uk). We would appreciate the chance to resolve your concern first, at privacy@tribue.io.

12. US state privacy rights (including California)

12.1 Notice at collection. The data we collect is listed in Section 4. In CCPA terms, the categories are:

• identifiers (name, email, handle, IP address, device IDs);
• customer records (billing identity, phone);
• commercial information (transactions, campaigns);
• internet activity (pages, clicks, device data);
• approximate geolocation (city or coordinates derived from your IP address);
• audio and visual content (submitted videos and images);
• professional information (brands worked with, niches, portfolio);
• education information (education level, school and major, where provided);
• characteristics (date of birth, and gender where provided);
• inferences (trust scores, leagues).

Sources and purposes are in Section 4, and retention in Section 9.

12.2 Sensitive personal information. We do not use sensitive personal information to infer characteristics about you. The coordinates in device records are approximate, derived from your IP address, not precise geolocation.

12.3 Selling and sharing. We do not sell personal information, and we do not "share" it for cross-context behavioural advertising. Our own sites run no ad trackers. We do not knowingly sell or share data of consumers under 16. The disclosures in Section 8 are to service providers or contractors for business purposes, or at your direction.

12.4 Your rights. You can ask to know, delete or correct your information, and to limit the use of sensitive information, using the routes in 11.2. You can use an authorised agent. We will not discriminate against you for exercising these rights.

12.5 Financial incentive. The referral programme pays referrers a share of our fee on referred users' payouts.

13. Children

You must be 18 or older to use Tribue, for every account type. We check your date of birth at onboarding and on the waitlist and refuse sign-ups under 18, and Whop checks your identity before you can withdraw money. We do not knowingly collect data from anyone under 18. If you believe a minor has an account, contact support@tribue.io and we will delete it.

14. Do Not Track

We do not respond to browser "Do Not Track" signals. You choose whether we use analytics through our cookie banner (see our Cookie Policy).

15. Changes to this policy

15.1 We post every change here and update the date at the top.

15.2 If a change materially affects how we use your data, including a new feature that uses new data, we will tell you by email or in the app at least 15 days before it takes effect.

15.3 Where a change needs your consent, we will ask for it. We will not apply a change to data collected earlier unless we have a legal basis to do so.

16. Contact

Questions about this policy or your data: privacy@tribue.io. Our other contacts are in Section 1.