Portlight ("the App", "we", "us") is a developer tool that serves folders of files as websites, from your iPhone or iPad, to your own browsers and, if you allow it, to devices on your local network. This policy explains what information the App handles, where it is stored, and the choices you have.
We designed Portlight to be private by default: your sites are files in your iCloud Drive or on your device, and we do not run a server that receives them.
At a glance
- We do not operate a server that stores or processes your sites, your files, or anything you type. Your sites, if they're in iCloud Drive, and your settings sync through your own iCloud account, and your Git accounts and the assistant's API keys through iCloud Keychain, if it's on.
- The App has no user accounts to create or maintain: there is nothing to sign in to.
- There are no analytics, no telemetry, and no crash-reporting SDKs. The App sends us nothing, ever: not on first launch, not when it crashes, and there is no update check.
- We do not sell, rent, or share your data, and there is no advertising or tracking.
- The App's network traffic is the pages it serves: to the browsers of your device, and to devices on your local network if you turn on Allow Other Devices. Beyond that, there is iCloud, which syncs your sites if they're in iCloud Drive, your settings, and your Git accounts and API keys if iCloud Keychain is on; the Git servers you add, if you use Git; the AI provider you choose, if you use the assistant, and the web addresses it downloads files from, each one you allow; and whatever your own pages load from the internet.
- The assistant is off until you choose a provider for it. Then what you ask it, and the files of your site it reads to answer, go straight from your device to that provider, such as Anthropic or OpenAI, or to your own Ollama or LM Studio, with your own API key and under the provider's terms. They never pass through us.
Who this policy covers
This policy applies to the Portlight app for iOS and iPadOS distributed through the Apple App Store and TestFlight.
Information the App handles
Everything the App holds is content you created, imported, or chose:
- Your sites. The folders and files in Portlight's folder: the pages, stylesheets, scripts, images, and other files you write, import from Files, or add from Photos, and the JSON, Markdown, and text files your pages save.
- Settings. The port, whether other devices are allowed, the access key and whether it is required, whether pages can save data files, folder listings, live reload, keeping the screen awake, keeping serving in the background, the editor's theme, line numbers, code folding, code completion, bracket closing, tag closing and renaming, and text size, where the Console and Edit Files open on iPad, the appearance, the language, and the name and email address your Git commits carry.
- The request log. For each request the server answers: its time, method, path, status, size, and duration, and the network address of the device that sent it. It is kept in memory only, up to the last 500 requests, until you clear it or the App quits. It is never written to a file or sent anywhere.
- The console. What the page on screen in the preview logs, and the JavaScript you run in it, kept in memory only while that preview is open. The last 100 commands you ran are also kept on the device, with the settings, so that ↑ and ↓ can bring them back after the App quits.
- Unsaved editor changes. If changes typed in the editor cannot be saved before the editor goes away, for example because the file changed elsewhere while Portlight was in the background or because its window closed, the App keeps the text on the device, in its own storage rather than in your iCloud Drive. It comes back as unsaved changes the next time that file opens, for you to save or discard.
- Git, for the sites you use it with. Each one's history: its commits, with their files, messages, the names and email addresses of their authors, and their dates; its branches; its tags, with the message, name and email address an annotated tag carries; and the address of its server. A site using Git also holds a small hidden file,
.portlight-git, naming its repository, its server and its branch, so the link travels with the site. - Git accounts. The user name and personal access token you add for a Git host, such as github.com.
- The assistant, if you use it. Your conversations with it, for each site: what you asked, what the model answered, and the changes and scripts it asked to make, with what came of them. The API key you add for a provider. Its settings: the provider, and for each the model, the address, Thinking and Effort; whether it asks before each change; and the providers you agreed to send to.
- Website data from your pages. What your pages store in the built-in browser, such as
localStorage, cookies they set, and cached files. WebKit keeps it on the device, in the App's own storage, as Safari keeps website data.
The App does not collect or receive your name, email address, contacts, location, browsing history, health data, or advertising identifiers. It does not read files you have not explicitly chosen in a file picker or the photo picker, other than those in Portlight's own folder.
Where your data is stored
- In iCloud Drive (if you choose it). Once you turn on Settings › Keep Sites in iCloud Drive, your sites are the Portlight folder of your iCloud Drive, a folder you can see and change in the Files app, on your other devices, and on iCloud.com. Apple stores and syncs it under your Apple Account, under Apple's terms. We have no access to it.
- On your device (unless you choose iCloud Drive). This is where your sites start: in the App's own folder, which the Files app shows as On My iPhone › Portlight or On My iPad › Portlight. Nothing there leaves the device unless you move or share it yourself.
- In the App's storage on the device. The settings, including the access key, the last commands run in the console, unsaved editor changes, the website data your pages store in the built-in browser, the Git history of each site you use Git with, and your latest 50 conversations with the assistant, which stay out of your device's backups. Git histories are kept outside your sites and outside iCloud Drive, which would damage them: each device keeps its own.
- In your iCloud (if you're signed in). A copy of the settings that are the same on all your devices: the editor's, the name and email address your Git commits carry, the assistant's but for its API keys, the appearance, and where the Console and Edit Files open on iPad. Apple keeps it in iCloud for the App, under your Apple Account, and brings it to your other devices. The server's settings, including the access key, and the language stay on each device. We have no access to it.
- In your keychain. Your Git accounts, with their tokens, and the assistant's API keys. If iCloud Keychain is on, it brings them to your other devices, encrypted end to end, so that neither Apple nor we can read them.
- In memory only. The request log and what the console shows, gone when the App quits.
We hold none of it. There is no Portlight-operated database, log, backup, or cache of your content anywhere.
The server, and the devices that reach it
This is the part of the App that involves other devices, and it is worth being precise about.
- On this device. The App serves your sites to the browsers of this device at
localhost, which nothing else can reach, and doesn't answer what other websites ask of it. - Other devices, only if you allow them. With Settings › Allow Other Devices on, devices on the same local network can open your sites at your device's network address. Never over cellular or through a VPN on your device, and only by an IP address,
localhost, or a.localname, which keeps websites elsewhere from reaching it through a trick of the browser's address resolution (DNS rebinding). - The access key. By default another device's browser must present a 6-character key once, from the QR code, the network link, or typed in. The App then sets a cookie in that browser,
portlight_key, holding the key for a year, so it is not asked again. The cookie is kept by that browser, on that device, and is sent only back to your Portlight. New Key in Settings replaces the key, and every browser holding the old one must enter the new one. The App counts wrong keys per device address in memory, for a minute at a time, to slow down guessing. - Plain HTTP. Pages are served without encryption. Anyone able to observe your local network may be able to read what is served, including the access key. Turn on Allow Other Devices only on a network you trust.
- What visitors can do. A device that can open your sites can download any file they serve. With Pages Can Save Data Files on, a page it opens can also create, replace, and delete JSON, Markdown, and text files in your sites, once that device has entered the access key.
- Language. The pages the server writes itself (error pages, folder listings, the list of sites, the access key page) follow the language a visiting browser asks for. The App reads that preference to choose a language and keeps nothing of it.
Your pages
Your sites run their own code, in the built-in browser and in every browser that opens them.
- What your pages load. A page that names a font, a script, an image, or an API on the internet makes the browser showing it fetch that from there, as any browser would. Those servers then learn that the page was opened, and from what address. That is the page's doing, not the App's: the App adds nothing of its own to what a page loads, apart from a small live reload script that talks only to your Portlight and, in the built-in browser, a request for the page's own icon, to show beside its title, which the App makes only to your Portlight or reads from the page itself.
- Markdown previews. The preview of a Markdown file in the editor shows the pictures it names: those in your site through your Portlight, and any elsewhere on the internet from there, as a page would. Scripts in its HTML never run, and its links open in your browser.
- Links to other websites open outside the App, in your default browser, once you agree. So do other apps a page asks to open.
- The console runs what you type inside the page on screen, with the same access as the page's own scripts. To suggest names as you type, it looks through the page and its own scripts, reading only those your Portlight serves.
- Code completion in the editor suggests from lists built into the App and from your site: the names of its files, and the classes and ids its pages and stylesheets use, which it reads on the device and keeps only in memory. Previews of the images your code names, which show when you rest a pointer on one, are read the same way: an image anywhere else on the internet is never loaded for one.
Git (optional)
Git is there only for the sites you set it up for, in the Git tab of Edit Files, or clone with Clone a Repository.
- The servers you add. When you clone, fetch, pull or push, and when you open the Git tab of a site that has a server, the App connects over HTTPS to that site's Git server, such as GitHub or GitLab, and exchanges the site's commits and files with it. That server learns your device's network address and, if you added one for it, your user name and token. What it does with them is governed by its own terms and privacy policy.
- What pushing publishes. Pushing sends your commits, with the files they hold and the name and email address Settings › Git gives them, to the server, where anyone who can read the repository can see them. GitHub and GitLab can give you a private email address to use instead of your own.
- Your token goes only to the host you added it for, and never with a redirect to another host. Without one, the App reaches only public repositories, and pushes nowhere that asks for one.
- The App doesn't use SSH, so it never reads or makes SSH keys.
The assistant (optional)
The assistant, in the Assistant tab of Edit Files, is off until you choose a provider in Settings › Assistant: Anthropic, OpenAI, or Ollama or LM Studio, which run a model on a computer of your own.
- What it sends, and when. Only when you send it a question: your question, the conversation so far, the site's name and its address on your device, and what the model asks for to answer: the list of the site's files, the files it reads, what the preview's console shows, and what the scripts it runs in the page return. Nothing is sent in the background, and nothing from your other sites. Test Connection sends only your API key, to list the provider's models.
- Where it goes. Straight from your device to the provider you chose, at its own address or the one you gave, with your API key: to Anthropic or OpenAI over HTTPS, or to Ollama or LM Studio on your local network, possibly over plain HTTP, which anyone able to observe the network may be able to read. It never passes through us. The provider handles it under its own terms and privacy policy, which say what it keeps and whether it may use it to train its models: Anthropic's at anthropic.com/legal/privacy and OpenAI's at openai.com/policies/privacy-policy. Ollama and LM Studio keep it on your own computer.
- Your agreement first. The first time you send a question to a provider, the App says what will go to it, and sends nothing until you agree. It doesn't ask for Ollama or LM Studio, which run on your own computer.
- What it can change. Only the site open in Edit Files, and in it only pages, stylesheets, scripts, JSON, Markdown, text and SVG files, pictures, sounds, videos and fonts, never hidden files or symbolic links. It can also move files to the Trash, run JavaScript in the page on screen in the preview, and, when the site uses Git, do what the Git tab does: commit, fetch, pull and push it with its server, and work with its branches, merges, tags, reverts, cherry-picks and stashes. Each change, each page it opens and each Git operation that changes something waits for your Allow, unless you turn off Ask Before Each Change; a script in the page, deleting a branch or a tag, which can delete it on the server too, and dropping stashes ask every time.
- Downloads from the web. The assistant can ask to download a file, such as a picture, from an address on the web into the site. The App asks you every time, showing the address, even after Allow All in This Conversation or with Ask Before Each Change off. Allowed, it fetches the file straight from that server, over HTTPS, without cookies, and that server learns your device's network address, as any website does.
- Your API key goes only to the provider, at the address in Settings › Assistant.
Photos and files you add
The App uses the system's pickers. In the photo picker, you see your library, and the App receives only the photos you pick: it needs no access to your library and does not ask for it. Picked photos are copied into your site as files; HEIC photos arrive as JPEG. A copied photo may carry the metadata the picker includes with it, such as where it was taken, and anyone who can open your sites can download it. Files you import or add from the Files app are copied the same way, and the App receives access to those files and nothing else.
Keep Serving in Background (optional)
iOS suspends apps shortly after they leave the screen, which stops the server. This setting, on unless you turn it off, keeps the server running while you test your sites in Safari. It uses a task iOS lets apps run for something you asked for: tapping Open in Safari starts an hour of serving, which iOS shows as a Live Activity with a button to stop early. It uses none of your data.
How your data is used
Your information is used only to make the App work: to serve your sites, to show them in the preview, to edit their files, to let your pages save their data files, to let the devices you allow open them, to keep serving in the background if you turn that on, to commit, fetch, pull and push your sites with Git when you ask, and to send the provider you choose what the assistant needs to answer you, when you ask it something.
We do not use your data for analytics, profiling, advertising, machine-learning training, or any purpose unrelated to the App's core function. We cannot, because we never receive it.
Third-party services
The App integrates no third-party SDKs at all: no analytics, no advertising, no crash reporting, no feature flags, no A/B testing. Its only platform dependency is Apple iCloud: iCloud Drive, if your sites are there, iCloud to sync your settings, and iCloud Keychain, if it's on, to sync your Git accounts and API keys; your use of them is governed by Apple's privacy policy: apple.com/legal/privacy. Its Git is its own, written for it, with no third-party code.
The Git servers you add, such as GitHub or GitLab, and the AI providers you choose for the assistant, such as Anthropic or OpenAI, are services you use directly, with your own accounts and keys, under their own terms and privacy policies. We have no part in them.
Settings › About links to the App's page and to this policy on our website. Tapping one opens it in Safari, outside the App, like any link; the App itself sends nothing.
Any diagnostics you may choose to share with Apple are governed by your device's analytics settings and Apple's privacy policy. If you send us a crash report or a file yourself, by email, we receive whatever you chose to include.
Permissions the App may request
You are always in control. The App may ask for the following, and you can change or revoke each in the Settings app:
- Local Network: only when you turn on Allow Other Devices, so other devices on your network can open your sites, or when the assistant reaches Ollama or LM Studio on a computer on your network.
- iCloud Drive (optional): to keep your sites in your iCloud Drive, only once you turn on Settings › Keep Sites in iCloud Drive, and while iCloud Drive is on for the App.
Photos and files you add come through the system's pickers, which need no permission. The App never requests camera, microphone, contacts, calendar, reminders, health, motion, Bluetooth, or full photo library access, because it has no feature that needs any of them. As a result, pages shown in its preview cannot use the camera or the microphone either.
Data retention and deletion
- Everything the App stores stays until you delete it. There is no expiry and no server-side copy to outlive it.
- Your sites stay until you delete them. Moving a site or a file to the Trash in the App puts it in Recently Deleted in the Files app, where the Files app's rules for keeping and deleting it apply.
- The request log and what the console shows are cleared when the App quits, and the log whenever you clear it.
- The last 100 commands run in the console stay on the device until you delete the App; newer commands replace the oldest.
- Unsaved editor changes stay until you save the file they belong to or choose Don't Save, or until you delete the App.
- A site's Git history stays on the device until you remove Git from the site, in its repository settings, or delete the App. What you pushed stays on the server, under its rules.
- Conversations with the assistant stay on the device until you delete them, with Delete Conversation, or until newer ones replace them: the App keeps the latest 50. What a provider received stays with it, under its terms.
- Git accounts and the assistant's API keys stay in the keychain until you delete them, in Settings › Git Accounts or by clearing the key in Settings › Assistant, which deletes them from every device iCloud Keychain syncs. iOS can keep an app's keychain items after the app is deleted: if you install Portlight again, on its first launch it deletes those it kept on that device only, and keeps those in iCloud Keychain, which your other devices share.
- Deleting the App removes from the device its settings, the console's commands, unsaved editor changes, the website data your pages stored, the Git histories, the conversations with the assistant, and the sites kept On My iPhone or On My iPad. Sites in iCloud Drive are not deleted with the App: they stay in your iCloud Drive until you delete them there. Nor is the copy of your settings in iCloud, which your other devices share; clearing the name and email in Settings › Git clears them there too.
- The
portlight_keycookie in another device's browser lasts a year, or until that browser's data is cleared, and stops working as soon as you choose New Key.
Security
- The server answers only this device, unless you allow other devices, and then only devices on your local network, never over cellular or through a VPN on your device.
- Other devices need the access key by default; repeated wrong keys from one device are slowed down; and the server refuses requests addressed to names it does not recognize, which blocks DNS rebinding.
- Hidden files, symbolic links, and paths outside your sites are never served. Pages can write nothing but JSON, Markdown, and text files (such as
.json,.md,.txt, and.csv) inside your sites, and a website elsewhere cannot make a visitor's browser save into them: a save must come from a page Portlight served. - Pages are served over plain HTTP, without encryption, which is why other devices should only be allowed on a network you trust.
- Data in transit to iCloud is protected by Apple's encrypted services, Git reaches its servers over HTTPS only, and the assistant reaches its provider over HTTPS, except for Ollama or LM Studio on your local network, which may answer over plain HTTP.
- The assistant works only inside the site open in Edit Files: it never reads or changes hidden files, follows symbolic links, or reaches your other sites, and each change it makes waits for your Allow unless you turn that off.
- Git tokens and the assistant's API keys are kept in the iOS keychain, which iCloud Keychain syncs encrypted end to end, and Git histories outside your sites, so they're never served.
- No Portlight-operated server ever stores or processes your content.
While no method of transmission or storage is 100% secure, we rely on Apple's platform protections to safeguard what is on your device, and we minimize risk by never receiving your data in the first place.
Children's privacy
Portlight is a developer tool, is not directed to children under 13 (or the equivalent minimum age in your country), and we do not knowingly collect personal information from children.
Your rights
Because we hold none of your data, there is nothing for us to disclose, correct, or delete on your behalf. You can access, move, or delete everything directly in the App, in the Files app, or through your iCloud settings. Depending on where you live, you may have additional rights (such as access, correction, portability, or deletion) under laws like the GDPR or CCPA; since we operate no server and hold no personal data, those requests are satisfied by the App and the Files app. For anything else, contact us using the details below.
Changes to this policy
We may update this policy from time to time. When we do, we will revise the "Last updated" date shown on this page, and significant changes may also be noted in the App or its release notes. If required by applicable law, we will provide additional notice or request your consent before changes take effect.
Contact
If you have questions about this policy or how Portlight handles your data:
Email: cliffrubio.dev@gmail.com