Privacy Policy

Effective 11 August 2026. Last updated 7 October 2026.

Claritea reads a creator's YouTube channel and turns it into analytics. Doing that means handling data about the creator, about the people they invite, and about members of their audience who left public comments. This policy explains all of it, including the parts that are uncomfortable.

1. Scope and who this covers

This policy applies to claritea.ai, the Claritea application, our documentation site, and the shared dashboards we serve. It covers four groups of people, and the fourth is the one most policies leave out:

• Account holders are creators who sign up and connect a YouTube channel.
• Invited viewers are people a creator gives a seat to, so they can sign in and see that creator's dashboards.
• Share recipients are people who open a share link. They do not sign in and have no account with us.
• Audience members are people who commented publicly on a connected creator's videos. If that is you, you have no relationship with Claritea, you did not agree to anything, and you probably do not know we exist. We still hold your display name and the text of your comment, because the creator connected their channel and we retrieved them from YouTube's public API. Section 13 is written for you and tells you how to get them removed.

2. Who is responsible, and how to reach us

PayPer Technologies Inc. d/b/a Claritea ("Claritea", "we", "us" or "our") is the organisation accountable for the personal information described here. Our registered address is 505 - 70 Montclair Ave, Toronto, Ontario, M5P 1P7.

We have a designated Privacy Officer accountable for compliance with this policy. Privacy questions, access requests, deletion requests and complaints go to privacy@claritea.ai, which reaches them directly. We answer privacy requests within 30 days, and we will give you the name of the individual holding that role if you ask at the same address.

3. What we collect

Account and profile

Your email address, first and last name, display name, time zone, locale, subscription tier, account type, and a referral source if you gave one. If you subscribe to a paid plan we also store the customer identifier our payment processor assigns you, so we can tie your subscription to your account. We never receive or store your card number. Your card details go to the payment processor, and what comes back to us is limited billing records such as your plan, the history of charges, and a billing contact.

Authentication and session

Claritea has no passwords. Signing in sends a one-time code to your email address; we store a keyed hash of that code, and the code itself only for as long as it takes to send you the email. It expires after 10 minutes. A successful sign-in creates a session record holding a hash of the session token, the IP address the session was created from, a shortened browser user agent string, and an expiry 30 days out that moves forward as you keep using the service.

Google account identity

When you connect a channel, Google returns your email address and a stable account identifier for your Google account, plus access and refresh tokens. We do not request the Google profile scope, so we never receive your Google display name or profile picture. Access and refresh tokens are encrypted at rest. The account email and identifier are stored in plain text so we can show you which Google account a channel is connected through.

YouTube channel, video and analytics data

Channel details, the list of uploads, per-video metadata such as titles, descriptions, publication dates, durations and thumbnails, and the analytics metrics YouTube Analytics reports for your channel, such as views, watch time and audience figures.

Video audio and transcripts

We process the audio of your videos to detect sponsor segments and to generate transcripts. The transcript text and the extracted audio file are stored against the video.

Audience comment text and display names

The text of public comments on your videos and the public display name attached to each one. These are stored as raw files and as the published tables that power the comment, sentiment and sponsor-sentiment views.

Derived insights

Detected sponsor segments and brands, sentiment scores and selected representative quotes, niche classification, and the aggregates built on all of it.

Product usage and error telemetry

Page views and feature interactions go to PostHog, and technical error reports including browser, operating system, page URL and stack trace go to Sentry. Both flow through same-origin proxies on our own domain rather than directly to the provider. We strip our session cookie and authorisation header on those hops, and we redact sensitive query parameters such as sign-in tokens from recorded URLs. We do forward your IP address to both providers so they can resolve an approximate location.

Page views also go to Google Analytics, directly from your browser. We use it to see how visitors find Claritea. Each page view carries the page address, the address you came from, the page title, your browser and device, and an approximate location that Google works out from your IP address. Before anything is sent, we cut both addresses down to the site, the page path and any campaign tags, and drop everything else, including sign-in links. The access token in a shared dashboard or invite link is replaced with a placeholder, and so is the title of those pages, so it never names the creator or the brand. Google signals are switched off, and consent for advertising storage, advertising data and ad personalisation is denied, so what Google Analytics collects is not used for advertising or for demographic reporting.

Sentry also records session replays. A replay is a reconstruction of what was on your screen and what you clicked, captured for a sample of sessions and for sessions where an error occurs, so we can see what a fault actually looked like. Text on the page is captured as it appeared, which on a dashboard means the figures, video titles and audience comments you were looking at. What you type into form fields is masked and images and video are not captured. This applies to shared dashboards too, so a replay may be recorded while a share recipient is viewing one.

Share-link view logs

Every time someone opens a share link we record the link, the time, the viewer's IP address and their browser user agent, and increment a view count the creator can see. If you were sent a share link, this means the creator can see that the link was opened and we hold your IP address against that view.

Contact and waitlist submissions

If you use a contact form, we keep what you submitted and your email address so we can reply.

If you join the agency waitlist, we keep your email address and whatever else you chose to give us: your agency name, the size of the roster you manage, what you said you would use Claritea for, and any comments you wrote. If the address you used matches an existing Claritea account we note the link between the two.

We also record the IP address the submission came from, whether or not you opt in to hearing from us. We use it to tell real submissions from automated ones and to show where interest is coming from.

The waitlist form has an opt-in box for hearing about Claritea for Agencies. It is never pre-ticked. If you tick it, we record that you did, the exact wording you were shown, and when you agreed. Together with the IP address above, that is what lets us prove consent later, which anti-spam law requires. Leaving it unticked does not stop you joining the waitlist, and you will still get a single confirmation of what we recorded. Every message sent on the basis of that box carries an unsubscribe link.

4. How and why we use it

Every use below serves a feature you can see in the product. If you hold an account, we rely on your consent for connecting your Google account and for optional communications, on the necessity of performing our contract with you for running the service you signed up for, and on our legitimate interests for security, abuse prevention and keeping the service working.

Audience members are different. If you commented on a creator's video you have no account with us and gave us no consent. We retrieve only comments already published publicly on YouTube, we use them solely to produce that creator's analytics, and section 13 gives you the right to have yours removed on request, without an account and without giving a reason.

• To run your dashboards. Retrieving, processing and displaying channel, video, analytics and comment data is the product. Without it there is nothing to show.
• To detect sponsors and score sentiment. Transcripts and comment text are analysed to find sponsor segments, identify brands, and measure how your audience reacted.
• To sign you in and keep your account secure. One-time codes, session records, rate limiting and abuse detection.
• To deliver sharing. Building the scoped files behind a share link, serving them, and reporting view counts to you.
• To take payment. Processing subscriptions, renewals and refunds, and keeping the records that go with them.
• To support you and tell you about the service. Replying to your messages, sending transactional email, and notifying you about pipeline or account events.
• To improve reliability. Aggregate usage analytics and error reports so we can find and fix what is broken.
• To understand how people find Claritea. Page views in Google Analytics show which sites, searches and campaigns bring visitors to us.
• To meet legal obligations and to enforce our terms.

To be explicit about what we do not do:

• We do not sell or rent personal information.
• We do not use your data for advertising, retargeting or ad measurement.
• We do not use your content, your audience's comments, or your transcripts to train our own models.
• We do not use any of this for credit, insurance, employment or eligibility decisions.
• We do not build profiles of individual audience members, and our terms forbid you from using the service to do so either.

5. YouTube API Services disclosure

What we ask for. Exactly four OAuth scopes: your OpenID identifier, your email address, youtube.readonly, and yt-analytics.readonly. Both YouTube scopes are read-only. We request no write scope of any kind, so Claritea cannot post, edit, delete or comment on your behalf.

Which APIs we call. The YouTube Data API v3 for channel, playlist, video and comment data, and the YouTube Analytics API v2 for channel reports. We do not use the YouTube Reporting API.

Two different kinds of access. The scopes above are how we reach the data that is private to you: your Google account identity, the list of channels you own, and your YouTube Analytics reports. Separately, we use a Google API key to retrieve information that is public on YouTube anyway, such as video metadata and the comments on your videos. That second kind is not obtained through your authorisation and is not unlocked by connecting your channel, though we only go looking for it once you have connected a channel and told us which one to read.

How we access, use, store and share Google user data. We access it only through the read-only scopes above, when you connect a channel and on the refresh schedule your plan sets. We use it only to produce the dashboards, sponsor detection and sentiment analysis you can see in the product. We store it in our own infrastructure, on the schedule in section 9 and in the locations in section 11. We share it only with the processors listed in section 7, and with the viewers and share recipients you choose yourself.

How long we keep it. Analytics metrics and public video statistics are kept for as long as your channel stays connected, so your historical charts remain intact, and your authorisation is re-verified at least every 30 days. Other data retrieved from the API is covered by the retention table in section 9.

Comment text and video metadata for videos still live on YouTube are kept for as long as your channel stays connected. Video metadata is reconciled daily, and comments are re-fetched once a video has gathered enough new ones to be worth re-reading, rather than on a fixed clock.

Disconnecting. Removing a channel in Claritea stops us using it and removes it from your dashboards. It does not, on its own, end the authorisation you granted or delete the artifacts already stored for that channel. To end the authorisation, revoke it at the Google permissions page linked above, which takes effect at Google immediately, and email us to have the stored data removed.

Deleting here does not delete there. Removing data from Claritea has no effect on anything stored by YouTube or Google. Your videos, comments and channel remain exactly as they were. To change those, use YouTube directly.

6. Automated processing

Transcription and analysis run through third-party model providers. What each one receives, and what it is permitted to do with it:

• OpenAI receives the audio of your videos for transcription. OpenAI's API policy is that data submitted through the API is not used to train or improve its models unless the customer opts in, which we have not done. OpenAI retains API data for abuse monitoring for up to 30 days.
• Anthropic receives transcripts and comment text for sponsor extraction, sentiment analysis, validation and niche classification. Anthropic's commercial terms state that Anthropic may not train models on customer content submitted through its services. The sponsor-sentiment prompt also includes commenter display names alongside the comment text.
• OpenRouter receives comment text only, with no display name attached, for per-comment sentiment scoring. OpenRouter is a broker: it forwards the request to a model provider we select by configuration, so the effective processor is whichever provider serves that model. Whether an upstream provider may train on forwarded prompts depends on OpenRouter's per-provider policies and on the training setting on our account.

Each provider acts on our instructions for the purpose described, and none is engaged to use the content for its own purposes. Where a provider's own policy rather than our instruction governs whether the content may also be used to train a model, the bullets above say so. None of this processing produces a decision with a legal or similarly significant effect on any individual.

7. Who we share with

We use the service providers below. Each receives only what its function needs. We do not sell personal information to anyone.

We may also disclose information where the law requires it, to enforce our terms, to protect against fraud or security threats, or to a buyer as part of a merger or acquisition, in which case we will tell you before your information becomes subject to a different policy.

8. Sharing you initiate

When you create a share link, we build a set of files scoped to the sponsor, channels and date range you chose, and serve them to anyone holding the link over a time-limited signed URL. A share link is an unlisted URL, not authenticated access.

A share recipient receives:

• the sponsor-scoped metrics and charts for the date range you selected,
• representative audience comment quotes. A shared report is the one place we substitute a neutral label for the commenter's name, but the name itself is present in the data file behind the report,
• negatively scored comments and quotes, only if you chose to include them. They are left out by default,
• a CSV export of the underlying data, unless you turned downloads off. They are allowed by default.

Treat sending a share link as disclosing the commenter names it covers. Hiding the name in the shared report is a display choice, not redaction, and a recipient who downloads the CSV or reads the underlying file can see it. Everywhere else in Claritea, including your own dashboards and those of anyone signed in, comments appear with the commenter's name as posted on YouTube.

Invited viewers sign in with their own email address and see the full dashboards for the channels you granted, including comment text and commenter display names.

You control the scope, the negative-sentiment setting, the CSV setting and the expiry of every link, and you can revoke a link at any time. Revocation does not reach anything already downloaded.

9. Retention

These are the periods configured today.

Video metadata, comment text and commenter display names for videos still live on YouTube are retained for as long as the channel stays connected. Metadata is reconciled daily and comments are re-fetched on a volume trigger rather than a fixed clock.

Removing a channel does not delete your Google tokens. It stops us retrieving anything further for that channel, but the stored authorisation for your Google account is held separately from the channel and stays until your account is deleted. To end the authorisation itself, revoke it at the Google permissions page, which invalidates it at Google immediately, and email us if you also want our stored copy removed.

Share-link view logs outlive the link. When a link expires or you revoke it, the files behind it are deleted and the link stops working, but the record of who opened it, including the recipient's IP address and browser user agent, is kept with no fixed end date. If you received a share link and want the record of your visit removed, use the contact address in section 2.

What happens to channel data when you leave. Deleting your account removes your account record and the links between you and the channels you connected. Much of what we hold about a channel is built from information that is public on YouTube: video metadata, transcripts, detected sponsors, and the metrics derived from them. We may keep that material in a form no longer connected to your account, so that aggregate benchmarks stay intact and so that reconnecting a channel later does not have to start from nothing. We keep it current, and remove content that has been deleted upstream, as the YouTube API Services requirements expect.

If you would rather that material were deleted as well, ask us at the address in section 2 and we will delete it, except anything we are required to keep. If you are an audience member whose comment is part of it, section 13 is your route and you do not need an account to use it.

10. Security

• Google access and refresh tokens are encrypted at rest under keys held in a managed key service.
• Everything in transit is protected with TLS.
• Session tokens are stored only as hashes. A sign-in code is held in readable form only until the email carrying it has been sent, then cleared, and it expires 10 minutes after it is issued.
• Dashboard and share files are served over signed URLs that expire, not from a public bucket.
• The session cookie is HTTP-only, so scripts on the page cannot read it. It is also marked Secure, so it only travels over HTTPS, and set to SameSite=Lax.
• Sign-in and other sensitive endpoints are rate limited.
• Access to production data is limited to the people who need it to operate the service, and is bound by the human-access rule in section 5.

No system is perfectly secure. If a breach affects you and creates a real risk of significant harm, we will notify you and the relevant regulator as the law requires.

11. International transfers

Claritea is a Canadian organisation, but our infrastructure runs in Amazon Web Services in Ohio, in the United States, and most of the providers in section 7 are US-based. Your personal information is stored and processed outside Canada.

While it is there it is subject to the laws of that country, including lawful access by courts and government authorities. Under Canadian privacy law we remain accountable for it: we use contractual and other means to require a comparable level of protection from every provider that handles it on our behalf.

12. Your rights

Whoever and wherever you are, you can ask us to:

• Access the personal information we hold about you and how we use it.
• Correct anything inaccurate or incomplete.
• Delete your personal information.
• Withdraw consent, including by disconnecting your Google account at any time. Withdrawing consent may mean we can no longer provide the service.
• Receive a portable copy of the information you gave us, in a machine-readable format.

Send requests to privacy@claritea.ai. We respond within 30 days. We may need to confirm your identity first. There is no charge unless a request is clearly unfounded or excessive, and we will tell you before any charge applies.

Deletion is by request to the address above rather than a button in the product. We process those requests manually and confirm when they are complete. Section 9 explains what happens to the channel material we built from public YouTube data, and how to have that removed too.

If you are not satisfied, you can complain to the Office of the Privacy Commissioner of Canada at priv.gc.ca, or to your provincial privacy regulator. We would rather you came to us first so we can put it right.

If you are in the EU or the UK

You also have the right to object to processing based on legitimate interests, to ask us to restrict processing, and to lodge a complaint with your national supervisory authority. Where we transfer personal data out of the EEA or the UK, we do so under the appropriate safeguards recognised by the relevant law.

If you are in California

You have the right to know what we collect, to delete it, to correct it, and not to be discriminated against for exercising those rights. We do not sell personal information and we do not share it for cross-context behavioural advertising, so there is nothing for you to opt out of. Use the same contact address above.

13. If you commented on a creator's video

14. Children

Claritea is a business tool for creators and is not directed to children. We do not knowingly collect personal information from children, and Claritea is not a child-directed API client under the YouTube API Services Developer Policies. If you believe a child has created an account, contact us and we will delete it.

We cannot control who comments on a public YouTube video. If you are a parent or guardian and believe your child's comment is in our data, use the removal route in section 13 and we will treat it with priority.

15. Cookies and browser storage

We set no advertising cookies and run no ad network. The first three below come from our own servers: all are HTTP-only, so no script on the page can read them, marked Secure, and set to SameSite=Lax. The other three are set in your browser, one by PostHog and two by Google Analytics.

Your theme choice, whether the sidebar is open, the filters you last used on each dashboard, which shared channel you are viewing, and a cached copy of your account details are kept in your browser's own local and session storage, as are the identifiers our analytics and error monitoring use to tie a visit together. Those stay in the browser and are not sent to us with any request. Clearing site data for claritea.ai removes them, and signs you out.

Our own three cookies cannot be opted out of, because without them you cannot sign in. To stop product analytics, block the PostHog cookie and clear site data for claritea.ai. The identifier is kept in both a cookie and local storage, so clearing both is what stops it, and nothing in Claritea breaks if you do. To stop Google Analytics, block the two _ga cookies or install Google's opt-out browser add-on. There is no common industry standard for the browser "Do Not Track" or Global Privacy Control signals, and we do not currently respond to them, so they will not switch analytics off. To object to error monitoring or session replay, contact us at the address in section 2.

Our content delivery network does not use signed cookies. Dashboard and share files are protected with signed URLs, whose policy and signature travel in the query string and expire on their own, which is why a share link works in a browser that has never visited Claritea before.

We do not show a cookie consent banner. We set no advertising or cross-site tracking cookie and the cookies we set ourselves are necessary to sign in. The non-essential technologies are product analytics, Google Analytics, and the error monitoring and session replay described in section 3.

16. Changes and contact

We will update this policy as the service changes. Changes take effect on the Effective Date reflected at the top of this page, and for changes that materially affect your rights we give you at least 30 days' notice by email or in the product first.

Privacy questions and requests go to privacy@claritea.ai. General questions go to hello@claritea.ai. See also our Terms of Service.

PayPer Technologies Inc.
505 - 70 Montclair Ave, Toronto, Ontario, M5P 1P7