NAGO.TV
Privacy
Last updated 17 August 2026
This is a description of a real system, not a template. Every claim below was checked against the code that runs this site, and where something is still unfinished it says so rather than glossing over it.
1. In short
NAGO.TV sets one cookie of its own, and only with your consent. There is no advertising network, no tracking pixel and no data broker. Analytics runs only if you allow it, with your address anonymised and ad personalisation off. Nothing you do here is profiled, sold, or used to target advertising, and we do not build a picture of you across sites.
You can watch all four channels, listen to all seven Nago FM stations, read every chart and every programme page without telling us anything at all. Four features do ask for something — an account, the newsletter, the prayer wall and the live streams — and each is set out in full below.
2. Who is responsible for your data
NAGO.TV is operated by ZIRC ART TECHNOLOGY, which is the data controller for everything described here. Under the UK and EU GDPR, "controller" means we are the ones who decide what is collected and why, and the ones you can hold to account for it.
You can reach us about anything on this page through privacy@nago.tv.
Written enquiries reach us at:
ZIRC ART TECHNOLOGY
175-61 Hillside Avenue, Suite 202 #1165
Queens, NY 11432
United States
3. What we collect, why, and on what legal basis
Nothing here is collected "just in case". Each item below exists because a specific feature cannot work without it.
3.1 If you create an account
Accounts are optional and the site is fully usable without one. If you make one, the following is held:
| What | Why | Legal basis |
|---|---|---|
| Email address | It is how you sign in, and how a password reset reaches you. | Performance of a contract (giving you the account you asked for) |
| Password | To verify it is you. Stored only as a one-way hash by our authentication provider. We never see it — which is precisely why a forgotten password is reset rather than looked up. | Performance of a contract |
| First name, last name, display name, country — all optional | So the site can greet you by name. | Consent — you type them or you leave them blank |
| Preferences: your usual channel, your usual station, your language, whether you want the newsletter | So the site opens where you left it. | Consent |
| Liked songs: the artist, the title and the sleeve image address | To show you the list you built. | Consent |
| Sign-in records kept by our authentication provider, including the IP address and time of a sign-in | To detect someone else trying to get into your account. | Legitimate interests (account security) |
You can delete the account and everything attached to it at any time by asking us; see section 8.
3.2 If you subscribe to the newsletter
We store your email address, the date you subscribed, and which page you subscribed from. That is the entire record — there is no name field, no tracking pixel in the emails, and no record of what you opened or clicked.
Legal basis: consent. Every message carries an unsubscribe link that works without signing in or writing to anybody, and using it deletes the address rather than marking it inactive.
3.3 If you send a prayer request
The form asks for a first name and the request itself. A surname, an email address and a phone number are optional, and exist only so we can reach you if you have asked us to.
If you do give them, they are never published. This is not a promise about our intentions — it is how the code is built: the public wall is assembled field by field from the first name, the text and the date, so there is no route by which a surname, an email address or a phone number can appear on the site, even by mistake.
Requests are read by a moderator before anything appears, and appear only if you tick the box asking for that. If you do not tick it, the request stays private and is seen only by whoever moderates the wall.
We also store a hashed form of your IP address — a one-way fingerprint, not the address itself — purely to stop the form being flooded. It cannot be turned back into an IP address.
Legal basis: consent for the request; legitimate interests for the anti-flooding fingerprint.
3.4 When you watch or listen
Live streams are signed with a short-lived token tied to the IP address that asked for it. That is what stops a stream link being copied and replayed on another site. Your IP address is used at the moment the token is generated; it is not written into any database of ours. The streaming server keeps its own delivery logs, as every streaming provider does.
Legal basis: legitimate interests — protecting broadcasts we are licensed to carry.
3.5 Ordinary server logs
The web server writes the standard request log: IP address, timestamp, the page requested, the referring page and the browser's user-agent string. It is used to diagnose faults and to spot attacks. It is not joined to any account and is not used to profile anyone.
Legal basis: legitimate interests — keeping the site up and secure.
4. What we do not do
- We do not sell or rent personal data. There is no circumstance in which we would.
- We do not share it for anyone else's marketing.
- We do not run advertising or behavioural targeting on this site.
- We do not track you across other websites.
- We make no automated decisions that produce legal or similarly significant effects about you, and we do not profile you.
5. Companies that process data for us
Running a site means using other companies' infrastructure. These are all of them, and what each one actually receives:
| Who | What they do | What they see |
|---|---|---|
| Supabase | Accounts and the account database. | Your email address, the password hash, your profile and preference rows, your liked songs, and sign-in metadata including IP address. |
| Our hosting provider | Runs the server the site and the newsletter and prayer records sit on. | Everything stored on the server, as any host technically can. |
| The embedded football highlights (YouTube). | Nothing until you press play — after that, YouTube applies its own policy and sets its own cookies. | |
| Apple and Deezer | Sleeve artwork is loaded from their servers rather than copied onto ours. | Your IP address when an image loads. |
Chart, artist and song information is fetched by our server, not by your browser, so Apple and Deezer do not see visitors when that data is looked up — only when an image is displayed.
We will also disclose data if we are legally required to, and we will tell you if we are permitted to.
6. Where your data goes
Our authentication provider and our host may store or process data outside your country, including in the United States. Where data leaves the UK or the EEA, it is transferred under the safeguards those providers have in place — Standard Contractual Clauses or an adequacy decision — rather than on an ad-hoc basis.
7. How long we keep things
| What | Kept for |
|---|---|
| Account, profile, preferences and liked songs | Until you delete the account. |
| Newsletter address | Until you unsubscribe, which deletes it. |
| Prayer request | Until you ask us to remove it. |
| Hashed IP fingerprint on the prayer form | Rolling — it exists only to rate-limit and is not retained as a record. |
| Server logs | Rotated on the ordinary server schedule, a matter of weeks. |
8. Your rights
If you are in the UK or the EEA, the GDPR gives you the following. We apply them to everybody, wherever you are, because operating two standards would be worse than operating one.
- Access — ask for a copy of what we hold about you.
- Rectification — have anything wrong corrected. Most of it you can correct yourself on the account page.
- Erasure — ask us to delete it.
- Restriction — ask us to stop using it while a dispute is resolved.
- Portability — receive it in a machine-readable file.
- Objection — object to anything we do on the basis of legitimate interests.
- Withdraw consent — at any time, without giving a reason. Withdrawing it does not undo what was lawful beforehand.
Ask through privacy@nago.tv. We will respond within one month. There is very little held here, which makes all of the above quick to honour, and we do not charge for it.
If you think we have got something wrong, please tell us first — but you have the right to complain directly to your data protection authority. In the UK that is the Information Commissioner's Office (ico.org.uk); in the EEA it is the authority for the country you live in.
9. If you are in California
You have the right to know what personal information is collected, to have it deleted, to correct it, and not to be discriminated against for exercising any of that. We do not sell or share personal information as the CCPA defines those terms, and we have not in the preceding twelve months. The categories we collect are identifiers (email, IP address), internet activity (server logs) and, if you supply them, name and country. Use the same contact route above.
10. Security
The whole site is served over HTTPS. Passwords are hashed by our authentication provider and never reach nago.tv in a readable form. Access to the account database is restricted by row-level security, which means the database itself refuses to return one person's rows to another — it is not left to the website to remember to filter them. Prayer moderation runs on a separate approval step so nothing is published by accident.
No system is perfectly secure, and anyone who tells you otherwise is selling something. If you find a weakness here, please report it to us before anywhere else and we will fix it.
11. Children
NAGO.TV is a general-audience service and is not directed at children under 13. We do not knowingly collect anything from a child under 13, and none of the forms on the site should be completed by one. If you believe a child has sent us something, tell us and we will delete it.
12. What your browser stores
No cookies are set by nago.tv. A small number of values are kept in your browser's local storage, including your signed-in session if you have an account. The cookies page lists every one of them, what it holds, and how to clear it.
13. Changes to this page
If this policy changes, the date at the top changes with it. Where a change materially affects what we do with your data, we will say so on the site rather than relying on you to notice a date.
Questions about this page? Use the contact form.