Privacy Policy
Last updated: October 2026
1. Overview
Smok ("we", "us") runs the smok.to website and the Smok app for Android ("the app"): a free map and guides to designated smoking areas in Japan. You can use the map and read every page without an account.
This policy explains what we keep if you create an account (section 2), what we record when you visit the website or use the app (section 3), what is stored on your own device (section 4), how we use it (section 5), which other companies handle data and why (section 6), how long it is kept (section 7), and how to turn analytics off or have your data deleted (section 8). Where the website and the app differ, we say so. We do not sell personal data, show ads or use advertising trackers.
2. Your Account
An account is optional. It is only needed to keep saved places on every device, write reviews, answer whether you could smoke at a place, and report problems. If you create one, we keep:
- Your email address, if you sign in with a code sent by email, or if Google or LINE share an address with us (we use an address from Google only once Google has confirmed it; an address from LINE is used as LINE reports it, so it may not have been confirmed). We use it to sign you in and to send you sign-in codes. We may also occasionally write to you personally about your account, for example to thank you or to ask a question, but never for newsletters or marketing.
- An identifier from Google or LINE, if you sign in with them. We do not keep your name or profile picture from those services.
- The username you choose, the tobacco brand you may show beside it, and whether your profile is private.
- What you post and save: reviews and ratings, your answers to "Could you smoke here?", the places you save, and the reports you send about a place or about someone's review.
- When you joined, and when each sign-in on a device started and ends. A sign-in lasts 30 days.
What other people see. Your username, the tobacco brand you chose to show, when you joined, how many reviews you have written, and your reviews. Reviews stay visible on each place even if your profile is private; a private profile only hides the list of your reviews on your profile page. Other readers see your reviews translated into their own language (section 6). Your email address and your saved places are never shown to anyone, and reports are read only by us.
You can sign in on the website and in the app with an emailed code, with Google or with LINE, and it is the same account in both. Your sign-in is kept in your browser's local storage, not in a cookie; in the app it is kept in the phone's protected storage (the Android Keystore). It is removed when you sign out. If you save places in the app while signed out, they stay on your phone and are added to your account when you sign in.
Tester accounts. If we invite you to test the app, the account is made by us, with an email address of our own choosing and a six-digit code that we give you; you sign in with that code and nothing is emailed. What it writes is shown to that account alone. Section 3 says what we record about a tester.
3. Analytics: What We Record When You Visit
We run our own analytics, on our own servers, to understand how the website and the app are used and to find what is broken. No analytics or advertising company receives this data. On the website we record:
- The pages you open, the address of the page or search engine that sent you (we keep the whole address, including any search or campaign tags in it), and how you use each page: scrolling, reading time, the links and buttons you click (with a few words of their text) and any errors.
- What you do on the map: where the map is showing (down to about 10 metres in the most detailed records, and less precisely in the others), which places you open, the filters you use, the places you save and the buttons you press on a place card.
- Searches: what you type in the map's search box is sent to our server, encrypted, so that it can suggest results; the server does not store it, and it is not recorded as you type. When you pick a result, or nothing is found, the search is recorded in lower case, with long numbers and email addresses removed, and deleted after 30 days.
- A simplified replay of each visit, once per second: how far you have scrolled, where the mouse pointer and your taps are (as a share of the screen), and where the map is. It does not record what you type, the text on the page or anything you enter in a form.
- Technical details: browser and device type, screen and window size, language and time zone settings, memory and processor count, connection type, and how fast our pages and servers respond.
- The page request itself: our servers also note each page they deliver, even when scripts are switched off or the visitor is a search-engine robot, with the page, the answer given, the page that sent you, your browser and your network (below).
- Your network: your IP address is turned into keyed hashes straight away — one that changes every day and a coarser one for the network it belongs to — and the readable address is not stored in our analytics. We also record the network provider and the approximate country and city, which our hosting provider Cloudflare derives from the address.
To tell visits apart, each browser gets a random identifier, kept in a cookie (__smk_d, 400 days) and in local storage. We link identifiers that probably belong to the same person — for example, two devices on the same network on the same day, or a link shared from one device and opened on another — so that we count people rather than browsers. Each page load also gets a short random number, which is attached to the map's requests to our server so that we can tell which visit a slow or failed request belonged to. If you have an account, your account number is recorded with the events for signing up, signing in and restoring a sign-in (when you open a page while signed in), so we can see how people with an account use the site. Your email address is never recorded in analytics.
If you use "Show my location", your browser shares your position with the map. It is sent to our server, encrypted, only to find the places near you. Our analytics does not record it as such, but because the map then centres on you, the map position recorded above can be where you are.
Activity on places, on the website and in the app. To put useful places first in the lists, our server also counts what happens to each place: when it is opened, when someone taps Route, and when it is saved, voted on or reviewed. For each action it keeps the place, the kind of action and who did it: your account number if you are signed in; otherwise a keyed hash of your IP address and browser type that changes about once a month, and a coarser hash of your network. This is part of how the lists work, so it does not depend on the analytics choices in section 8. These records are kept for 120 days (section 7).
In the Android app the analytics works in the same way, with one difference: it asks first. When you open the app for the first time, the welcome slides are followed by a screen that asks whether to share usage statistics. Until you answer, nothing is recorded or sent for analytics (the Back button means "ask me later"). If you choose "No thanks", nothing is recorded (a tester account is the one exception, below). If you say yes, you can switch it off at any time (section 8), which also deletes any records still waiting on your phone. The website has no such screen. Whatever you answer, the app still has to talk to our server to work: it loads the map, the places, the photos and your searches, uses your position to find places near you if you allow it (below), checks whether a newer version of the app exists (sending the app version and its release channel), and counts the places you open and the Route taps as described above.
With your consent, the app records: your taps; the filters you use; your searches, handled as on the website (above); the places you open, what you do on them (save, vote, tap Route, Call or Website, write or delete a review, with the place, the rating and the length of the text, never the text itself) and the movements of the place sheet; when you sign in, sign up or reopen the app while signed in; how the app was left the last time (for example after a crash); and errors and how fast our servers respond. It also records technical details: your Android version, the brand and model of your phone, screen size, language and time zone, the version of the app, and the type of connection (for example Wi-Fi or mobile data). It does not record a replay of your screen or touches, what you type into a form, or anything about your contacts or your other apps.
To tell installations apart, the app creates a random identifier the first time you agree to share statistics. It is not your advertising ID, Android ID, IMEI, MAC address or phone number, and it is kept in the app's own storage. It is removed when you uninstall the app or clear its data. If you later say "No thanks" or switch statistics off, nothing is sent and the identifier stays on your phone, unused, until then. In the app's Privacy screen you can see it, copy it, or (while statistics are on) replace it with a new one that is not linked to the old. If you sign in, your account number is recorded with the sign-in events, as on the website, which links this identifier to your account. In the analytics your IP address is kept only as keyed hashes, as above. The app talks to our server directly rather than through Cloudflare, so no approximate country or city is derived from it.
Map position in the app. The app records where the map is pointed (the centre of the map you are looking at) and its zoom, rounded to a square of about one kilometre. This is a place you chose to look at, not where your phone is. The app never records your phone's GPS position in its analytics. If you press the locate button, the map moves to you and from then on it is where you are looking, so the recorded map position can be where you are, to about a kilometre.
When you press the locate button, the app asks Android for permission to use your phone's location. If you allow it, the position is used to show where you are and is sent to our server, encrypted, only to find the places near you. You can refuse or withdraw the permission in Android's settings and still use the map. Without a position, the app lists places near Tokyo Station.
Tester accounts (section 2) are the one exception to the choice above. Straight after you sign in to one, the app shows a full-screen notice saying that we can track your actions in the app, that a reward is possible for testing, and that you have to test actively every day for 14 days to get it. You can sign out of the tester account instead of pressing OK. Until you press OK we only note that the account has signed in, and when. After that, our server keeps a log of what the account does, whether or not you chose to share usage statistics: what you search for (the text, up to 80 characters), the places, stations and airports you open, taps on Route, votes, reviews, saved places, reports and changes to your profile, and that you browsed the map (not where). For each of them it keeps the time, the kind of action and the place, if there is one, with the calendar day in the time zone your phone reports. The log has no IP address, phone model or analytics identifier. We use it to see whether the rules of the testing programme were met, for example 14 days of real use in a row, and to find what is broken. Only we can read it, and it is kept until the account is deleted (section 7). The sign-in code of a tester account is kept as it is, not as a hash (section 9).
4. Cookies and Local Storage
smok.to sets these cookies itself:
smok_lang— the language you chose (1 year). It is also saved when you open the map from a page, so that the map opens in the same language.smok_nag— that we already suggested a language to you, so we do not ask again (1 to 30 days).__smk_d— the analytics identifier described in section 3 (400 days), set by our host Cloudflare on your first visit and not readable by scripts on the page.smk_off— set only if you turn analytics off (1 year).
One more cookie, smk_role, is set only in the browsers of our own team and never reaches visitors. We also use your browser's local and session storage for what the site needs to work: your sign-in if you have an account, the language of the map, the random device identifier for analytics, banners you have closed, and analytics records waiting to be sent. We use no advertising or third-party cookies of our own. The services in section 6 may set their own cookies when you use them.
The app uses no cookies. It keeps in its own storage on your phone: your answer to the privacy screen; the random identifier from section 3; analytics records waiting to be sent (for at most 24 hours, except a short note about a crash, which is sent the next time you open the app); the places you saved while signed out; the last view of the map (used only if you come back within 30 minutes, so that the map reopens where you left it); a copy of the places and place cards you opened (for 24 hours, so that the map still works with a poor connection); the saved map style and the map's tile and photo caches; and, if you are signed in, your sign-in, kept in the Android Keystore (section 2).
5. How We Use Information
We use the information above to:
- Run the account you asked for: sign you in, show your reviews, and keep your saved places on every device.
- Understand which pages and features help people find a place to smoke, and fix what is broken or slow.
- Put useful places first in the lists, using what happens to each place (section 3).
- Show reviews in your language: every review is translated automatically into the site's other languages (section 6).
- Keep the service safe: limit how many sign-in codes and requests one network can make, and detect abuse.
- Moderate: we are notified when an account is created, when a review is posted or changed, and when an account is deleted, so that spam can be removed quickly.
- Run the testing programme: for a tester account, check whether the rules of the programme were met, for example 14 days of real use in a row (section 3).
We do not sell or rent personal data, use it for advertising or build advertising profiles. Where the GDPR applies, we rely on providing the service you asked for (your account) and on our legitimate interest in running, securing and improving a free service (analytics, the order of the lists, security and moderation). In the app, analytics is recorded only with your consent, which you can withdraw at any time (section 8).
6. Service Providers and Third Parties
Some data is handled by other companies for us, or reaches them when you use the website or the app. We do not sell data to any of them. These are the ones we use:
- Cloudflare hosts the website and processes every request to it, including your IP address. A Cloudflare Worker running our own code delivers the pages, sets the analytics cookie and records the page requests described in section 3. Cloudflare provides the approximate location used in our analytics, and, depending on how our account is set up, may also collect its own cookieless statistics (Cloudflare Web Analytics).
- Our API server. Map data, accounts and analytics are stored on a server we rent in Finland (EU). The app talks to this server directly, not through Cloudflare: its map, places, accounts and analytics all go there.
- Google Play distributes the app. When you install or update it, Google handles that under its own terms and privacy policy. Google also collects, by its own rules and if you have allowed it on your phone, statistics about crashes and how the app performs (Android vitals), which we can see only in summary. When you allow location in the app, Android may work out your position with Google Play services, Google's location service, under Google's own rules.
- Postmark delivers sign-in codes to your email address. It receives your address and the code, with open and click tracking turned off, and keeps its own delivery records under its privacy policy.
- Google and LINE, only if you choose to sign in with them. They give us an identifier and, if you allow it, your email address. In the app their sign-in page opens in your phone's browser and then returns you to the app.
- Telegram. We are notified in a private Telegram chat when someone asks for a sign-in code (the email address partly hidden, for example ab***@gmail.com, and the username if the account exists), when an account is created (the account number and the partly hidden email address), when a review is posted or changed (username and account number, rating, place, the first 200 characters of the review and a link to the place), and when an account is deleted (the account number only). The same chat receives technical alerts about the service, which contain no personal data.
- OpenRouter and an AI model provider translate reviews. After a review is posted or edited, its text, and nothing else (not your username, account number, rating or place), is sent to OpenRouter, a service that passes it to an AI language model, at present one made by OpenAI, to be translated into the site's other languages. We ask OpenRouter to route the text only to providers that do not collect or keep user data. The translations are stored on our server, together with a copy of the review text used to make them, until the review is deleted or changed. Reviews are public and are translated automatically: if you do not want a review translated, do not post it, or delete it.
- Google serves the site's fonts, so Google receives your IP address, your browser details and the address of our page whenever a page of the website loads. The small site icons in the "Sources" lists of articles come from Google's icon service, which learns which sites an article cites. Maps embedded on shop pages are loaded from Google Maps, and your browser connects to Google as soon as such a page opens, before you scroll to the map. The maps on individual spot pages come from OpenStreetMap. If a chain's logo is missing on the map, its icon may be fetched from Google's or DuckDuckGo's icon service.
- Links to Google Maps directions (in the app, Route opens Google Maps or another maps app with the place's position), the share buttons for LINE, WhatsApp, Telegram, Facebook, X and email, and the links on our contact page (LINE, WhatsApp, Telegram, Instagram, X, WeChat, email) send nothing until you press them. After that, the service you open handles what you send there under its own policy.
Each of these services has its own privacy policy. Some of them process data outside your country, including in the United States and Japan.
7. How Long We Keep Data
We keep:
- Account data, reviews, votes and saved places until you delete them, delete your account or ask us to delete it. The automatic translations of a review, and the copy of its text used to make them, are deleted with the review.
- Sign-in codes for 15 minutes; a sign-in on a device for 30 days.
- A sign-in code sent by email is stored only as a hash, next to your email address (the code of a tester account is the exception, section 3). One that is never used stays in our database until your next request for a code replaces it or the account is deleted; we do not remove them on a timer. A sign-in that has ended stays until you sign out or delete your account.
- Search text for 30 days.
- Detailed analytics records for 180 days in our database and 400 days in our raw logs; then they are deleted.
- Hashed IP addresses and browser details on page-request records for 30 days in our database and 400 days in our raw logs. The hashed IP addresses and network hashes on each analytics record are kept with that record, in the raw logs for 400 days.
- Records that link identifiers that probably belong to the same person, for 180 days after they were last seen. The summary kept for each device (its random identifier, technical details, and when it was first and last seen) and the statistics built from them may be kept longer.
- The technical details the app records (phone model, Android version, app version, screen size, language and time zone) stay with the random identifier and may be kept longer, like the browser details above. The map position it records is part of the detailed analytics records and is deleted with them.
- Analytics records waiting to be sent are kept on your phone for at most 24 hours (a short note about a crash, until the next time you open the app). Switching statistics off in the app deletes them.
- The records of what happens to each place (section 3) for 120 days.
- The log of a tester account and the code it signs in with (section 3) until the account is deleted.
- Reports about places and about reviews as long as they help us correct the map and moderate. Deleting your account removes your name from them (section 8).
- The access logs of our servers, which include IP addresses, for a limited time, for security and troubleshooting. Our application's own log records the page requested, the answer and how long it took, but not your IP address or what you searched for; the app's check for a new version leaves one line in it (app version and release channel, no IP address). To limit abuse of sign-in codes, your IP address is also held in our server's memory, not stored, for up to 24 hours.
- Backups of our databases made before a software update, for a limited time.
8. Your Choices and Rights
You can:
- Turn analytics off in this browser: turn analytics off. This sets the
smk_offcookie, and nothing more is recorded from this browser while it is there. Clearing your cookies removes it too. To turn analytics back on: turn analytics on. This does not switch off the counts of what happens to each place (section 3), and we do not respond to "Do Not Track" or Global Privacy Control signals. - Turn analytics off in the app: open the More tab, choose "Privacy & analytics" and switch off "Share anonymous usage statistics" (or answer "No thanks" on the first screen; the same switch is under Profile, Settings, Privacy when you are signed in). The app then stops recording and deletes records still waiting to be sent, and sends nothing about your choice. The same screen lets you copy your random identifier or replace it with a new one. You can switch it back on at any time. The website and the app are switched off separately. The app shows these names in your phone's language; the English ones are quoted here.
- Change your username, make your profile private, and edit or delete your reviews and votes at any time, on the website or in the app.
- Delete your account yourself in the Smok app: open the Profile tab, tap the gear (Settings), choose Delete account… and confirm. There are instructions for people without the app on the account deletion page. Deleting deletes your account at once, with your sign-ins, saved places, votes and reviews (and their translations), the reports others made about your reviews, your email address, the links to Google or LINE and, for a tester account, its activity log and code, and your public profile disappears; so do the records of place activity kept under your account number. The reports you sent, about places or about reviews, stay, with your account removed from them, because we use them to correct the map and to moderate. You can later sign up again with the same email address. Analytics records are not tied to your name or email address and are deleted on the schedule in section 7 (the account number stored with a sign-in event then points to no one). Notifications we have already received (section 6), server logs and text already sent for translation (section 6) are not recalled.
- Ask us for a copy of your data, to correct it, or to delete your account together with everything attached to it — reviews, votes, saved places and sign-ins. This is also the way to delete your account if you use only the website, or no longer have the app. Write to us (section 12), from the email address of your account if it has one; we answer within 30 days.
- Object to how we process your data and, if you are in the EU/EEA, the UK or Japan, complain to your data protection authority.
9. Security
Every connection to Smok, from the website and from the app, is encrypted (HTTPS). Sign-in codes sent by email and sign-in tokens are stored only as hashes, and in our analytics IP addresses are kept only as hashes. The one exception is the code of a tester account (section 3): we keep it as it is so that we can give it to the tester, and it opens only that test account. No system is perfectly secure; if a breach affects your data, we will tell you.
10. Children's Privacy
This website and the app provide information about tobacco smoking. They are not directed at anyone under the legal smoking age (20 in Japan), and accounts are for adults aged 20 and over. In Google Play the app is listed for adults (18 and over), the highest age group the store offers; our own rule is unchanged. We do not knowingly collect any information from minors; if you believe a minor has created an account, tell us and we will delete it.
11. Changes to This Policy
We may update this policy from time to time. The "Last updated" date at the top of this page reflects the most recent revision. Continued use of the website or the app after changes constitutes acceptance of the updated policy.
12. Contact
Questions about this policy and requests about your data can be sent to office@vhc.capital or through any channel on the contact page.