WorkerKit Privacy Policy

What data we hold, what we do with it, how long we keep it, and the rights you have over it.

Last Updated: November 5, 2026
Effective Date for This Revision: As provided in Section 1.4.
Version: 1.1

WorkerKit ("WorkerKit," "we," "us," or "our"), with offices at 10900 Stonelake Blvd, Austin, TX 78759, United States, operates https://workerkit.ai and the related applications, APIs, runtimes, and services described in our Terms of Service (the "Service").

This Privacy Policy explains what personal data we collect, how we use it, who we share it with, how long we keep it, and what rights you have. Capitalized terms not defined here have the meaning given in the WorkerKit Terms of Service.

Read this alongside the Terms of Service before you connect any account. WorkerKit connects to accounts you hold with third parties and runs software agents that read from and write to them. Section 2.3 (Credentials) and Section 2.4 (Connected Account Data) describe how that works, and Section 4 explains what we do and do not share.

THE SERVICE IS OFFERED ONLY IN THE UNITED STATES. WorkerKit is not offered, marketed, or directed to persons outside the United States. This offering restriction is not a data-residency guarantee and does not exclude obligations or rights imposed by applicable law. See Section 9 and Sections 2.2 through 2.4 of the Terms of Service.

1. Scope, Roles, Territory, and Changes

1.1 Scope

This Privacy Policy applies to personal data we process when you:

• visit https://workerkit.ai and any page or property that links to this Policy (the "Site");
• create or use a WorkerKit account, individually or as part of an Organizational Account;
• connect a third-party account to the Service;
• configure, deploy, or run Workers, in our Hosted Harness or in your own runtime;
• publish or install a Kit; or
• communicate with us.

It does not apply to: the practices of App Providers, Model Providers, Kit Creators, or any other third party; or personal data processed entirely within a Self-Managed Runtime that you operate and to which we have no access.

1.2 Our Role: Controller and Processor

Our role depends on the data, the purpose of the processing, applicable law, and any applicable written agreement.

We are a controller for personal data about you as a WorkerKit user: your account details, billing information, Site usage, support correspondence, and marketing preferences. This Policy governs that processing.

For customer-directed processing, such as handling Connected Account content to run a Worker, we process personal data to provide the Service under your instructions and the applicable agreement. You or your organization is responsible for having authority to provide that data and direct its processing. Where applicable law and our agreement make us a processor or service provider, those requirements apply. A Data Processing Agreement applies only if entered into with us; contact privacy@workerkit.ai about availability and applicable terms. A link or reference to a DPA does not by itself establish one. An applicable signed DPA governs to the extent it conflicts with this Policy.

If your data is in someone else's Connected Account, contact that customer first about access, correction, or deletion. We may refer requests to the relevant customer and assist as required by applicable law and our agreement. This does not limit any obligation we have to respond directly under applicable law.

1.3 Territorial Scope

We offer the Service solely in and to persons and entities located in the United States. The Service is provided in English only, priced and billed in U.S. dollars only, and operated from Austin, Texas. We do not target, solicit, market to, or intend to serve users outside the United States, and the mere accessibility of the Site from outside the United States is not an offering of the Service in any other jurisdiction.

Under the Terms of Service, access from outside the United States is prohibited. If you access the Service from outside the United States in breach of those Terms, you do so on your own initiative and at your own risk. You are responsible for the obligations that apply to your use. We make no representation that the Service is suitable for use under any non-U.S. data protection framework, but territorial restrictions do not override mandatory legal obligations. We may block, restrict, or terminate access from a jurisdiction as permitted by applicable law and the Terms.

1.4 Changes to This Policy

We may update this Policy. When we do, we will post the revised Policy and update the "Last Updated" date.

If we make a material change to how we collect, use, or disclose personal data, or a change that materially affects your rights under this Policy, we will provide at least thirty (30) days' advance notice by email to the address associated with your account or by prominent in-product notice, and the change will take effect at the end of that period. Non-material changes take effect when posted.

You are responsible for maintaining a current, active, deliverable email address. Your continued use of the Service after a change takes effect means you accept it. We may also provide "just-in-time" notices in the Service that supplement or clarify this Policy.

The Last Updated date does not establish that required notice has been delivered. Material changes take effect only after the applicable notice period, and any additional consent required by law must be obtained. This revision does not retroactively reduce commitments governing data already collected, override an applicable signed agreement, or limit non-waivable rights.

2. Personal Data We Collect

2.1 Data You Provide

• Account data: name, email address, password or federated identity, organization name, role, and profile information.
• Billing data: billing name, billing address, tax identifiers, and transaction records. We do not store full payment card numbers or crypto wallet private keys. Payment credentials are collected and stored by our payment processors.
• Support and correspondence: the content of your messages, tickets, bug reports, and any attachments, plus the email address and metadata associated with them.
• Survey and research responses, where you choose to provide them.
• Kit Creator data: if you publish a Kit, the Kit itself, its Kit Metadata, your publisher identity, and any contact details you supply.

2.2 Data Collected Automatically

• Device and connection data: IP address, browser type and version, operating system, device identifiers, time zone, and language.
• Usage data: pages and screens viewed, links clicked, features used, session timing, referring URLs, API endpoints called, request volumes, error and diagnostic data.
• Cookies and similar technologies, as described in Section 6.

2.3 Credentials for Connected Accounts

This is the most sensitive category of data we hold, and we describe it explicitly.

When you connect an account, we receive and store authentication material for it, which may include OAuth access tokens, OAuth refresh tokens, API keys, and other secrets (collectively, "Credentials").

• Stored BYOK model-provider keys use application-level encryption. Credential handling differs across integrations and sign-in flows; we do not represent that every stored Credential has separate application-level encryption, a separate per-account encryption key, or a particular key-management standard. Our current technical measures and their limits are described at https://workerkit.ai/security.
• Credentials are used to authenticate authorized requests and to maintain, refresh, test, or troubleshoot the connections and features you use. A connection may be shared by multiple Workers or authorized users within an account.
• We do not use Credentials to access your accounts for our own purposes, and we do not access a Connected Account except as directed by a Worker you configured or as necessary to operate, secure, troubleshoot, or lawfully investigate the Service.
• A Credential's scopes and permissions depend on the authorization granted by the provider and the type of Credential. WorkerKit settings do not change what someone holding the provider Credential could access directly. See Section 6.3 of the Terms.
• Deleting or revoking a Worker does not by itself delete a shared app connection or revoke its Credential at the provider. Disconnect a connection separately when it is no longer needed. Retention and deletion are described in Section 8.
• Use the provider's own controls to revoke authorizations or rotate keys when needed. Revocation can be affected by provider behavior, cached authorization, and requests already in progress. It does not recall data already delivered or undo completed actions.

Please read Section 7 (Security). No storage or transmission method is completely secure, and we do not guarantee that Credentials are protected against every threat.

2.4 Connected Account Data and Worker Activity

When a Worker runs, it reads from and writes to the Connected Accounts you authorized. The data it touches may include email, messages, files, documents, calendar entries, contacts, customer records, and any other content in those accounts, and may include personal data about people other than you.

What we process and retain depends on the feature, your configuration, and your plan. Storage is not limited to an optional transcript:

• Execution and run history. We process content to construct Model requests and carry out actions. Run prompts, reports and summaries, questions and answers, and evaluation results or explanations may be stored for run history, follow-up runs, and review or improvement features.
• Execution and activity records. We record information such as timestamps, the Kit and Worker involved, Connected Accounts and endpoints touched, actions and outcomes, Models, token counts, errors, and cost. These records may include content, such as subjects, recipients, identifiers, and error details. They are not guaranteed to be a complete record of every action. See Section 8 for retention.
• Transcripts. New supported hosted deployments default to seven-day transcript storage, with exceptions such as Workers with protected instructions. Review the Worker's actual deployment setting before running. A shortened transcript can still contain personal or sensitive data; truncation is not anonymization or redaction. Turning off transcript storage does not turn off all content storage. Authorized account users may access stored content according to their role and the features available to them.
• Memory and stored context. If you enable memory features, the facts and context you configure or that a Worker records are stored so they can be reused on later runs.
• Processing-related storage and access. Features may store content to route or complete requests. WorkerKit personnel may access stored content as necessary to operate, support, secure, troubleshoot, or investigate the Service, or comply with law and applicable agreements. Do not treat content storage as inaccessible to WorkerKit personnel or as subject to a universal zero-retention guarantee.

If you run Workers in a Self-Managed Runtime, execution happens in your infrastructure, but the data we receive depends on the client, tools, integrations, and features you use. Requests routed through WorkerKit, reports, telemetry, and synchronization features may send content to the Service. Review your runtime configuration rather than assuming that self-management means no content reaches us.

2.5 Data Transmitted to Model Providers

To generate Outputs, we transmit your Inputs, and content a Worker has read, to the Model Provider you selected or that automatic routing selected under parameters you configured. See Section 4.4.

2.6 Data From Third Parties

We may receive data about you from: App Providers, when you authorize a connection (for example, your account identifier and profile on that service); identity and authentication providers, if you sign in through one; payment processors, regarding transaction status; analytics and security vendors; and publicly available sources, for business contact and fraud-prevention purposes.

2.7 Sensitive Data

Do not use the Service to process special category data or sensitive personal information unless you have confirmed that doing so is lawful for you and appropriate for the Models, App Providers, and Kits you have selected. This includes health data, biometric data, genetic data, precise geolocation, government identifiers, financial account numbers, data concerning children, and data revealing racial or ethnic origin, political opinions, religious beliefs, trade union membership, sex life, or sexual orientation.

Do not submit sensitive personal information as ordinary profile or support data unless necessary. Account credentials themselves may be sensitive personal information, and Connected Account content may contain it. Where you direct processing of such content, you are responsible for having the required authority and for the consent, notice, assessment, and safeguards that apply to your use. Our role is described in Section 1.2. We use sensitive personal information to perform the Service, not for WorkerKit's independent profiling or advertising purposes. Customer-directed Worker analysis may produce inferences about individuals; you are responsible for lawful instructions and use of those results.

3. How We Use Personal Data

We use personal data for the purposes below.

Providing the Service

• Create and administer your account and Organizational Account.
• Authenticate you and secure your sessions.
• Connect, maintain, refresh, and revoke Connected Account authorizations.
• Configure, schedule, execute, and monitor Workers.
• Transmit Inputs to the Model Provider you selected and return Outputs.
• Make Kits available, and publish and maintain the Kit directory.
• Store run and activity records, prompts, reports, evaluation results, transcripts where enabled, memory, and other content as described in Sections 2.4, 3.2, and 8.
• Provide support and respond to your requests.

Billing and administration

• Process payments, Wallet loads, transaction fees, and refunds.
• Meter usage and enforce plan limits, rate limits, and quotas.
• Send service, transactional, security, and legal notices.
• Collect amounts owed and manage chargebacks.

Security, integrity, and abuse prevention

• Detect, investigate, and prevent fraud, abuse, spam, malicious Kits, credential misuse, unauthorized access, and violations of the Terms and the Acceptable Use Policy.
• Monitor for and respond to security incidents.
• Maintain audit and access logs.

Improving the Service and evaluating performance

• Measure and evaluate the reliability, accuracy, latency, cost, and safety of the Service, and the performance of Kits, Models, Model Providers, runtimes, and integrations, as described in Section 3.2.
• Evaluate whether a Kit succeeded at the job it states it performs, and how that varies by Model, by producing Outcome Scores as described in Section 3.2.
• Detect defective, unsafe, abusive, or misdescribed Kits.
• Analyze aggregated and de-identified usage to understand performance, reliability, and feature adoption.
• Produce and publish aggregated statistics, rankings, benchmarks, and research.
• Provide Kit Creators with aggregated analytics about their own Kits.
• Debug errors and improve reliability.
• Conduct internal research and product development.

Communications and marketing

• Send product updates, newsletters, and promotional messages, where permitted.
• Measure engagement with our communications.

Legal and compliance

• Comply with legal, regulatory, tax, and accounting obligations.
• Establish, exercise, or defend legal claims.
• Enforce the Terms, the Acceptable Use Policy, and our other policies.
• Screen against sanctions and restricted-party lists and verify location and eligibility, as described in Section 23 of the Terms of Service.

3.1 What We Do Not Do

• We do not use your Inputs, Outputs, Connected Account data, Credentials, or Operational Metadata to train, fine-tune, or improve generative AI models, our own or anyone else's. We do measure and evaluate how the Service, Kits, and Models perform. Measurement is not training. See Section 3.2.
• We do not publish private run content as part of statistics or rankings. Statistics, rankings, and Outcome Scores we publish are aggregated across users and de-identified as described in Section 3.2. This does not restrict content you choose to publish or share.
• Evaluation is not a guarantee of transient or zero-retention processing. Automated evaluation may retain scores, explanations, and findings. Personnel access is described in Section 2.4. See Section 3.2.
• We do not sell personal data, and we do not share personal data for cross-context behavioral advertising, as those terms are defined under U.S. state privacy laws.
• We do not use Credentials to access your Connected Accounts for our own purposes.
• Installing a Kit does not itself give its Creator access to your private account or run history. A Kit may nevertheless send data to a Creator-controlled destination through the access you grant. See Section 4.3.
• We do not use sensitive personal information for WorkerKit's independent profiling or advertising purposes. Customer-directed Worker analysis may produce inferences about individuals, as described in Section 2.7.

3.2 Analytics, Evaluation, and Published Rankings

We evaluate how the Service performs, including how Kits, Models, Model Providers, runtimes, and integrations perform, and we publish some of what we learn. This is governed by Section 10.7 of the Terms of Service. In summary:

What we measure. We collect and generate Operational Metadata: run counts, technical success and failure rates, error types and codes, latency, token consumption, retries, timeouts, cost, the Model selected, the Kit invoked, the categories of App Provider and scope types touched, runtime type, plan tier, and Outcome Scores as described below. Operational Metadata describes how the Service performed. Source run records and evaluation explanations may also contain personal data or content; calling a record metadata does not make it anonymous.

Outcome scoring. Automated evaluation may assess a run against the Kit's stated job or other configured criteria and record a result, category, and Model used. We call this result an Outcome Score. Scoring and other review or improvement features may process prompts, Outputs, tool results, reports, and related run content.

What may be retained. Run records, reports, scores, criterion-level reasons, explanations, findings, and proposed changes may be stored. These can include or reflect run content and are not limited to a score or an anonymous category. Turning off transcripts does not remove these separate records. Retention and personnel access are described in Sections 2.4 and 8.

Evaluators and provider retention. Evaluation may use the Model selected for a run or another evaluator supported by the feature. Provider handling depends on the provider, access mode, and applicable agreement; we do not promise that every evaluator has zero retention or is subject to the same contractual restrictions. A transcript setting or provider request option does not by itself establish zero retention across the Service or a provider. If a specific retention or evaluation restriction is essential to your use, obtain an applicable written agreement and confirm the supported configuration before supplying the data. See Section 4.4.

What we never do with it. We do not use Operational Metadata, Inputs, Outputs, Connected Account data, or Credentials to train, fine-tune, or improve any generative AI model, ours or anyone else's. Evaluation is measurement, not training.

What we publish. We may publish aggregated and de-identified statistics, rankings, leaderboards, benchmarks, comparisons, success and failure rates, Outcome Score summaries, reliability indicators, and usage trends about Models, Model Providers, Kits, Kit categories, integrations, and the Service generally. This includes results by Kit and Model pairing, for example how often a given Kit succeeds at its stated job on a given Model. We take reasonable measures to reduce the risk that published statistics can be linked to you, your organization, a Connected Account, or an individual, as described below. This does not make account-linked source records anonymous or guarantee that every inference or linkage is impossible.

Outcome Scores are estimates. Automated evaluations can be wrong, incomplete, or based on inaccurate Kit descriptions. Limited Kit checks do not establish the truth of every description or the accuracy of a score. See Sections 10.7(d) and 20(m) of the Terms of Service.

Our de-identification commitments. For data we maintain or disclose as de-identified, we commit to: (i) take reasonable measures to prevent association with, or reasonable linkage to, you, your organization, a Connected Account, or an individual; (ii) maintain and use it in de-identified form; (iii) not attempt to re-identify it except as applicable law permits to test whether de-identification safeguards satisfy legal requirements; and (iv) impose applicable contractual restrictions on recipients to whom we disclose de-identified data under an agreement. Public statistics are subject to the same de-identification standard; publication cannot guarantee what an independent third party may attempt.

Enterprise customers. Where you have a Data Processing Agreement or a separate written agreement with us, that agreement governs analytics and evaluation to the extent it conflicts with this Section.

3.3 Automated Decision-Making

We do not use personal data to make decisions producing legal or similarly significant effects about you through solely automated means, other than automated fraud, abuse, and security controls that may restrict or suspend an account. Where such a control affects you, you may contact us at privacy@workerkit.ai to request human review.

Note on your own use: if you configure a Worker to make decisions about individuals, you are the controller of that processing and are responsible for any transparency, human-review, assessment, or opt-out obligations that apply. See Section 7.7 of the Terms.

4. How We Share and Disclose Personal Data

We share personal data only as described in this Section.

4.1 Service Providers

We use third parties to provide the Service. The categories of service providers we use are: cloud hosting and compute; data storage and backup; content delivery and network security; queueing, caching, and scheduling; authentication and single sign-on; payment processing and fraud and sanctions screening; email delivery; error monitoring and observability; product analytics; customer support tooling; and automated evaluation, as described in Section 3.2.

These providers may process personal data in connection with the functions they provide. Their roles, access, retention, and permitted uses depend on the service and applicable agreements and law; this Policy does not represent that every third party operates under identical restrictions.

For information about the providers used for your intended features, or about a DPA and related provider disclosures, contact privacy@workerkit.ai. Any applicable signed DPA governs its required disclosures.

4.1.1 App Providers, Model Providers, and Integrations You Add

Providers may be accessed through your Credentials or through platform-funded access, depending on the feature and billing mode. Do not assume that every request uses a provider account you hold directly.

When you connect your own App Provider or Model Provider account, its terms and your agreement with that provider may govern its handling of data. Other features use arrangements maintained by WorkerKit. A provider's legal role depends on the actual processing and applicable agreements and law, not simply on who supplied a key or selected a Model.

Review the provider's applicable terms and data practices before use. Provider disclosures are not a guarantee by WorkerKit of that provider's conduct. See Sections 4.2 and 4.4 below, and Sections 6.6 and 8 of the Terms of Service.

For integrations you add yourself, including an MCP server, gateway, webhook, or endpoint, you are responsible for assessing the operator, requested access, and destination. Such integrations can receive content and other data through the access you grant. We do not guarantee their security or data practices. See Section 6.9 of the Terms of Service.

Evaluation features may also send content to Model Providers, as described in Sections 3.2 and 4.4. The applicable arrangement depends on the feature; there is no single universal provider classification or retention promise for all evaluation.

4.2 App Providers

When a Worker you configured acts on a Connected Account, we transmit the necessary data and Credentials to the relevant App Provider. That transmission happens at your direction, and the App Provider's own privacy policy governs what it does with the data. See Section 6.6 of the Terms.

4.3 Kit Creators, and What a Kit May Do

Installing a Kit does not itself give its Creator access to your account, Credentials, private run history, Inputs, or Outputs. A Kit Creator may nevertheless receive data through a destination used by the Kit or through content you choose to share, as described below.

Kit Creators may receive aggregated, de-identified analytics about their own Kits, including install counts, run counts, technical success and failure rates, Outcome Scores in aggregate and by Model pairing, error categories, and performance metrics. These analytics exclude the substance of your Inputs and Outputs and are subject to the de-identification safeguards in Section 3.2. See Section 10.7(i) of the Terms of Service.

A Kit runs with the access you grant it and may transmit data to destinations its Creator specifies. The Terms require Creator disclosures and prohibit undisclosed collection or transmission. WorkerKit may apply limited automated checks, security scans, or moderation; these do not verify every statement, destination, or behavior and are not a comprehensive audit, certification, or safety guarantee. See Sections 4.1, 4.2, and 5.3 of the Terms.

Review what a Kit says it does before you grant it access, grant the narrowest scope that works, and monitor what your Workers do. If you believe a Kit is collecting or transmitting data it did not disclose, report it to security@workerkit.ai.

4.4 Model Providers

We transmit Inputs and related content to the Model Provider selected for the run, including selection through supported routing features. Access may use your BYOK Credentials or platform-funded access.

Evaluation and improvement features may also transmit run content to a Model Provider, including the Model used for the run, as described in Section 3.2. Their provider handling and retention depend on the actual arrangement and supported settings. We do not represent that every such transmission is transient, excluded by a transcript setting, or subject to a universal zero-retention contract.

Model Providers have different data practices. Some retain Inputs and Outputs. Some use them for model training or improvement. Some do not. We surface each provider's disclosed practice in the Service or Documentation as a convenience, but we do not verify, control, or guarantee it.

Review the applicable Model Terms, access mode, and data settings before selecting a Model. WorkerKit's own no-training commitment does not establish a separate commitment by every Model Provider. If a particular provider restriction is essential, confirm that it applies to the actual feature and account used before sending data. A Self-Managed Runtime does not remove the terms of a Model Provider it calls.

4.5 Within an Organizational Account

If you are an Authorized User of an Organizational Account, authorized account administrators and other users may access your activity, configurations, connections, logs, prompts, reports, transcripts, and other stored content according to their roles and the available features. Your organization manages access within that account.

4.6 Legal Process, Compliance, and Safety

We may preserve and disclose personal data if we believe in good faith that doing so is reasonably necessary to:

(a) comply with any applicable law, regulation, legal process, subpoena, warrant, court order, or governmental or regulatory request, including requests from authorities outside your country of residence;
(b) enforce the Terms, our policies, or any agreement with you, including investigating potential violations;
(c) detect, prevent, or address fraud, abuse, security incidents, or technical issues;
(d) respond to claims that content violates the rights of a third party; or
(e) protect the rights, property, safety, or security of WorkerKit, our users, our providers, or the public, including to prevent death or imminent bodily harm.

Where legally permitted and consistent with our obligations, we will notify you before disclosing your data in response to legal process, so that you have an opportunity to seek protective relief.

4.7 Corporate Transactions

If WorkerKit is involved in a merger, acquisition, financing, reorganization, bankruptcy, receivership, dissolution, or sale of all or part of its assets, personal data may be transferred to the counterparty or successor as part of that transaction or diligence, subject to customary confidentiality protections. We will notify you of any such transfer that materially affects how your personal data is handled, and the successor will remain bound by this Policy or provide notice of a replacement policy.

4.8 Affiliates and Professional Advisors

We may share personal data with our corporate affiliates and subsidiaries for the purposes described in this Policy, and with our auditors, insurers, accountants, and legal counsel under duties of confidentiality.

4.9 With Your Direction or Consent

We share personal data with any other third party when you direct us to or otherwise consent, including when you use a feature that publishes or shares content.

4.10 Aggregated and De-identified Data

We may publish aggregated and de-identified statistics, rankings, benchmarks, and comparisons publicly, on the Site, in the Kit directory, in our documentation, and in marketing, research, and public communications, and may share them with affiliates and partners, as described in Section 3.2. This data is subject to our de-identification commitments in Section 3.2. We impose applicable restrictions on recipients under an agreement; we cannot guarantee the conduct of independent visitors to public statistics.

5. Content You Publish or Share

Certain features let you publish or share content, including publishing a Kit to the directory and sharing configurations or results by link. Anything you publish or share this way may be viewed, copied, and retained by anyone with access, and we cannot retrieve or unpublish it from third parties once shared. Do not include personal data or confidential information in content you make public.

6. Cookies and Similar Technologies

6.1 What We Use

• Necessary storage. Used for functions such as authentication, session management, carrying you back to the right page after you authorize an app, and security. Most is browser storage rather than cookies. Your browser may allow you to block it, but doing so can prevent parts of the Service from working.
• Site analytics. One web analytics tool records page views and usage so we know what to improve. It may run on public and signed-in pages, subject to the controls described below. We do not enable its advertising features.
• Campaign measurement. The First Workflow application page loads the LinkedIn Insight Tag to measure applications attributed to LinkedIn ads. The tag can use cookies and send page URLs, referrers, IP addresses, browser and device information, and timestamps to LinkedIn. Our application conversion event contains a conversion identifier; we do not include application answers, names, email addresses, or company details in that event. LinkedIn's handling is described in its Privacy Policy.

We do not use session replay. Google Analytics advertising features remain disabled.

Site analytics is about pages, not about your Workers. It is a separate thing from the records the Service keeps when a Worker runs, which are described in Section 3.2 and are not governed by this Section 6. See Section 6.2.

6.2 Your Choices, and the Limits of Them

We do not currently provide a cookie banner or on-site cookie toggle. Site analytics and campaign measurement may load by default unless a supported privacy signal or browser control prevents them. The choices described here do not limit consent or opt-out rights required by applicable law.

You can stop Site analytics and campaign measurement yourself. Block cookies or scripts for this site in your browser settings or with an extension, or turn on Global Privacy Control, which we honor as described in Section 6.3. Disabling strictly necessary storage will prevent parts of the Service from working. Information about browser cookie controls is available at https://allaboutcookies.org.

These browser choices concern Site analytics and campaign measurement. They do not disable Service records, including run and activity records, prompts, reports, evaluation results, memory, or transcripts controlled separately by deployment settings. Operational records are used to operate, meter, secure, support, and bill the Service. Content storage is not universally off by default, and transcript settings do not control all retained content. See Sections 2.4, 3.2, and 8.

6.3 Global Privacy Control

When the Site detects a Global Privacy Control (GPC) signal before measurement initializes, it suppresses loading of the Site analytics and LinkedIn Insight tags, regardless of a previously stored analytics choice. We also check this signal before sending an application conversion event. This check is not a promise that changing a browser signal after initialization removes previously sent data or already-set storage. Reload the page after changing the signal. We also honor applicable legal requirements for opt-out preference signals. GPC does not disable the Service records described in Section 6.2.

6.4 Do Not Track

We do not currently respond to browser "Do Not Track" signals, because no common standard for them has been adopted. We do respond to GPC as described above.

7. Security

We use measures designed to reduce the risk of accidental loss and unauthorized access, use, alteration, and disclosure, including HTTPS for public Service endpoints, account authentication, permission checks, operational logging, and encryption mechanisms whose coverage varies as described in Section 2.3. These are controls in a shared service, not a dedicated environment, a comprehensive audit record, or a guarantee of isolation from every defect or attack. Our current practices and their limits are described at https://workerkit.ai/security. We do not claim a particular certification or security framework compliance through this Policy.

No method of transmission over the internet and no method of electronic storage is completely secure. While we work to protect your personal data, we cannot and do not guarantee its absolute security, and any transmission is at your own risk.

We do not warrant that the Service is secure or will remain secure against every threat. Descriptions of security practices are not additional warranties or certifications. Security measures reduce risk; they do not remove it, and practices may change subject to applicable law and our agreements. If you are not willing to accept the risk that your personal data or Credentials could be exposed, lost, or altered, do not connect the account in question or use the Service. Nothing in this Section removes obligations under applicable law, this Policy, or an applicable signed agreement. See Sections 20 and 21 of the Terms of Service.

The security of your data also depends on you. You are responsible for keeping your account credentials confidential, enabling available account protections, granting Workers the narrowest access that works, and promptly revoking access you no longer need. Notify us immediately at security@workerkit.ai if you believe your account or a Connected Account has been compromised.

Breach notification. If we become aware of a personal data breach affecting your personal data, we will notify you and any applicable regulator as required by law and within the timeframes in any applicable signed DPA.

8. Data Retention

We retain personal data as needed for the purposes described in this Policy, including providing and securing the Service, supporting account administration, complying with legal, tax, accounting, and regulatory obligations, resolving disputes, and enforcing agreements. There is no single retention period for all Service data. We consider the type and sensitivity of the data, the feature and configuration, account status, operational need, applicable agreements, and legal requirements.

Data subject to a legal hold, active investigation, or unresolved dispute may be retained until the matter and related obligations are resolved. Residual copies may remain in archived records or backup and recovery systems where used. This Policy does not promise a fixed backup rotation or deletion deadline for every copy. Any mandatory deletion requirement or applicable signed retention commitment continues to apply.

Where we act as a processor or service provider, applicable law and any applicable signed agreement govern retention instructions and exceptions. Contact privacy@workerkit.ai with a specific retention or deletion requirement before relying on the Service for that requirement.

9. Where Your Data Is Processed

We are based in the United States and offer the Service only in the United States. This is not a guarantee that every provider, integration, support function, or processing activity is located in the United States. Data may be processed where the providers and integrations used for the feature operate, subject to applicable arrangements and law. This Policy does not provide a universal U.S.-only residency commitment.

We do not offer or direct the Service to persons outside the United States, or represent that a particular transfer mechanism or local representative arrangement is available for your use. See Section 1.3 and Sections 2.2 through 2.4 of the Terms of Service. Contact privacy@workerkit.ai before relying on any specific transfer or residency requirement.

If you access the Service from outside the United States in breach of the Terms of Service, you do so on your own initiative. Data protection laws in processing locations may differ from those where you are located. Nothing here replaces a legally required transfer safeguard or excludes obligations imposed by applicable law.

10. Your Rights and Choices

10.1 Rights Available to You

We extend the following rights to all U.S. users, regardless of state, with respect to personal data we hold about you as a controller. Residents of states with comprehensive privacy laws, including California, Texas, Colorado, Connecticut, Virginia, Utah, Oregon, Montana, and others, have these rights by statute; we honor them for everyone as a matter of policy.

• Right to know / access. Confirm whether we process personal data about you and obtain a copy, along with the categories, sources, purposes, and recipients.
• Portability. Receive certain personal data in a structured, commonly used, machine-readable format, and have it transmitted to another controller where technically feasible.
• Correction. Have inaccurate personal data corrected.
• Deletion. Have personal data deleted, subject to exceptions.
• Restriction. Restrict processing in certain circumstances.
• Objection. Object to processing based on legitimate interests, and object at any time to direct marketing.
• Withdraw consent. Where processing is based on consent, withdraw it at any time. Withdrawal does not affect the lawfulness of processing before withdrawal.
• Opt out of sale, sharing, and targeted advertising. We do not sell or share personal data or use it for targeted advertising, but you may exercise this right and we will honor GPC signals as described in Section 6.3.
• Limit use of sensitive personal information. You may request limits on use as provided by applicable law. We do not use it for WorkerKit's independent profiling or advertising purposes; customer-directed processing is described in Section 2.7.
• Non-discrimination. We will not deny service, charge a different price, or provide a different quality of service because you exercised a privacy right.
• Appeal. If we decline your request, you may appeal by replying to our response or writing to privacy@workerkit.ai with "Privacy Appeal" in the subject line. We will respond to appeals within the period required by applicable law.

10.2 How to Exercise Your Rights

Submit requests to privacy@workerkit.ai, or by mail to WorkerKit, Attn: Privacy, 10900 Stonelake Blvd, Austin, TX 78759, United States.

We will verify your identity before acting, typically by confirming control of the email address on your account, and we may request additional information for sensitive requests. An authorized agent may submit a request on your behalf with written authorization, and we may ask you to verify the agent's authority directly.

We respond within the time required by applicable law, generally 45 days, extendable by a further 45 days where permitted and where we notify you. We may decline a request where we have a lawful basis to do so, and will explain why.

10.3 Account Deletion

You may request deletion by emailing privacy@workerkit.ai or using the deletion controls available in your account. We may require identity verification and confirmation before acting. Some shared-account or multiple-membership situations require support assistance rather than a single self-service action. Contact us to confirm which account, memberships, Workers, and connections are affected before proceeding. Completed deletion actions may be irreversible.

Processing a deletion request may disable access or remove active records, but it does not mean every related record or archive has been erased. Identity, account, billing, consent, audit, and other records may remain for the purposes and subject to the requirements described in Section 8. Shared connections and organization-held data can have a different lifecycle from an individual membership. Revoke or disable affected Workers and provider credentials separately where needed.

Deleting your WorkerKit account does not revoke the authorizations you granted at each App Provider. Revoke those directly with each App Provider as well.

We may retain data where required for legal, regulatory, tax, security, fraud-prevention, or dispute-resolution purposes.

10.4 Marketing Communications

You may opt out of marketing emails using the "unsubscribe" link in any such message or by emailing privacy@workerkit.ai. Opt-out requests may take a reasonable time to process. You cannot opt out of service, transactional, security, billing, and legal communications while you maintain an account.

10.5 Users Outside the United States

The Service is not offered outside the United States. This offering restriction does not exclude any privacy right or obligation that applicable law makes mandatory.

If you are outside the United States and believe we hold personal data about you, contact privacy@workerkit.ai. We will assess and respond to your request under applicable law, including any required access, deletion, appeal, or complaint rights and lawful exceptions. This does not authorize access to the Service in breach of the Terms.

Data protection contact: privacy@workerkit.ai

10.6 Requests About Data in a Customer's Connected Account

If your personal data is in the Service because a WorkerKit customer connected an account containing it, contact that customer first. If you contact us, we may refer your request to them and assist under applicable law and our agreement. We do not ordinarily access or modify customer-controlled data in response to an unverified third-party request, but nothing here limits obligations we have to respond or act directly under applicable law.

11. Children

The Service is not directed to and may not be used by anyone under 18 years of age. We do not knowingly collect personal data from children. If we learn we have collected personal data from a person under 18, we will delete it and terminate the associated account. If you believe a child has provided us personal data, contact privacy@workerkit.ai.

12. U.S. State Privacy Disclosures

This Section supplements the rest of this Policy for residents of U.S. states with comprehensive privacy laws, including the California Consumer Privacy Act as amended by the CPRA, the Texas Data Privacy and Security Act, and the comparable laws of Colorado, Connecticut, Virginia, Utah, Oregon, Montana, and other states as they take effect.

We are headquartered in Austin, Texas. We honor applicable obligations under the Texas Data Privacy and Security Act and other applicable state privacy laws, including the rights and processes described below.

12.1 Categories of Personal Information

In the preceding twelve months, we have collected the following categories of personal information, as defined by the California Consumer Privacy Act (CCPA/CPRA):

De-identified and aggregate data. A legal exclusion for de-identified or aggregate data applies only where the data and its handling actually satisfy the requirements of applicable law, including any required safeguards, public commitments, and recipient contracts. See Section 3.2. Account-linked Operational Metadata, evaluation explanations, and other identifiable source records remain personal data where applicable; they are not excluded merely because we also publish de-identified statistics. Rights requests remain available for identifiable personal data, subject to applicable law and its exceptions.

Sensitive personal information. Account credentials, including Credentials, are "sensitive personal information" under the CCPA. Connected Account content may also contain sensitive personal information. Our role depends on the processing and applicable arrangements as described in Section 1.2. We do not use sensitive personal information for WorkerKit's independent profiling or advertising purposes. Customer-directed Worker analysis may produce inferences as described in Section 2.7. You may contact privacy@workerkit.ai about applicable rights to limit use; nothing here excludes a right or obligation imposed by law.

12.2 No Sale or Sharing

We do not sell personal information and we do not share personal information for cross-context behavioral advertising, as those terms are defined by the CCPA and equivalent state laws. We have not done so in the preceding twelve months. We do not sell or share the personal information of any individual, including anyone under 16.

12.3 Retention

We retain each category of personal information under the criteria described in Section 8 and any applicable legal or signed contractual requirements.

12.4 Exercising Your Rights

See Section 10. Requests to privacy@workerkit.ai. Authorized agents may submit requests with proper authorization.

12.5 Notice of Financial Incentive

We do not offer any financial incentive or price or service difference in exchange for personal information.

12.6 Shine the Light

California residents may request information about disclosures of personal information to third parties for their direct marketing purposes. We do not make such disclosures.

12.7 Texas Notice

As required by the Texas Data Privacy and Security Act: we do not sell personal data, and we do not sell sensitive personal data or biometric personal data. Texas residents may exercise the rights in Section 10 by contacting privacy@workerkit.ai, and may appeal a denial as described in Section 10.1. If an appeal is denied, you may submit a complaint to the Texas Attorney General at https://www.texasattorneygeneral.gov/consumer-protection/file-consumer-complaint.

12.8 Non-Waivable Rights

Nothing in this Policy, the Terms of Service, or any other agreement waives or limits any right or remedy that applicable U.S. state privacy law provides and does not permit to be waived, including the private right of action under California Civil Code § 1798.150. See Section 21(g) of the Terms of Service.

13. Third-Party Sites and Services

The Site and Service link to and integrate with third-party websites, applications, and platforms, including App Providers, Model Providers, payment processors, Creator-published Kits, and integrations you add, such as an MCP server, gateway, webhook, or endpoint. We do not control or guarantee a third party's independent privacy practices. The applicable third-party terms and processing arrangements govern its handling of data. This Policy describes WorkerKit's processing and disclosures; it does not remove obligations we have under applicable law or an applicable signed agreement concerning a provider we use. See Section 4.

14. Governing Law

This Privacy Policy is governed by the laws of the State of Texas, without regard to conflict of law principles, except to the extent applicable law provides rights or obligations that cannot be waived or varied by contract, which continue to apply regardless. Dispute resolution is governed by Sections 25 and 26 of the Terms of Service.

This choice of law does not itself determine whether another jurisdiction's mandatory privacy law applies.

15. Contact Us

WorkerKit
10900 Stonelake Blvd
Austin, TX 78759
United States

• Privacy requests and questions: privacy@workerkit.ai
• Security reports: security@workerkit.ai
• General support: support@workerkit.ai
• Legal notices: legal@workerkit.ai

Related documents:

• Terms of Service: https://workerkit.ai/terms
• Acceptable Use Policy: https://workerkit.ai/aup
• Data Processing Agreement inquiries: privacy@workerkit.ai
• Security overview: https://workerkit.ai/security