Cookie 政策

Cookies are small pieces of text a website asks your browser to keep and send back with later requests. Browsers also give websites other storage (local storage, session storage and IndexedDB) that stays on your device and is not sent to the website on its own.

Strictly necessary cookies are the ones a website needs to do what you asked it to, such as keeping you signed in. RuneManga uses those, and analytics and Google sign-in cookies that you can turn off.

rm_session

• Purpose: keeps you signed in on the website.
• When: set only after you sign in (with Google, Discord or an email link). Signing out deletes it.
• Duration: 14 days.
• Type: strictly necessary, first party (runemanga.com). HttpOnly, Secure and SameSite=Lax. Our database stores only a hash of it.

rm_browser

• Purpose: a random id for this browser, so the free credits for new accounts can be given only a few times a day per browser. It identifies the browser, not you, and nothing else is read from it.
• When: set the first time you sign in. Signing out keeps it.
• Duration: 2 years.
• Type: strictly necessary (it protects the free credits from abuse), first party (runemanga.com). HttpOnly, Secure and SameSite=Lax.

rm_ref

• Purpose: remembers the invite code of the link you opened (a link like runemanga.com/?ref=CODE), so that the person who invited you gets their referral credits if you create an account.
• When: set only if you open an invite link. It is read once, when you create an account, and used for nothing else.
• Duration: 30 days.
• Type: first party (runemanga.com), used only for the invite program: no tracking, no advertising. HttpOnly and SameSite=Lax.

rm_src

• Purpose: remembers where your first visit came from, as a kind of source (for example "google, search", "chatgpt, ai" or "direct"), the campaign tag of the link if it had one, the kind of page you landed on and the day. If you create an account, it is copied onto the account once, so we can see which sources bring people who sign up and later buy. It holds no id and nothing about you.
• When: only with the same answer as Google Analytics: in the EU and EEA, the UK, Switzerland and Türkiye (and when we cannot tell your country), only after you press Accept in the cookie notice; elsewhere from your first page. A later visit from another source does not replace it, except one that came direct. Declining with Cookie settings stops it from being set or renewed.
• Duration: 30 days.
• Type: analytics (not strictly necessary), first party (runemanga.com). HttpOnly and SameSite=Lax.

rm_oauth_nonce

• Purpose: protects a Google or Discord sign-in from forgery while it is in progress, and holds its one-time PKCE code.
• When: set when you click "Continue with Google" or "Continue with Discord" and deleted as soon as you are sent back. It is sent only to our sign-in addresses. Email-link sign-in sets no cookie of its own.
• Duration: 10 minutes at most.
• Type: strictly necessary, first party (runemanga.com). HttpOnly and SameSite=Lax.

rm_onetap_nonce

• Purpose: protects Google's quick sign-in (One Tap) from forgery: the answer Google signs must carry the same one-time value.
• When: set only while Google's quick sign-in prompt is offered to you (signed out, and allowed by your cookie answer, as for g_state below). Deleted when you use it. It is sent only to our quick sign-in address.
• Duration: 10 minutes at most.
• Type: strictly necessary for that sign-in, first party (runemanga.com). HttpOnly and SameSite=Lax.

rm_lang

• Purpose: remembers the language you picked in the language menu. Without it, your first visit to a page opens in your browser's language when we have it; once you pick one, the website stops doing that for you.
• When: set only when you pick a language in the menu at the top of the page.
• Duration: 1 year.
• Type: strictly necessary (it does what you asked for), first party (runemanga.com). SameSite=Lax, Secure.

_ga and _ga_2HL2YZJP9Q (Google Analytics)

• Purpose: a random id that lets Google Analytics count visits and see which pages people use (the Privacy Policy lists what it records). Not used for advertising.
• When: in the EU and EEA, the UK, Switzerland and Türkiye (and when we cannot tell your country), only after you press Accept in the cookie notice; elsewhere from your first page, as the cookie notice says. Declining with Cookie settings at the bottom of every page deletes them.
• Duration: 13 months.
• Type: analytics (not strictly necessary), set on runemanga.com by Google Analytics' script.

g_state (Google)

• Purpose: set by Google's sign-in script to remember that you closed its quick sign-in prompt, so it does not keep asking.
• When: only while Google's quick sign-in may show, which follows the same answer as Google Analytics: in the EU and EEA, the UK, Switzerland and Türkiye (and when we cannot tell your country), only after you press Accept in the cookie notice; elsewhere from your first page while you are signed out. Declining with Cookie settings deletes it.
• Duration: set by Google's script.
• Type: not strictly necessary, set on runemanga.com by Google's script. While the script runs, Google also receives your IP address and browser details and uses its own cookies on accounts.google.com, under Google's privacy policy.

If you never sign in, never pick a language and analytics and Google's quick sign-in are off (declined, or not accepted where a yes is needed first), runemanga.com sets no cookies at all.

These stay in your browser. The website reads them on your device; they are not sent to us.

• rm-theme (local storage): your light or dark choice.
• rm-consent-v2 (local storage): your answer in the cookie notice (Google Analytics and Google's quick sign-in accepted, or OK, or declined), so it is not asked again. Cookie settings at the bottom of every page asks again. It replaced rm-consent, whose yes covered analytics only: the website deletes that key, keeps a no and asks again after a yes.
• Your choices on the Translate page, such as the lettering font and how long history is kept (local storage), and your translation history, the original and translated pages of your past jobs (IndexedDB), with each translated page's balloons (where they are, the text read on the page and its translation, the lettering's font, size and colours) and a copy of the page with the lettering removed, so its balloons can still be edited in Edit mode. History older than the period you pick is deleted the next time you open the Translate page, and you can delete it from the page at any time.
• rm-job-prefs and rm-own-ai-key (local storage): your Translate settings (who translates, the job options and your own instructions) and, if you enter one, your own AI key. The key is sent only to the AI provider it belongs to. Removing the key in the settings deletes it.
• Your edits in the WebApp's Edit mode (IndexedDB, a database named runemanga-edits, apart from the history): for each page you edited, its text boxes, brush strokes and the pictures you added (an edited balloon adds a piece of the page without lettering under its new text), with the size of the translated page they sit on, so the page opens again as you left it and your downloads, ZIP and history card include the edits. They belong to a page in your translation history and are deleted with it: when you delete that entry, when it is older than the period you picked, or when the history makes room for new pages. A page that is not in your history keeps its edits in that tab only, until you close it. Revert to original deletes a page's edits (Undo brings them back while the tab stays open).
• rm-editor-presets, rm-editor-wheel and rm-editor-hint (local storage): the style presets you saved in the Edit mode, whether the mouse wheel scrolls or zooms the page, and that you closed the first tips.
• rm-support-seen (local storage): which of your reports you have opened on the Support page, so new replies can be marked.
• rm-low-credits (local storage): that you closed the note about having few or no credits left, and on which day, so it stays closed until the next day.
• An error you chose to report (session storage): its text is carried to the report form and is gone when you close the tab.
• rm-visit and rm-visit-at (session storage): that this tab's visit was already counted, and the page it started on, so a visit counts once however many pages you open in the tab. Gone when you close the tab.
• The browser extension keeps its settings and sign-in in the extension's own storage, not in website cookies. The Privacy Policy lists what it keeps.

• Where you need to say yes first (the EU and EEA, the UK, Switzerland and Türkiye, or when we cannot tell your country), Google Analytics and Google's quick sign-in run only after you press Accept in the cookie notice; before that no Google script loads and nothing is sent. Elsewhere they run from your first page and the cookie notice tells you so. If you decline, neither runs.
• When it runs, it records pages without anything after a ? in their address, never on the Control Room, Support or sign-in pages, and Google removes email addresses and sign-in codes as a second safeguard. Its advertising features are off.
• No advertising, social media or tracking cookies, and no tracking pixels. Google Analytics and Google's sign-in script (only while you are signed out) are the only scripts of another company that run on our pages, and only while your answer allows them.
• When you sign in with Google, you go to accounts.google.com, with Discord to discord.com, and when you buy a plan or credits, to Whop's checkout. Those pages set their own cookies on their own domains, under their own policies; nothing of theirs runs on runemanga.com except Google's quick sign-in script described above.
• When you are signed in, your Google or Discord profile picture is fetched by our server and served from our own address; your browser does not contact Google or Discord for it.
• The WebApp loads the Japanese, Chinese and Korean lettering fonts of the Edit mode from Google Fonts when an edited page's text box needs one (on screen, or to draw a download or history card) (the Privacy Policy says what Google sees). Those requests carry no cookies, and no Google cookie is set for them.

Where a yes is needed first, refusing is as easy as accepting: Decline and Accept sit side by side and nothing optional is set before you accept. Everywhere, Cookie settings at the bottom of every page changes your answer at any time.

• Cookie settings, at the bottom of every page, opens the cookie notice again: Decline stops Google Analytics and Google's quick sign-in and deletes their cookies.
• Sign out on the Account page: that deletes rm_session and ends the session on our side too.
• Your browser's settings let you see, delete or block the cookies and site data of runemanga.com. Clearing the site data also removes the local storage, the translation history and the edits listed above.
• If you block cookies, you cannot sign in, and the WebApp needs a sign-in. The rest of the website works without cookies.
• Removing the browser extension deletes everything it stored.

Questions about cookies or this page: [email protected].