Viewlio
Back to login

Privacy Policy

Last updated 20 August 2026

1. Who we are

Viewlio (“Viewlio”, “we”, “us”) provides a web application that analyses a YouTube creator’s own videos and audience retention data, and returns insights about hooks, pacing, packaging and drop-off points. This policy explains what personal data we collect, why we collect it, and what you can do about it. We are the data controller for that data.

Questions about this policy or your data: privacy@viewlio.ai.

2. Data we collect

  • Account data. When you sign in with Google we receive your name, email address and profile picture, and we store them against your account.
  • Google authorisation. We store the OAuth refresh token issued by Google so the service can keep reading your YouTube data between sessions. It is held server side only and is never exposed to the browser.
  • YouTube data. With your permission we read data for your own channel through the YouTube Data API and the YouTube Analytics API: video metadata such as titles, descriptions, thumbnails, tags and publish dates; audience retention curves, views, watch time and related analytics; and captions or transcripts for your own videos.
  • Files you upload. If you run a deep analysis you can upload the source video file for a video. We also store material derived from it, including a lower resolution proxy, extracted frames and audio, transcripts, on screen text recovered by OCR, and scene and event data.
  • Analysis output. The insights, scores, comparison reports, tips and checklists generated for you, plus any feedback or ratings you give on them.
  • Billing data. Your plan, subscription status, usage counters, credit consumption, invoices and any cancellation feedback you submit. Card details are handled by Stripe and never reach our servers.
  • Technical data. Session cookies used to keep you signed in, plus standard server and error logs from our hosting and database providers.

3. How we use it

  • To create and run your account and keep you signed in.
  • To fetch your YouTube videos and retention data and produce the analyses, comparisons and recommendations you ask for.
  • To build your private cross-video library, so later analyses can draw on patterns across your own channel.
  • To meter usage against your plan, take payment, and send service notifications such as an analysis finishing.
  • To keep the service secure, debug faults, monitor processing costs and improve how the product works.

We do not sell your data, we do not use it for advertising, and we do not use your content to train our own or any third party’s general purpose AI models.

4. Legal bases

Where UK or EU data protection law applies, we rely on: performance of our contract with you, for running the service and billing you; legitimate interests, for security, fault diagnosis, cost control and product improvement; consent, which you give through the Google permission screen when you connect your YouTube account and can withdraw at any time; and legal obligation, for tax and accounting records.

5. YouTube API Services

Viewlio uses YouTube API Services. By using the service you also agree to the YouTube Terms of Service, and Google’s handling of your data is described in the Google Privacy Policy.

You can revoke Viewlio’s access to your Google and YouTube data at any time at Google security settings. Revoking access stops any further reading of your YouTube data. To also remove data we already hold, delete it in the app or contact us.

We only request read access to your own channel, plus the caption scope Google requires to download captions from videos you own. We never request access to other people’s channels, and we do not post, edit or delete anything on YouTube.

6. AI processing

Analyses are produced by sending relevant material to third party AI models. Depending on the analysis this can include video metadata, retention figures, transcripts, and extracted frames and audio clips from your video. We send only what a given analysis needs, and our AI provider processes it on our instructions and under terms that prohibit using it to train their models.

7. Who we share it with

We share data only with service providers that run the product on our behalf:

  • Google / YouTube, the source of your channel data and our sign-in provider.
  • Supabase, for authentication, database and file storage.
  • Vercel, for application hosting.
  • OpenAI, for the AI analysis described above.
  • Qencode, for transcoding uploaded video into an analysis proxy.
  • Stripe, for payments, invoices and card handling.

We may also disclose data where the law requires it, or to establish or defend legal claims. If the business is ever sold or reorganised, data may transfer to the acquirer under this policy.

8. International transfers

Some of these providers process data outside the UK and EEA, mainly in the United States. Where that happens we rely on the transfer safeguards those providers offer, such as standard contractual clauses.

9. Retention and deletion

We keep your account data for as long as your account exists. Analysed videos, uploads and derived media stay until you delete them or close your account. Deleting an analysis removes the analysis and the data hanging off it, including extracted media. Closing your account removes your profile, stored Google token, analyses and uploads, other than records we must keep for tax, accounting or fraud prevention, such as invoices, and backups which age out on their normal cycle. To close your account, email us and we will action it.

10. Your rights

Subject to local law you can ask for a copy of your data, correct it, delete it, restrict or object to processing, or receive it in a portable format. Email privacy@viewlio.aiand we will respond within one month. If you are in the UK you can also complain to the Information Commissioner’s Office, and if you are in the EEA to your local supervisory authority.

11. Security

Data is encrypted in transit. Your Google refresh token sits in a table that is unreachable with the public API key and readable only by our server. Database rows are protected by row level security so one account cannot read another’s data, and uploaded files are served through short lived signed URLs scoped to your own account. No system is perfectly secure, but we take these controls seriously and review them as the product changes.

12. Cookies

We use cookies only to keep you signed in and to remember interface preferences such as theme and sidebar state. We do not use advertising or cross site tracking cookies.

13. Children

Viewlio is not intended for anyone under 16. We do not knowingly collect data from children. If you believe a child has given us data, contact us and we will delete it.

14. Changes

We may update this policy as the product changes. The date at the top shows the current version, and material changes will be notified in the app or by email.

Privacy Policy · Terms of Service