Privacy Policy

ViewsBase is run by Adam T, LLC, a Delaware company ("we"). For any privacy question or request, email team@viewsbase.com.

This policy covers the viewsbase.com website and app, and the people who use them: teams (brands, app studios and agencies that run creator campaigns), creators who join those campaigns, and visitors.

A team decides which creators it works with, what it pays and which data it asks creators for. For that campaign data, we act on the team's instructions. If you are a creator, the team running your campaign also sees the data you give for that campaign, and their own privacy policy applies to how they use it.

Team accounts: email address, workspace name and logo, team member emails and roles, invites, and billing status from Stripe.

Creator accounts: email address, display name, social media handles, and follower counts.

Campaign data:

• Post links, captions, thumbnails and public view, like, comment and share counts, with their history over time.
• Copies of public posts, so the team can review them.
• Application answers, photos and clips that a creator sends to a campaign.
• Analytics screen recordings that a creator uploads, and the numbers read from them, such as audience countries.
• Offer details, amounts owed and payment records.
• Discord user IDs, if a team uses Discord.

Payout details: the payout method a creator adds, such as a Wise tag, UPI ID, bank details or a USDC wallet address. We keep a history of changes to protect creators from fraud.

Technical data: sign-in cookies (see below) and your IP address, which we use in memory to limit repeated requests. We do not store IP addresses in our database. Our hosting providers keep standard server logs.

We do not collect dates of birth, government IDs or phone numbers.

• To run the service: track posts, count views, calculate what each creator is owed and build reports.
• To read analytics recordings and check posts, with AI, so teams can confirm views before they pay.
• To sign you in and keep accounts safe, for example by flagging payout changes to the team for 72 hours and emailing you about them.
• To bill team subscriptions.
• To send emails about your account. We do not send marketing emails without your consent.

We do not sell personal data, show ads or use advertising trackers. We do not use your data to train AI models.

The team running your campaign. If you are a creator, the team sees your campaign data, including your payout details, so it can pay you.

Service providers. We use these companies to run ViewsBase. Each gets only the data it needs for its task:

Supabase

Database, sign-in and file storage. Holds all the data on this page.

Vercel

Hosts the website and app.

Stripe

Subscriptions and card payments. Gets your workspace name, email and card details. We never see or store your full card number.

Resend

Sends our emails: sign-in codes, invites and payout alerts. Gets your email address and the email content.

Trigger.dev

Runs scheduled jobs, such as refreshing view counts every 6 to 24 hours, depending on the plan.

RapidAPI data providers

Read public TikTok and Instagram data. Get post links and handles.

YouTube API Services (Google)

Read public YouTube data. Get post links and channel IDs.

OpenRouter and Google Gemini

Read the numbers in analytics screen recordings, and check submitted posts. Get the recording or media and the post's public details.

Discord

Sends campaign messages when a team connects its Discord server. Gets Discord IDs, creator names, post links and payout amounts.

Dub

Makes tracking links. Gets the creator's handle and counts clicks.

Sentry

Error reports. We remove user details, cookies and request content before errors are sent.

The law. We share data when the law requires it, or to protect people from fraud or harm. If ViewsBase is sold or merged, the data moves with it under this policy.

ViewsBase uses YouTube API Services to read public YouTube data. When you track YouTube posts, you also agree to the YouTube Terms of Service, and Google handles data under the Google Privacy Policy.

We use only the cookies ViewsBase needs to work. There are no analytics or advertising cookies, so there is no cookie banner.

• Sign-in cookies keep you signed in. Creators who use a personal access link get an access cookie that lasts 30 days.
• Settings, such as your light or dark theme and table layout, are kept in your browser.

We keep data while your account or campaign is active. When a team deletes a creator or campaign, the posts and stats go with it. Payment records and the history of payout detail changes are kept, because teams and creators need them for disputes, fraud checks and taxes.

To close your account, email team@viewsbase.com. We delete your data within 30 days, except the records the law or open disputes require us to keep.

You can ask for a copy of your data, or ask us to correct or delete it. Email team@viewsbase.com from the address on your account. We answer within 30 days. If the data belongs to a team's campaign, we pass your request to that team.

If you live in the EU, UK or a US state with a privacy law such as California, you have these rights by law, and you can also complain to your local data protection authority. We do not sell or share personal data for targeted advertising.

We and our providers process data in the United States and other countries. When data leaves the EU or UK, our providers use the standard legal safeguards for that transfer.

Sign-in codes and API keys are stored only as hashes. Payout changes are flagged to the team for 72 hours and emailed to the creator, who can lock the account in one click. No system is fully secure: if a breach affects your data, we tell you without delay.

ViewsBase is for people 18 and older. We do not knowingly collect data from anyone younger.

We update this page when our practices change and show the date at the top. For important changes, we email account holders before they take effect.