Privacy Policy

Last updated November 4, 2026

The short version: Ovenlight and ovenlight.app have no ads, tracking or analytics code, and no server of ours carries your apps or their data, except what an app's owner sends through Pilot Light, sealed so only the phones it's meant for can open it (or, for a starter copy, anyone holding its invite link). The only other things that reach us are emails you choose to send, what Apple passes on (such as crash reports and test feedback), your phone's own requests to Pilot Light's relay, and the ordinary request when a page on ovenlight.app loads, when you download the connector, or when the connector checks for and downloads its updates.

Who we are

Ovenlight is an app for iPhone made by Snowy Ghost LLC ("we," "our," or "us") for opening web apps that you, or friends who invited you, run on your own computers. This policy explains what happens to your information when you use it.

Data we collect

We never see the apps you open or what you do in them, and we build no profile of you. The only things that reach us are emails you choose to send (such as a problem report), what Apple shares with us (see Apple), what an app's owner sends through our relay if they have Pilot Light, and your phone's own requests to it (see Pilot Light), and the ordinary web request when a page on ovenlight.app loads, such as an invite page (see Invite links), when you download the connector, or when the connector, on the computer it runs on, checks for a newer version (once a day, again within the hour after a check fails, when it first starts on a newly installed release or on the one an update went back to, and just before it downloads or installs one) and downloads one. An older connector's ovenlight doctor checks too. Like any web request, each carries the computer's IP address. An update's download also shows which system the computer runs (macOS, Linux or Windows), on Linux and Windows its processor type, and the version it installs, since they're in its address. Nothing else about you, the computer's owner or their apps is sent. Cloudflare carries these requests and emails for us (see Who handles it for us).

On your phone

Ovenlight keeps its list of apps, your settings, and each app's own storage (such as cookies and saved data) on your phone, with each app's storage kept separate from the others. From version 1.1.0, for apps that keep one, it also keeps a read-only copy of the app's pages (those you opened, or for an invite, its start page), so an app can still open while its computer is asleep. A copy stays out of your iPhone's backups, and it's deleted with its app, when you clear the app's data, or after 30 days without a new one. Face ID, Touch ID or your passcode unlocks Ovenlight. Your phone handles that, and Ovenlight never receives your face, your fingerprint or what you enter to unlock your phone. The keys that connect your phone to other computers are left out of your phone's backups, so they can't be restored onto another device. Ovenlight also keeps a key for each app whose computer runs Ovenlight's connector, so that if its owner has Pilot Light, their computer can seal notifications and copies that only your phone can open. From version 1.1.0, when you share a link or text to Ovenlight from another app, it waits on your phone until you choose an app for it. It stays out of your iPhone's backups and can't be read while your iPhone is locked. A new share replaces it. Sent or not, it's deleted when you close the screen where you choose an app for it, or the next time you open Ovenlight a day or more after you shared it.

Camera, microphone, photos and local network

Ovenlight itself uses the camera only to scan invite QR codes, which it reads on your phone. Apps you open can also use the camera or microphone, for example to record a spoken answer. Your phone asks you before Ovenlight can use either one. After that, an app still asks you before it uses the camera, and an app someone shared with you also asks before it uses the microphone. Apps on your own computers can use the microphone without asking again. What an app records goes where the app sends it, usually to the computer that runs it. While Ovenlight is locked, no app can use the camera or microphone, and locking cuts off any camera or microphone an app is already using.

iOS asks for your permission the first time you save an image from an app to your photo library. Ovenlight can add photos to your library but can't see it. Local network access lets Ovenlight find a faster, direct path to a computer on the same network as you.

The computers you connect to

When you open an app, your phone connects to the computer that runs it over an encrypted connection: directly when possible, otherwise through Tailscale's relays, which pass the traffic along but can't read it. That computer belongs to you or to the person who invited you, and it can see what you do in their app, as with any website. You can add only apps that run on your own computers, and a link in an app to any other website opens in your browser, outside this private connection. An app's pages can also load content from other websites, as any web page can, and those sites see your IP address. Feedback you send from inside an app goes to its owner's computer, where the owner and tools they run there can read it. It includes the page's address, any note you add, and a screenshot unless you leave it out. What you share into an app from another app goes only to that app's computer, and only after you choose the app. Whoever runs the app can read it. Before it goes to an app someone shared with you, Ovenlight asks you.

What the person who invited you sees

An invite carries the name its sender gave you. If you join from a group invite, you type your own name instead, and their computer and apps get it. Your phone joins their network under a random device name, so they can't tell which of your devices it is. They see that you joined, which of their apps you can open, the day you last opened each one, and anything you send them as feedback. Their computer's log also records each page and request your phone makes to their apps, with your name, the time and the address up to any question mark. Their computer also keeps your phone's key for each of their apps and, if they have Pilot Light, your phone's push address and, for each of their apps, a code the relay checks before it lets that app's messages through, so Ovenlight can notify you about their apps as your phone's settings allow and your phone can get fresh copies. It also keeps whether your phone takes notifications about each of their apps, as Ovenlight last told it. For a week, it also keeps how many times a day your phone opened one of their apps while it couldn't reach their computer and had no copy or only one over a day old, and how long your invite waited for their computer to accept it. If they let guests keep a copy of an app, their computer also keeps the pages you open in it, with their full addresses and what they showed you, until 30 days after you last open the app. The page where they manage their network also shows basic details, such as your IP address, what kind of phone you use and its iOS version, and when Ovenlight was last connected. They can also move your phone to another person, as when you opened an invite meant for someone else. Their apps then see you as that person. They can stop sharing at any time. When they do, the next time Ovenlight connects, it removes their apps and everything those apps stored on your phone.

The plugin for Claude Code

An app's owner can build, publish and check their apps with Ovenlight's plugin for Claude Code. The plugin runs the connector on the owner's own computer and sends us nothing. What the connector gives the owner's coding agent can include their apps' status and output, and the feedback you send them, with your name, the address of the page you sent it from, and any screenshot. That goes to the AI company behind the agent (Anthropic, for Claude Code), which handles it under its own terms. The same goes for any other coding agent the owner uses with the connector.

Tailscale

Ovenlight uses Tailscale's networking software to make private, encrypted connections. If you sign in to your own computers, you sign in with your Tailscale account, on Tailscale's own sign-in page. Signing out deletes that connection from your phone. If you join from an invite, your phone joins the inviting person's private network. Tailscale's service helps devices find each other and sees basic device information, such as a device name, IP address and how well its connection works (such as its delay to Tailscale's relays), but not the content of your apps. Tailscale's terms let it use this information only to run, develop and protect its service, and protect it as this policy does. If an invite uses a server the inviting person chose instead of Tailscale's, Ovenlight tells you before you join, and that server plays Tailscale's part.

Tailscale's software normally sends diagnostic logs to Tailscale. Ovenlight turns that off, so the app sends no logs to Tailscale from your phone. The connector that an app's owner runs on their own computer keeps Tailscale's usual setting and sends its diagnostic logs to Tailscale, as Tailscale's own app does. See Tailscale's privacy policy.

Pilot Light

Pilot Light is an optional subscription for people who share apps from their own computers. When the owner of an app you use has it, their computer sends some things through our relay, a service we run on Cloudflare: notifications about their apps, the alert that tells them their computer can't be reached, and copies of their apps kept for when the computer is asleep. Each is sealed on the owner's computer so that only the phones it's meant for can open it. A starter copy opens with the key in its invite link. We can't read any of it, and neither can Apple or Cloudflare.

Notifications. A notification goes from the owner's computer through the relay to Apple's push service, and then to your iPhone. We see your iPhone's push address, when each message was sent and its size, never its words or which app it's from. A computer's notifications reach at most 15 phones, so for that count the relay keeps a scrambled form of each push address it reaches, not the address itself, until 30 days after the last notification sent to it or the last check-in carrying an alert for it.

Which apps can reach your iPhone. The relay sends to your iPhone only for the apps it allows. Every iPhone that uses an app whose owner has Pilot Light, a guest's too, sends its push address to the relay, as does an iPhone whose own purchase sends it a test notification. It sends it again whenever its set of apps changes, and at least every 300 days while you use Ovenlight. An iPhone with neither never sends it. For each push address, the relay keeps a scrambled form of it, a scrambled form of a secret your iPhone made, a counter, a scrambled code for each app your iPhone allows, when it last checked that your iPhone holds the address and how many times it did that day, and the day the address was last used. Nothing in it names an app or a computer, and it can't be matched to another phone's. It's deleted when the push address stops working, when your iPhone tells the relay to forget it (as when its push address changes), or 400 days after it was last used. If your iPhone never answers that check, the relay keeps only its time and count, until the end of that day (UTC). Since it names no one, we can't find it from an email request, so it's deleted only in those ways.

The alert. To warn the owner when their computer stops answering, the relay keeps the time the computer last checked in and the alert it sealed in advance for the owner's phones, with their push addresses, a scrambled code for each, and the purchase it belongs to, and, while it holds the alert for the owner's quiet hours or a restart, the time the hold ends. It deletes them as soon as the alert is sent, after a day of failed tries to send it, if the subscription has ended by the time the alert is due, or when a check-in carries no alert, as when the owner turns it off. It also deletes them when the connector ends the watch while the computer is online: when the connector is uninstalled, when an update fails and goes back to the release before it, and when the connector stops or restarts while the alert isn't wanted. A check-in with no alert leaves only the time of the last one that carried an alert, deleted 30 days later. A sent alert leaves only the time it was sent, so the computer can send the owner an all-clear once it's back, and that time is deleted once the computer is back, or 30 days later. Ending the watch also leaves the time it ended, deleted ten minutes later. The alert and the all-clear that follows it carry a random ID for the computer, which Apple sees too, so a phone can put one in the other's place.

Copies kept for your people. The owner's computer also leaves copies of their apps with us, sealed so only the phones of the people each copy is for can open them. A personal invite sent while the subscription is active, to an app that keeps copies, also leaves a starter copy that only its link opens. We see each copy's size and when it changes, never what's in it. When a copy changes, the relay may wake your iPhone so it fetches the new one. So it doesn't wake it too often, or more for one subscription than for another, it keeps a scrambled form of its push address for an hour after each wake and a short scrambled form of each subscription whose computers ask to wake it, until 2 hours after they last ask. Your iPhone fetches copies over the public internet, so we see its IP address as it connects (see below). If an invite's link shows its sender keeps a starter copy, an iPhone that opens it while their computer can't be reached asks us for that copy. While the subscription is active, a copy is deleted when its person's access ends, leaving a sealed note of that for 30 days so their phones remove it too. If their access ends after the subscription has ended, the copy is deleted no later than the rest of the computer's copies. Once a starter copy's invite is used, canceled or expires, the computer replaces it with an empty one the next time it reaches us while the subscription is active, so the starter copy stays until then. Either is deleted at the latest 30 days and an hour after the invite expires, or 92 days after the link was made if that comes first. If the rest of the computer's copies go sooner, a starter copy's contents go with them, but its name stays reserved for that computer, with nothing in it, until that date, so no one else can put a copy there. All of a computer's copies are deleted 30 days (and up to an hour) after it last sends us copies, or the list of copies it keeps, while its subscription is active.

The subscription. Apple handles payment. The owner's iPhone hands the App Store's signed record of the purchase to their computers, which show it to the relay. When the iPhone has no purchase of its own, it shares one a computer already holds with the owner's other computers. To learn of renewals and refunds, the relay asks the store that sold the subscription for its status and keeps the answer, with Apple's newest signed record for an App Store purchase, a random ID for each of the owner's computers, and counts of what they send per minute and per day. The store also tells the relay when a subscription changes, as with a refund, and the relay keeps when it last did. It deletes all of this 30 days, and up to an hour, after the subscription ends or a computer last used it, whichever is later. When no later request tells the relay of a refund, the deletion comes 30 days after the paid period would have ended. For 15 minutes, or until the next check-in after that, it also keeps a short scrambled form of each purchase whose computers checked in, to tell its own outages from quiet computers. Once the owner's iPhone has a push address after buying or restoring a purchase, it sends itself a test notification through the relay.

We see the IP address of every computer and phone that reaches the relay, as any server does. The relay uses it only to limit how many calls one network can make, and doesn't store it. Cloudflare's record of each request does, for about a month (see Keeping and deleting your information). The relay's own logs hold counts and, for each notice a store sends it, the store and the kind of notice. They never hold push addresses, records or contents.

Apple

If you install Ovenlight through TestFlight or the App Store, Apple may share crash reports and any feedback you choose to send, under Apple's own privacy policy. The App Store shows us statistics such as installs and sessions from people who choose to share them with developers. TestFlight also shows us how often you install and open Ovenlight and, if we invited you by email, your name and email address. We use all of this only to fix and improve Ovenlight.

Reporting and leaving

You can report a problem with any app from its menu. That opens an email to us, filled in with the app's name and address, who shared it, how its connection is doing, your Ovenlight version, and your phone's iOS version. You can edit it first, and nothing is sent until you send it. You can leave apps someone shared with you at any time. Leaving removes their apps and data the same way. Your phone can stay on their network until their computer hears that you left, for 30 days at most. Until then, they can see it online with its IP address while Ovenlight runs. The person who shared still sees you listed until they remove you.

Opening an invite link without Ovenlight installed loads a page on ovenlight.app, which, like any website, receives your IP address and browser details when it loads. The invite itself stays in your browser and is never sent to us.

Keeping and deleting your information

We keep emails you send us, and what Apple shares with us, for as long as we need them to help you or to fix and improve Ovenlight, and we delete them when you ask. Cloudflare keeps a record of each request to ovenlight.app, including the connector's downloads and update checks, and to Pilot Light's relay, for about a month: its IP address, what it asked for, the browser or program that sent it and its country. We read it only to count visits, downloads, update checks and relay traffic, and we keep only those counts. Deleting Ovenlight removes everything it keeps on your phone except the keys it keeps for notifications and copies (see On your phone). iOS keeps those until Ovenlight is installed again, and its first launch deletes the ones it no longer needs. What Pilot Light's relay keeps, and when it's deleted, is under Pilot Light.

Who handles it for us

Cloudflare runs ovenlight.app and the connector downloads, runs Pilot Light's relay and stores its sealed copies, and forwards email sent to team@snowyghost.com to our Gmail mailbox. Cloudflare handles that information only to provide its services to us, under terms that protect it as this policy does. Google keeps our mailbox under its own privacy policy, and Apple (including its push service) and Tailscale handle what this policy describes under theirs. We're in the United States, as are Cloudflare and Google. Both are certified under the EU-U.S. Data Privacy Framework, which the European Commission has found adequate. We don't sell your information or share it with anyone else, unless the law requires us to.

Your rights

You can ask for a copy of what we hold about you, or ask us to correct it, delete it or limit how we use it, by emailing team@snowyghost.com. Where a law such as the GDPR applies, our legal basis is our legitimate interest in answering your emails, fixing and improving Ovenlight, running ovenlight.app and the downloads, providing Pilot Light to those who subscribe, and delivering what they send to the people they share with. You can object to that at any time. You can also complain to your data protection authority. What an app's owner keeps about you on their own computer, such as the record that you joined, when you last opened their apps, any feedback you sent, and any copy they keep of the pages you opened, is in their hands: ask them to delete it.

Children

Ovenlight is not directed to children under 13. If you think a child under 13 has sent us personal information, email us and we'll delete it.

Changes to this policy

If this policy changes, the updated version will be posted here with the date above revised.

Contact

Questions? Email team@snowyghost.com and a human will reply.