Privacy, written plainly
The short version. risha lives on your TV, and so does what it knows about you. No account, no analytics, no advertising, and it never reads what's on your screen. When hudhud answers on risha's own AI, your question passes through our relay to an AI provider and the answer comes back; we keep no questions or answers, only counts (listed below). Beyond that, jarada labs collects nothing from risha unless you press "Something's not right?". risha does talk to a few services, each for a feature you can switch off or simply not use (plus, during the free trial, a daily check of its dates); this page names every one and what it hears.
Who we are. risha is made by jarada labs, a brand of Steep Endeavours L.L.C-FZ (licence 2531671.01), Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, UAE. Your purchase is processed by Polar, our merchant of record. hello@risha.tv reaches a real person.
What stays on your TV
Your things. Settings, watch history, the word families you've seen, Scenes favourites and hidden photos (and your own photos, if you add some), hudhud's settings and spending, the Guard's records, and risha's own crash and memory logs. None of it leaves the TV unless you send it yourself.
Your AI keys. If you connect your own AI account for hudhud (OpenRouter or any OpenAI-compatible service), its key is kept in Android's protected key store and only ever sent to that service. Nothing else in risha needs an account.
What hudhud learns about your household. Unless you switch it off (the gear › hudhud › Learn from how we use risha), hudhud notices a few habits over time, with no extra AI request: the language and Arabic dialect you speak, whether you prefer short or longer answers, Celsius or Fahrenheit, how careful to be with spoilers, whether you look at picture answers, the time of day a habit holds, and which apps and shows you watch (from Continue watching, never from your questions). Nothing about health, religion, politics, names, relationships or children. A habit counts only once it has shown on several different days, it fades after about a month without new signs, and none forms while people in the household differ. It stays on your TV, in risha's private storage: never shown, never in a report, never moved to another TV. It travels only inside a question, to the AI that answers it, as a short hint of at most 50 words, and the relay keeps none of it. "Forget what hudhud has learned" deletes it all at once.
Follow-up questions. If you ask hudhud again within two minutes while he's still on screen, your previous question and his answer go with the new one, so "And tomorrow?" makes sense; after two minutes, or once he closes, they're dropped. They're never written down, on the TV or by the relay.
What's playing. risha reads what other apps publish about what's playing (title and position), through the notification access you grant, for Continue watching and for your questions. It never reads the screen.
Moving to a new TV. Customize › Move to another TV saves your settings to a file on the TV or a USB stick, or hands them to your phone. Your AI keys, your licence and your watch history never go with them.
Who risha talks to, and what they hear
Open-Meteo, for the weather (api.open-meteo.com, air-quality-api.open-meteo.com, geocoding-api.open-meteo.com). Every 30 minutes while Home or Rest mode is on screen, unless you hide the weather (Customize › Weather). It hears your location rounded to about 1 km, and the city name you type when you search.
GeoJS, for your city (get.geojs.io). Once a day, unless you chose your city yourself (Customize › Location). It hears only the request: it sees your internet address, as any website does, and answers with your approximate city.
Wikimedia Commons, for Scenes and hudhud's pictures (commons.wikimedia.org, upload.wikimedia.org). For Scenes, risha only downloads the photos themselves: each once, about 0.6 MB (about 2 MB where the TV's interface is 4K), at most 60 new a day. The list of photos and their credits comes with risha, so it never searches Commons for Scenes. For hudhud's pictures, Commons hears the words of the picture search.
Wikidata and Wikipedia, for facts about what you watch (www.wikidata.org, en.wikipedia.org, ar.wikipedia.org). Only while hudhud is awake (during the trial or with a licence): when a film or series starts in another app, and when you ask hudhud about it (never for YouTube videos). They hear the title, and the season and episode if the app gives them.
YouTube, for titles and thumbnails (www.youtube.com/oembed, i.ytimg.com). Only if you turn them on (Customize › Watch history; off unless you choose it). It hears the ID of each YouTube video you play.
risha's AI, hudhud's brain unless you connect your own (www.risha.tv/ai/). When you ask hudhud something and haven't connected your own AI account. Your TV sends our relay the recording of a spoken question (to turn it into text) or the question you typed, with what hudhud needs to answer: the date and time, your city and country, the weather, prayer times, the word of the day, your apps' names, the sleep timer, and what's playing. From Jellyfin that's the title, position, summary, cast and the last few minutes of subtitles; from another app its title, channel and position, with facts from Wikidata and Wikipedia. About twice a day, when it opens a session, the TV also sends your licence key so the relay can check it with Polar (the relay keeps only a one-way hash of it, never the key), or during the trial an anonymous TV ID; each question then carries only a short signed token. The relay is a small function of jarada labs on Tencent EdgeOne (below); it passes your question to an AI provider and streams the answer back. Normally every question goes through OpenRouter, and each request asks for its "zero data retention" endpoints that don't collect data. OpenRouter's terms say it doesn't store prompts or answers unless logging is switched on for the account, and doesn't use them for training. Claude, which answers, then runs only on endpoints OpenRouter lists as keeping no data (Amazon Bedrock and Google Cloud Vertex).
When OpenRouter can't answer. Only if OpenRouter refuses a question, doesn't start answering within 15 seconds or can't be reached does the relay ask a second provider, so hudhud keeps working through an outage: SiliconFlow (SILICONFLOW LABS PTE. LTD., Singapore), which runs DeepSeek V4.1 Flash for us. It gets the same question and context. SiliconFlow's terms say it is under no obligation to store what is sent, and that it won't access it or use it without authorisation; its home page says "No data stored, ever". They give no retention period, don't mention training, and don't name the countries where it runs.
Listening when OpenRouter can't. hudhud's listening normally goes through OpenRouter too: first Google's Gemini on Google Cloud Vertex, whose terms let Google keep a recording its safety checks flag for up to 90 days, and say it isn't used for training; if Gemini fails, Xiaomi's MiMo, on endpoints OpenRouter lists as keeping no data. Only when OpenRouter can't take a recording (it refuses it, doesn't answer within 15 seconds, or can't be reached) does the relay send that one recording, and nothing else, to DeepSeek's speech-to-text, so a spoken question still works through an outage. DeepSeek (Hangzhou DeepSeek Artificial Intelligence Co., Ltd.) is a Chinese company. Its privacy policy says it collects, processes and stores personal data in the People's Republic of China, keeps it for as long as the account exists, and may use it to train its models, with a right to opt out; its terms for developers don't say whether what developers send is kept or used for training, and its speech-to-text guide says nothing about recordings.
What the relay keeps. No questions, recordings or answers. Only: for each licence (by Polar's ID for it, or a hand-granted licence's serial number, never the key itself), how many questions and transcriptions it used each month and what they cost, for 13 months; during the trial, for each TV, the anonymous TV ID (a SHA-256 of the ID Android gives risha on that TV; a factory reset changes it), the day the trial started and how many questions it asked, until 90 days after the trial ends; a keyed hash of the first part of your internet address (the /24 or /48 network), for 48 hours, so one network can't start trial after trial. What our host keeps is under "Who hosts www.risha.tv" below.
The trial check. During the 14-day trial, when the TV is online, it asks the relay once a day to confirm the day the trial started and today's date. It sends the anonymous TV ID, the day the trial started as the TV remembers it, and risha's version, nothing else.
OpenRouter, if you connect your own account (openrouter.ai). Optional. Only when you ask hudhud something with your own account connected, when you connect it, or when you open hudhud's model list. It hears the recording of a spoken question (to turn it into text) or the question you typed, then what hudhud needs to answer: the date and time, your city and country, the weather, prayer times, the word of the day, your apps' names, the sleep timer, and what's playing. From Jellyfin that's the title, position, summary, cast and the last few minutes of subtitles; from another app its title, channel and position, with facts from Wikidata and Wikipedia. OpenRouter passes it to the AI models you chose and bills your account. None of it passes through jarada labs. When you connect, OpenRouter sends your phone back through a page of ours (www.risha.tv/c) carrying a one-time code and your TV's address on your home network; the page only passes them to your TV. The code works once, for 10 minutes, and is useless without a secret that never leaves your TV.
Another AI service, if you set up your own (the address you choose: api.deepseek.com, api.siliconflow.com, api.openai.com, generativelanguage.googleapis.com, openrouter.ai, or any other OpenAI-compatible address, such as a server in your home). Optional (gear › hudhud › hudhud's AI › Use your own AI). Only when you ask hudhud something with it set up, and for a few test questions (one with half a second of silence) right after you set it up. It hears the same as OpenRouter above: the recording of a spoken question or the question you typed, and what hudhud needs to answer; only the standard fields of such a request leave the TV. Plain http goes only to an address in your home; anything else uses https. The service bills your account under its own terms. None of it passes through jarada labs.
Your Jellyfin server. If you set one up (Customize › Jellyfin): your requests to your own server, with a device ID risha makes for it. To find a server, risha sends one "Who is JellyfinServer?" message on your home network.
Polar, for your licence (api.polar.sh). Once when you enter a licence key, a quiet check about once a week, and when you move the licence to another TV. It hears your licence key, the activation ID it gave this TV, and a label ("risha TV · " and the TV's model) so you can tell your TVs apart. Nothing about what you watch or do. Our relay also asks Polar whether your licence and hudhud's AI subscription are active, and when you scan a QR code to buy a licence or renew the subscription, it asks Polar to open a checkout for you; for that it sends Polar your licence key or your Polar customer ID. Polar also has your purchase and subscription details, under its own privacy policy.
Our update feed (www.risha.tv/download; not live yet). Once a day from Home and when you choose Check now, unless updates are Off (Customize › Updates). It hears nothing about you: risha only downloads the list of releases and, when you agree, the new version. If www.risha.tv can't be reached, risha may fetch the same signed files from a mirror at dl.jrd.la/risha/, which hears nothing about you either. The mirror is on a second host, Cloudflare, so updates still arrive if one is down.
Who hosts www.risha.tv. Tencent EdgeOne (Tencent Cloud's international service, its region outside mainland China) serves www.risha.tv: these pages, our update feed, risha's AI relay and Help shape risha. Like any web host it sees the internet address of each phone, computer or TV that asks for something. We don't switch on EdgeOne's access logs (they are off unless a site owner turns them on), and our functions write no question, answer, report or address to a log. Tencent keeps its own records of running the service, which can include internet addresses: its privacy policy says it keeps access logs for up to 180 days and usage and diagnostic data, such as traffic logs, for up to a year. Tencent Cloud's privacy policy and data processing addendum cover that.
Help shape risha (www.risha.tv). Only when you press "Something's not right?" and then Send. Our service hears what you chose (wrong meaning, typo, idea or bug), which word, interface text or kind of answer it's about, risha's version, the interface language, your Android version, whether risha is licensed, and an anonymous reporter ID made from your licence (or a random number) that we can't turn back into your licence. If you type more on your phone, that text goes too. hudhud's question and answer go only if you tick "Include this question and answer", and you see them first. A bug report can also carry your TV's maker, model and Android version, and a short slice of risha's own log (at most 40 lines of what risha did, such as "hudhud answered in 2 seconds"), but only if you tick them, and the TV shows all of it before you send. Never your name, account, licence key, address or anything you watch.
Cleaned twice, kept 90 days. Before a log leaves the TV, risha takes out Wi-Fi names, internet addresses, emails, account names, licence keys and the titles of what's watched, and our service does it again when the report arrives. What you type on your phone, and hudhud's question and answer, are cleaned of names, phone and other long numbers, addresses, emails and the like before they're stored. Reports are stored on Tencent EdgeOne for jarada labs and checked by an AI model through OpenRouter. Each report is deleted, with everything in it, 90 days after it was sent (or last added to); after that we keep only counts (how many reports of which kind, about which part of risha, from which version, each month) and, for each group of similar reports, its short title and the risha versions and TV models it was seen on. Switch the button off in Customize › Help shape risha.
How risha introduces itself. To Wikimedia, Wikidata, Wikipedia, OpenRouter (and the AI service you set up yourself), Polar, risha's AI, our update feed (and its mirror) and Help shape risha, by name with our address (hello@risha.tv), as Wikimedia asks apps to do. No advertising ID, and no identifier of its own except the Jellyfin device ID, Polar's activation ID, the random tester ID in feedback you send, the anonymous TV ID during the trial, and the anonymous reporter ID above. Each service has its own privacy policy.
Things only you can send
By email, from your phone. Feedback (Customize › Updates › Send feedback), the compatibility report (Customize › Compatibility report) and the support code (the gear › Support code) each show a QR code. Your phone opens an email to hello@risha.tv; you read it and decide whether to send it. The TV sends none of them. The compatibility report shows every line first and never holds serial numbers, network addresses, accounts, keys, your apps, places or history; the support code holds risha's version and setup, the TV's model and Android version, and the kind of licence (never the key).
On your home network
risha listens only while a phone page is on screen: connecting your own AI account, adding a licence, pairing for Set up, moving your settings (at most 10 minutes each), or the Ask hudhud card (while it's open). It answers only devices on your home network, and what your phone sends is sealed with a one-time secret that travels only inside the QR code. Set up and risha's recovery use the TV's own debugging connection, from the TV itself.
Children. risha has no accounts, and we keep nothing that says who is watching. hudhud's family-friendly answers are on by default (the gear › hudhud), but please keep an eye on children's use.
Questions about your data? Write to hello@risha.tv. A real person answers.