Privacy Policy

This policy covers three things: the EveryLaunch website at www.everylaunch.space, the Orbitburn website and browser game at www.orbitburn.space, and the Orbitburn Android app, package com.wyatt.deltav. Both websites keep ordinary server logs and show Google ads, and it measures visits with Google Analytics 4. They record more only when you act: joining the mailing list, signing in on the ad-free page, using the cart, or opening the browser game, which backs its save up under a random account identifier. The app collects an account identifier, your cloud-saved game progress, purchase records, crash reports, usage analytics and an advertising identifier. Each of them is described below, with the company that processes it named. Last updated 10 November 2026.

Scope of this policy

One document covers all three. Google Play requires that the privacy policy URL attached to an app listing actually describe that app, so this page describes the Orbitburn Android app as well as both websites. Where a section applies to only one of them, it says so in the heading or the first line.

The two websites run from one service. www.everylaunch.space is EveryLaunch, and www.orbitburn.space is the Orbitburn home page and the browser game. Other domains we own only redirect to one of those two. This policy covers both, but your browser treats them as two separate sites. Each one keeps its own consent choice and its own browser storage, and neither can read the other’s. A choice you make on one doesn’t carry to the other, and signing in on one doesn’t sign you in on the other.

“We” means the independent developer who publishes Orbitburn and operates this site under the name Cadenic Studios, acting as the data controller for all of them. Neither EveryLaunch nor Orbitburn is affiliated with, endorsed by, or operated by NASA, SpaceX, ESA, or any other agency or launch operator whose public data appears on this site.

This policy does not cover third-party websites you reach from links here. Once you leave, that operator’s policy governs, not this one.

What the websites collect

This section applies to both www.everylaunch.space and www.orbitburn.space, except where it names one of them.

Server logs

Every request to a web server produces a log line. Vercel, the host, records your IP address, the page requested, the time, the referring page, and your browser’s user agent string. Those logs exist to keep the site up and to investigate abuse, errors and traffic spikes. They are held for a short period by the host and then discarded. They are not used to build a profile of you, and they are not combined with anything else on this page.

Website analytics

Both websites use Google Analytics 4, provided by Google, to measure which pages are visited and where visitors came from. It sets two first-party cookies, _ga and _ga_<id>, holding a random identifier for your browser and your current session. Shop pages also report products viewed, added to or removed from a cart, and checkouts begun, with the product name, variant, price and quantity, and the play page reports that the browser game was started. Google also receives your IP address and browser details with each request, which is how it derives an approximate location and device type. Your name, your email address, your cart identifier and your payment details are not sent to it by this site.

We estimate your region from your device’s time zone. Where that points to the EEA, the UK or Switzerland, or tells us nothing about your location, analytics does not load until you accept. Everywhere else it loads on arrival, and the cookie settings control turns it off. Google’s handling of this data is described in its partner-sites notice.

The mailing list

Only if you submit the signup form do we store the email address you typed and send it through Resend, which delivers the message and holds the list. The address is used for dispatches about the game and the site. It is not sold. To leave the list, use the unsubscribe link in any email: the address stays on the list marked as unsubscribed, which is what stops it being mailed again. To have the record deleted as well, ask through the Contact section.

The signup endpoint also keeps a short-lived rate-limit record (your IP address, the email address you entered and a timestamp, held in memory for sixty seconds) so one visitor cannot flood the form. It is never written to disk.

Advertising on the website

Advertising on both websites is served by Google AdSense, and it is switched on only when a publisher account is configured. Until then no ad script loads and no advertising cookie is set. When it is on, Google may set cookies and read device identifiers to select and measure ads. What is set, and how to refuse it, is spelled out in the Cookie Notice. You can also control personalisation directly at Google Ad Settings.

Signing in on the ad-free page

The websites have one optional account feature: signing in with Google on the ad-free page. There is one on each domain, www.everylaunch.space/ad-free and www.orbitburn.space/ad-free. Google gives Firebase your name, email address and avatar, and Firebase Authentication creates an account record in the game’s project if that Google account does not already have one. The page then reads your cloud save and keeps your email, name, account identifier and the ad-free result in your browser so a return visit needs no network.

That sign-in, and what it stores, belong to the domain you signed in on. Signing in on www.everylaunch.space affects ads on www.everylaunch.space only. Signing in on www.orbitburn.space affects ads on www.orbitburn.space only, and on that domain the session is shared with the browser game, as described below. The Orbitburn Android app is separate from both and manages its own ads.

Depot orders

The depot is on www.everylaunch.space. Product pages are rendered by our own servers, but the checkout is not. Adding to a cart creates a cart at Shopify and stores its identifier in your browser, and our server passes that identifier back to Shopify to read the cart. Pressing checkout hands you to Shopify’s hosted checkout, where Shopify and its payment processors collect the name, shipping address, email address and payment details needed to fulfil the order. Card numbers never reach us and are never stored on our systems. Shopify processes that order data under its own privacy policy, and we see what the store needs in order to fulfil the order and answer questions about it.

Your position on the live page

The observer panel on the live page of www.everylaunch.space can use your browser’s location, only after you press its button and your browser asks you. Our code keeps the coordinates in that tab and does not send or store them. Other scripts running on that page, such as an ad script, are not code we control.

What the websites do not do

• They set no cookie of their own for visitors other than the analytics cookies above. The one optional sign-in is kept in browser storage rather than a cookie.
• They run no analytics product other than Google Analytics 4, and no pixel from a social network.
• Our code does not fingerprint your browser. Google’s advertising and analytics services work across sites under Google’s own policies, within the choices described in the Cookie Notice.

Paid links and images from other hosts

Some outbound links on the site are paid links. Book and gear links go to Amazon through the Amazon Associates Program, and partner links go to advertisers through the CJ Affiliate network. These links load nothing from Amazon, CJ or the advertiser on our pages. If you click one, you go through a tracked address that tells that operator the click came from this site, including the page you were on, and we may earn a commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases.

Third parties, including Amazon and other advertisers, may serve content and advertisements, collect information directly from visitors, and place or recognize cookies on visitors’ browsers. After a click, that happens under their own policies: Amazon’s privacy notice, Amazon’s advertising preferences and CJ’s privacy policy. These operators are independent companies rather than processors acting for us, which is why they are listed here and not under Third-party processors.

Some images are loaded directly from the servers that publish them, including The Space Devs’ image storage, NASA and Wikimedia Commons. Your browser contacts that host to fetch the image, which gives it your IP address and the usual request details, and the host can set its own cookies. These images are not held back by the consent request.

What the Orbitburn browser game does

The game on the play page at www.orbitburn.space asks you for no account, but it is not offline. Nothing of it loads until you press LAUNCH or FULLSCREEN. It then signs in anonymously to Firebase, which creates a random account identifier that the browser keeps in IndexedDB. It keeps your save in this browser, and it also backs that save up to Cloud Firestore under that identifier and merges in whatever is already there. When you beat your best on a level, it submits a public leaderboard entry, as described in Public leaderboards, under the name “Pilot” unless you have chosen another. It runs no in-game ads today, and it does not load Firebase Analytics or Crashlytics.

The game shares one browser session with the ad-free page on www.orbitburn.space, because they are on the same domain. If you have signed in with Google there and then open the game in the same browser, it uses that Google account, and your browser save is merged with that account’s cloud save in both directions. The game does not see a sign-in made on www.everylaunch.space.

What the Orbitburn Android app collects

The app does more than the website does, because a game with cloud saves, purchases and leaderboards cannot work otherwise. Everything it collects is listed here.

• Account identity: Firebase Authentication. On first launch the app signs in anonymously, which produces a random user identifier (a UID) and nothing more. If you choose to sign in with Google, it gives the app account your name, email address and avatar URL so progress can follow you to another device. Signing in is optional.
• Cloud-saved progress: Cloud Firestore. Level completions, star ratings, best times, currency balances, unlocked parts and one-time purchases are written to a document keyed to your UID. Subscription status is deliberately left out of it. Security rules restrict that document to the owning account: it is not publicly readable.
• Purchases: Google Play Billing and RevenueCat. Product identifiers, purchase and expiry timestamps, receipt data and entitlement status are recorded against an app user identifier derived from your UID. Payment itself is processed by Google Play; card numbers, billing addresses and bank details never reach the developer.
• Crash diagnostics: Firebase Crashlytics. When the app crashes it sends a stack trace, the device model, the OS and app version, a Crashlytics installation identifier, your UID, and a short breadcrumb trail of what the game was doing beforehand. This is how a bug that only reproduces on one chipset ever gets fixed.
• Usage analytics: Firebase Analytics. Gameplay and store events: app opens, level starts, completions, failures and retries, store views, purchases and purchase attempts, rewarded ads watched and daily rewards claimed. They carry the app instance identifier Google attaches and your UID as the analytics user identifier. Google also derives an approximate country and device class from the request. There is no keystroke logging and no screen recording.
• Advertising: Google AdMob. Ad requests carry your device’s advertising identifier plus standard request data (app version, coarse locale, device type) so an ad can be selected, rendered, capped and measured. See Advertising and consent.
• Integrity check: Firebase App Check. The app requests a Play Integrity attestation token and attaches it to its Firebase requests. The token describes the app and the device’s integrity verdict, not you.

Device permissions

The app itself declares two Android permissions: internet access, and billing. The Google Mobile Ads SDK adds the advertising-identifier and ad-services permissions when the app is built, and other bundled SDKs can add routine ones such as network state. It requests no access to location, camera, microphone, contacts, call logs, SMS or your photo library, and it cannot read files outside its own storage.

Public leaderboards and display names

Leaderboards are public by design, in the app and the browser game, and this is the only place where anything you provide becomes visible to other people. When a score is submitted, the entry holds your display name (twenty characters maximum), the star rating, the completion time, the level, the app version, the submission timestamp, your account identifier and a session identifier. If you choose a display name, it and the time you set it are also held on a public profile record under that identifier. Anyone can read them.

Pick a handle rather than your legal name. You can change your display name from the leaderboard screen, and you can ask for your entries to be removed entirely using the request route in Your rights.

Advertising and consent

Google AdMob serves the ads inside the Orbitburn app. Before the first ad request, the app runs Google’s User Messaging Platform (UMP) consent flow. Where consent is legally required (the EEA, the UK, and anywhere else Google’s consent policy applies), the UMP form is presented and no personalised ad request is made until you have answered it. Your answer is stored by the UMP SDK on your device.

You can change that answer at any time: open Settings → AD PRIVACY SETTINGS in the app. The control appears wherever Google actually provides a form, which in practice means EEA and UK users; elsewhere there is no consent form to reopen. Choosing non-personalised ads does not remove ads. An ad request is still made, and it carries less about you.

Ad placement is deliberately narrow. Banners appear on menu screens, and rewarded video is opt-in: it plays only when you tap a control that offers something in exchange. The app does not interrupt a run with a forced full-screen ad.

How Google uses data from apps and sites that use its services is described in Google’s partner-sites notice.

Third-party processors

These are the companies that handle personal data on our behalf for EveryLaunch and Orbitburn, what each one does with it, and where their own policy lives. Independent operators you reach through a link or an image are covered under Paid links and images.

• Google LLC: Firebase Authentication and Cloud Firestore for the app, the browser game and website sign-in; Firebase Analytics, Crashlytics and App Check in the app; Google Play Billing for purchases; AdMob for in-app ads; AdSense for website ads; Google Analytics 4 for website measurement. Privacy policy
• RevenueCat, Inc.: Records which in-app products an account owns, so entitlements survive a reinstall or a new device. Privacy policy
• Shopify Inc.: Holds the cart, and runs the hosted checkout, payment processing and order records for anything bought from the depot. Privacy policy
• Resend: Delivers mailing-list and transactional email. Holds the address you submitted and the delivery result. Privacy policy
• Vercel Inc.: Hosts and serves both websites, and generates the request logs described above. Privacy policy

Data is shared with a processor so it can perform the function listed. We are not paid for personal data. EveryLaunch and Orbitburn do earn money from advertising and from commission on paid links, as the sections above describe.

Children

EveryLaunch and Orbitburn are not directed at children under 13, or under the higher minimum age that applies where you live. The app is not enrolled in a children’s programme, it is not COPPA-certified, and no claim of certification is made here. Ad requests are made without the under-age-of-consent flag set, which is another way of saying the app is built for a general audience.

We do not knowingly collect personal data from a child under 13. If you are a parent or guardian and believe a child has provided data, such as a real name on a leaderboard or an email address on the mailing list, ask through the Contact section and it will be deleted.

Your rights and how to exercise them

Depending on where you live, you have some or all of these rights: to know what data is held about you, to get a copy of it, to correct it, to have it deleted, to restrict or object to how it is used, and to withdraw consent you previously gave. You do not need a lawyer to use them, and exercising them costs nothing.

To make a request, use the route in the Contact section. If you signed in with Google, say which address; if you played anonymously, include your in-game display name and roughly when you started playing, so the right account can be found.

A deletion request removes your cloud save, your leaderboard entries and your stored display name, and asks the relevant processors to delete the analytics and crash identifiers tied to your installation where their tooling allows. It cannot undo a purchase. Google Play holds those records under its own retention rules, and a refund is a Play Store matter. Uninstalling the app removes the local copy of your progress but not the cloud copy; ask for deletion if you want both gone.

If you are in the EEA, the UK or Switzerland, the legal bases used are: performance of a contract (cloud saves, purchases and order fulfilment), legitimate interests (security, abuse prevention, crash diagnostics), and consent (personalised advertising, website analytics and the mailing list). You may also complain to your national supervisory authority. If you are in California, we do not sell personal information for money. The personalised advertising described above may count as “sharing” under the CCPA, and you can turn it off with the cookie settings control on each website and AD PRIVACY SETTINGS in the app. You will never be treated differently for exercising a privacy right.

How long data is kept

• Cloud saves and leaderboard entries are kept while the account exists, and are deleted when you ask.
• Server logs are kept briefly by the host for operational and security purposes, then rotated out.
• Website analytics follow the retention period configured in Google Analytics. The _ga cookies last up to two years in your browser unless you reject analytics or clear them.
• Crash reports are retained by Firebase Crashlytics for a limited window set by Google, currently 90 days for the detailed report.
• App analytics events follow the retention period configured in Firebase; aggregate counts may persist after the underlying events expire, but they no longer identify a device.
• Mailing-list addresses are kept until you ask for removal. An unsubscribed address is kept, marked as unsubscribed, until then.
• Order records are kept by Shopify for as long as tax and consumer-protection law requires.

International transfers

Every processor named above is based in, or operates infrastructure in, the United States, so using EveryLaunch or Orbitburn means your data crosses a border. If you are in the EEA, the UK or Switzerland, those transfers rely on the safeguards each processor publishes: Standard Contractual Clauses, the EU-US Data Privacy Framework, or both, as set out in their policies. No additional transfer happens beyond what running the service requires.

Security

Traffic to both websites and to the game backend is encrypted in transit. Cloud saves are protected by Firestore security rules that allow a document to be read or written only by the account that owns it, and writes are shape-checked so a modified client cannot smuggle extra fields in. Payment credentials are handled entirely by Google Play and Shopify and never touch our infrastructure.

None of that makes a system perfectly secure. If you find a vulnerability, please report it through the Contact section rather than demonstrating it on other players.

Changes to this policy

This policy changes when the product does, for example with a new processor, a new data type or a removed feature. The revision date in the rail at the top of this page is the date of the current version. For a change that materially affects how your data is used, notice will be given in the app or on the site before it takes effect. Continuing to use EveryLaunch or Orbitburn after that means the current version applies.

Common questions

Contact

A contact address for privacy requests has not been published yet. It will appear here as soon as it is. For anything about a depot order, use the order confirmation email from Shopify. For a purchase in the app, Google Play handles billing and refunds.

This policy sits alongside the Terms of Use and the Cookie Notice.