Privacy
What leaves your browser
In short
- Most of Publishly never sends your files anywhere. Screenshots, the editor, video encoding, the APK and app bundle check, the icon maker and Store files all run in this browser.
- Some features need another computer — AI, sign-in and Google Drive, Firebase Test Lab, reading a store listing from a link. Each one is listed below with what it sends, to whom, and when. None of them runs until you use it.
- No ads, no analytics, no tracking. The one automatic report is a crash report: the error message, its stack and the page's path.
- You don't have to take our word for it: open your browser's network panel while you work, or read the code — it is open source.
1. What stays in your browser
These work on files in this browser and send none of them anywhere:
| Tool | What it does here |
|---|---|
| Screenshot studio | Designing, translating the layout, and exporting every PNG and the zip. |
| Video studio and device mockups | Rendering and encoding the MP4, WebM or GIF with your browser's own encoder. Screen recordings are decoded here. |
| App check (APK and app bundle) | Reading the build, every check, the report and its fixes. While it reads, the page counts its own network requests and shows the count — it stays at 0 for your app. |
| Store files | Reading, checking and re-saving pictures and videos, HEIC photos included. |
| App icon maker | Drawing, checking and exporting every icon size. |
| Strings studio | Reading strings.xml, APKs and bundles, and the files it writes. Translating with Chrome's built-in translator also stays on this device. |
| Listing text checks | Counting characters and checking the stores' wording rules. |
What your browser keeps between visits (your project, the app you're working on, settings) is listed in the privacy policy. None of it is sent anywhere by keeping it.
2. What is sent when you use a feature
Nothing in this table happens until you use the feature. “Our server” is the computer this site runs on; it passes each request on and keeps none of it.
| When you… | What is sent | Where it goes |
|---|---|---|
| Use an AI feature that runs on Gemini: analysing your screens, captions, backdrops, translating captions, strings or the listing, writing listing text, the YouTube text, logo ideas, a voice-over, music, the AI director | What that feature needs: your screens scaled down (640–1,024 px JPEG), your app's name and description, the words to translate or write. Your Gemini key goes with it. | Our server, then Google's Gemini API on your key. With no key of yours and none on the site, nothing is sent: you're asked for a key instead. In the screenshot wizard AI is on by default and runs when you continue; choose Offline there to keep it all in your browser. |
| Plan a video with the AI director on Claude | Up to 10 screens (1,024 px JPEG), the brief, and your Claude key. | Our server, then Anthropic's API on your key. |
| Import a Google Play or App Store listing from a link | The link. | Our server fetches the public listing page and its pictures and hands them to your browser — Google and Apple see our server, not you. |
| Check your privacy policy's page from the app report | The address you typed. | Our server fetches the page (never a private or local address) and returns its text. |
| Look for newer library versions in the app report | The names of the SDKs found in your build (like com.google.firebase:firebase-messaging) — not their versions, your package name or the build. | Our server, then Google's Maven repository. |
| Sign in with Google | The sign-in itself, on Google's page. Afterwards your profile picture loads from Google. | Google. Our server keeps nothing: your sign-in lives in an encrypted cookie in your browser. |
| Keep projects in Google Drive (signed in) | Your projects, their pictures and recordings, brand kits, translation memory and exports — saved as you work. | Straight from your browser to your own Google Drive. |
| Record or review your app with Firebase Test Lab | Your APK or app bundle, the test account's sign-in if you add one, and your Google access token. | Our server, then your own Cloud Storage bucket and Test Lab project. The recording, screenshots and logs come back the same way. The files stay in your bucket; Publishly never deletes them. |
| Record on Android, or run a design review, on your own computer | Your APK or app bundle and any test account. | Your own computer only (this site running locally, or the Publishly helper). The helper downloads Google's bundletool from GitHub once, for app bundles. |
| Match a layout with the on-device engine — or let AI Remix fall back to it, when Gemini isn't available | Ordinary downloads: the Florence-2 model (about 280 MB) and the code that runs it. Your screenshots stay here. | Hugging Face (the model) and cdn.jsdelivr.net (the ONNX runtime). Both are kept in your browser afterwards. |
| Send feedback | Nothing from the site: it opens your own email app with the message to send or not. | Wherever you send the email. |
3. What happens on its own
- Loading the site: the pages and their code, from this site. Once loaded, a service worker keeps a copy so the tools that need no network open without one; it only ever asks this site.
- Two small questions to our server: whether the site has a Gemini key of its own, and whether you're signed in. Neither carries anything of yours but the sign-in cookie, if you have one.
- Crash reports: when a page hits an error, the error message, its stack and the page's path (without its query) go to our server — at most five a visit, and never from a copy running on your own computer. The server takes out anything shaped like a key or token, and the hosts and queries of web addresses, before writing one line to its log.
4. What our server keeps
- No database, no files of yours, no copies of what passes through.
- For a minute at a time, a count of requests per IP address, to stop floods. It lives in memory and is never written down.
- For a day, which library versions it last looked up on Google's Maven, in memory.
- A line in its log when something fails: the error, never the request, its pictures or a key.
5. Check it yourself
- Open your browser's developer tools (F12, or ⌥⌘I on a Mac) and choose Network.
- Use a tool — export screenshots, encode a video, check an APK, fix a file in Store files.
- Every request is listed. You'll see this site's own code and pictures load; you won't see your files go anywhere. Turn the network off and those tools keep working.
The code is open source under the AGPL: github.com/Trilokia/publishly. Everything the server can do is in src/app/api. The formal version of this page is the privacy policy.