Legal
Privacy policy
In short
- Most of Publishly runs in your browser. Your recordings, screenshots, designs and app files stay on your device unless you use a feature that needs our server, listed below.
- You don't need an account. If you sign in with Google, projects are saved in your own Google Drive, in files Publishly creates. We run no database and keep no copies.
- AI features send what they need to Google's Gemini API, on your own Gemini key if you've added one. The video studio's AI director can use Anthropic's Claude instead, only on your own Claude key. Offline mode sends nothing.
- No ads, no analytics, no tracking cookies, and we never sell your data.
- Every feature that sends something — what, to whom and when — is also listed in plain words on What leaves your browser.
1. Who we are
Publishly is a web app for making app store screenshots, device mockups, promo videos, store listing text and app translations, and for checking an app before it goes to Google Play. This website is run by Trilokia Inc. (“we”, “us”), who is responsible for the personal data described here.
Questions, or requests about your data: contact@trilokiainc.com.
2. What stays on your device
The editor, the video studio, image and video export, the Android strings studio and the app report all work inside your browser. APK files you open are read in the browser and are not uploaded. When you choose the on-device layout engine, your browser downloads an open AI model (Florence-2) from Hugging Face and the code that runs it (ONNX Runtime) from the jsDelivr CDN, so Hugging Face and jsDelivr see those download requests; the model then runs locally and your screenshots stay on your device. AI Remix uses the same engine by itself when you give it a listing to match and Gemini isn't available, if your browser can run it. Chrome's built-in translator, when you pick it, also runs on your device.
Your browser keeps:
| Where | What |
|---|---|
| IndexedDB | Your current project and video, brand kits, app string translations, your translation memory, app reports, your last design review with its screenshots, and cached voice-over clips, so work survives a reload and can go in the release zip. Also the app you are working on — its name, package, description, icon and, up to 250 MB, the APK or app bundle you last opened — so the next tool doesn't ask for the same file again. Work on a different app, under the app's name at the top of a page, removes it. |
| Cache storage | Copies of this site's own pages and code, kept by its service worker so the tools that need no network open without one, and — once you've used the on-device layout engine — that model and its runtime. Nothing of yours is in it. |
| Local storage | Your Gemini key and your Claude key (if you add them), a count of today's Gemini requests on your key, light or dark theme, saved styles, the Firebase project you last chose for Test Lab, small preferences such as the video resolution and the export options, and — if you pair this browser with the Android helper — its port and pairing token. |
Clearing this site's data in your browser removes all of it. We can't see or recover it.
Two optional tools run on your own computer. The Android helper (npx @publishly/cli connect) lets this site drive your emulators and USB phones: the page talks to it directly at 127.0.0.1, so your APK, screenshots and recordings go from the page to your computer, not through our server. To install an app bundle, the helper downloads Google's bundletool from GitHub once and keeps it on your computer. The command-line renderer (npx @publishly/cli render) opens this site's renderer page in a browser on your computer and draws your project file there; only the page's code is downloaded, and the project never leaves your machine.
3. Signing in with Google and Google Drive
Signing in is optional. It asks Google for your basic profile (name, email address, profile picture and account ID) and the drive.file permission. With drive.file, Publishly can only see and change files it created or that you open with it, never the rest of your Drive.
- Where your sign-in is kept: in an encrypted, http-only cookie in your browser, which holds your profile and the token that lets Publishly reach your Drive. It isn't stored on our server. While you're signed in, your profile picture is loaded from Google's image servers.
- How Drive is reached: each time Publishly needs Drive, your browser asks our server for a short-lived access token made from that cookie, then talks to Google Drive directly. Your projects go from your browser to your Drive, not through our server.
- What goes into your Drive: a “Publishly” folder (still called “Play Store Screenshots” if you first signed in before the app was renamed) with your projects, videos, brand kits and their images, your translation memory, plus the version history you save. Everything stays in your Drive under your control.
- Sharing: only when you use “Share preview”, Publishly makes that one preview readable by anyone with the link, or asks Drive to email an invitation to the address you type.
- Stopping: sign out to remove the cookie from this browser, or disconnect to also withdraw Publishly's access. You can also remove it at myaccount.google.com/connections. Your Drive files stay until you delete them.
Publishly's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features you ask for. We don't use it for advertising, don't sell it, don't use it to train AI models, and no person reads it.
4. AI features
These features send data through our server to Google's Gemini API, only when you use them:
- Choosing screens and writing captions: reduced-size frames from your recording or screenshots.
- Reading captions off screenshots, and matching a store listing's style or layout: those screenshots.
- Translation: your captions, or your app's strings, plus any screenshots you add for context. Strings already in your translation memory aren't sent.
- Store listing text and voice-over scripts: your app's name, description and on-screen words. When you read your build on the Store listing page, the listing request also carries the same lines of the app's own text described below.
- Describing an app that isn't on Google Play yet: its name, package, screen names, permissions and up to 300 lines of its own text, read from the APK or app bundle in your browser. The build itself is never sent, and text that looks like a key, an address or an id is left out. The page shows exactly which lines go.
- Voice-over: the script to be spoken. Music: your description, tempo, energy and brightness (Lyria RealTime), or your description and tempo (Lyria 3, which Google offers on paid keys only).
- The video studio's AI director: reduced-size copies of up to 10 of the screens in your video, one frame from each recording, your app's name and description, its main colours, and the length, size and closing line you chose.
- The YouTube title and description: your app's name, tagline, description, category and Google Play link, the video's captions and its length.
- Logo ideas in the App icon maker: your app's name, category and description, what you typed you want the logo to show, and the icon's background colour. The icon itself stays in your browser.
Our server passes each request on and returns the answer. It doesn't store the content. If you've added your own Gemini key, it stays in your browser, is sent with each AI request, and is used only for that request. It is never saved or logged on our server. Without a key, the site's own key is used if the operator has turned it on; with neither, nothing is sent and you're asked for a key instead.
Some AI steps start on their own once you've chosen AI: in the screenshot wizard, where AI analysis is on unless you pick Offline, the screens are analysed when you continue, and reading an unreleased app's build there describes it straight away. AI Remix writes captions, a voice-over and music unless you untick them, and reads a listing you ask it to match with Gemini first.
Google handles this data under its Gemini API terms. On Google's free tier, Google may use what you send to improve its products, so don't send anything confidential with a free key. Offline mode and the no-AI drafts don't send anything.
If you choose Claude in the AI director, that one request goes through our server to Anthropic's Claude API instead of Gemini, on your own Anthropic API key. There is no site key for Claude. Your key stays in your browser, is sent only with that request, and is never saved or logged on our server. Anthropic handles the data under its commercial terms and bills your Anthropic account for it.
5. Other requests our server makes for you
- Importing a store listing: fetches the public Google Play page, or asks Apple's public iTunes lookup, for the app you name.
- Checking a privacy policy link: fetches the web page you enter, without your cookies. Addresses on private or internal networks are refused.
- Library versions in the app report: when you ask, sends the names of the libraries found in your app (such as
com.google.firebase:firebase-messaging) and reads their public version lists from Google's Maven repository. Their versions, your package name and the build aren't sent.
6. Firebase Test Lab (optional)
Recording or reviewing an app with Firebase Test Lab asks Google for one more permission on your sign-in: access to your Google Cloud projects (cloud-platform). Publishly uploads your APK or app bundle to a storage bucket in your project, starts the test there and reads the results back. The file — and the test account's email and password, if you give them for the test to sign in with — passes through our server on its way to your project, and the recording, screenshots and logs come back the same way; our server keeps none of it. Each request carries a short-lived Google access token, made from your sign-in when a test needs one and kept only in the open page's memory and for that one request. The files stay in your bucket until you or your project's settings remove them: Publishly doesn't delete them. The test runs, and is billed, under your project and Google's terms. Disconnecting Publishly (see above) withdraws this permission too.
8. Server logs
Like any website, our hosting provider may record standard request logs (IP address, time, page requested and browser type) to keep the service running and secure. They aren't used to profile you, and they're kept only as long as the host's normal log retention. To stop one visitor from overloading the service, the server counts requests per IP address in memory for one minute at a time; that count is never written anywhere. If a page crashes, your browser sends us the error message, the technical trace and the path of the page (for example /studio) so we can fix it — at most five reports a visit, never from a copy running on your own computer, and without cookies. Before a report goes into the same server log, the server takes out anything shaped like a key or token and the hosts and queries of web addresses. An error message can still quote a few words of what the page was working on, so reports are kept only as long as the host's normal log retention.
9. The community showcase (optional)
The community page shows work people chose to share. Nothing is sent to it from the tools: you share through a GitHub issue form, which GitHub hosts under its own privacy statement, or by email. What you send — pictures, a video or YouTube link, the app's name and store link, the name and link you want shown, and your note — is published on this site and kept in Publishly's public GitHub repository, and the issue shows your GitHub username. Pictures may be resized or cropped. Nothing is added until a person has looked at it and you have ticked both permission boxes.
Ask on the issue or by email and it comes off the page in the next update; copies can stay in the repository's history. The page itself loads nothing from other sites: a YouTube video is a link, not an embedded player.
11. How long data is kept
Our server keeps nothing after it has answered a request, apart from the server logs above. Cookies last as shown above. Browser storage lasts until you clear it. Drive files last until you delete them.
12. Security
The site is served over HTTPS. The sign-in cookie is encrypted and can't be read by scripts, and addresses our server fetches are checked so they can't reach private networks. No system is perfectly secure, so please keep your Google account and Gemini key safe, and tell us if you find a problem.
13. Children
Publishly is a tool for app developers. It isn't directed at children under 13, or under the age of digital consent where you live, and we don't knowingly collect their data.
14. Your choices and rights
Most of your data is already in your hands: in your browser, which you can clear, and in your Google Drive, which you can edit or delete. Depending on where you live (for example under the GDPR or the CCPA), you may also have the right to access, correct, delete or move your personal data, and to object to or restrict its use. To use these rights, or to complain, contact contact@trilokiainc.com. You can also contact your local data protection authority.
15. Changes to this policy
If this policy changes, we'll update the date at the top. If a change is significant, we'll also say so on the site before it takes effect.
16. Contact
Trilokia Inc. · contact@trilokiainc.com
Send feedback (in the settings menu and the page footers) doesn't send anything from this site. It opens your own email app with your message written, plus — only if you leave the box ticked — the page you were on, your browser's name and version, and your window's size. You see all of it before you press send, and what you send is an ordinary email to the address above.