Ploze was created by Atadore, a Swiss company, owned by Damian Mehers
Ploze has no cloud component of its own and no analytics and tracking. Your data stays on your device. Nor does the app use third party services for analytics, advertising etc.
Atadore does not collect or store any data on servers when you use the app.
When you ask Ploze a question, Ploze answers it with Apple Intelligence. By default it uses Apple’s Private Cloud Compute when your device is online: your question and the entries Ploze found for it are sent to Apple’s servers, used only to answer the question, and never stored. Atadore never sees them. You can turn this off in the Ask Ploze section of Ploze’s Settings, and Ploze then answers on your device alone, as it also does when you are offline or have reached Private Cloud Compute’s daily limit.
When you sign in to a service such as GitHub, Gmail or Mastodon to import from it, Ploze talks to that service directly (for GitHub, github.com and api.github.com), with read-only access. The sign-in is kept in your device’s keychain and never passes through Atadore’s servers; there are none involved.
What Ploze reads from Hacker News and Stack Exchange is public, so it does not sign in. For Hacker News, it asks Hacker News’ own service (hacker-news.firebaseio.com) whether the username you typed exists, then reads the stories and comments you posted from Algolia’s search of Hacker News (hn.algolia.com), which Hacker News links to from every page, every hour. For Stack Exchange, it reads the sites you have joined and the questions, answers and comments you posted there from Stack Exchange’s own service (api.stackexchange.com). Both see the username or account id Ploze asks about and your device’s internet address, as any website you visit does.
What Ploze reads from Bluesky is public, so it does not sign in unless you give it an app password. When you add your account by its handle, Ploze asks Bluesky’s public website (public.api.bsky.app) which account the handle names, then reads your posts, reposts, likes and follows from the server that keeps your account (which plc.directory names). Every hour it asks that server whether anything is new, also for an account whose export you imported, and reads only what changed.
Bluesky names other accounts only by an id and gives none of the pictures. When you import, Ploze also asks Bluesky’s public website (public.api.bsky.app, and plc.directory for where your own posts’ files are kept), without signing in, for the names of the accounts your posts, likes and follows name and the text of the posts you liked, reposted or quoted, and afterwards downloads your posts’ pictures and videos from Bluesky. These requests go from your device to Bluesky directly, never through Atadore, and name only your own account and the accounts and posts it already refers to on Bluesky.
Your direct messages and saved posts are not public. Only if you enter an app password does Ploze read them, and only them, signed in as you: from the server that keeps your account, which passes the requests on to Bluesky’s chat service (api.bsky.chat) and its main service (api.bsky.app). The app password stays in this device’s keychain, is sent only to that server, and is never synced to your other devices. What Ploze reads from them goes where the rest of your timeline goes: it stays on your device, and in the sync folder if you chose one. An app password could also post and delete, which Ploze never does. Sign Out in a Bluesky source’s settings forgets it, and deleting it in Bluesky’s settings withdraws it for good.