Question 1

What is your privacy posture?

Accepted Answer

You never create an account with us, and the app asks for nothing tied to your identity — no name, no email, no phone number. There are no analytics, attribution, or advertising SDKs in the app; it never automatically sends usage data or crash telemetry. Your session content — transcripts, agent questions and your answers, approval requests, file contents, and credentials — flows directly between the app and the backend running on your own machines, over a connection pinned to your server certificate. That content is never routed through, stored on, or readable by our infrastructure, which means we could not read it even if we wanted to.

Question 2

Is billing handled entirely through the App Store?

Accepted Answer

Yes. Olympus Console Pro is sold and billed exclusively as an Apple in-app purchase, managed by the App Store through your Apple Account. We never see your payment details, your name, or your billing address. The app reads your subscription status on-device from StoreKit and presents an Apple-signed proof of purchase to the relay so it can apply Pro entitlements — that proof contains pseudonymous transaction identifiers and the product and expiry, not your identity. Manage, cancel, restore, or request a refund from Apple directly; we do not operate a separate billing system.

Question 3

Do you collect any telemetry?

Accepted Answer

No. The app contains no analytics SDKs, no usage-data collectors, and no crash beacons of any kind. Nothing leaves your device unless you send it — and the only thing the app sends on its own is the data the push relay needs to wake your phone when a session needs a decision. We publish the exact, full list of what does and does not leave the app on the Privacy Policy, and the entire backend is open source so the network traffic is auditable, not just asserted.

Question 4

How is this different from a cloud-relay competitor?

Accepted Answer

Cloud-relay competitors terminate your session traffic on their own servers, which means your transcripts, your files, and your credentials pass through infrastructure they operate and can technically read. Olympus Console does not. Both the companion and the backend run on your own machines; the connection between your devices and your backend is pinned to your own certificate and never passes through Fortune Five infrastructure. The only thing on our side is a deliberately minimal push relay — a dumb pipe that carries end-to-end encrypted pointers so your phone can be woken, with no view of session content. We cannot read your transcripts, your files, or your credentials, and the open-source backend proves it.

Question 5

Where does my data live?

Accepted Answer

On your own machines. The companion and the backend both run on your infrastructure, so prompts, code, transcripts, credentials, and project files stay on the network you operate. Setting up Olympus Console on a Mac or Linux box is the only step required to bring it online; there is no Polsia-operated hosted instance, no signup that provisions a cloud worker for you, and no region your data is shipped to. The push relay keeps only what it needs to deliver an end-to-end encrypted notification — device push tokens, routing credentials, subscription tier and expiry, and operational counters — and nothing that would identify what is in your sessions.

Frequently asked questions

What is your privacy posture?

Is billing handled entirely through the App Store?

Do you collect any telemetry?

How is this different from a cloud-relay competitor?

Where does my data live?