Information We Collect
Do not send Proofable a private key, seed phrase, account password, or information that is not needed for the feature you are using.
Some identity checks use a third-party service to create a privacy-preserving proof. In those flows, the provider may inspect an identity document, while Proofable is designed to receive the proof result or derived identifier rather than the document itself. The provider’s notice applies to its processing.
What the Proofable Tools Process
An MCP client such as ChatGPT, Claude, Cursor or Codex calls the Proofable MCP service on your behalf. Some tools return only public information and work without an account. The rest run against your signed-in profile and process the information below. This section states what each tool takes in, what it returns, and where the information goes, so you can see the tool surface as it exists.Tools that run without an account
Tools that run against your signed-in profile
Several tools send a request to a third party to do their job. A URL fetch and a web search reach the site or the search provider you named. A browser action loads the pages you point it at. A connected-app or provider call reaches the provider you chose. A job that uses a model sends its prompt to the inference path described in this policy. When you point a tool at a third-party service, that service receives the request and its own privacy policy applies.
The tool names above map to this policy as follows, so you can check any single tool against the row that covers it:
These are the tools the hosted Proofable MCP service exposes. A client may show a different subset depending on whether you are signed in and what your client supports.
How We Use Information
We use personal information only for the following purposes:
We do not use personal information for advertising profiles, targeted advertising, or data-broker services. We do not sell personal information or share it for cross-context behavioral advertising, and we have not done so in the preceding 12 months.
We use account credentials and other sensitive personal information only to provide and secure the feature you request. We do not use it to infer personal characteristics.
Google User Data
Signing in with Google and connecting Google as an agent capability are separate choices:- Google sign-in requests only your Google account identifier and email address (
openidandemail) to authenticate you and link the sign-in method to your Proofable account. - Google connection (for example Gmail, Google Drive, or Google Calendar) is made through Composio, our connection provider. Google’s consent screen shows the exact access requested. Proofable uses the connection only when you ask an assistant or agent to use it.
- Access: Proofable accesses data only through the permissions you approve and only to provide the user-facing feature you request.
- Use: Retrieved data is used to answer your request, perform the tool action, and show or save the result in your private Proofable session or proof when that feature is enabled.
- Storage: On the Composio path, Composio stores and refreshes the connection tokens and Proofable stores a reference to your connection. When you grant a connection to an agent so the agent can keep calling the provider, Proofable instead receives the provider’s refresh or access token and stores it encrypted in your Vault as a server-written credential record. Retrieved content may be retained in a private chat, job, or execution proof if it forms part of that record.
- Sharing: Data may be processed by Composio, the Proofable hosting stack and, when needed to answer your request, by the hosted AI provider or the AI provider you selected. It is not shared for advertising or unrelated purposes.
- AI training: Proofable does not use raw or derived Google Workspace data to train or improve a generalized artificial-intelligence or machine-learning model.
- Hosted model isolation: When you use Proofable-hosted assistant inference (the Default and Advanced tiers), Proofable sends the model request through RedPill’s confidential-computing gateway. Proofable requires a verified serving path and, for each completed model call, checks the gateway identity and the signed receipt’s exact request and response hashes. When the gateway forwards to a separate model host, Proofable also checks the cited serving-session record, its evidence digest, claims, and channel binding. The chat shows TEE verified only when every model call that contributed to the answer passed the checks that apply to its serving path. This verifies the recorded processing path; it does not mean the browser-to-model request is end-to-end encrypted. Proofable-side retention of the conversation or proof is separate and described above. When you supply your own AI provider key (bring-your-own-key), Proofable sends your request to the provider you selected. The same TEE verified checks can apply when that provider is RedPill’s verified gateway; they do not apply to other bring-your-own-key providers. The selected provider’s terms and privacy policy govern its processing.
- Control: You can disconnect Google in Proofable. Proofable removes the local connection and attempts provider-side revocation. You can also revoke access from your Google Account connections.
Limited Use Compliance
The use of raw or derived user data received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Proofable does not use, transfer, or sell Google user data, including raw, aggregated, or derived data, to create, train, or improve foundational or generalized artificial-intelligence or machine-learning models. This commitment applies to both Proofable-hosted inference and any third-party AI provider integration described in this policy.Other Connected Providers
Proofable may offer sign-in or connected-account access from providers such as Microsoft and GitHub.- Microsoft sign-in requests basic identity information (
openid,profile,email). GitHub sign-in requests your profile and organization membership (read:user,read:org). - Access to data in those accounts, such as Outlook mail, OneDrive files, or GitHub repositories, is made through Composio. The provider’s consent screen shows the exact access requested. GitHub’s
repopermission can cover private repositories when you approve it. - Other sign-in providers may supply the account identifier and basic profile information shown on their consent screen.
AI and Automated Processing
Proofable sends prompts, relevant conversation context, and requested tool results to an AI provider when you use assistant or agent features.- Proofable-hosted inference uses RedPill. For completed hosted model calls, Proofable can verify the gateway’s hardware identity, measured software, key-release chain, and TLS channel, plus the exact request and response hashes in its signed receipt. For forwarded calls, Proofable also checks the cited serving-session record.
- If you provide your own key, Proofable sends the request to the provider you selected, such as OpenAI, Anthropic, Google Gemini, OpenRouter, or another configured provider.
- Information from Gmail, Drive, Outlook, OneDrive, GitHub, or another connected service is included in model context only when needed to complete the action you requested.
Third-Party AI Providers
Proofable offers two inference paths with different data-isolation guarantees. Proofable-hosted inference (Default and Advanced tiers). When you use the included Proofable assistant without supplying your own key, Proofable sends the model request through RedPill’s confidential-computing gateway and requires verified serving. For every completed model call, Proofable can check the gateway’s hardware-backed identity, measured software, key-release chain, and TLS channel, plus the exact request and response hashes in its signed receipt. When the gateway forwards to a separate model host, Proofable also checks the cited serving-session record, its evidence digest, claims, and channel binding. A TEE verified label means all model calls that contributed to that answer passed the checks that apply to their serving paths. The session check relies on the approved gateway’s attested verification result; Proofable does not separately rerun every model host’s provider-specific attestation process. The checks do not independently prove exclusive custody of the gateway’s private keys. The label does not claim end-to-end encryption or prove how a model developer handles data outside this serving path. Proofable-side retention of the conversation or proof is separate and described above. Bring-your-own-key inference. When you supply your own AI provider key, Proofable sends your request to the provider you selected, and that provider’s terms and privacy policy apply. A RedPill key can use the same verified gateway and TEE verified checks described above. Other bring-your-own-key providers do not receive that label. If you connect Google Workspace and then select a bring-your-own-key provider for a turn that uses Google data, you direct the transfer of that data to the provider, and you are responsible for confirming the provider’s terms permit your use. The following third-party AI providers may be available as bring-your-own-key integrations, each governed by the provider’s own terms: OpenRouter, OpenAI, Google Gemini, Anthropic, DeepSeek, Groq, RedPill, Ollama Cloud, NEAR AI, Alibaba DashScope, Featherless AI, Mistral, Together, xAI, NVIDIA NIM, and Fireworks AI. Proofable does not control how a provider processes data you send with your own key. The Proofable-hosted path uses RedPill as its sole platform-managed provider and requires the verified serving path described above.When We Disclose Information
We disclose personal information only as needed:- to service providers that host, secure, support, or process the Service;
- to a connected provider or AI provider when you direct the interaction;
- to another user or the public when you choose public visibility or submit information to a public network;
- to an organization administering a workspace you join;
- to comply with law, enforce our agreements, or protect users, Proofable, and others; or
- as part of a merger, financing, acquisition, or sale, subject to appropriate confidentiality protections.
Providers may process information in the United States and other countries. Those countries may have different privacy laws. Where applicable law requires a transfer safeguard, we use the safeguard available for the relevant provider arrangement. Contact us if you need information about a transfer that affects you.
Public Networks and Visibility
You control whether supported profile, proof, and file content is private or public. Before publishing:- public proof references, wallet addresses, transaction records, and smart-contract events may be permanently visible on a blockchain;
- public files may be stored through IPFS or public object storage and copied by others; and
- deleting your Proofable profile cannot erase data already written to a public blockchain or copied outside Proofable.
Cookies and Similar Storage
Proofable uses first-party cookies and local browser storage that are necessary for authentication, security, wallet connection, preferences, and continuity of a requested flow. The primary authentication cookie is protected from browser-script access and is sent only with qualifying requests. Connected providers may set their own cookies when you visit their sign-in or consent pages. Proofable does not use third-party advertising cookies. Because we do not sell data or use it for targeted advertising, the Service does not currently respond differently to browser “Do Not Track” signals.Retention and Deletion
We keep information only for the period needed for the purposes described above:- account, profile, private proof, connection, chat, session receipt, and agent records remain until you delete or revoke them, delete your profile, or they are no longer needed;
- a saved secret remains until you replace it under the same name, revoke it, or delete your profile. Replacing a secret revokes its prior value immediately;
- a saved tool, skill or agent instruction remains until you update or delete it, or delete your profile;
- a remote MCP connection remains until you remove it or delete your profile;
- a comment or vote remains with the proof it attaches to until you clear it or the proof is deleted;
- browser session content, screenshots and run artifacts from a job remain with that job’s output until you delete the job or your profile;
- contact requests, support messages and security reports remain for the period needed to answer them and keep a record of the request;
- connected-provider credentials remain until you disconnect, reconnect and replace them, the provider invalidates them, you revoke the agent grant that created them, or you delete your profile;
- authentication and OAuth transaction data expires after the applicable security period;
- service, security, and diagnostic records remain for the period needed to operate, secure, and audit the Service;
- public and third-party source records are kept only as part of the proof that used them, and are governed by the proof’s own retention above. Public blockchain and other public network records are outside our control and may never be erasable; and
- payment, dispute, and compliance records remain as required by tax, accounting, fraud-prevention, and other laws.
Security
Proofable uses administrative, technical, and organizational measures designed to protect personal information. These include:- encrypted network connections;
- server-side credentials and protected authentication cookies;
- encryption of the connected-account tokens Proofable holds on the agent-grant path, and of user-provided secrets;
- authenticated access to private files and private proof content;
- signed service-to-service requests and scoped access controls;
- rate limits, abuse controls, security monitoring, and incident logging; and
- separation of public and private storage paths.
Your Privacy Rights
Depending on where you live, you may have the right to:- access or receive a copy of your personal information;
- correct inaccurate information;
- delete personal information;
- restrict or object to certain processing;
- withdraw consent, without affecting earlier lawful processing;
- receive portable data;
- appeal our response to a request; and
- complain to your local data-protection authority.
- revoke a saved secret, which removes its stored value;
- update or delete a tool, skill or agent instruction you saved;
- remove a remote MCP connection you added;
- revoke an agent delegation, which ends that agent’s authorized actions and removes the connection credential it was granted;
- disconnect a connected account, which removes Proofable’s reference and requests provider-side revocation;
- change a proof to private or revoke it, which removes it from public access where technically possible;
- clear a vote or comment you left, and delete a comment on a proof you own;
- delete a job and the output and receipts it produced;
- request a copy of your payment and billing records;
- ask us to delete support correspondence you sent us, subject to the record we must keep to answer it; and
- close your account, which deletes your profile record as described above.
info@proofable.me for anything the interface does not expose.
You may also email info@proofable.me. We may need to verify your account, wallet control, or identity before completing a request. An authorized agent may submit a request where local law permits. We will not discriminate against you for exercising a privacy right.
Proofable does not offer an opt-out of sale or targeted advertising because Proofable does not engage in those activities.
Children
The Service is not directed to children under 13, and we do not knowingly collect personal information from a child under 13. The Terms of Use require users to be at least 18, or the age of legal majority where they live, so the Service is not offered to anyone younger even where local law would allow it. If you believe a child has provided personal information to Proofable, contact us so we can investigate and delete it where required.Changes to This Policy
We may update this policy when the Service or legal requirements change. We will post the updated policy with a new date. If a change materially affects how we use information already collected, we will provide additional notice and obtain consent where required before using that information for the new purpose.Contact
For privacy questions or requests:- Email:
info@proofable.me - Mail: NEUS Network, Inc., 1111B S Governors Ave STE 39950, Dover, DE 19904, USA