1. Scope and contact
This policy applies to AgentMarkit's website, hosted agent setup, support, and optional integrations. "AgentMarkit," "we," and "us" mean the US-based business operating the AgentMarkit service at agentmarkit.com.
This pilot is intended for adults in the United States. If you use it for a business or give the agent information about someone else, you are responsible for having permission and using that information lawfully.
Use the privacy contact form to ask a question or make a request. Do not send passwords, API keys, or private workspace content through the form.
2. Information we collect
Account and setup information
We collect the email address you use to sign in, a service-specific account identifier, your policy acceptance, the starter and add-ons you choose, machine name and status, setup history, and operational logs. Public demo sessions use an isolated identifier instead of a customer account.
Billing information
Stripe collects the billing details you provide at checkout, such as your email, name, billing address, and payment method. AgentMarkit receives customer, order, subscription, and payment-status identifiers. We do not receive your full card number.
Agent workspace and conversations
Your prompts, outputs, memory, files, installed skills, integration data, credentials, and configuration live on your hosted machine. When you use AgentMarkit's web chat, the full message and reply pass through our Cloudflare Worker to and from that machine. We do not save the full chat content in the AgentMarkit customer database. We do save the machine's chat-session identifier, message count, last-chat time, input and output character counts, and limited error and setup logs.
Credentials and connected services
A model API key entered during setup passes through AgentMarkit so it can be installed on your machine. We do not save that key in the AgentMarkit customer database. The machine or the connected service may store the credential. Before you connect an optional integration, we will identify the access it requests and any additional provider involved.
Support and contact information
If you contact us, we collect the topic, reply email, message, optional name, and any diagnostics or permissions needed to respond. The contact record is private. We use a short-lived, one-way network identifier to limit spam and do not keep the raw IP address in the contact record.
Website activity
We record visits to public pages, workshop sign-in steps, lessons opened, checkpoint changes, prompt-copy actions, and clicks through to Agent37 to understand where people need help. A first-party browser identifier connects visits. When you sign in, we link that browser's recent activity to your account. Only the site operator can view the activity dashboard. The operator may also receive email alerts for successful sign-ins and hosted-machine creation. These operational alerts identify the account and, for a new machine, its name and starter kit.
Activity records contain the page category, time, lesson identifier, and, when available, a referring website hostname or tagged source label. They do not contain full URLs, form contents, prompts, agent files, conversations, or integration data. We do not record sharing through private messages or verify machines created in your own hosting account.
Website and security information
Cloudflare processes ordinary request and security information, including IP address, browser details, requested page, timing, and threat signals. AgentMarkit currently does not use advertising pixels, session replay, or a separate behavioral analytics product.
3. How we use information
We use information to authenticate users, provision and operate machines, install requested starters and add-ons, process payment, send service messages, provide support, prevent abuse, diagnose failures, maintain records, and comply with law.
We may use operational information that does not include private agent content or Google-derived data to improve setup reliability and security.
We do not sell personal information. We do not use personal information for targeted advertising, data-broker enrichment, credit decisions, or generalized AI model training.
4. Where your agent's data goes
Your hosted agent currently runs on infrastructure provided by Agent37. AgentMarkit can provision, update, restart, and delete that machine through provider APIs. Agent37 maintains infrastructure-level access and encrypted backups. The workspace is not end-to-end encrypted from AgentMarkit or its hosting provider.
The model provider you choose receives the prompts, context, and tool results sent to that model. Integrations receive the requests needed to perform the action you selected. Those companies have their own terms and privacy practices. Current providers are listed on our service providers and subprocessors page.
Technical access is not blanket permission for an AgentMarkit person to browse your workspace. We inspect private prompts, files, memory, outputs, credentials, or connected-service data only when you request support and give separate, specific written permission. Before access, we identify the machine, the material, the purpose, whether we need read-only or change access, and the expected duration. Accepting the Terms or connecting an integration is not support consent.
We may act without advance support consent when reasonably necessary to secure or isolate the service without reviewing private content, or when access is required by law. Provider personnel may separately access infrastructure under their own controls and legal obligations.
Optional personal Oura connection
Connection on your Hermes machine
The portable connector stores your personal Oura application credentials, OAuth tokens, connection status and access choices on your Hermes machine. It contacts Oura directly to read recent sleep, readiness and activity summaries, including steps. You can manage the connector code and data on your machine and disconnect Oura at any time. The connector keeps connection metadata but does not maintain a separate health database.
When you enable Coach access, relevant summaries become tool results available to your selected AI provider and may remain in conversation history. Scheduled reads require your separate choice and an agreed coaching schedule. Your hosting provider and administrators retain the access described above. Using a customer-owned hosting account changes who administers that machine; it does not remove your AI provider's handling of messages and tool results.
Using AgentMarkit's website chat or workout interfaces can still send their contents through AgentMarkit as described above. The portable connector does not change those interfaces or remove earlier connections, history or backups. Disconnecting the portable connector stops future reads and attempts revocation from the machine. If revocation fails, credentials are retained for retry with Coach access stopped.
Earlier connection through AgentMarkit
During the personal pilot, a user can connect their own Oura developer application to their Coach. AgentMarkit stores the application credentials, OAuth tokens, connection status and permission choices in private Cloudflare storage associated with that user's account and Coach. The hosted agent receives a separate, revocable connection credential. Application secrets are not included in prompts or model tool responses.
The initial connection reads recent daily sleep, readiness and activity summaries, including activity steps. When the workout page opens, AgentMarkit refreshes the recent daily summaries and sends only today's activity-step count and connection status and freshness into the workout frame. AgentMarkit does not cache the returned summaries in its connection store. The workout frame keeps that step reading in memory for the current page session and does not add it to the workout edit queue. If the user separately enables Coach access, requested summaries pass through AgentMarkit to the hosted Hermes agent and its selected model provider. The results may appear in conversation history and provider logs under those services' settings. Scheduled reads require a separate choice and use the user's agreed coaching schedule.
Disconnecting stops future Coach reads and removes the saved connection after Oura confirms revocation. If Oura is temporarily unavailable, access remains stopped and the credentials are retained only so revocation can be retried. Deleting the associated machine or account also attempts this removal. Disconnecting does not erase earlier conversation history or saved workouts.
5. Optional Gmail metadata test
This connection is optional and available only to Google accounts approved as test users while verification is pending. The connection starts only after the user selects it, reviews the in-product disclosure, and authorizes their own Google account.
What the feature can access
The feature requests only https://www.googleapis.com/auth/gmail.metadata. It uses two fixed, read-only tools to retrieve From, To, Cc, Bcc, Date, labels, internal date, and stable Gmail message or thread identifiers. It cannot send, draft, delete, or modify email. The gateway removes subjects, snippets, message bodies, attachments, and fields outside this list before returning a result.
Why it is used
The user's agent uses the filtered metadata to answer user-requested questions about relationship history and communication recency. AgentMarkit does not use Google-derived data for its own analytics, research, profiling, advertising, credit decisions, or product development.
How the data moves
When the user or their agent invokes the feature, the request goes from the user's agent through an AgentMarkit gateway and Composio to Gmail. The filtered result returns through the gateway to the user's agent on its hosted machine. If the selected model needs that result to answer the user, the result is also sent to that model provider.
What is stored
AgentMarkit's gateway database does not store the returned Gmail metadata. It stores a pseudonymous user identifier, a Composio session identifier, a hash of the private endpoint token, expiration information, and rate-limit records. Composio stores and refreshes the Google OAuth tokens and may retain connection or execution records under its settings and privacy policy. Depending on the user's instructions and the agent's behavior, filtered metadata may appear in agent chat history, files, or relationship memory on the hosted machine and in the machine's encrypted backup.
Human access and AI training
AgentMarkit personnel do not routinely read Google-derived data. We access it only with the user's specific consent for support, when necessary for security purposes, or when required by law. AgentMarkit does not use Google Workspace data to develop, improve, or train generalized or non-personalized AI or machine learning models. Any model processing is limited to the personalized, user-facing function the user requested.
Google Limited Use
AgentMarkit'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.
Disconnecting and deleting
A user can revoke future access through Google Account connections. During the test, the user can also ask us to revoke the private gateway endpoint and delete the related Composio session. Revoking access stops future Gmail requests. It does not automatically remove filtered metadata that the user's agent already saved on its machine. The data controls page explains each deletion step.
7. How long we keep information
Website activity events expire after 30 days. Browser identifiers last up to 30 days; account links expire within 60 days. Account deletion removes these links, leaving retained activity anonymous until it expires.
- Magic sign-in links expire after 15 minutes. Email sessions expire after 30 days, public demo sessions after 24 hours, and private pilot sessions after seven days.
- Contact-form records expire after 180 days.
- Account, setup, entitlement, payment-status, and operational records are kept while the service is active and afterward as reasonably needed for support, security, accounting, disputes, and legal obligations. Most of these records do not yet have an automatic deletion schedule.
- Agent workspace data remains on the machine until the user deletes it or the machine. Agent37 currently describes a seven-day encrypted recovery period after a Cloud API instance is deleted.
- Google access tokens remain with Composio until the connection or session is deleted or the authorization is revoked. Gateway access records remain until the private token expires or is revoked. Filtered metadata saved in the agent workspace follows the workspace retention above.
- Stripe and other providers keep records under their own legal and contractual retention periods.
We use the type of information, why it is needed, security risk, user expectations, and legal requirements to decide when deletion is appropriate.
8. Your choices and requests
You can ask to access, correct, export, or delete eligible AgentMarkit account information. You can also ask to delete a machine, cancel hosting, or disconnect an integration. We may need to verify that the request is yours. Some payment, security, dispute, and legal records may need to remain.
Instructions are on the data controls page. If a privacy law gives you additional rights, including a right to appeal a decision, use the privacy contact form. We will respond as required by applicable law and will not discriminate against you for making a request.
9. Cookies, browser storage, and tracking signals
AgentMarkit uses cookies and browser storage for sign-in, security, policy acceptance, setup progress, and local session state. We also use a first-party cookie and browser session storage for the website activity described above. We do not currently use this site for targeted advertising or cross-site behavioral tracking.
Do Not Track and Global Privacy Control are honored: either browser signal stops website activity collection. Sign-in and essential security functions continue to work.
10. Security
We use measures designed to protect the service, including encrypted network connections, hashed or short-lived access tokens where appropriate, restricted administrative routes, rate limits, and provider access controls. The hosting provider states that machine disks and backups are encrypted at rest. No service is perfectly secure, and we cannot guarantee that unauthorized access or loss will never happen.
If we learn of an incident affecting personal information, we will investigate, contain it, notify affected users and regulators when required, and take reasonable steps to prevent a repeat.
11. Location and children
AgentMarkit is operated from the United States. Providers may process information in the United States and other countries where they operate, which may have different data-protection laws.
The service is not intended for anyone under 18. We do not knowingly collect personal information from children. Contact us if you believe a child has provided information.
12. Changes to this policy
We will post an updated effective date when this policy changes. If a change materially affects how we use information, we will provide additional notice before the change applies when reasonably possible and legally required.
13. Contact
Use the privacy contact form. It reaches the private AgentMarkit support queue without publishing an individual's name or email address.