Version 2026-08-14
Who is responsible for your data
“KomaLume” is the name this service operates under. It is not a company. The service is run by the people named below, and they are the data controllers under Thailand's Personal Data Protection Act.
- komalume.com
For anything about your personal data, including using any of the rights below: support [at] komalume.com
What we hold, and why
Your account
A display name, an email address, and — if you signed in with Google — the account identifier Google gives us. We keep sign-in times, IP addresses and browser details to secure the account and to answer “was this me?”.
If you connect Discord, we hold the Discord account id, the username it shows, and whether you have collected the rewards for joining. Connecting is not a way of signing in — it is a separate thing you turn on, and you can disconnect it whenever you like.
We do not ask for your date of birth, anywhere. A birth date would be data held for no reason, and data held for no reason is only ever a liability.
The files you upload
Your pages, the text found in them, the translation, and the finished pages. Every upload is decoded and re-encoded on arrival, which strips metadata — including any location a camera or phone wrote into the file.
Your files are served only back to you, through a route that checks who is asking. They are never shared, never indexed, and never used to train anything.
If you drop pages onto the front page before you have an account, they are held for up to 24 hours in your browser's own storage (IndexedDB) — not on our servers, and not readable by any other site. They are cleared the moment your job is created, and otherwise the next time you open the site after those 24 hours have passed. You can also clear them yourself at any time, with the button on the panel that holds them.
The browser extension
The extension reads the page images on one tab, and only at the moment you invoke it there — when you press its toolbar button or use its right-click entry. It holds no standing access to any website. When a reader serves its images from somewhere the page itself cannot read, it asks you for that one site, on a click, in Chrome's own prompt — and Chrome is where you take it back.
What it keeps, it keeps on your own machine. The pages you have collected sit in your browser's storage (IndexedDB) until you send them or empty the basket, next to the language and view you chose and the key that stands in for your password. That key belongs to that one browser, and you can revoke it per device from your account settings — the extension never sees the password itself.
When you press translate, the pages travel from your browser to your own account here, and from that moment they are held under exactly the rules above for anything you upload. The addresses of the sites you read are never sent to us — not the page you collected from, and not any other. Our servers are never handed a link to go and fetch.
If you have turned measurement on, the panel also reports four things by name and nothing else: that a browser was connected, that pages were added to a basket and how many, that a chapter was submitted, and that a site's images could not be read. No page content, no image and no site address rides along, and the name it reports itself by is derived from the key above, so revoking the device ends it.
Payments
What you bought, what it cost, and which method you used. Card details never reach us — the payment provider handles those. If you pay by bank transfer, the slip you upload is a photograph of your bank app, so it is held under the same access check as your artwork and shown only to the person confirming the transfer.
How long we keep it
| What | Kept for |
|---|---|
| Translated pages | 7 days on the free tier, 90 days once you have bought credits, then deleted automatically |
| The pages you uploaded | Until you close your account, or ask us to delete them |
| Working copies made while translating | 24 hours after the job finishes |
| Security logs — IP address and browser | 90 days, then erased from the record while the record of the action itself stays |
| Payment and credit records | Kept as long as we may need to answer a question about a payment |
| Backups | 30 days |
Backups matter to one of your rights: when we delete something at your request it goes from the live service immediately, and the copies in our backups age out within 30 days.
Who else sees it
Only the services the product cannot run without:
| For | Who | Where |
|---|---|---|
| Translation and reading the text on a page | OpenAI | United States |
| Hosting, storage and the database | Self-hosted — our own servers | Thailand |
| Card payments | Stripe | United States |
| PromptPay and Thai payment methods | Omise | Thailand |
| Signing in with a provider account | Google — only the account you choose to use | United States |
| The community server, if you connect it | Discord | United States |
| Sending email — sign-in links, and notices about your jobs | smtp.resend.com | Wherever your mail provider is |
| Measuring how the site is used — only after you agree, and never on a page address that identifies your work | Google Analytics | United States |
Cookies and measurement
The site sets a small number of cookies it cannot work without: the one that keeps you signed in, the one that stops other sites posting forms on your behalf, and the one that remembers which language you chose. Those are not optional and nobody outside our servers sees them.
Beyond those we use Google Analytics to count visits, and only if you agree. Until you do, the tag on the page is told to store nothing: no analytics cookie is written and nothing is kept that could recognise you on your next visit. It is honest to say that even then your browser has contacted Google, so Google sees your IP address the way it does for any file a page loads.
What we send is deliberately blunt. Page addresses go out as their shape rather than their contents — a job page is reported as “/jobs/:uuid/”, never as the address that identifies your chapter — so the report can say how often job pages are opened and can never say whose. The staff console and the admin are not measured at all. We have turned off Google's advertising features, so nothing here feeds an advertising profile.
You can change your mind at any moment, and it takes effect on the page you are looking at.
Your rights
Under Thailand's PDPA you can ask to see the data we hold about you, ask for a copy of it, have it corrected, have it deleted, have its use suspended, object to how it is used, and withdraw any consent you gave for something optional.
Two of these are buttons in the product, on your settings page: Download my data gives you everything we hold as one file, and Close my account deletes it. For the rest, write to support [at] komalume.com and we will answer within 30 days, which is the window the law gives us.
Two limits worth saying plainly rather than in a footnote: we cannot delete a payment record while we may still need it to answer a question about that payment, and closing your account does not retract a translation you have already downloaded.
And one thing we keep on purpose after you close your account: a scrambled, one-way note of the email address, and of any Discord account you connected, saying that the welcome credits were already paid to it. It cannot be turned back into your address, it says nothing else about you, and it exists so that closing an account and opening a new one is not a way to collect free credits over and over. If you sign up again on the same address, everything else starts fresh — the welcome credits do not.
Files that are not yours
When you upload something, you are telling us you have the right to. If a page contains personal data about someone else, that is yours to have a basis for — your permission cannot stand in for theirs. This service is not built to handle sensitive personal data about real people, and should not be used for it.