Privacy policy

What we collect

Your account

• Sign-in details: your email address, whether it is verified, and your first and last name if you give them. Our authentication provider stores these and your password; we never see your password.
• Workspaces: workspace names, who belongs to which workspace and with what role, and invitations (the invitee's email address, the role and who invited them).
• Sign-in security: our authentication provider may use your IP address and browser details when you sign in, to protect accounts from fraud and abuse.

What you put into the Service

• Webhooks: names, endpoint URLs, chosen events, providers, filters and alias groups, and each webhook's signing secret. We record which user created or last changed a webhook.
• API keys: their names, when they were created and last used. Our authentication provider stores and checks the keys themselves.
• Provider requests: the provider's name, website and the coverage you describe, with your workspace and your name (or email address if you gave no name).
• Alias proposals: the change you propose, with your user id and email address, and the reviewer's comment.
• Preferences: your provider watchlist and saved price views.
• Support emails you send to support@oimo.com.

Webhook deliveries

For each event we send, we keep a delivery log: the event, and for every attempt its time, how long it took, the HTTP status, any error message (up to 500 characters) and the first 1,024 characters of your endpoint's response body. We do not keep the response headers. Each delivery is deleted 30 days after its last attempt (see How long we keep it).

Usage connectors (Beta)

If a workspace admin connects an account at an AI or cloud provider (OpenAI, Anthropic, xAI, Baseten, Modal, Fireworks, AWS, Azure, Google Cloud, Snowflake or Nebius AI Cloud):

• Credentials and identifiers: the API key, token or service-account key the admin gives us, and the account, organization, project or billing identifiers the provider needs. We record which user created or changed a connector.
• Usage and cost reports: the reports the provider makes available to that account, for the backfill period chosen (up to 90 days back) and then on an ongoing basis. Depending on the provider they can include identifiers from your provider account, such as project, workspace, user and API key ids or names, and resource names, along with models, quantities and costs.
• Connector changes: for each request to create or change a connector we keep a SHA-256 hash of the request body, credentials included, to recognise a retried request. The hash cannot be turned back into the credentials.

We use these credentials only to check access and to collect those reports. For Google Cloud (your Cloud Billing export in BigQuery) and Snowflake, both run queries inside your own project or warehouse: they use your compute or credits and leave job and query history in your account. Collected usage is not shown in the app yet. Oimo staff may inspect it to build and check the collectors; it is not used for anything else.

Logs and technical data

• Request logs: our hosting provider logs every request to the Service with its time, URL, status, IP address, user agent and referrer.
• Application logs: our own logs record the method, route, status and timing of each request, without your IP address or user agent. Some lines name the workspace, user, webhook or API key involved (for example when an API key is created or a webhook delivery is attempted), and error lines can include up to 1,000 characters of a failed call's response, which may contain what was submitted (such as an invitee's email address).
• Your email address in internal requests: your requests to our internal price service carry your email address. That service records it only for actions Oimo staff take, such as approving a price. Staff actions in the app are also logged with the staff member's email address.
• Performance timings: after you sign in, the app reports how long screens and requests took, with the screen name and the HTTP status. These samples carry no URL, user id or IP address and go only to our logs.
• Product analytics: which pages and screens you open, where your visit came from (the referring site's address and any utm_ campaign tags in the link), your browser details, and your IP address, from which our analytics provider estimates your approximate location (country and city) and keeps the address with the event. When you are signed in, we also record account actions (signing up and in, and how you signed in, creating a workspace, webhook or API key, inviting a member, adding a usage connector, requesting a provider) with your user id, your workspace id and the domain of your email address, never the address itself or your name. A signed-out visitor gets a random id that lasts one page load. Oimo staff are not counted.
• Rate limiting: we use your IP address in memory to apply rate limits. It is not stored.

The CLI

oimo login saves your session on your own computer, in ~/.config/oimo/sessions.json, readable only by your user. oimo logout deletes it there. The CLI reads API keys from the OIMO_API_KEY environment variable and never saves them. Nothing about the CLI login is stored on our side beyond the session itself at our authentication provider.

Cookies

We use only the cookies the Service needs to work: no analytics, advertising or third-party cookies, and no browser local storage. Product analytics works without cookies: the app reports page views to our own server, which forwards them to PostHog, so no tracking script from another company runs in your browser and a signed-out visitor is not recognized from one visit to the next.

All of them are first-party, HttpOnly, Secure and SameSite=Lax.

How we use it

• to provide the Service: sign you in, run your workspaces, deliver webhooks, answer API requests and collect connected usage;
• to keep it secure and reliable: apply limits, detect abuse, investigate errors and measure performance;
• to understand how the Service is used, which pages bring people to it and where they stop, so we can improve it (product analytics);
• to support you when you write to us; Oimo staff can open any workspace for this. In the app, staff view a workspace read-only and cannot see its signing secrets or connector credentials;
• to tell you about important changes to the Service, such as pricing or the end of the beta;
• to comply with the law and enforce our Terms of service.

We do not sell personal data, share it for advertising, or use it to profile you. We do not send marketing email today. Our legal bases where data-protection law requires one: performing our contract with you, our legitimate interest in securing and improving the Service, and legal obligations. Decision needed

AI models

Oimo uses AI models (from Anthropic and, optionally, xAI) to read vendors' public pricing and terms pages and to suggest which vendors' resources are the same model. These models receive public vendor content and our public catalog of resources. They do not receive your account details, workspace data, webhooks, delivery logs, usage data or connector credentials.

One exception: when Oimo staff accept a provider request and start adding that provider, the website address in the request is given to a model as the page to start reading from, and is fetched by our page-fetching services (see Who processes it for us). Your name and the rest of the request are not.

Who processes it for us

When you use a usage connector, we call your provider's own API with your credentials; that provider already holds the data and is your vendor, not ours. The AI model and page-fetching services above receive no data from your account (see AI models).

Where it is stored

Service data is stored with Google Cloud in the United States (us-central1 and the US multi-region); logs are kept in Google Cloud Logging's default storage location. Our authentication provider and Cloudflare may process data in other countries under their own terms. PostHog stores product analytics in the United States. If you are in the EU, the UK or another country with transfer rules, we rely on [transfer mechanism, e.g. Standard Contractual Clauses] for these transfers. Decision needed

How long we keep it

Security

The Service is served only over HTTPS. Data is encrypted at rest by our hosting provider. Usage connector credentials are kept in Google Cloud Secret Manager, one secret per connector. Only the collection job is given read access to them; a few Oimo administrators and deployment systems have project-wide rights that include them. The app never shows them again, even to admins. API keys are stored and checked by our authentication provider. Access to production systems is limited to Oimo staff who need it. No system is perfectly secure; if you believe your data or account is at risk, write to support@oimo.com.

Your choices and rights

In the app you can change your workspaces' members, webhooks, API keys, connectors and preferences, and delete most of them. Email support@oimo.com to:

• get a copy of your personal data, or of a workspace's data, in a portable format;
• correct it;
• delete your account, a workspace or collected usage;
• object to or ask us to restrict a use of your data.

We may need to confirm your identity first. We answer within [number] days Decision needed. Depending on where you live you may have further rights, including to complain to your data-protection authority. [Region-specific notices, e.g. GDPR and California]. Decision needed

Children

The Service is for professional use and is not directed to anyone under [minimum age]. We do not knowingly collect their data; if you believe we have, write to support@oimo.com and we will delete it.

Changes to this policy

We will post any change here and update the "Last updated" date. If a change materially affects how we use your personal data, we will tell you in the app or by email before it applies.

Contact

[Oimo legal entity name], [registered address]. Email support@oimo.com. [Data-protection representative or contact, if required]. Decision needed

Open questions for review