Privacy policy

This policy explains what Arbitir Inc ("Arbitir", "we") collects, why, and what we do with it. It covers the Arbitir application at app.arbitir.ai, the marketing site at arbitir.ai, and the emails we send. It is written to be read, not skimmed, so it is short.

The one thing to know first

Arbitir reads usage metadata from the AI providers and business systems a customer connects: token counts, model names, timestamps, dollar amounts, and the identifiers that say which key or which person spent them. It never reads prompts, completions, conversation text, Slack messages, CRM notes, or email bodies. There is no code path that could, and every credential a customer connects is scoped so that it cannot.

What we collect

Account information. When someone signs up or is invited, we store their name, work email address, and their role in their organization. We use it to sign them in, to show who did what inside their organization, and to send the emails the product sends.

Data a customer connects. When an administrator connects a provider, we read what that provider's usage and cost endpoints return: spend by day, by model, by API key, by workspace, and by member. From a CRM we read owners, deals, and the figures the customer has mapped to their outcomes. From Slack we hold the channel a customer chose for notices and the requests and decisions made there. The credentials that make these reads possible are stored in an encrypted vault, and every read of one is recorded.

People and teams. An administrator may import or map the people in their organization: names, work emails, teams, roles, and managers. This is how spend is attributed to a person. Unattributed spend stays unattributed rather than being guessed.

Access requests. When someone asks for access through the marketing site, we keep what they told us: their name, work email, company, and how AI spend is governed today.

The marketing site. We count page views and visitors using Vercel Web Analytics, which does not set cookies and does not track anyone across sites. We also use a visitor identification service, which works out the company a visit appears to come from and may identify a business contact there, along with the pages visited and the campaign parameters in the link someone arrived on. We use it to follow up on interest in the product. It runs on the marketing site only. It is not in the application, and it stops at the point someone signs in. We do not run advertising trackers, and we do not sell what it returns. To have your information removed from it, write to hello@arbitir.ai.

The application. We use a session cookie to keep a signed-in person signed in, and a cookie for interface preferences such as whether the navigation is collapsed. We also set a cookie that remembers the campaign link or referring site someone first arrived on, so that we know which of our own pages and campaigns bring people to sign up. It records only that first visit, it is read when somebody signs up or tries to and at no other time, it never leaves Arbitir, and it says nothing about any site other than this one. It expires after 90 days. We also note the days each person uses the application, the date alone, never the pages they open or what they do there, so that we can tell whether an account is in use; a cookie remembers that today has been noted, so it is noted once, and it expires after two days. The days are kept for ninety days. That is all.

What we do with it

We use the data above to run the product: to attribute spend, to put it beside outcomes, to apply the budgets a customer sets, to send the notices they asked for, and to keep the ledger of capital decisions. We use operational logs and error reports to keep the service working. We do not sell data, and we do not use a customer's data to build anything for anyone else.

Who else handles it

The service runs on a small number of providers, each of which handles only the data its job needs. The current list, with what each one handles, is on the security page. The systems a customer connects, such as Anthropic, OpenAI, HubSpot, Salesforce and Slack, are the customer's own accounts, read on the customer's behalf; they are not our subprocessors.

We disclose data when the law requires it, or to protect the rights and safety of Arbitir, our customers, or others. We would tell the affected customer unless we were prohibited from doing so.

How long we keep it

Customer data is kept for as long as the customer's organization is active. When an administrator removes a connection, its credential is deleted from the vault. When an organization is closed, its data is deleted within ninety days, except for records we are required to keep and the audit trail, which is kept for as long as a legal or security need remains. Access requests are kept until they are answered and for a reasonable period afterward.

How it is protected

Every record is tagged with the organization it belongs to, and the database itself refuses reads and writes across organizations. Credentials sit in an encrypted vault separate from the rest of the data. Every connection, credential read, budget change, capital decision, identity mapping, export, and view of a person-level page writes an audit row naming who did it and when. Logs carry identifiers, never names or emails. More on the security page.

Your choices

A person can see and correct their own account information inside the product. An administrator can export or delete their organization's data, remove any connection, and remove any person. Anyone can ask us to access, correct, or delete the information we hold about them by writing to hello@arbitir.ai; we answer within thirty days. If you are in a jurisdiction that gives you additional rights over your personal data, those rights apply and the same address is where to exercise them.

Where the data lives

Arbitir Inc is a United States company and the service is hosted in the United States. Customers outside the United States should assume their data is processed there.

Children

The service is for businesses and is not directed at anyone under eighteen.

Changes

When this policy changes, the date at the top changes with it, and a change that affects what we collect or how we use it is announced to administrators by email before it takes effect.

Contact

Arbitir Inc, hello@arbitir.ai.