Cutline

PRIVACY POLICY

What we store,
and who else sees it.

Last updated 1 August 2026

Cutline (“the service”) is operated by Dayanand Kumar, an individual based in India rather than a company — so the person accountable for your data under this policy is a person, and writing in reaches them directly. This policy describes what the service collects, why, and what you can do about it. It is written to be read rather than to be survived.

What we collect

Account information

Your email address and a user identifier, handled by our authentication provider. We do not store your password — we never receive one.

Things you type into the service

Channel and video links you paste, topics you enter, ideas you select, scripts and posts generated for you, and any notes you leave when revising a paragraph. These are saved to your account so you can return to them.

Your brand voice answers

The onboarding questions — who you write for, how it should sound, what your field gets wrong, words you never want used, and any writing sample you provide. These are stored on your account and included in the prompts that generate your scripts. That is the entire point of them, and it is also the reason they leave our systems: see below.

Usage records

For each generation we record the action, credits charged, whether it succeeded, how long it took, the model used, and token counts and cost. This is how billing stays honest and how failures get found. It is also how a refund is issued when a run takes credits and returns nothing.

What we do not collect

No advertising or tracking cookies, no analytics profile, no third-party trackers, and no payment card details — we never see a card number. We do not sell personal data, and there is no arrangement under which we would.

Channel reports are public

This is the part most people would not guess, so it is stated plainly. When you analyse a YouTube channel, the resulting report is cached and published at a public address such as /channel/mkbhd. Those pages are listed in our sitemap and can be indexed by search engines.

Those reports contain only public YouTube data — the channel’s name, subscriber count, video titles and view figures, plus the analysis produced from them. They do not say who requested the analysis, and they contain nothing from your account, your voice answers, or your scripts. But the fact that a channel has been analysed is public. If you would prefer a specific report taken down, write to us and it will be removed.

Who else your data goes to

We use a small number of processors, each for one job:

  • Clerk — authentication. Holds your email and session.
  • Supabase — the PostgreSQL database where accounts, sessions and usage records are stored.
  • Vercel — hosting and request logs.
  • Google (Gemini API) — text generation. The prompts we send include the channel data being analysed and, where relevant, your brand voice answers and the script being worked on.
  • Google (YouTube Data API) — retrieves the public channel and video information being analysed.

Each of these operates under its own terms and privacy policy. We share with them only what the job requires.

How long we keep things

Account data and saved sessions are kept while your account exists. Usage records are kept longer, because they are the accounting trail behind credits charged. Cached channel reports are kept until they are refreshed or removed on request.

Your rights

You can ask for a copy of your data, ask for it to be corrected, or ask for your account and its contents to be deleted. Write to daya@cutlinehq.com. Deletion is honoured — we will not try to talk you out of it. Some usage records may be retained in an anonymised form where required for financial record-keeping.

Cookies

Only what is needed to keep you signed in, set by our authentication provider. No advertising or analytics cookies are set, which is why you are not being asked to consent to any.

Security

Data is transmitted over HTTPS and stored with our hosting providers under their security controls. No service can promise perfect security, and anyone who does is not being straight with you. If we ever discover a breach affecting your data, we will tell you.

Children

The service is not intended for anyone under 18, and accounts should not be created by them.

Changes

If this policy changes materially, the date at the top changes and significant changes will be announced in the product. Continuing to use the service after a change means you accept the updated policy.

Contact

Questions about this policy, or about anything it does not cover, go to daya@cutlinehq.com. The terms of service cover the rest of the relationship.