GalaramaGalarama
Privacy Terms Refunds Support
On this page Today, before launch Which apps this covers The waitlist Pairing Samsung TV trial and payments Popular-title rails What we store If sync is on What we never do Codes and sign-in On your TV This website · diagnostics Crash reports Usage counts Export and deletion Türkiye — KVKK Your rights Contact
Legal

Privacy

Last updated 17 November 2026

Everything we store, why we store it, and how to switch the optional parts off.

Today, before launch

Accounts and sync are not live yet. Until they are, the only personal data we hold is your email if you join the waitlist, short-lived server logs, crash reports from the apps unless you turn them off (see Crash reports), and, for the Samsung TV app, the trial and payment record of each TV (see Samsung TV trial and payments). You can have your waitlist entry deleted at any time (see The waitlist). Sections marked “when accounts launch” describe what changes on that day; this page will say so when it happens.

Which apps this covers

This page covers this website and both Galarama TV apps: the app for Android TV and Google TV, and the app for Samsung TVs (Tizen). The two apps work the same way and contact the same places. Where they differ, the section says so.

The waitlist

If you join, we keep your email address, the screens you ticked and the day you joined. Nothing else, and not your IP address. We use it for one thing: to email you when Galarama opens on a platform you ticked (or, if you ticked none, when it first opens). No marketing list. It is shared only with the providers that store and send it: Cloudflare, which hosts this site and the list, and the email provider that sends that email, which we will name here before the waitlist opens. Our legal basis is your consent, given when you submit the form. You can withdraw it at any time. We delete your entry once we have emailed you about every platform you ticked, or 24 months after you joined, whichever comes first. To be removed sooner, use the unsubscribe link in the email, or write to the contact address on this page from the address you joined with. We delete it within 30 days.

Pairing

A pairing code is a short-lived token linking the companion page to one TV. It expires after 10 minutes or on first use. What you type — a playlist URL, a server address, a username and password — is relayed to that TV over an encrypted connection and held only in memory for the seconds the relay takes. We do not write it to our databases, log it, or keep a copy after delivery.

Once delivered, your source details live on the TV, in the app’s storage. Remove them there at any time from Settings → Sources (Settings → Playlists in the Samsung TV app).

Samsung TV trial and payments

The Samsung TV app has a free trial, and after it the TV is paid for yearly or once (see the terms). There is no login, so the TV itself is the account. To know whether a TV is on its trial, paid for or locked, we keep one record per TV, and nothing more:

Device identifiers, hashed twice. On Samsung TVs we derive a device identifier from the TV’s own id and its network hardware (MAC) address — the Wi-Fi and the Ethernet one when the TV gives both — plus a random id the app keeps in its storage. The Android apps do not collect a device identifier for this and do not contact this service today; if a paid Android version ships, this page will say how it identifies a device before it does. Each identifier is turned into a SHA-256 hash on the device, so the id or address itself never leaves it; our server then hashes it again with a secret key, and only that second hash is stored, with the kind of id it came from and when it was first and last seen. We use these identifiers only to enforce the trial and the licence: they are how a TV that deletes and reinstalls the app is recognised, so its trial does not start over and a purchase is not lost. They are never used for advertising, never shared, and never combined with anything else about you.

The account code. The 8-character code the TV shows, which we create when the TV first contacts us. You type it, or the QR code carries it, at galarama.app/pay, and the payment carries it back to us.

Dates and the plan. When the record was created, when the trial ends, the paid plan (yearly, lifetime or a voucher’s) and when it ends, and the time of the last payment event applied to it.

The payment reference. How the TV was unlocked (a payment through Whop, or a voucher) and, for a payment, Whop’s membership or payment reference, so a renewal, a cancellation or a refund reaches the right TV.

We do not store your name, your email address or any card or bank details. Whop (Whop Inc.), which takes the payment, collects those when you pay and holds them under its own privacy policy. The payment form on galarama.app/pay is Whop’s. Before it opens, the page asks for your consent: a box, unticked, that you tick to agree that Whop and Stripe store the cookies and device identifiers listed here. The pay button does nothing until you tick it, and nothing of Whop’s or Stripe’s loads or is stored before you tick it and press the button. When you do, the page loads Whop’s script and the form opens, so what you type into it, and technical data about your browser and device, go to Whop and not to us. We checked what that script does on 17 November 2026. It loaded the form from cdn.whop.com and talked to api.whop.com. It loaded Whop’s own measurement scripts from t.whop.tw, which include a device-fingerprint script and a record of the checkout. It loaded Stripe’s script from js.stripe.com, which handles the card and runs a bot check, and scripts from Apple, PayPal and Braintree for their pay buttons. It also stored things in your browser under galarama.app: Whop’s cookies whop_anonymous_id (one year), _wuid and _wuid_link (about 13 months) and _whop_ssk (until you close the browser), Stripe’s cookies __stripe_mid (one year) and __stripe_sid (short-lived), and Whop’s entries in the browser’s local storage, which hold a device id. These belong to Whop and the companies it works with, which use them to take the payment, to stop fraud and to measure their checkout; we do not read or use them, and no other page of this site loads them. You can withdraw that consent at any time: unticking the box takes the form away, Whop’s script stops when you close or reload the page, and clearing the site data for galarama.app in your browser removes what was stored there. That does not take back what Whop and Stripe have already received; they hold it under their own privacy policies. Without the tick you cannot pay on galarama.app/pay, because Whop’s form is the only way to pay there; write to the address in Contact if you want to pay and cannot agree. Whop can change what its script does without telling us; we will check again and update this paragraph when we learn that it has. Whop’s message to us about a payment includes details such as your email address; we read from it only the plan, its dates and Whop’s reference, and keep those against the account code. Whop’s seller dashboard shows us the buyer’s name and email address for each payment, which we use only to answer you about a purchase or a refund.

Two short-lived records stop abuse. When a TV that gives us none of those identifiers except the app’s own random id starts a trial, we keep a one-way keyed hash of the network address it came from, with the time, so one network cannot start an endless run of trials; it is deleted once it is more than 30 days old, the next time any such trial starts. When a voucher code is typed wrongly, we keep the TV’s record id and the time, so a TV cannot try codes without limit; it is deleted once it is more than an hour old, the next time any wrong code is typed. When a voucher is redeemed, we keep which voucher (as a hash of its code, never the code), the account code and the time, so each TV uses a voucher once.

The TV keeps a signed token from us that states its account code, one of its hashed identifiers, its plan and when that ends, so it can check its own state when it is offline. We use this record only to run the trial, the payments and the vouchers. It is stored by Cloudflare, which hosts this site. We keep it until you ask us to delete it, because it is what keeps a TV’s trial from starting over and what shows that a TV was paid for. To have a TV’s record deleted, write to the address in Contact with its account code; deleting it ends any paid access on that TV. Whop keeps its own payment records for as long as the law requires of it.

Popular-title rails

Home, Movies and Series can show rows such as “Now Popular”, “Trending” and “Top Rated”. To build them, the app downloads small public files from lists.galarama.app, in the background and after the screen has appeared. There are seven lists, each in three languages. The app asks for up to three of those languages, so it downloads at most 21 files, a few kilobytes each. A device that uses only one of those languages downloads at most seven. Each file is downloaded about once a day, and a download that fails is tried again later. The files are the same for everyone and are built once a day from TMDb’s public lists. These downloads are on unless you turn them off in Settings → About → Privacy → “Popular rows on Home”; with it off, the app stops them and deletes the list files it has kept. That switch covers these downloads and the pictures described under Artwork below, and nothing else: the app’s check for updates still asks galarama.app for one small file each time the app starts.

The address contains only a list’s name and a language (English, Turkish or Arabic). The app asks for the language it is set to, the language your library’s titles are written in (it works that out on your device from the letters in those titles) and any other language your device is set to, each only when it is one of those three; when the app is set to none of them, it asks for English in its place. The request has no query string, no cookie, no account, device or profile identifier and no referrer. The host can see your IP address and the request itself, which names the lists and languages you ask for: a rough sign of the languages you use. Cloudflare, which hosts the files, processes each request as described under This website · diagnostics.

The app then compares those files with your own library, on your device. Apart from the request described above, whose address can name a language worked out from your library’s titles, and the picture requests described under Artwork below, whose addresses name pictures of titles in your library, nothing about your library, your sources, what you watch or your device is sent to us or to anyone to do this, and a title that is not in your library is never shown.

Artwork. A card on these rows, a wide card on the rows of your own categories in Series, the large picture at the top of Home, and the page of a title in your library can show a wide picture. It comes from one of two places. The first is the artwork address your own library already holds for that title, exactly as the rest of the app does: that address is whatever your own source supplied, so the image is requested from wherever that source points it (some sources point their own artwork at TMDb’s image host too, and that request is then your source’s own address). The second is TMDb’s image host, image.tmdb.org: for a title in your library that one of the lists above also names, the app asks it for that title’s picture. The address is that host, a size and the picture’s file name, and nothing else. The request is a plain GET over an encrypted connection with no query string, no cookie, no account, device or profile identifier, no referrer and none of your source’s sign-in details or headers; it carries only the standard headers of the app’s network library, which name the library and its version. It is made when such a card is drawn on Home or on a category row in Series (there, only for a title one of that tab’s own lists names; the category rows in Movies show posters and never ask for one), when such a title comes up in the large picture at the top of Home (the app asks for the next title’s picture while the one before it is showing, so that it is ready in time), and when that title’s page is opened. This request goes to TMDb’s image host and not to us.

The image host sees your IP address and which pictures are requested; because each picture belongs to one title, it can tell which of those titles are drawn and which title’s page you open. You can turn this off, together with the rows above, in Settings → About → Privacy → “Popular rows on Home”. It is on unless you turn it off, and your choice stays on the device when you sign out. With it off, the app stops downloading the list files and deletes the copies it has, the rows built from them and the TMDb notice under them leave the screen at once, and nothing the app shows from then on asks TMDb’s image host for a picture. Turning it off does not take back what has already happened: a picture already on its way, or already stored on the device, is not recalled, and a picture that was already showing (on a card, at the top of Home or on a title’s page) may stay until that screen is shown again, and may still be asked for once more if the title’s own picture fails to load. Turning it off does not stop the app’s other requests, such as its check for updates. If a later version loads artwork from anywhere else, this page will say so before that version ships.

This application uses TMDB and the TMDB APIs but is not endorsed, certified, or otherwise approved by TMDB.

What we store When accounts launch

Your email address, your billing record (from our payment provider — never your card number) and the list of screens linked to your account: the name you gave each one, its platform and when it last checked in.

If sync is on (Plus and Pro) When accounts launch

To keep your screens in step we also store your sources — including their credentials — plus favourites, playback positions and recording schedules. Credentials are encrypted, but our service holds the keys, so it can technically decrypt them. You can turn off credential sync in Account → Privacy & data: each screen then keeps its own credentials and we delete our copy.

What we never do

We never proxy or see your streams — playback runs directly between your screen and your source. No ads, and we never sell or rent your data. We run no cross-site trackers of our own, and the apps contain none. The one place another company’s scripts and cookies appear is the payment form on galarama.app/pay, after you tick the consent box and press the pay button; Samsung TV trial and payments lists them.

Codes and sign-in

TV link and pairing codes last 10 minutes; sign-in codes, once accounts launch, last 15 minutes. Each works once.

On your TV

Both apps keep your data in their own storage on the TV: the sources you add, with their addresses and any username and password; your profiles; watch history, resume points, likes, favourites and lists; your settings; and, if you set a parental PIN, a salted check value made from it, never the PIN itself. None of it is sent to us. Apart from the requests described on this page, the app contacts only the sources you add, and playback runs directly between your TV and them. Uninstalling the app removes all of it from the TV.

The Samsung TV app reads the TV’s model name and free storage to show them under Settings → Device & storage. The free storage is never sent; the model name is sent only inside a crash report (see Crash reports). In the Samsung TV app, the switch for the popular rows is in Settings → About → “Popular rows on Home”.

The Samsung TV app also keeps a second copy of your sources, with their addresses and any username and password, and of your stream-quality and channel-version settings, in a separate store in the same app storage. It is used for one thing: if the app’s library is damaged and you clear it with Start over, the app offers to restore your playlists from this copy (choosing Start empty deletes it). Signing out empties it, and uninstalling the app removes it with the rest. It never leaves the TV and is never part of a crash report.

This website · diagnostics

Our hosting provider, Cloudflare, processes request data (IP address, timestamp, user agent, error codes) for security and debugging; we will state how long it is kept here before the waitlist opens. To stop the waitlist and pairing forms, and the Samsung TV app’s trial and voucher requests, being flooded, we turn your IP address into a one-way hash and count attempts against it for 60 seconds. Neither the address nor the hash is stored with your waitlist entry.

Crash reports

Crash reports are on by default. You can turn them off at any time with Send crash reports in the app, under Settings › About; turning it off stops reports at once, without a restart, and it stays off. While they are on, a report is sent when the app closes unexpectedly or meets an error. It carries the error and its stack trace, the app version, the device model, the Android or Tizen version (and on Android TV the memory state), and a random identifier made for this installation (on a Samsung TV, turning reports off deletes it). Web addresses, IP addresses and logins that appear in an error’s text are removed on the TV before the report is sent. It never carries your sources or their addresses, logins, the titles you watch, or the name of your device. It carries no account, email or advertising identifier. We send them because they are the only way we can see and fix a crash on your TV, which is our legitimate interest; the switch is your right to object, and it works straight away. Reports go to Sentry, which processes them for us in the EU, and are kept for up to 180 days.

Usage counts

Usage counts are on by default. You can turn them off at any time with Share usage counts in the app, under Settings › About; turning it off stops them at once and it stays off. While they are on, the Android app tells us, at most once a day, that it was opened, which kinds of source it has (for example M3U or Xtream), and whether something was played, plus once ever when each of those first happens. Each message carries only those event names, the source kind, whether it is a TV or a phone, and the app version. It carries no identifier of any kind, so we cannot link two messages or tell who sent one. It never carries your sources or their addresses, logins, the titles or channels you watch, or anything about your device. Our server adds one to a daily total and keeps nothing else; the totals are deleted after 90 days. We use them to see whether people get from installing the app to adding a source and playing it, which is our legitimate interest; the switch is your right to object. The totals are stored with Cloudflare.

Export and deletion When accounts launch

Export everything we hold as JSON from your account. Deletion of your account data is immediate; invoices are kept as long as tax law requires.

Türkiye — KVKK

This is our disclosure under Article 10 of Law No. 6698 (KVKK). The data controller is Taha Altındağ, an individual, Kavacık Subayevleri Mah. Fethibey Cad. 43/10, Keçiören / Ankara 06135, Türkiye (see Contact). Today we process waitlist data (your email address, the platforms you ticked and the day you joined) and, unless you turn them off in the app, the crash reports described in Crash reports, on the basis of our legitimate interest in finding and fixing crashes (Article 5(2)(f)). Usage counts (see Usage counts) are anonymous daily totals with no identifier, so they are not personal data; they are stored with Cloudflare and may be processed outside Türkiye. Waitlist data is collected electronically through the form on this site, for the single purpose of telling you when Galarama opens on your platform, on the basis of your explicit consent, which you can withdraw at any time. It is stored with Cloudflare and passed to our email provider only to send that email. Both may process it outside Türkiye. Crash reports are collected automatically by the app and processed by Sentry in the EU, outside Türkiye. For the Samsung TV app we also process the trial and payment record described in Samsung TV trial and payments, collected automatically by the app and by our payment provider, to provide the trial and what you paid for (Article 5(2)(c), the performance of a contract); it is stored with Cloudflare and may be processed outside Türkiye, and Whop Inc., in the United States, processes your payment details to take the payment; we can see the buyer’s name and email address for each payment in Whop’s seller dashboard. Under Article 11 you may ask whether we process your data, request details of it, learn its purpose and who it has been transferred to in Türkiye or abroad, have it corrected or deleted, object to an outcome of automated analysis, and claim compensation for unlawful processing. We reply within 30 days. This section will be updated before accounts or payments collect any other data.

Your rights

Wherever you live, you can ask us for a copy of what we hold about you, and ask us to correct it, delete it, or stop using it. You can withdraw consent at any time; that does not affect anything done before you withdrew. We answer within 30 days. If you are in the EU or UK and are unhappy with our answer, you can complain to your local data-protection authority. In Türkiye you can complain to the Personal Data Protection Authority (KVKK).

Contact

For anything on this page, including a request under Your rights, write to help@galarama.app. Galarama is made and operated by Taha Altındağ, an individual and not a company, who controls the data described here. Postal address: Kavacık Subayevleri Mah. Fethibey Cad. 43/10, Keçiören / Ankara 06135, Türkiye.