კონფიდენციალურობის პოლიტიკა

1. Data we collect

• Account & identity: name, email, password (hashed by our auth provider), role, organization, and language preference.
• Profile: creator/brand profile details you provide (handle, bio, niche, links, rate card, social accounts).
• Connected social accounts: if you connect a YouTube, TikTok, Instagram or Facebook account, the account details, content and statistics described in Sections 4 and 5.
• Tracking & attribution: when a tracking link is clicked we record the IP address, user-agent, referrer, timestamp, and set a visitor identifier cookie (mr_vid) to attribute later conversions. Conversions are received from connected stores via webhooks and may include an order identifier and a hashed customer reference.
• Financial: commission and payout records, and payout details you provide (e.g. bank/IBAN or payout-provider account). Payments to brands are processed by our payment service provider.
• Verification (KYC): identity information and documents needed for identity verification, and — for businesses — the names, dates of birth and nationalities of directors and owners of 25% or more. We check verified members, and each of those people, against sanctions, politically-exposed-person and related watchlists before approval and while money or campaigns are in progress.
• Contract signing: when you sign an agreement we record your typed name, the timestamp, your IP address, your browser user-agent, and a cryptographic fingerprint of the document as the signature record. These details are reproduced in the sealed PDF, which is sent to both parties to that agreement and kept as evidence that the signing took place.
• Communications & usage: messages you send through the Platform, your conversations with the in-app assistant (Section 4), support requests, in-app notifications, and technical/usage logs.

2. How we use data and our legal bases

• To provide the service (accounts, campaigns, tracking, commissions, payouts) — performance of a contract.
• Attribution, analytics, fraud prevention, and security — our legitimate interests in operating a trustworthy marketplace and preventing abuse.
• Identity verification, tax, accounting, and AML — compliance with legal obligations.
• Optional cookies and certain communications — your consent, which you may withdraw at any time.

3. Cookies and tracking

We use strictly necessary cookies to run the Platform and an attribution cookie for tracking links. For details and choices, see our Cookie Policy.

We do not embed players or other content from YouTube, TikTok, Instagram or Facebook, so those platforms cannot place cookies on your device through our pages.

4. Connected social accounts

Creators may connect one or more social accounts (YouTube, TikTok, Instagram, Facebook). Connecting is entirely optional — the Platform works without it — and you choose which accounts to connect. You sign in on the platform’s own page and grant access through its official authorization flow; we never ask for or store your social account password. The access is read-only: we do not post, comment, message, or take any other action on your behalf.

Where we offer it, you can instead add an account by its username and prove it is yours with a code you place in its bio. For such an account we read only what anyone can see on its public profile — through the YouTube Data API for YouTube, and through a public-data provider (Section 6) for the other platforms.

With your authorization, we read the following from each account you connect:

• YouTube: set out in full in Section 5.
• Instagram (professional accounts): the account’s ID, username, name, profile picture, bio, website, and follower, following and post counts; its posts and reels (caption, type, link, image or thumbnail, publish time, and like and comment counts) with their insights (views, reach, saves, shares, interactions, profile visits, follows, and watch time for reels); account insights (reach, views, profile views, accounts engaged, link taps, and when your followers are online); and follower demographics (age and gender, countries and cities, as counts). Permissions requested: instagram_basic, instagram_manage_insights and pages_show_list when you connect through Facebook, or instagram_business_basic and instagram_business_manage_insights when you connect with Instagram directly.
• Facebook Pages: the Pages you manage and, for the ones you choose, each Page’s ID, name, picture, link, about text, website, verification badge, follower and like counts, and whether you own the Page or manage it for someone else; its posts and reels (text, link, picture, publish time, video length, likes, reactions, comments and shares) with post reach and video views and view time; and Page insights (impressions, reach, Page views, new followers and video views). Permissions requested: pages_show_list, pages_read_engagement and read_insights.
• TikTok: the account’s IDs, display name, username, profile picture, bio, profile link, verification badge, and follower, following, like and video counts; and its videos (title, description, cover image, link, duration, publish time, and view, like, comment and share counts). TikTok provides no daily history, watch time or audience demographics, so we hold none. Permissions requested: user.info.basic, user.info.profile, user.info.stats and video.list.

For Facebook and Instagram we also store the ID Meta assigns you for our app, which is how Meta tells us when you remove the app or ask for your data to be deleted.

How we use it. Only for features you can see:

• your public Meet Referral profile shows each connected account’s name, handle, picture and link with its follower, post and view counts, and totals such as followers, views and engagement rate — visible to anyone, including brands and search engines;
• brands see those figures when they browse creators and, for a video you submit to their campaign, its link, title, and view, like, comment and share counts;
• only you see per-post statistics, daily history and audience demographics, in your dashboard;
• we check a video you submit to a campaign against your connected accounts to confirm it is yours, and let you pick it from a list instead of pasting a link;
• when you ask the in-app assistant a question, it reads what it needs for the answer — which can include your connected accounts’ figures, daily history, audience and top posts — and sends it with your question to an AI provider, which writes the answer (below).

We do not sell this data, use it for advertising or to target ads, or share it with anyone other than the service providers who host and process it for us (Section 6) or where the law requires. These numbers never change how much you earn.

The assistant. It reads only what the person asking can already see on the Platform — a brand’s assistant, for example, only the figures brands see — and sends nothing to an AI provider until they ask. The answers are written by Google (Gemini API) or, where we enable it, Anthropic (Claude API); spoken questions are written down, and answers read aloud are spoken, by Google. Under the paid API terms we use, neither provider uses this data to train its models, and each may keep it for a limited time to detect misuse. Where a manager workspace (below) holds a live voice conversation with the assistant, Google keeps that conversation’s audio and text for up to a day so it can resume. To answer faster, our cache (Upstash) keeps the summary the assistant reads, its answer to a conversation’s first question and the names it listens for in spoken questions — each for ten minutes at most. Your conversations stay in your account until you delete them or your account is erased, and a deletion request from Meta deletes them too (below).

Where a connected account belongs to someone else (for example a Facebook Page you manage for a client), it is shown as work you do and its audience is not counted as your own reach.

Storage and refresh. Access tokens are encrypted at rest (AES-256-GCM) and are never shown to brands or other users. While an account is connected we refresh its data automatically, normally once a day, unless you pause it.

Disconnecting. You can disconnect any account at any time from Connected accounts in your dashboard. We stop reading from it and remove it and its numbers from your public profile immediately, and we ask the platform to revoke our access where it gives apps a way to: for YouTube and TikTok, and for Facebook once no other Page or Instagram account you connected through the same Facebook login still relies on it. Instagram gives apps no way to revoke access to an account connected directly with Instagram, so also remove Meet Referral in Instagram’s settings (see below). Within 7 days of disconnecting we delete everything we stored for the account — its access tokens, posts, statistics and audience data. If you reconnect it before then, its history is kept.

Deletion. Besides disconnecting:

• YouTube access that stops working: if you revoke access in your Google Account, or it stops working for another reason, we delete the channel’s data within 30 days (Section 5).
• TikTok, Instagram or Facebook access that stops working without you disconnecting: the account is marked as needing to be reconnected, and its data stays until you disconnect it, ask us to delete it, or delete your Meet Referral account. A deletion request from Meta is handled immediately (below).
• On request: email privacy@meetreferral.com and we will delete the data we hold from any of your connected accounts within 7 days.
• Deleting your Meet Referral account deletes all connected-account data, including access tokens, when the account is erased at the end of its 30-day cancellation period — disconnect your accounts first if you want it gone sooner.

Two records stay after deletion because they are part of your campaign history: a video you submitted to a campaign (its link, title, and the counts we recorded for it during the campaign), and the record that it was claimed and paid for (its platform, ID and link, and the account it was published on), which stops the same video being paid for twice.

Revoking access at the platform. You can also withdraw Meet Referral’s access in each platform’s own settings:

• Google (YouTube): https://security.google.com/settings/security/permissions;
• Facebook: Settings → Apps and websites (Pages connected for business use can appear under Business integrations);
• Instagram: Settings → Apps and websites;
• TikTok: in the TikTok app, Settings and privacy → Security → Manage app permissions.

When you remove Meet Referral on Facebook or Instagram, Meta notifies us and we stop reading from those accounts straight away. You can also ask Meta to have your data deleted, which Meta offers for apps you have removed. We handle that request immediately: the moment Meta sends it, we delete those accounts’ access tokens, posts, statistics and audience data and remove them from your public profile. We also delete all your conversations with the in-app assistant, because any of its answers can quote those accounts’ numbers. Meta shows you a confirmation code and a link to our data deletion page, which explains what the request covered.

Manager workspaces. An agency or manager can run its clients’ work in a Meet Referral workspace and connect a client’s Instagram, Facebook, YouTube, TikTok, Twitch, Reddit or Spotify account to it. The client connects it through a link the workspace sends, or the workspace’s team connects it for the client; either way, on the platform’s own sign-in page, as above. The permissions are the same read-only ones as for creators (above, and Section 5 for YouTube); for Twitch they are moderator:read:followers and channel:read:subscriptions, for Reddit identity, history and read, and for Spotify playlist-read-private, playlist-read-collaborative and user-follow-read. From the account the workspace reads:

• its profile (name, handle, picture and link) and follower count;
• its daily insights, where the platform reports them: reach, profile views, accounts engaged, link taps, watch time, and subscribers gained and lost;
• its audience, where the platform reports it: countries, cities, age and gender;
• for Twitch, its paid subscriber count; for Reddit, its karma; for Spotify, the artists it follows and its playlists, read when the team opens them and not stored.

This is read for that workspace only. Its team sees it, each teammate as their role allows, and so do the people the workspace shares that client’s pages with; the workspace’s assistant reads it for them as described above. We never read the account’s messages, and we never post, comment or take any other action on it.

Disconnecting the account in the workspace stops the reading at once and deletes its access tokens. Within 7 days we delete everything else we stored for it — its name, handle, picture and follower count, its daily insights and its audience data. If the workspace reconnects it before then, its history is kept. If the access stops working, the account is marked as needing to be reconnected and its data stays until the workspace disconnects it — except a YouTube channel’s, which we delete no later than 30 days after we last refreshed it (Section 5). If the client removes Meet Referral on Facebook or Instagram, the reading stops; if they also ask Meta to delete their data, we delete the account and everything we stored for it at once, together with the workspace’s conversations with the assistant about that client, because any of its answers can quote the account’s numbers.

5. YouTube API Services

Meet Referral uses YouTube API Services — the YouTube Data API and the YouTube Analytics API — to let creators connect their YouTube channels and to read public information about YouTube videos and channels. Google’s handling of your information is governed by the Google Privacy Policy at http://www.google.com/policies/privacy. By using our YouTube features you agree to be bound by the YouTube Terms of Service (see our Terms).

What we access, collect and store. When you connect a channel you sign in with Google and grant read-only access (the youtube.readonly and yt-analytics.readonly permissions). With it we access, collect and store:

• Channel details: channel ID, name, handle, description, country, creation date, profile picture and link, and its subscriber count (unless you hide it), video count and total views;
• Your videos: for each video uploaded to the channel, its ID, title, thumbnail, link, publish date, duration, tags, category and whether it is marked as made for kids, with its view, like and comment counts;
• YouTube Analytics reports: for the channel, day by day — views, watch time, average view duration, likes, comments, shares, and subscribers gained and lost; for each video, day by day — views, watch time, average view duration, average percentage viewed, likes, comments, shares and additions to playlists; and, over the last 90 days, the age groups and genders of your viewers and the countries your views come from, as percentages;
• Authorization: the access and refresh tokens Google issues for the connection, and the permissions you granted.

We do not receive your Google password or email address, and we do not read your comments, subscriptions or watch history.

Without any sign-in, we also use the YouTube Data API with our own API key to read public information: for a YouTube link submitted to a campaign, the video’s title, channel name, thumbnail, and view, like and comment counts; and, where these features are available, for a channel added by its handle (by a creator claiming it, or by a brand following it in our tracking tool), the channel’s public details and its videos’ public statistics.

How we use, process and share it.

• Your public profile shows your channel’s name, handle, picture and link with its subscriber, video and view counts, and includes them in your profile totals — visible to anyone, including brands and search engines.
• Brands see those figures when they browse creators and, for a video you submit to their campaign, its link, title, and view, like and comment counts.
• Your YouTube Analytics data — daily history, per-video performance and audience demographics — is shown only to you, in your dashboard. A channel connected in a manager workspace is read for that workspace instead (Section 4).
• We check a video you submit to a campaign against your channel’s uploads to confirm it is yours.
• If you ask the in-app assistant about your channel, the figures it needs are sent to the AI provider that writes the answer, and briefly cached by us (Section 4).
• It is stored in our database (Supabase, in Frankfurt), with a copy of your channel picture in our file storage (Cloudflare R2). If something fails, our error monitoring (Sentry) may receive technical identifiers such as a channel or video ID.

We do not sell YouTube data, use it for advertising, or share it with anyone else except where the law requires.

Advertising and third-party content. Meet Referral shows no advertising, and we do not allow third parties, including ad networks, to serve content or ads on it.

Your device. Our YouTube features store and read nothing on your device beyond the cookies and browser storage described in Section 3 and our Cookie Policy. We do not embed YouTube’s player or other Google content, so Google does not set cookies through our pages; when you connect a channel you sign in on Google’s own site, under Google’s Privacy Policy.

Revoking access. You can disconnect your channel at any time from Connected accounts in your dashboard, which also asks Google to revoke our access. You can also revoke Meet Referral’s access in your Google Account’s security settings at https://security.google.com/settings/security/permissions.

Deletion. When you disconnect your channel we delete the YouTube data we stored for it — channel details, videos, statistics, analytics reports and tokens — within 7 days. If you revoke access in your Google Account, or it stops working for any other reason, we can no longer refresh that data, and we delete it no later than 30 days after we last refreshed it — so within 30 days of the revocation. You can also ask us to delete it at any time by emailing privacy@meetreferral.com, and we will do so within 7 days. Only the campaign records described in Section 4 are kept after that. A channel connected in a manager workspace is deleted on the same terms when the workspace disconnects it or its access stops working (Section 4).

Google API Services User Data Policy. Meet Referral’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Questions. For questions or complaints about how we handle YouTube data, contact privacy@meetreferral.com.

6. Who we share data with

We share personal data with service providers (processors) only as needed to run the Platform:

• Hosting — Vercel. It runs our application; our server functions run in Frankfurt, Germany.
• Database & authentication — Supabase (Frankfurt, Germany).
• File storage — Cloudflare (R2): files uploaded to the Platform, and copies of profile pictures from connected social accounts.
• Payments (brand charges) — our payment processor, where applicable.
• Creator payouts — the payout/bank rail you select (e.g. Wise).
• Transactional email — Resend.
• Error monitoring & diagnostics — Sentry.
• Background jobs — Inngest. Work we run in the background, such as sending email notifications and refreshing connected accounts, passes through it with what each job needs — for example the recipient’s email address.
• AI assistant — Google (Gemini API) and, where enabled, Anthropic (Claude API). They write the in-app assistant’s answers from the question and the records it reads (Section 4), and read the documents a manager workspace gives them. Google also writes down spoken questions and speaks answers aloud.
• Caching and rate limiting — Upstash (Frankfurt, Germany): short-lived counters, keyed by account or IP address, that limit how often requests can be made, and the assistant’s short-term cache (Section 4).
• Product analytics — PostHog (EU Cloud, Frankfurt). Used only on signed-in dashboards and during onboarding, to see where people get stuck. We send a pseudonymous account identifier and the step reached — never your name, email, or any amount of money.
• Public social data — ScrapeCreators and Apify. When a TikTok, Instagram or Facebook account is added by its username rather than connected (Section 4), or followed by a brand in our tracking tool, we send its public username or link to read its public profile and posts.
• Sanctions and PEP screening — OpenSanctions Datenbanken GmbH (Berlin, Germany). We send the name, date of birth, nationality and company registration number you provide; the results are kept in our compliance records. Identity documents are reviewed by our own staff and are not sent to them.

We may also disclose data where required by law, to enforce our terms, or to protect rights, safety, and security. We do not sell your personal data.

7. International transfers

Our database and application servers are hosted in the European Economic Area (Frankfurt, Germany), and so is our cache. Some providers process data outside Georgia and the EEA, including in the United States: Google (Gemini API), Anthropic (Claude API, where enabled) and Inngest (background jobs). For transfers to the United States we rely on standard contractual clauses. For other international transfers we rely on appropriate safeguards such as standard contractual clauses or an adequacy decision, as applicable.

8. Retention

We keep personal data for as long as your account is active and as needed to provide the service. Financial, tax, and AML records are retained for the periods required by law. Tracking/click data is retained only as long as needed for attribution, fraud prevention, and reporting, after which it is deleted or anonymized. Records of each sign-in to your account (the time, your email address and IP address) are kept for 90 days, to look into account takeovers and payout disputes, and then deleted. Data from connected social accounts is kept and deleted as described in Sections 4 and 5.

When your account is erased at the end of its 30-day cancellation period, its sign-in is closed too: your email address is released, so you can sign up with it again as a new account, and your sign-in records, sessions and any Google sign-in linked to it are deleted.

9. Your rights

Subject to applicable law, you have the right to:

• access a copy of your personal data;
• rectify inaccurate data;
• erase your data (“right to be forgotten”), subject to legal retention obligations;
• restrict or object to certain processing;
• data portability;
• withdraw consent at any time; and
• lodge a complaint with a supervisory authority — in Georgia, the Personal Data Protection Service.

To exercise these rights, contact privacy@meetreferral.com.

10. Security

We use technical and organizational measures including encrypted transport, tenant isolation with row-level security, hashed credentials, and access controls. No method of transmission or storage is completely secure; we work to protect your data and to notify you and the authorities of breaches where required.

11. Children

The Platform is not intended for, and we do not knowingly collect data from, anyone under 18.

12. Changes and contact

We may update this Policy and will notify you of material changes. Questions or requests: privacy@meetreferral.com.