Privacy policy

Who we are

inseam is a context network. It connects your devices and the services where your data lives, so that you and your AI agents can search and read that data in one place. AIUI operates inseam at inseam.io and app.inseam.io. In this policy, “we” and “us” mean AIUI.

This policy applies to the website, the web app, the inseam apps and command line tools, and the inseam API. inseam is in development: it changes often, and this policy changes with it.

What we collect

Your account

• Your email address, and your name and profile picture if you give them or your sign-in provider shares them.
• How you sign in: a one-time email link, a passkey (we keep its public key only), or Google or GitHub. For Google and GitHub we keep the account id and the verified email address the provider gives us.
• Your sessions: when they start and expire, and the IP address and browser or app that started them.

Your networks

A network is the set of devices and services (hosts) that you connect. For each network we keep:

• The search index. For each object on a host (a file, an email, a record): its address, a hash of its bytes, its metadata (such as name, size, type, dates, sender and recipients), the text we extract from it, and vectors computed from that text for search.
• Credentials for your hosts. The tokens or keys that let inseam read a service you connect, such as an OAuth token for Gmail or an API key. They are encrypted. Credentials for hosts on your own device stay in that device’s keychain and never reach us.
• The pad. Each network includes a storage host of its own, the pad. Files that you or your agents save to the pad are stored by us, like files in any cloud storage service.
• Temporary copies. When you ask for a temporary link to an object, or a staged read, we keep a copy of that one object. It expires after at most 24 hours, and we delete it then.
• Members, grants and agents. Who belongs to the network, what each person and agent may read or write, and the agent sessions you approve.
• An audit log. Records of sign-ins, grants, credential use and other changes to the network.

Billing

If you choose a paid plan, Stripe collects your payment details. We never see your full card number. We keep your plan, your Stripe customer id, and the status of your subscription and invoices.

Operational logs

Our servers log requests to keep the service running and secure: the time, the route, the status, the timing, and the IP address. These logs never contain the contents of your objects, your extracted text or your credentials.

Messages you send us

If you write to us, we keep the message and our reply.

What we do not collect

• Your objects. inseam reads a file or an email where it is, extracts its text, and keeps the index. It does not keep the file or the email. When you or your agent ask for an object, inseam reads it from its host and passes it through. The pad and temporary copies, above, are the only exceptions.
• Tokens from your sign-in provider. When you sign in with Google or GitHub, we delete the provider’s access, refresh and ID tokens before we store anything. Signing in never lets us read your email, files or repositories.
• Passwords. inseam has no passwords.
• Advertising and tracking data. We use no advertising, no third-party analytics and no tracking pixels.

How we use it

We use your data only to provide inseam to you:

• to sign you in and keep your account secure;
• to index your hosts, answer your searches, and fetch objects for you and the agents you approve;
• to enforce the grants and limits of your network and plan;
• to bill you, if you have a paid plan;
• to send you sign-in links and messages about your account and the service;
• to find and fix faults, and to prevent abuse;
• to obey the law.

We do not sell your data or share it for advertising. We do not use it to build profiles of you. We do not use the contents of your index to train or tune any AI model.

Google user data

inseam asks Google for data in two cases, each with its own consent screen.

Sign in with Google

We ask for your basic profile and email address only (openid, email, profile). We use them to create and identify your inseam account. We keep your Google account id, name, email address and profile picture. We do not keep the tokens Google issues.

Connect Gmail or Google Drive

When you connect Gmail or Google Drive as a host, we ask for read access to that service, and write access only if you choose a feature that needs it. We use this access to:

• read your messages or files to build the search index of that host for you;
• fetch a message, a file or an attachment when you or an agent you approved ask for it;
• make changes you or an agent you approved ask for, when you have given write access.

We keep the token in your network’s encrypted credential store. We do not keep your messages or files; we keep the index described above. We do not use Google user data for advertising, we do not sell it, and we do not use it to train or improve AI or machine learning models. People at AIUI do not read it, except with your explicit permission for a specific message or file, when it is needed for security purposes, or when the law requires it.

inseam’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

You can disconnect a Google host in inseam at any time, which deletes its token and its index. You can also remove inseam’s access at myaccount.google.com/permissions.

GitHub

The same rules apply to GitHub. Sign in with GitHub reads your public profile and verified email address, and we keep no GitHub token. Connecting a repository as a host is a separate consent, and its token goes to the encrypted credential store.

AI models and agents

• Search vectors. We compute the vectors in the index with an embedding model that runs on Cloudflare, our hosting provider. The model does not learn from your data.
• No training. We do not use your index, your objects or your searches to train or tune any model, ours or another company’s.
• Your agents. When you connect an AI agent, such as Claude or ChatGPT, it can search and read what you grant it. What the agent reads goes to the agent’s provider, and that provider’s terms and privacy policy apply to it. You choose the grant when you approve the agent, and you can revoke the agent at any time.

Who can read your data

• You and the people you add. Members of a network read what their grants allow.
• Agents you approve. Each agent reads what its grant allows, until you revoke it.
• People you send a link to. A temporary link gives anyone who has it read access to one object until it expires. They can keep what they read.
• The inseam service. Our code reads your index to search it and keep it up to date, and decrypts your host credentials to read your hosts. Like most cloud services, the service can read the data it holds. We say so plainly because it matters.
• Our staff. Staff have no standing access to your network’s data. A person at AIUI reads it only to answer a request from you, to investigate a security incident or abuse, or because the law requires it. Each access needs a stated reason, and we record it.

If a government or court asks us for your data, we tell you first, unless the law forbids it.

Service providers

We use these companies to run inseam. Each one gets only what it needs for its task.

Google and GitHub receive a sign-in request from us only when you choose them. The services you connect as hosts receive our requests on your behalf. We will update this list before we add a provider that handles your data.

If AIUI is sold or merges with another company, your data may transfer as part of that deal. This policy will continue to apply to it, and we will tell you first.

Retention and deletion

• A host. When you remove a host, we delete its credential at once and its index entries within 30 days.
• A network. When you delete a network, we delete its index, pad, credentials and audit log within 30 days.
• Your account. When you delete your account, we delete your account data and the networks you own within 30 days. Records we must keep by law, such as invoices, we keep for as long as the law requires.
• Temporary copies expire after at most 24 hours.
• Operational logs expire after at most 30 days.
• Backups of account data expire after at most 30 days.

The index is built from your hosts. Deleting it never deletes anything on the hosts themselves.

Security

• All traffic uses TLS. Data is encrypted at rest.
• Each network is isolated from every other network: its own storage prefix, its own processes, its own keys.
• Host credentials are encrypted with a key per credential. Only one component can decrypt them, and every decryption is logged.
• Connectors that read your hosts run in a sandbox. They never see your credentials and can reach only the addresses you approve.
• Changes to code that handles decrypted credentials need a second reviewer.

No system is perfectly secure. If a breach affects your data, we will tell you without undue delay.

Your rights

Wherever you live, you can ask us to:

• tell you what data we hold about you, and give you a copy;
• correct it;
• delete it;
• stop or limit how we use it;
• give it to you in a portable format.

You can do most of this yourself in the app. For the rest, write to hello@inseam.io. We answer within 30 days. We may need to confirm your identity first. You also have the right to complain to your local data protection authority.

Where the GDPR or a similar law applies, our legal basis is: the contract with you, to provide the service; our legitimate interests, to keep it secure and improve it; your consent, for the hosts and agents you connect; and legal obligations.

Cookies

We set one kind of cookie: the session cookie that keeps you signed in, shared by inseam.io and app.inseam.io. Your browser also stores your light or dark theme choice. We use no advertising or analytics cookies, so there is nothing to opt out of.

Children

inseam is not for children under 16. We do not knowingly collect data from them. If you think a child has given us data, write to us and we will delete it.

Where data is processed

Cloudflare runs inseam on its global network, so your data may be processed in countries other than yours. We rely on Cloudflare’s data protection terms, including standard contractual clauses, for these transfers.

Changes to this policy

We will post every change on this page and change the date at the top. If a change reduces your rights or changes what we do with your data, we will tell you by email at least 30 days before it takes effect.

Contact

For questions about privacy or this policy, write to hello@inseam.io.