Help
Who can see your requests?
Ompera passes requests through in memory and never stores them. Whether the owner of the model can read them depends on the kind of model.
By model type
| Model | Ompera | Device owner |
|---|---|---|
Your model my/…Unshielded | Reads it in memory to route it; never stores it. | That's you. Your model server and its logs see it. |
Pool models <pool>/…Unshielded | Reads it in memory; never stores it. | The member who runs it can read it on their model server. |
| Network models and services Shielded · Android app | Reads it in memory; never stores it. | The standard app does not show requests to the phone's owner. Someone who controls or modifies the device may still inspect them. |
HTTPS protects requests on the internet between your app, Ompera and the device. It does not hide the content from the service that processes it or guarantee privacy from a device owner. Send only what you are comfortable sharing with Ompera and the device that runs the model.
What Ompera keeps
Account details, key fingerprints (never the keys), and request metadata — time, model, duration, token counts, result — for 7 days. If you share a model, daily totals of its time online and of the requests it served are kept longer, as your sharing record and rating. No prompts or answers. Details: Privacy.
Protect your account
- Passkeys can't be phished or guessed. Add a second passkey (for example on your phone) or a wallet in Account so you never get locked out.
- API keys act as your account for AI requests. Use one per app, keep them out of code and public pages, and revoke any key you suspect has leaked.
- Removing a passkey or wallet signs out the devices that used it.
- Wallet already used for another account? Choose Link a wallet in Account, review the data to bring over, then confirm your current account. Both accounts' sign-in methods, keys, devices and pools stay together. Models become available to members of either account's pools; reconnect your models afterwards.
The Chrome extension
The Ompera Browser Connector can only reach localhost on your computer and only while the Ompera connector page asks. It runs only on that page, stores no keys or content, and its toolbar icon can Stop all browser connections, which stays in effect after Chrome restarts.
- Keep your model server on
localhost; you don't need “Serve on local network”. - If your server has an API token, enter it only in the connector's Advanced settings.