01What this page is
This is the register of what is stored on your device when you use Cinemere, why, for how long, and which of it you get a choice about. Everything Cinemere stores itself is named here: each cookie and cache by name, and the app's own storage by its prefix, with every key on your device listed live, with its size, on the privacy page. The other companies that can store something while you use it, Cloudflare, Paddle, Google and your browser's push service, each have their own row: what it stores is named where we have read it off our own site, and otherwise described by purpose, with a pointer to that company's own list.
It is a separate document from the Privacy Notice on purpose, because it answers to a different law. What we do with personal data is governed by the GDPR. Putting anything on your device, or reading anything already on it, is governed by 9 kap. 28 § of the Swedish Electronic Communications Act (2022:482), which applies whether or not the thing stored is personal data at all. Different rule, different test, different regulator, so it gets its own page rather than a subsection. That rule applies to everything we do, wherever you are. If you live in the United States, section 07 of the Privacy Notice says which American privacy laws we follow and how to use your rights under them.
The authority that supervises this is Post- och telestyrelsen (PTS). Section 09 has the contact routes.
02What counts as a cookie here
Most cookie policies quietly list only cookies. The law is broader than that, and so is this page.
9 kap. 28 § is written about storing information in, or gaining access to information already stored in, a user's terminal equipment. It does not say "cookie" anywhere. A cookie is simply the oldest way of doing that, so three other things on Cinemere fall under exactly the same rule and are listed here as first-class entries:
- localStorage, which is where the app keeps your library. On cinemere.com it is a cache of what the server holds. In a local copy without a server it is the database.
- The offline app cache, which the installable app uses to open when your connection is bad.
- The push subscription, if you ever turn notifications on.
Leaving those out would have made this page shorter and would have made it wrong. If something of ours lives on your machine, it is in the table below.
03Everything we store, in full
No company outside this table stores anything on your device through Cinemere. There is no second table somewhere for partners: the one advertising partner is in this table, marked as not started, because a list that only grew on the day ads began would be a list you had no chance to read first.
localStorage and sessionStorage, keys beginning cm_
Cache Storage, cinemere-shell-*
Not started. Names listed here when ads begin
Not started. Names listed here when ads begin
Fonts are worth a line because they are usually the quiet exception. Ours are self-hosted. Cinemere does not load fonts from Google, so no request about you goes to Google for a typeface.
Two catalogue services are reached by your browser directly and store nothing on your device: posters come from TMDB and currently airing series from TVmaze. Both see your IP address when your browser asks them for something, as section 03 of the Privacy Notice explains.
In the Cinemere app for iOS and Android, a copy of your data that you ask to export is written to the app's own cache so that the share sheet can hand it to you. Only the newest copy is kept, and it never leaves your device unless you send it somewhere.
04Why the necessary ones need no consent
9 kap. 28 § has one exemption, and it is narrow: storage that is necessary to transmit a message, or to provide a service the user has expressly requested, needs no consent. It still has to be disclosed, which is what section 03 is for.
Each of the necessary entries sits inside that exemption for a reason we can state plainly:
- cin_session exists because you asked to sign in. A sign-in cookie is the textbook example of the exemption.
- Application storage is how the service works, not a convenience added to it. It holds five kinds of thing, and each is there for its own reason:
- Your account and library (diary, lists, watchlist, ratings, messages, settings). Every page reads them from here in order to draw them, including what our server has just sent. Without it there is no diary to open.
- Choices you made yourself, such as game sound off, a prompt you dismissed or a member you blocked. Remembering a choice you expressly made is part of the service you asked for; forgetting it would mean asking you again on every page.
- Catalogue lookups, such as which poster belongs to which film. What each one stores is a public fact about a title, and they do on this device what the browser's own cache does for every website: they spare the page from fetching the same fact again. Which titles they hold, though, follows what you have opened, logged or saved, so anyone using this browser could tell from them which titles you have dealt with. They never leave this device, they are not sent to us, and they stay after you sign out, which is why section 07 says to clear this site's data on a shared computer.
- Recently viewed, the titles and people you opened, is different, because it records what you did rather than something you asked us to keep. So it is off until you turn it on from the row itself, nothing is noted before then, and turning it off clears it. Once you have turned it on, it is a service you expressly asked for.
- Oracle history, the picks The Oracle gave you, works the same way and for the same reason: asking for a pick is not asking us to keep it. It is off until you turn it on from the history panel, nothing is kept before then, and turning it off clears it.
- The offline cache holds only Cinemere's own pages, styles and fonts, never anything about you, and it is what lets the site you asked for open at all on a bad connection. It reads nothing from your device and tells us nothing.
- __cf_bm and cf_clearance keep the site standing up. A service you asked for has to be reachable.
- Paddle's checkout storage exists to take a payment you asked for.
- Your advertising choice, once ads start, exists so that a no stays a no. Without it we could not honour your answer, and would have to ask you again on every page.
We are not claiming the exemption for anything that merely suits us. If we ever wanted to measure how you use Cinemere, that would be analytics, it would not be necessary, and it would go in section 05 with a switch on it. Today there is nothing in that category.
05The two things we ask about
YouTube trailers, and ads from Google on the free plan. That is the entire consent surface of this site, and the second of the two has not started yet.
A trailer is embedded from a third party that can set its own cookies, so it is not ours to decide for you. Until you switch it on, the title page shows a prompt where the player would be and makes no request to YouTube at all. Not a hidden one, not a preconnect, nothing. When you accept, we record that choice and embed through youtube-nocookie.com rather than the ordinary player.
You can withdraw it at any time, as easily as you gave it, with the control in section 06. Declining costs you the trailer embed and nothing else: every other part of Cinemere works identically.
Advertising works the same way, and it is described now so that it is not new to you on the day it starts. Before any ad appears we will tell you in the app, and the banner will ask you whether Google may show you ads. Until you say yes, nothing loads from Google and your browser sends it nothing. If you say yes, Google may store the cookies in section 03. The free plan carries ads either way: without your yes they are our own ads, served from cinemere.com, which store nothing on your device and read nothing from it, so they need no consent and no cookie. We set Google's ads to be non-personalised, so Google chooses them from the page and your approximate location, never from your account or a profile of you. Paid plans never show ads, whatever you answer. Saying no costs you no feature. Google describes its own cookies, and how long each lasts, on its own cookie page; the names it actually sets on Cinemere go into section 03 when advertising starts, read off a real browser rather than copied from that list.
Notifications work the same way but are handled by your device rather than by us. Your browser asks you first, and we never see them switched on unless you said yes to that prompt.
06Your choices
Your current setting, and the button that changes it, are right here. It is the same control as the one on the privacy page and in the banner, because there is one setting and it should not matter where you reach it from.
The first-visit banner offers Accept all, Essential only and Customize, and the three are equally prominent. Nothing is pre-ticked, refusing takes exactly one tap, and once you have answered the banner does not ask you the same question again. It comes back only for something new that needs your consent, such as advertising when it starts, and to check an advertising answer once it is 13 months old. No Swedish rule sets that number: it is our own choice, so that an answer never outlives the longest-lived advertising cookie Google describes, and you are asked again before either is older than the other. Leaving the banner unanswered, or closing the Customize panel without saving, is treated as a refusal: nothing optional loads until you say yes.
You can change either answer at any time, with the button above, and taking consent back is exactly as quick as giving it. What stops, stops from that moment. A cookie YouTube or Google has already set lives under their name, not ours, so we cannot delete it for you; your browser settings can (section 07).
07Controlling it in your browser
Your browser can block or clear all of this without asking us, and we would rather tell you what happens than have you discover it:
Most browsers also offer a do-not-track or global privacy signal. We run no tracking for it to switch off, and we will not sell or share your personal information under any signal or any absence of one. We still give it something to do: while a Global Privacy Control or Do Not Track signal is on, we treat it as a no to Google's ads, and nothing loads from Google. On the free plan you then see our own ads, which store nothing.
What is on your device is guarded by your device. Anyone who can use your unlocked device and browser can read the application storage, just as they could open the app. We keep it to what the pages need, the sign-in cookie cannot be read by any script, and the offline cache holds nothing about you. Signing out ends your session and clears this browser’s copy of your account and activity; device settings, cached catalogue data and Recently Viewed (if you turned it on) stay. On a shared computer, sign out and then clear this site’s data as the table above describes. Do not use Erase for that: it deletes your account itself. How we protect what is on our side is in section 09 of the Privacy Notice.
08What we deliberately do not do
Stated as commitments rather than as absences, so you can hold us to them:
- No ad network except Google's, and none of its cookies before your yes. Our own ads set no cookie and use no storage at all. No ad exchange or header bidding of our own, and no personalised ads. Google runs its own auction for each ad, as the Privacy Notice explains.
- No analytics, of any kind, first party or third.
- No social media pixels or share-button trackers.
- No data brokers, no audience lists, no fingerprinting.
- No cookie wall: refusing never locks you out of anything.
- No consent by scrolling, by continuing, or by silence.
If any of that ever changes, it changes here first, with a version bump and a fresh ask. Adding a tracker quietly would break the promise this page is for. Advertising is the example: it was written into this page before it started, not after.
09Changes, contact and supervision
If we add or remove anything in section 03, we update this page and move the version at the top. If the change means storing something new that needs your consent, we ask you again rather than assuming an old answer covers it. We keep every earlier version of this page, and we will send you the one that applied on any date you ask about.
Questions about this page: [email protected].
If you think we have got this wrong, you can complain to Post- och telestyrelsen (PTS), which supervises the Electronic Communications Act, at pts.se. For anything about personal data rather than device storage, the authority is Integritetsskyddsmyndigheten (IMY), at imy.se. You do not have to come to us first. If you live in the United States, you can also complain to the Federal Trade Commission or to your state's attorney general.
Cinemere AB, —, —, Sweden · Company number —