Privacy Policy

1. Scope

HeyMall, Inc., doing business as AgentSky (“AgentSky,” “we,” “us,” or “our”), operates agentsky.dev, the app, APIs, and CLI — together, the “Service.” This policy explains what personal data we collect, why, how long we keep it, and who we share it with. It applies to everyone who visits our site, runs an agent, or reaches an agent through a channel we operate.

Our Terms of Service govern the contract; this policy describes the practice. Where the Terms grant us a license over your Content, the setting that controls it is described in section 4 below and in section 7 of the Terms.

2. What we collect

Account data — name, email, organization, and authentication identifiers from the identity provider you sign in with.

Billing data — plan, credit balance, usage counts, invoices, and the payment identifiers our payment processor returns to us. We never receive or store your full card number.

Content — the prompts, files, connector data, and agent configuration you provide (“Input”), and the output, logs, and execution traces your agents produce (“Output”). Content routinely contains whatever you put in front of an agent, including source code and data pulled through connectors.

API request records — for every request made to our developer API with an API key: the full request and the full response, including prompts, files, and model output, every request header except credentials, which we reduce to a short prefix, the IP address and country the request came from, the client software it identifies as, the key and account that made it, the model and provider that served it, and its tokens, cost, timing, and outcome.

Connector data — the data an agent reads or writes through a connector you authorize, for the duration of the request. Connector access tokens are held by our managed OAuth broker, not stored by AgentSky, except Google connections made through AgentSky sign-in, described in section 4A.

Device and usage data — IP address, browser and operating system, pages viewed, and requests made, collected through our servers and through analytics cookies.

Support and correspondence — what you send us by email or through support channels.

3. How we use it

To provide the Service: authenticate you, run and recover your agents, route requests to models and connectors, deliver messages over your channels, and show you your workspace.

To bill you: meter usage, charge your balance, and produce invoices.

To keep the Service safe: detect abuse, fraud, and attacks, enforce our Terms, and debug failures.

To comply with law and to establish, exercise, or defend legal claims.

To correspond with you about the Service, and — if you have agreed to it — about our products.

To review Content and use it to develop, evaluate, and improve the Service and AI models, including by training models. For Content submitted on or after October 20, 2026, this applies by default across the Service, including the API, unless you opt out or your Workspace is under Zero Data Retention — see review and model improvement in section 4. Publishing results and licensing Content in anonymized form apply only under trace contribution.

4. The settings that control your Content

Storing your Content and using your Content are separate, and each has its own setting. Each setting's default is stated below, and you can change it at any time. Section 7 of the Terms states the license each setting grants.

Trace history — when enabled, we store your Content so we can display it back to you: session history, replay, and debugging for you and your Workspace members. We do not use Content stored under this setting for anything else, and we do not access it except as necessary to operate, secure, or troubleshoot the Service, or as required by law.

API request records — regardless of your settings, we store the API request records described in section 2. We use them only to operate, secure, and troubleshoot the Service, detect and investigate abuse and fraud, enforce our Terms, bill you, and meet legal obligations. They are not trace history, and trace contribution does not apply to them.

Processing-related storage — regardless of your settings, we hold Content for as long as needed to execute a request. We do not access it except as necessary to operate, secure, or troubleshoot the Service, or as required by law.

Trace contribution — on by default for Content submitted on or after October 20, 2026. It lets us use your Content, with identifying details removed, to improve AgentSky and the agents and models we route to, to publish comparisons on our Playground and leaderboards, and to share it in anonymized form. We do not try to link it back to you. You can turn it off any time by writing to support@agentsky.dev from your account email; it then stops for what you send afterwards.

Review and model improvement — on by default for Content submitted on or after October 20, 2026. Your chats may be reviewed and used to improve AgentSky and AI models, including by training models; we reduce the personal information in them first, and we do not sell them under this setting. You can turn it off any time with “Improve the model for everyone” in Settings, or by writing to support@agentsky.dev; it then stops for what you send afterwards.

Categorization of Inputs — we categorize Inputs in anonymized form to track and share usage metrics. Where trace contribution is off, Inputs are not retained or associated with you or your account after categorization.

Provider training routing — some model providers store or train on what is sent to them. Your Workspace carries separate settings for paid and free models controlling whether we may route your requests to providers that do not offer a training opt-out. Where a provider offers an opt-out, we take it.

Zero Data Retention — for Enterprise Workspaces under an enterprise agreement. Nothing is kept beyond what it takes to run each request, except API request records, and none of the uses above apply. Where the model provider offers Zero Data Retention, we pass it through. Write to support@agentsky.dev for an enterprise agreement or a data processing addendum.

4A. Google user data and Limited Use

This section applies to Google user data that AgentSky receives through its own Google API access — when you sign in with Google, or connect Gmail, Google Calendar, or Google Drive through AgentSky sign-in — and to information derived from it. For that data it overrides any other section of this policy that would allow a broader use, including service and model improvement, trace contribution, categorization, sharing, and retention. A Google app you connect through a third-party connector provider is authorized by that provider under its own Google access, and the connector data terms in section 2 apply to it.

What we access. When you authorize Google access, we process only the categories of data covered by the permissions you grant. Sign-in uses your name, email address, and profile picture. Gmail may give access to message content and attachments, senders and recipients, subjects, timestamps, and labels. Google Calendar may give access to your calendar list, event titles and descriptions, participants, times, and free/busy availability. Google Drive may give access to the names, metadata, and content of the files in your Drive, and to the files an agent creates or opens for you. Connecting Google does not by itself authorize any action beyond your instructions.

How we use it. We use Google user data only to provide or improve the user-facing features you request from an agent: finding, summarizing, and drafting or sending email, organizing your inbox, checking availability and creating or updating calendar events, and finding, reading, summarizing, creating, and updating Drive files. An agent acts on Google data only within a request you make or a workflow you set up.

What we never do. We do not sell Google user data, use it for advertising, or use it to develop, improve, or train generalized AI or machine-learning models, and it is never contributed as a trace or licensed to others. These restrictions also cover copies, summaries, logs, and de-identified or aggregated information derived from Google data. Your account settings and your choice of model do not waive them.

Who receives it. We share Google user data only with the service providers needed to deliver the feature you asked for: our hosting and sandbox infrastructure, and the model provider for the agent or model you selected, which processes it to generate the response you requested. A provider that is not bound to the same restrictions on sale, advertising, and generalized model training is not eligible to receive Google user data. When you connect Google through AgentSky sign-in, the OAuth credentials are held encrypted by our identity service and are never sent to agents, models, or your browser.

Human access. No person at AgentSky reads your Google user data unless you give us affirmative permission for specific data, it is necessary for security purposes such as investigating abuse, it is required to comply with applicable law, or the data has been aggregated and anonymized for internal operations as Google's Limited Use requirements permit.

Retention. Google user data can appear in your sessions, task results, files, and action records while those are needed to provide the features you requested, and the retention periods in section 7 apply. Retaining it does not permit any use this section excludes.

Disconnecting and revoking. You can disconnect Gmail, Google Calendar, or Google Drive in Settings → Connectors at any time; agents then stop using it. Disconnecting does not delete records already saved in your workspace. You can also revoke AgentSky's access entirely at https://myaccount.google.com/permissions. Deleting your AgentSky account does not delete anything in your Google account.

Deletion. To ask us to delete Google user data and information derived from it, delete the sessions or agents that contain it, delete your account as described in section 9, or write to support@agentsky.dev from the address on your account. We will verify the request and delete the data within the windows in section 7, except where the law requires us to keep it.

AgentSky's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

5. Model providers

Running an agent sends your Content to the model provider you selected. Those providers process what they receive under their own terms, and their own retention and training practices apply. We describe each provider's practice accurately to the best of our knowledge and update it as they change.

The model picker identifies the provider that will receive your Content. Because provider practices change independently of AgentSky, review that provider's current data policy before selecting it.

If you do not want your Content sent to a provider that retains it, leave provider training routing off and choose a model whose provider commits to zero retention, or use an Enterprise Workspace.

6. Who else receives data

Service providers who process data on our behalf under contract: cloud hosting and sandbox infrastructure, our identity provider, our payment processor, error monitoring, analytics, and email delivery. They may use the data only to provide their service to us.

Platforms you connect. When you attach a connector or a channel, data flows to that platform at your direction and under its terms.

Legal and safety recipients, where we are required by law or where disclosure is necessary to protect rights, safety, or the integrity of the Service.

A successor, if we are involved in a merger, acquisition, or sale of assets. We will give notice before your data becomes subject to a different privacy policy.

We do not sell personal data, and we do not share it for cross-context behavioral advertising.

7. How long we keep it

Agent runtime and stored state — until you delete the agent, then purged within 30 days from active systems and 90 days from backups.

Trace history, when the setting is on — until you delete the session or the agent, subject to the same purge windows.

Content covered by trace contribution — up to 24 months, so that harness and model comparisons remain valid over time. Anonymized, aggregated results derived from it may be kept indefinitely.

API request records — kept indefinitely.

Other request, security, and abuse logs — ordinarily 30 days, longer where an investigation or legal obligation requires it.

Account data — for the life of the account, then purged within 30 days of deletion.

Billing records — for as long as tax, accounting, and payment-dispute obligations require, generally up to seven years.

Content under Zero Data Retention — not written to durable storage, except in API request records; otherwise held only for the duration of the request.

8. Security

Agents run in isolated, managed sandboxes. Data is encrypted in transit and at rest, access to production systems is limited to the people who need it and is logged, and connector tokens are held by our managed OAuth broker rather than in our application database.

No system is perfectly secure. Do not put credentials or secrets into a prompt; use a connector or a secret reference instead.

9. Your rights

You can access your agents' stored state through the Service, delete an agent, and change the settings in section 4 at any time. To delete your whole account, open Settings and choose Delete account; agentsky.dev/account/delete explains what is deleted and what is kept. If you cannot sign in, write to support@agentsky.dev. To export your account data or correct account details that you cannot edit, write to support@agentsky.dev.

Depending on where you live, you may also have the right to request a copy of your personal data, ask us to correct or delete it, object to or restrict a use, withdraw consent, and complain to a supervisory authority. We will not treat you differently for exercising a right.

To make a request, write to support@agentsky.dev from the address on your account. We respond within the period the applicable law requires, and we may need to verify your identity first.

10. International transfers

We operate from the United States, and our infrastructure and model providers may process data in the United States and other countries. Where we transfer personal data out of the European Economic Area, the United Kingdom, or Switzerland, we rely on the European Commission's Standard Contractual Clauses or another lawful transfer mechanism.

11. Children

The Service is not directed to children under 16, and we do not knowingly collect their personal data. If you believe a child has given us personal data, write to support@agentsky.dev and we will delete it.

12. Changes to this policy

We may update this policy. Material changes will be announced through the Service or by email before they take effect. A change that would widen how we use Content applies only to Content you submit after the change takes effect; we do not apply a new use retroactively.

13. Contact

Questions, requests, or complaints about privacy: support@agentsky.dev.