Privacy Policy
Your data stays on your device. Period.
Effective 2026-09-05 · iCore / HiNet, published by Humint Network
iCore is a personal AI application that you download and run entirely on your own computer. This policy explains, plainly, what happens when you connect an account (like Gmail or Google Drive) to your iCore, because that is the part of the app that touches a service we don't control.
The short version: there is no HiNet server in this picture. When you connect a Google account, your device talks directly to Google using your own credentials. The resulting data is stored in one local file on your own machine. We — the people who publish iCore — never see it, never receive a copy of it, and have no way to access it.
What iCore is
iCore is a native application (currently macOS) that runs a private language model directly on your hardware. It answers questions using your own data — files, and, if you choose to connect them, accounts like Gmail, Google Drive, Slack, or Telegram — so it can act as a personal assistant that actually knows your life. None of this requires a HiNet-operated backend: the model runs on your machine, and your data is indexed on your machine.
Website sign-in and early access
The website stores the email you submit, your invitation or waitlist status, and the signup time in our access database. We use this information to manage iCore early access and contact you about your invitation. Verification emails are sent through Resend. Successful email verification also creates a sign-in session and a login record, including the time, requested resource, IP address, and browser information. Your browser stores the session token so you can stay signed in.
If you are already signed in to the docs and visit the download page, we use that verified email to check the download whitelist. Docs access alone does not grant download access. A verified email that is not on the whitelist joins the waitlist, so we can tell you when you can download iCore. These website access records are separate from the personal files and connected-account data processed locally by the iCore app.
What each connector accesses, and why
When you click "Connect" for a source, you are sent to that provider's own sign-in page (Google's, Slack's) and you grant access directly to them — iCore never sees your password. The table below lists exactly what each connector requests:
| Connector | Access requested | Why |
|---|---|---|
| Gmail | Read-only (gmail.readonly) | To index your own email locally so your iCore can search it and answer questions about your own messages. |
| Google Drive | Read-only (drive.readonly) | To index your own documents locally for the same reason. |
| Slack | Read-only channel/message history for channels you're in | To index your own workspace conversations locally. |
| Telegram | Your own chat history, via your own Telegram login | Same — a local, private index of your own conversations. |
In every case, the request is read-only. iCore never sends email, posts messages, or modifies anything in your connected accounts on your behalf without you explicitly initiating that action inside the app.
Where the data goes
Nowhere but your own computer. Concretely:
- The OAuth token that lets iCore read your Gmail/Drive is requested directly from Google by your own copy of iCore, and stored only in a local database file on your machine (
~/.hinet/vault.db). - The content itself (emails, files, messages) is fetched directly from the provider to your machine, indexed into that same local file, and never transmitted onward — not to a HiNet server, not to any analytics or third-party service, because no such server exists in this data path.
- We do not use your connected data to train any shared or central model. Any learning iCore does from your data happens locally, on your device, for your copy of the app only.
A note on encryption at rest
The local database file is encrypted at rest (SQLCipher, AES-256) — so the file itself is unreadable without your device's key, even if someone copied it off your disk. That key is currently held in a protected local file on your device; moving it behind a biometric (Touch ID) gate is active development work. Regardless of that milestone, the core guarantee — nothing ever leaves your device — already holds and does not depend on it.
Revoking access
You can disconnect a source at any time from within iCore's Sources screen, and/or revoke iCore's access directly from your Google Account at myaccount.google.com/permissions (or the equivalent settings page for Slack/Telegram). Revoking access stops any further reads immediately; data already indexed locally remains on your device until you delete it or uninstall the app, since it was never anywhere else to begin with.
What we don't do
- We don't sell your data. There is nothing to sell — we never receive it.
- We don't share it with advertisers or any third party.
- We don't use it to train models on anyone else's behalf.
- We don't have a support dashboard, admin panel, or any tooling that could show us your connected data, because none of it is transmitted to us.
Changes to this policy
If this policy changes, the updated version will be posted at this same address with a new effective date above.
Contact
Questions about this policy or how a connector works: hi@quorumz.com.