Privacy

1. Who runs J-FOMO

J-FOMO is operated by L Doctor Citizen LLC, a New Mexico limited liability company. Postal address: 1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110, United States. Privacy questions and requests: [email protected].

2. What we collect about you

Accounts are optional. Every part of the calendar works without one. If you choose to sign in, we keep: your email address; the drops you save (each as a small note: the drop's title, its link on this site, the address of its picture, its end date, and when you saved it); the language you chose, if you chose one; and when the account was created. Sign-in is by a link or a six-digit code sent to your email, or with your Google account; there is no password either way, so there is none to lose. If you sign in with Google, Google tells us your email address, your name, the link to your Google profile picture and an identifier for your Google account. We use the email address, as above; the rest is kept with the account because the sign-in system stores it, is not shown or used, and is deleted with the account. This data is stored for us by Supabase, Inc., in a database in the United States (Ohio), and is protected so that each person can read and change only their own rows. We use it to show you what you saved and your trips, and, when that feature launches, your alerts. We do not sell it and do not use it for advertising. We may also email account holders, occasionally, about J-FOMO itself — a new feature, a change to these terms, a paid option when one launches; every such email carries an unsubscribe link, and sign-in emails are the only ones you get by default. You can delete the account and everything in it yourself, from the Profile page, at any time (section 7).

Feature analytics, without identifying you. To learn which parts of the site are used (the calendar or the list, the map's time slider, the language switch, the image gallery, saving), pages send a small number of anonymous events to PostHog, an analytics service, through our own domain (japanfomo.com/ph/). An event carries the page path, the event name (for example gallery_step, site_language or save), your browser type and screen size, and a random identifier held in your browser's session storage for the tab you are reading in. It lasts across clicks within one visit, so that a visit counts once rather than once per page, and your browser discards it when you close the tab — so two visits still cannot be linked, and there is nothing here that can follow you to another site or another day. It is not tied to your account: signing in does not attach your email or your saves to these events. No cookie is set, and the identifier is the only thing analytics writes to your browser; it is listed with the rest in section 3. No session recording, heat-map or replay runs. The site checks your browser's Do Not Track and Global Privacy Control settings and skips the events described here when either is set.

Searches that find nothing — the one exception, and why. What you type in the search box is normally not sent; we record only that a search was made. There is a single exception: if your search matches no drop at all, the words you searched for are sent with the event name search_zero_result. That list is how we find out what the calendar is missing, and it is the most useful thing we collect — if fifty people look for something we do not carry, we should go and carry it. It is still tied to nothing: the same tab-only identifier, no IP, no cookie. A search that does find something is never sent, and a term is only sent when it looks like a search term — we drop anything containing an @ or a web address, anything with a long run of digits, and anything longer than forty characters, so a password or an address typed into the wrong box does not reach us.

What we learn from everyone together. We look at saves and searches in aggregate — which drops are saved most, which searches find nothing, which categories draw attention in which month — to decide what to cover next and to understand demand. We may publish or license such aggregate statistics (for example, "interest in Kyoto collab cafés doubled in October"). They never identify a person, and we never sell or share an individual's account, saves, searches or trips.

Your location, only if you tap "Near me" on the map. The map has a "Near me" button. Tapping it asks your browser for your position, and your browser asks you first; if you allow it, the page uses the position once to move the map there and mark it with a dot. The page does not send it to us, does not include it in analytics, and does not keep it in your browser: the map stops remembering where you were looking (see section 3) for the rest of that visit. To draw that part of the map, your browser then fetches its map tiles from OpenFreeMap (section 4), as it does for any area you look at, so OpenFreeMap sees which area's tiles were requested. Nothing about your location is asked for unless you tap the button.

How fast the page was. Separately, our host runs Cloudflare Web Analytics. A small script served from cloudflareinsights.com measures how quickly the page loaded — the standard speed readings: how soon it first drew, how quickly the main content appeared, and how much the layout moved while loading — and reports them with the page path, your country, and your browser and device type. It sets no cookie, gives you no identifier, and cannot follow you between visits or to other sites. We use it to tell whether the site is slow for real readers rather than only on our own machines. Two honest caveats: Cloudflare adds this script to the page itself, after our code has been published, so it is not part of what we build and the Do Not Track and Global Privacy Control check described above does not reach it. If you would rather it did not run, any tracker-blocking extension stops it.

3. What stays in your browser

A few preferences are kept in your browser's storage so the site remembers how you left it. They are written and read only by your own browser and never leave your device. The last rows are the exceptions and are listed so the list is complete: the analytics identifier travels with the analytics events described in section 2 (random, tied to nothing, gone when you close the tab); the signed-in session is the credential your browser shows Supabase to prove it is you; a save you tapped, or an invite link you followed, before signing in waits in your browser until you are in; and a trip's plan, when you are signed in, is also saved to your account (section 6). Clearing your browser's site data removes them all.

The site also keeps a copy of the pages you have visited and of its own scripts in your browser, so it still opens when your connection drops. That cache holds only J-FOMO's own pages, never images, map tiles or anything from another site, and clearing your browser's site data removes it.

4. Third parties your browser talks to

Loading a web page means your browser makes requests, and each server it asks sees your IP address, the page you asked for and your browser type. That is how the web works and we cannot switch it off. What we can do is keep the list short:

• Our web host (Cloudflare) serves the pages. Like any host it sees the ordinary details of each request. Standard server logs may be kept for security and to operate the service.
• Cloudflare Web Analytics (page speed): the same host also adds a small measurement script to each page, described in section 2. It records how quickly the page loaded, the page path, your country and your browser and device type. No cookie, no identifier, and nothing that follows you elsewhere. Because Cloudflare adds it at delivery rather than it being part of our own code, our own Do Not Track and Global Privacy Control check does not reach it.
• Supabase (accounts and saves) — only if you sign in or save. Your browser talks to Supabase directly to send the sign-in email, to prove who you are, and to read and write your saves. Supabase therefore sees your email address, your IP address and the requests your browser makes. It acts for us under a data-processing agreement and does not use your data for its own purposes. Nothing is sent to Supabase until you use the sign-in form or a save control.
• Google — only if you choose "Continue with Google". Your browser goes to Google to sign in, and Google sees that you are signing in to J-FOMO. Google's own privacy policy covers what it does with that. Nothing is sent to Google unless you press the button.
• Official sources. Images are shown by linking straight to the company, shop, temple or venue that published them, so their server sees that your browser requested the image. We also keep a private working copy of those images in our own archive; it is not served to readers, and section 4 of the Terms of Service explains what it is for.
• PostHog (analytics): receives the anonymous events described in section 2, through our own domain, so your browser does not connect to PostHog directly. The analytics script is part of our own site, not loaded from PostHog.
• The map page only: map tiles come from OpenFreeMap and the map library from the unpkg CDN. Neither is loaded on any other page. The map's tabs for famous attractions, hidden gems, more places and classes show photos, each with its credit. Photos from Wikimedia Commons (Wikipedia's image library) are served from our own site (the same is true on the Trips page); a photo from an organiser's own site is linked from there, so that server sees that your browser requested it.
• Only if you click it: "Add to Google Calendar" on a drop page opens Google Calendar with the drop's title and dates. Nothing is sent unless you click.

Fonts are served from our own site, so no font provider sees your visit.

5. Advertising, affiliate links and payments

J-FOMO may show advertising, labelled "Sponsored", and may use affiliate links, marked as such, through which we earn a commission if you buy at no extra cost to you. Advertising partners may use cookies and similar technologies to show and measure ads. Where the law requires it, you will be asked for consent first, and this notice will name the partners involved. Nothing about your account or your saves is given to an advertiser.

Paid features (not yet live). Some features — trip planning tools, alerts, a pass for a trip or a subscription — may become paid. When they do, payments will be handled by a payment processor (we expect Stripe); your card details go to the processor and never to us, and we keep only what a receipt needs: what you bought, when, for how much, and the processor's reference. This section will name the processor before the first charge is possible.

6. Accounts, saved drops, trips and alerts

Saved drops are described in section 2 and kept until you remove them or delete the account.

Trips. A trip holds where you are going (a city or a prefecture) and your dates, what you said you are into, and the plan you make for each day: the places, drops and classes you put on it, their times and how long you stay. A stop you add yourself holds what you type into it — a name, where it is, which can be an address, a start time and a note — so put in only what you are happy to keep there. Signed out, a trip stays in your browser (section 3); its stops and dates are in the page's address, which the analytics in section 2 does not record. Signed in, the trip is also saved to your account, stored as described in section 2, and only you and the people you invite can read it.

Travelling together. You can invite people to a trip with a link, to plan it with you or only to view it. Anyone who has the link can join once they sign in, until the link expires fourteen days after you made it or you turn it off, so share it only with the people you mean. The people on a trip see the trip, its plan and each other's display name — the name you choose on the trip page — and not each other's email address. You can remove someone from your trip, and anyone can leave a trip they were invited to.

How long trips are kept. A trip is kept until you delete it or delete your account, and an account keeps at most twenty trips of its own. Travel dates say when you are away from home, so delete a trip you no longer need; you can do that at any time under "My trips" on the trip page, and deleting your account deletes them all.

Alerts are not built yet. Alerts will use your email address only to send the alerts you asked for, and every alert email will carry a way to stop them.

7. Your rights and how to use them

• Delete: the Profile page has a "Delete account" control. It removes your account, your email address and every saved drop at once, and it cannot be undone. If you would rather we did it, email [email protected] from the address on the account.
• See or export: your saves are listed on the Profile page. For a copy of everything we hold about you, email the same address; we answer within thirty days.
• Correct: the only thing to correct today is your email address; email us and we will change it. If you signed in with Google, your name and picture come from your Google account; change them there.
• Your browser preferences are yours to clear at any time.
• Residents of the EEA, the UK and Switzerland, and of US states with privacy laws, keep every right those laws give them. Nothing here limits them. Our legal basis for holding account data is that you asked us to, by creating the account; for analytics, our legitimate interest in knowing which parts of the site are used, which is why it is built to identify no one.

8. Children

J-FOMO is not directed at children under 13, and we do not knowingly let anyone under 13 create an account. If you believe a child has, email us and we will delete it.

9. Changes

We may update this notice at any time. The date at the top shows the current version, and a material change will be noted on the site; if you have an account, a material change to how account data is used will be sent to your email. The Terms of Service cover everything else.