Privacy Policy — Olympus Console

Effective: 26 July 2026

Olympus Console is built so your data stays on your devices and your machines. This policy explains, plainly, what little we handle and why.

It applies to the Olympus Console application distributed through the Apple App Store, including when it runs on an Apple Silicon Mac, and to the push relay we operate. The controller of the limited data described below is Fortune Five ("we", "us"). Contact: olympusconsole@polsia.app.

The short version

• No account. You never create an account with us. We do not ask for your name, email address, or phone number.
• No analytics, no tracking, no ads. The app contains no analytics, attribution, or advertising SDKs. It does not automatically send usage data or crash telemetry anywhere.
• Your session content never reaches us. Session transcripts, agent questions and your answers, approval requests and decisions, project files, and credentials all flow directly between the app and the backend running on your machines, over a connection pinned to yourserver's certificate. That content is never routed through, stored on, or readable by our infrastructure.
• One vendor service exists: a push relay, described next. It carries end-to-end encrypted payloads it cannot read.

What our infrastructure handles: push notifications

For your phone to be woken when a session needs you — for example, a credential approval that arrives while the app is closed — the notification must go through Apple's Push Notification service, and that requires a small relay we operate. The relay is a dumb pipe on purpose.

For each registered device it stores only:

• the device push token Apple assigns, which is required to deliver a notification;
• a routing credential, so that only your own backend can trigger pushes to your device and never to anyone else's;
• your subscription tier and the expiry date from its proof of purchase, so the relay knows whether Pro features apply — without knowing who you are;
• operational counters (for example notification counts and, for Pro voice users, daily voice-token counts) used for rate limiting, cost control, and abuse prevention.

Notification payloads are end-to-end encrypted and are minimal by design: enough for the app to show which kind of item needs you, never the substance of your sessions. The relay never sees transcripts, agent questions, approval contents, credentials, file contents, or project names.

Retention.Relay records for a device with no traffic for 90 days are purged automatically. Removing the app's pairing, revoking the registration in the app, or deleting the app stops registration; the automatic purge then clears the leftover record within that window. You can also ask us to delete a registration immediately — see "Your choices and rights".

Voice input (Pro)

If you use voice features, audio is streamed from your device directly to the speech-to-text provider, Soniox, to be transcribed. Voice audio never passes through our relay or any other infrastructure we operate, and we never receive or store it.

To start a voice stream, your device needs a short-lived transcription credential. Depending on how you have configured Olympus:

• if you supply your own speech-to-text key to your own backend, the credential is issued by your backend; or
• if you use the Pro voice feature, our relay mints a short-lived, single-use, duration-capped credential for you after checking your Apple-signed proof of purchase. Doing so tells the relay only that an entitled device asked for a voice credential and increments a daily counter. The relay does not receive the audio or the resulting transcript.

The transcribed text goes only to your own backend, exactly like text you type. Soniox's own handling of the audio is governed by its policies.

Purchases

Subscriptions are processed entirely by Apple through your Apple Account. We never see your payment details, name, or billing address.

The app reads your subscription status on-device from Apple's StoreKit and presents an Apple-signed proof of purchaseto the relay so it can apply Pro entitlements. That proof contains Apple's own pseudonymous transaction identifiers and the subscription's product and expiry — it does not contain your name, email address, or payment information, and we do not link it to any identity.

Reporting a bug from inside the app

The app includes an optional Report a bug flow. It is entirely user-initiated: nothing is sent unless you write a report and submit it.

When you submit one, the report — the description you write, any attachments you choose to include, and basic technical context such as app version, build, and device/OS type — is sent through our relay and filed as an issue in a private developer repository on GitHub, so we can act on it. GitHub processes that data on our behalf as a service provider.

Please do not paste secrets, credentials, or confidential source code into a bug report. Anything you include in a report is content you have chosen to send us; it is the one exception to "your content never reaches us", and it exists only because you triggered it.

Bug reports are kept for as long as needed to investigate and resolve the issue. You can ask us to delete a report you filed — see below.

Concretely, a submitted report contains only:

• the description you write (up to 4,000 characters);
• up to three photos you attach (JPEG or PNG, up to 4 MB each);
• app diagnostic logs, only if you switch on the "include logs" option (up to 256 KB);
• basic technical context: app version, build number, operating-system name and version, device model, and whether you are using the iPhone or the Mac surface.

Permissions the app may ask for on your device

These permissions serve on-device features. Data they produce goes to your own machines, not to us:

• Notifications — to alert you when a session is blocked and needs a decision.
• Camera — to scan a pairing code, and to take a photo you choose to upload into one of your own projects.
• Photo library — only for files you explicitly pick to upload to your own projects.
• Microphone — only while you are actively using a voice feature.
• Face ID / Touch ID — to unlock the app and to confirm high-risk approvals. Biometric matching is performed by Apple on your device; we never receive biometric data.

Third parties involved

• Apple — App Store distribution, subscription processing, and the Push Notification service.
• Soniox — speech-to-text transcription, only if you use voice features, and only as a direct stream from your device.
• Our hosting provider — operates the servers the push relay runs on, holding only the relay records listed above.
• GitHub — stores in-app bug reports you choose to submit.

We use no advertising networks, no analytics vendors, and no data brokers.

What we never do

• We never sell, rent, share, or monetize any data.
• We never store your session content, and could not read it if we wanted to — the connection between your devices and your machines does not terminate at our servers.
• We never collect device fingerprints, contact lists, location, health data, or anything else unrelated to delivering notifications.
• We never track you across apps or websites.

Your choices and rights

• Stop all data at the relay: revoke the device registration in the app, or remove the pairing. The stored record is purged as described above.
• Deletion, access, or correction: because we hold no account and no identity for you, the practical way to exercise these rights is to contact us at olympusconsole@polsia.app with the relevant device registration or bug report, and we will delete or provide the record.
• Depending on where you live, you may have additional rights under laws such as the GDPR or the CCPA. We do not sell or share personal information as those laws define it, and we will honour valid requests using the contact above.

Children

Olympus Console is a developer tool and is not directed at children. We do not knowingly collect personal information from children.

Open source

The backend you run is open source, so none of the above has to be taken on faith. You can read exactly what the software sends, and to whom, at github.com/olympus-console/olympus-console.

Changes and contact

If this policy changes, the new version will be published at https://olympusconsole.com/privacy with an updated effective date.

Questions or concerns: olympusconsole@polsia.app · GitHub Issues · Terms of Use