Your sign-in, and why scripts on the page can't touch it
How we keep you signed in on the website without any code on the page ever holding your sign-in, how to end a session properly, and how our WhatsApp and Telegram bot signs in on your behalf.
Lodge Internet · 14 November 2026 · 4 min read
You signed in on a friend's laptop to buy a plan before your data ran out, then handed the laptop back. Your sign-in is still sitting in their browser.
That's worth a minute's thought, so here is how sign-in works on Lodge Internet, what it can and can't be used for, and how to end it.
Where your sign-in lives
When you sign in on the website, our server opens a session for you: a record that says "this browser belongs to this account". The browser keeps its half in a cookie, which is a small note a website asks your browser to store and send back with each visit.
We mark that cookie so that no script can read it. A script is a small program a web page runs, and pages run plenty of them. The browser still sends our cookie along with every request to our server, but it refuses to show it to any code on the page. That includes our own code. The website you use never sees your sign-in at all.
Here's why that matters. If a harmful script ever ended up on a page, the worst kind would try to copy your sign-in and send it somewhere else. With our cookie, there is nothing for it to copy.
Why another website can't borrow it
Browsers send cookies automatically, which is normally what makes them useful. It would also be a risk if a page on some other website could make your browser contact us, and your sign-in would go along with the request.
So our server ignores the cookie unless the request also says which part of our own site it came from. Our pages say that on every request. A page on another website can't, because the browser won't let it without our permission. To our server, a request like that is just someone who isn't signed in.
Ending a session
Every request from the website is checked against your session on our server, so when a session ends, it ends at that moment. Nothing keeps working on borrowed time.
- Log out ends the session in that browser, on our server too, rather than only deleting the cookie. On your friend's laptop, that's the thing to do.
- Resetting your password ("Forgot password" on the sign-in page) ends every website session you have, on every device. If you think someone else has your password, reset it.
- Closing your account ends every session you have, everywhere, at once. Closing your account covers what else happens.
Left alone, a session ends by itself after a stretch of not being used. Coming back to the site pushes that end date back, which is why you aren't asked to sign in every day.
Our database doesn't even keep your session's secret, only a scrambled fingerprint of it. That's enough to recognise the real thing when your browser sends it, but no use to anyone who reads the database.
Two small things that guard your money
Before you pay for anything on the website, the server checks how long ago you last entered your password. If it was a while back, it asks you to type it again. A browser you signed in on long ago can't be used to spend from your wallet without your password.
And when a password is wrong, we say "Incorrect email or password" whether or not the email has an account with us. We also take the same time to refuse either way. Nobody can use the sign-in page to find out who our customers are.
How the bot signs in
Our WhatsApp and Telegram bot is a separate program running on its own server, so it can't use a browser cookie. You sign in to it with a six-digit code we email you, and it opens a session for your chat, much like the website does.
The bot doesn't send that session with every message, though. It trades it for a short-lived pass and uses the pass instead. The pass stops working soon after it's issued, and to get a new one the bot has to show a session that's still open on our side. If the account is closed or blocked, the bot loses access shortly after. Renewing the pass happens quietly, so you never get a message about it.
Two things to know:
- A password reset doesn't sign the bot out, because the bot never used your password in the first place.
- To sign the bot out, send logout in the chat. The bot throws away its session for your chat, and you'll need a fresh emailed code to sign in again.
If something looks wrong
If you see a purchase you didn't make, reset your password first, then message us. Getting help says who to contact and what to send.
Last checked against the product on 14 November 2026.