Nishimoto Works, Inc.("we", "us") operates LaunchSync (the "Service"). This policy explains what we collect and why.
1. No account, no personal identifiers
The Service does not require an account. We do not collect your name, email address, phone number, postal address, or precise location.
2. What we collect
- Anonymous ID — a random identifier generated per browser. Contains no personal information. Why: to recognize repeat visits so we can improve the app.
- Usage — screens viewed, actions taken (selecting a mission, syncing, arming effects), time spent. Why: to understand which features are used and where people drop off.
- Device — browser, OS, screen size, language, referrer, country of access (country code only). Why: to find and fix display problems.
- Error reports — technical details when something goes wrong (the error message, where in our code it occurred, the page it happened on, and the response code if a request failed). This includes cases where the app recovers and keeps running. Why: to detect and fix problems.
- Session recordings (limited period) — a replay of on-screen interactions; see section 7. Why: to find where the interface confuses people.
3. What we do not collect
- Name, email address, phone number, postal address
- Precise location (GPS)
- Photos, contacts, or any other data on your device
- Payment information (the Service is free during beta; there is no payment function)
4. How we use it
Only to improve the Service, diagnose problems, and understand usage in aggregate. We do not use it for advertising. We do not sell it or share it with third parties for their own purposes.
5. Third-party services
- PostHog (PostHog, Inc.) — analytics and session recording. Data location: PostHog Cloud EU (Frankfurt, Germany).
- Vercel (Vercel, Inc.) — hosting, including access logs. Data location: United States and others.
- Gemini API (Google LLC) — generating transmissions and briefings; see section 6. Data location: United States and others.
- Launch Library 2 (The Space Devs) — launch data. We fetch from it; no user data is sent.
6. What we send to the AI
We send nothing about you.
What we send is public launch data only: mission name, launch provider, vehicle, launch site, scheduled time, target orbit, and payload description. Your anonymous ID, your usage data, and your device data are never sent.
We use the Gemini API on a paid plan, under which prompts and responses are not used to train Google's models.
7. Session recordings
To find where the interface confuses people, we may record on-screen interactions in a form that can be replayed. This is limited:
- Limited period. Only for a short window after beta launch. We stop once we have what we need.
- Limited scope. Recording starts when you open the app and stops once you complete sync setup (or at T-10 minutes). Nothing after that is recorded.
- Input fields are masked. (The Service has almost no text input in any case.)
- Recordings contain no information that identifies you personally.
8. Data stored on your device
The Service stores the following in your browser. All of it stays on your device and is never sent to our servers (apart from the analytics described in section 2).
- To restore your transmission log — the messages shown on screen. Deleted after 24 hours, and limited to the last 8 missions and 40 lines per mission. It contains nothing you typed — only text the Service generated and displayed.
- To detect delays — the scheduled time and status of the launch you last viewed (a single entry, replaced when you view a different launch).
- To avoid repeating a prompt— a record that you dismissed the "add to home screen" prompt.
- To keep your language — the display language you selected, if you switched it.
- To fit the opening sequence to you — a record that you have seen the opening sequence at least once (used only to show the skip control from the second time onward).
- For analytics — your anonymous ID and a record of the launches you have observed (sections 2 and 4).
Notes:
- The mission you currently have selected, and whether the opening sequence has already played in this tab, are held in an area that clears when you close the tab (
sessionStorage). - Your clock offset and whether effects are armed are not stored. They reset to their defaults (offset +0.0s, effects off) when you reload.
You can clear all of this from your browser settings (clear site data). Doing so issues a new anonymous ID and disconnects you from any earlier record.
9. Cookies
The Service does not use cookies.Analytics uses your browser's local storage instead.
10. External links
The Service links to external sites such as broadcast pages. We are not responsible for how those sites handle your information. Please review their own privacy policies.
11. Retention
Analytics data is kept for one year and then deleted. Session recordings (section 7) are deleted once their purpose is served.
12. Opting out
If you would rather not send analytics data, enable your browser's "Do Not Track" setting, or contact us at contact@launchsync.space.
13. Changes
We will post any changes on this page. If a change is significant, we will say so in the app.
14. Contact
Nishimoto Works, Inc. / contact@launchsync.space
Effective: August 13, 2026