Privacy

Nichecast stores the minimum it needs to run your channels:

• Account — your email address, used for one-time sign-in codes and receipts. No passwords are stored.
• Channels & videos — your channel briefs, generated scripts, narration audio, and rendered videos, kept so you can inspect and retry jobs.
• YouTube connection — an encrypted refresh token, obtained through Google sign-in when you connect a channel, that lets Nichecast upload to your channel. It is used only for uploads and is deleted when you disconnect the channel.
• Billing — subscriptions are processed by PayPal; Nichecast never sees your card or bank details.
• Product usage measurements — which steps of the product are used (a page view, an idea-tool run, a sign-up, a channel, a video, a checkout), so we can see where people get stuck. This is cookieless and does not follow you between visits; the section below says exactly what it stores.

We don't sell your data or use it to train models.

Deleting your account

You can delete your account yourself, from the app: open Account & connections under the studio title, then Delete account. You'll be asked to type a word to confirm, because it is immediate and cannot be undone.

It removes the account and everything we hold for it — the channels you described, every video job and its rendered files, the stored access to your connected YouTube channel (which we also withdraw at Google), your billing records and credit history, your support-chat transcripts, and the single row that counts return visits. Videos already uploaded to your YouTube channel are not touched: they are on your channel and are yours to keep or delete there.

If you have a live subscription, cancel it first — the delete button refuses while one is running. Deleting removes our record of the subscription but does not stop PayPal, so it would keep charging for an account that no longer exists.

If you can't sign in, email support and we'll do it for you.

How we measure product usage

This describes what the code actually stores, rather than a general statement of intent.

• No cookies, and no identifier that survives your visit. Each visit gets a random id held in your browser's sessionStorage. It is deleted when you close the tab, so two visits cannot be linked to each other or to you.
• Your IP address is never stored. To count distinct people per day we hash your address together with that date and a secret unique to Nichecast, keep the first 8 bytes, and discard the address. Because the date is inside the hash it cannot be matched to another day, and because the secret is unique to this product it cannot be matched to another Tiraisoft product.
• Only named steps are recorded. An event has to be on a fixed list we declare in the code. We do not record the briefs or topics you type, and page addresses are stored without their query string.
• Referrers are reduced to the site name. If you arrive from a search engine we store the host (for example www.google.com) and never the search terms.
• Device and system are kept as broad buckets, never as the browser's own string. We record the kind of device (phone, tablet, desktop, or an automated crawler) and the operating system with its major version only — iOS 17, never iOS 17.4.1. The browser's User-Agent string is read once to work that out and then discarded, because the full string is detailed enough to single somebody out.
• Country and region come from Cloudflare, not from an address we keep. Cloudflare works out the country at its edge, so we get the answer without ever seeing or storing the address that produced it.
• These are counted separately and never combined. We keep a daily total per device kind, and a separate daily total per country, and never a row that joins them — so a total can never be narrowed down to "the one person on a tablet in Iceland". It also means we cannot ask which system a particular country's visitors run, which is the trade we chose.
• We measure how long a page was visible. The clock stops whenever you switch away from the tab, so a page left open in the background is not counted as time spent reading.
• It stays in our own database. These measurements go to no analytics company. The individual rows are deleted after 30 days; what remains is a set of daily totals — per step, per device kind, per system, per country, per region, and per page — none of which can be traced back to a visit. The one exception is the account row described next.
• If you are signed in, we count return visits using your account — and nothing else. We keep one row per account holding the first and the last day that account was active. No pages, no events, no times: that row cannot say what you did, only that you were here on those two days. It exists so we can tell repeat use from one-off curiosity, and it uses the account id we already hold rather than a cookie or a device fingerprint. Signed-out visits carry no such id at all and are counted only as an anonymous total. This is the one measurement kept for longer than 30 days, because a return after five weeks would otherwise read as a new person; it is deleted when your account is deleted.

Who else touches your data

These are categories of recipients, not a list of names. Article 13(1)(e) GDPR asks for the recipients or categories of recipients, and the category is the disclosure: a name here would go stale the day a provider changed, and this page would then be confidently wrong about where your text goes.

• A third-party large-language-model provider — the text you submit, meaning your channel brief and the scripts and image prompts derived from it, is sent to it so scripts, narration text and thumbnails can be produced.
• A third-party text-to-speech provider — the narration script is sent to it to be spoken.
• A stock-media library — search terms taken from your script are sent to it to find footage.
• A cloud compute provider — rendering runs on containers we rent; the audio, images and footage for that one job are processed there while it runs.
• Cloudflare — hosting and the database.
• PayPal — payments, as above.
• Google / YouTube — uploads to the channel you connected, as set out below.

Google user data

Nichecast uses YouTube API Services. Nichecast's use and transfer of information received from Google APIs adheres to theGoogle API Services User Data Policy, including the Limited Use requirements. TheGoogle Privacy Policy also applies to data Google processes. You can revoke Nichecast's access to your YouTube account at any time by disconnecting the channel in the app or via yourGoogle account security settings.