Privacy Policy | Tensor Admin

1. Scope and our role

This Privacy Policy explains how Tensor Autonomous LLC, which provides Tensor Admin ("Tensor," "we," "us," or "our") collects, uses, discloses, and retains personal information when you visit our website, create or use a Tensor Admin workspace, contact us, or interact with our AI operations platform and related services (collectively, the "Services").

Organizations use the Services to set up automations (work they hand to Tensor) that receive requests and carry them out through email, requests typed in the app, connected accounts (such as Google and Microsoft 365), and websites operated in a browser on the customer's behalf. Each time an automation does its work is a run. When we process communications, documents, contacts, request inputs, or other content on a customer's instructions ("Customer Content"), the customer generally determines why and how that information is processed and Tensor acts as its service provider or processor. The customer is responsible for its notices, permissions, legal bases, and instructions to Tensor. If you interact with one of our customers, direct requests about that customer's Customer Content to the customer first.

Tensor is responsible for personal information we use for our own website, account administration, security, support, billing, and business operations. A customer agreement or feature-specific notice may provide additional terms. A data processing addendum is available on request for Enterprise customers. If those terms conflict with this Policy for Customer Content, the applicable agreement controls to the extent permitted by law.

2. Personal information we collect

The information we collect depends on how the Services are configured and used. It may include:

Account and workspace information, such as name, work email address, telephone number, organization, role, workspace membership, authentication identifiers, settings, and support history.
Communications and contact information, such as the content of emails and requests a customer sends in (including forwarded emails and notification emails from website forms), sender and recipient names and email addresses, form submissions, meeting or appointment details, and message status. This may include summaries and extracted follow-up details.
Automation and request information, such as requests, prompts, instructions, schedules, request and run status, inputs and outputs, content read from or written to connected accounts and websites a customer has shown Tensor, approval decisions and the limits a customer sets, exception details, browser steps, and receipts generated to show what a request did. Receipts may include screenshots or files when the work and customer settings require them. When Tensor works in a website for you, it may keep screenshots or a recording of its own browser session as part of the receipt, for up to 7 days on Starter, 30 days on Operator and 90 days on Operations Team.
Documents and automation history, such as files you upload or link to an automation, records of what a customer has shown Tensor, and each automation's change history, including corrections.
Integration and configuration information, such as connected-provider account identifiers, calendars, mailboxes, spreadsheets, email settings, API configuration, and encrypted access tokens or credentials used to operate a customer-selected integration or website. A customer can connect Google accounts, Microsoft 365 (Outlook mail and calendar, and Excel workbooks in OneDrive), and other apps connected with a key or a sign-in (such as HubSpot, QuickBooks, or Xero). Tensor reads and writes only what an automation needs there, and the AI models that do the work never see the passwords, keys, or access tokens. If a customer connects a password manager for website sign-ins, Tensor borrows a sign-in when a request needs it and never stores it.
Billing and commercial information, such as plan, subscription and customer identifiers, invoices, usage, extra credits purchased, payment status, and transaction references. A third-party payment processor handles payment-card and bank details in the normal checkout flow; Tensor stores the references needed to administer the account rather than full payment-card numbers.
Device, usage, and security information, such as IP address, browser and device attributes, timestamps, pages or routes used, request and audit identifiers, sign-in and authorization events, feature usage, diagnostics, crash reports, fraud or abuse signals, and security logs.
Website, consent, and acquisition information, such as cookie and privacy preferences, opaque browser and session identifiers, sanitized landing and referrer URLs, UTM values and advertising click identifiers, campaign source, and information submitted through contact, signup, or demo experiences. If optional analytics is enabled, we may also process page-view and product-event data and a one-way hash of a lead identifier.
Other information a user or customer chooses to provide. Customer Content can contain sensitive or regulated information depending on the customer's use case. Customers must not provide information they lack authority to process and must configure appropriate safeguards for their use case.

Sharing a run with Tensor. If you choose "Share this with Tensor" on a run, we receive a copy of that one run's record (what was asked, the instructions it ran under, its steps, what it read and wrote, and its result) for the purpose you pick: help with that run, or helping us improve Tensor. Before you share, we show you exactly what will be included. A share never includes passwords, keys or account access, or the contents of attached files. We don't use shared runs to train models. You can remove a share at any time from the run or from Controls & Audit, and we delete the copy; we keep only a record that a share existed and when it was removed. Ratings (thumbs up or down, with an optional note) stay in your workspace.

Try it live. If you describe your work on our website to get a proposal and give a work email for it, we use what you tell us to make and send the proposal, to follow up with you about it, and to improve the product and the Library of ready-made automations. While you talk with Tensor there, we keep what you type, with contact details removed, for up to 90 days to see how the conversation went and to improve it; until you give an email, it isn't linked to you. Once you give an email, we keep what you gave us for 12 months, unless you become a customer or ask us to delete it sooner, and we never sell it.

Business outreach. We may contact businesses about Tensor using business contact details from public sources, such as business listings and company websites. Every such email includes a way to opt out, and we honor it. To ask us to delete your business contact details, email support@tensoradmin.com.

Website chat. If you use the chat on our website, we keep the text of your questions, without your IP address or identity, for up to 90 days to improve our answers.

Abuse prevention. To prevent abuse of our website and Try it live, we keep limited security records, such as a scrambled form of your network address or email and the reason for a block, for up to 30 days, or longer for an address confirmed as abusive.

3. Sources of information

We collect information:

Directly from you when you create an account, configure a workspace, submit a form, communicate with us, make a privacy choice, or use the Services.
From our customers and their authorized users, including the instructions, contacts, files, communications, and fixtures they place in a workspace.
From people who interact with a customer's work, such as email senders and recipients, form submitters, and meeting participants.
From customer-selected providers and integrations, such as email, calendar, spreadsheet, payment, identity, and browser providers, and websites a customer has shown Tensor.
Automatically from browsers, devices, servers, and security systems when the website or Services are used.
From public or third-party services when a customer directs a request to retrieve or update information there and has authority to do so.
From public sources, such as business listings and company websites, for business contact details we use to tell businesses about Tensor.

4. How we use information

We use personal information to:

Provide, operate, authenticate, maintain, and support the Services.
Receive requests and carry out customer-configured automations through email, requests typed in the app, connected accounts, and websites operated in a browser on the customer's behalf.
Generate summaries, proposed work, request outputs, and other AI-assisted results requested by a workspace.
Apply roles, approvals, limits, safety controls, audit trails, retention settings, receipts, and exception handling.
Configure workspaces, route incoming requests, schedule work, and synchronize customer-selected systems.
Process subscriptions, measure usage, administer monthly and extra credits, prevent unexpected spend, collect amounts due, and maintain financial records.
Respond to support, security, legal, and privacy requests and send service, account, billing, and policy communications.
Detect, investigate, and prevent fraud, abuse, security incidents, unauthorized access, and violations of our terms.
Debug and improve reliability, accessibility, safety, and product performance using appropriately limited operational data.
Measure website and campaign performance when the relevant optional consent is enabled, and attribute a form submission to the sanitized source information carried with that request.
Comply with law, enforce agreements, establish or defend legal claims, and protect users, Tensor, and others.

We may aggregate or de-identify information and use it for lawful analytics, reliability, capacity planning, and product improvement where it is not reasonably linkable to an individual. We do not attempt to re-identify information that we maintain as de-identified except to test whether our de-identification measures work.

5. AI-assisted processing

The Services use AI models from third-party providers to read requests, summarize emails and other content, propose or carry out work, and produce receipts. We use a primary AI model provider, and backup AI model providers only when the primary is unavailable; a backup provider receives the same information the primary would have received for that function. Information needed for a requested function may be sent to one or more of these providers. Provider handling is governed by the applicable provider configuration and contract. Our AI model providers may keep the content we send them for up to 55 days to monitor for abuse, under their own terms, longer only for content flagged as possible misuse (up to 2 years) or where the law requires it, and don't use it to train their models. We don't use your content to train AI models.

Features that let a customer show Tensor how a piece of work is done or correct an automation keep customer-specific records, such as the automation's change history, derived from Customer Content. These features support the customer's workspace and instructions. Customers decide whether to enable them, what material to provide, and what approval or human-review controls apply.

Tensor Admin is designed to expose approvals, receipts, and exceptions rather than hide consequential work. AI outputs can be wrong. Customers remain responsible for reviewing approvals, receipts, and outputs and for deciding whether an automated or AI-assisted process is appropriate. The Services are not intended to make a final decision about an individual's eligibility for credit, employment, housing, insurance, healthcare, legal services, or another similarly significant service without the customer's appropriate authority, notice, testing, and human oversight.

6. How we disclose information

We disclose personal information only as needed for the purposes described in this Policy, including to:

Infrastructure and data providers for database, authentication, application hosting, cloud infrastructure, email delivery, browser-runtime components, queues, encryption, and receipt storage where configured.
AI model providers (a primary provider, and backup providers used only when the primary is unavailable) for model and AI-assisted functions used by the Services.
Payment providers for checkout, subscriptions, invoices, payment processing, and fraud prevention.
Public-content and reliability providers for public website content and configured error monitoring.
Optional analytics and tag-management providers, only when those integrations are configured and the relevant browser consent permits them.
Customer-selected integrations, websites, recipients, and service providers when an authorized user directs or approves a request, message, transfer, or synchronization.
Professional advisers, auditors, insurers, financing sources, and service providers that support our business under appropriate confidentiality or data-protection obligations.
Government authorities, courts, counterparties, or others when we reasonably believe disclosure is required by law, needed to protect rights or safety, or necessary to investigate fraud, abuse, or a security incident.
A buyer, investor, lender, or successor in connection with a merger, financing, reorganization, sale of assets, or similar transaction, subject to appropriate safeguards and notice where required.

The service providers that process personal information for us fall into these categories:

AI model providers: read requests, write drafts, and do the work, including operating websites in a browser. A primary provider, and backup providers used only when the primary is unavailable, which receive the same information.
Cloud hosting and database: application hosting, the database, sign-in, email delivery, the isolated runners that do the work, and encrypted storage for receipts and files.
Payment processing: checkout, subscriptions, invoices, and payments.
Error monitoring: finding and fixing faults in the Services.
Content delivery and security: bot protection on our website's chat and Try it live.
Email connection: connecting a customer's Gmail account, and reading and sending its mail when the customer directs or approves work there.

A list of our service providers is available to customers on request under their agreement.

Apps a customer connects, such as Google (Gmail, Calendar, Sheets, Drive, and Docs), Microsoft 365 (Outlook mail and calendar, and Excel workbooks in OneDrive), and other apps connected with a key or a sign-in (such as HubSpot, QuickBooks, Xero, or a password manager), receive information when the customer directs or approves work there, as described above.

We do not sell personal information for money. We do not currently share personal information for cross-context behavioral advertising. Advertising storage in our consent interface is reserved for future measurement and remains off unless a visitor enables it and the related integration is configured. A customer may direct the Services to disclose Customer Content to its own providers or recipients; that disclosure is made on the customer's instructions.

Tensor's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

7. Cookies, local storage, analytics, and marketing choices

We use necessary cookies and browser storage for authentication, security, session continuity, consent records, and preferences. Optional analytics and advertising storage are off before a visitor makes a choice. The website uses a browser-timezone signal, without an IP lookup, to show the stricter regional consent experience when appropriate or when the region cannot be determined.

Before optional analytics is accepted, the website may create opaque browser and session identifiers and locally store sanitized acquisition context, including landing or referrer URLs with credential-like query parameters and URL fragments removed, UTM values, and click identifiers. This limited context preserves the source of a requested signup, contact, or demo interaction and may be included when you submit that request. It is separate from optional vendor analytics.

We measure clicks and visits from our marketing emails to improve them.

If you enable analytics, configured analytics and tag-management services may receive limited page, campaign, consent, and event information. We configure optional analytics to limit collection where supported, including disabling broad automatic capture. We do not record visitors' sessions. Turning analytics off sends configured services an opt-out or denied-consent signal and stops future optional events from Tensor in that browser, but it cannot retrieve information already transmitted.

Your consent record, locally stored acquisition context, opaque identifiers, and necessary authentication, security, or preference values may remain after optional analytics is turned off. You can remove those browser-side values by clearing site data in your browser. You can reopen Cookie settings or the Do Not Sell or Share control from the website to change future optional use. Transactional and service communications are not marketing; marketing email, if sent, includes an unsubscribe method where required.

8. Customer responsibility for the people in their work

Customers choose what work to hand to Tensor and are responsible for having a lawful basis to process information about, and to contact, the people in that work (such as people who write to them, appear in their connected accounts, or receive email sent on their behalf), for honoring opt-outs, and for providing any notice or consent required for monitoring, automated messages, or AI use. Tensor provides approvals, limits, and receipts, but those controls do not replace the customer's legal obligations.

Tensor acts in connected accounts and on websites a customer has shown it on the customer's instructions. The customer is responsible for being allowed to use those accounts and websites this way, for the approvals it gives, and for the limits it sets.

9. Retention and deletion

We retain personal information for the period needed to provide the Services, honor workspace controls and contracts, maintain security and receipts, resolve disputes, meet legal obligations, and exercise or defend claims. Different records have different clocks; the run-detail retention period does not apply to every account, billing, security, or audit record.

A run's working content (what it received, including any email it read, and the AI's working conversation for that run) is deleted 30 days after the run ends. What the run did and its receipt are kept for as long as the automation and the workspace exist unless you delete them, or for the period agreed with an Enterprise customer. Other operational records are kept only as long as their purpose needs. A workspace contract, plan, configuration, incident, legal hold, backup cycle, or legal requirement may produce a different period.

Documents and configured workspace content generally remain until the customer deletes them, the applicable retention job removes them, or the workspace is deleted. Integration tokens are removed or made unusable when the integration is disconnected or the credential is revoked, subject to bounded logs or backups.

When an authorized workspace owner schedules workspace deletion, the product immediately deactivates the workspace and opens a 30-day restoration window. Restoration through the product is unavailable after the deadline. To request permanent deletion of remaining personal information, contact support@tensoradmin.com. We verify the request and apply contractual and legal exceptions. We may retain limited billing, audit, security, fraud-prevention, suppression, backup, or legal records after a deletion request where necessary and permitted, and we isolate them from ordinary product use.

10. Security

We use technical and organizational measures designed to protect personal information, including encrypted transport, encrypted integration credentials, tenant-scoped access controls, database row-level security, role and permission checks, audit events, approvals, secret and log redaction, environment separation, service health checks, and security monitoring. Access is limited according to job responsibility and system role.

No transmission, storage system, or security control is completely secure. Customers are responsible for protecting their credentials, configuring roles and integrations, reviewing approvals, and notifying us promptly of suspected unauthorized use. If required by law or contract, we will notify affected customers or individuals of a qualifying incident.

11. International processing

Tensor and its providers may process personal information in the United States and other countries where they operate. Those countries may have data-protection laws different from the laws where you live. Where applicable law requires a transfer mechanism or additional safeguard, the transfer is governed by the relevant provider and customer contracts and legally recognized safeguards.

12. Your privacy rights

Depending on where you live and subject to legal exceptions, you may have the right to:

Know whether and why we process your personal information and obtain access to it.
Correct inaccurate personal information.
Delete personal information.
Receive a portable copy of certain personal information.
Restrict or object to certain processing, including direct marketing.
Withdraw consent for future processing that relies on consent.
Opt out of a sale, sharing for cross-context behavioral advertising, or certain targeted advertising or profiling where applicable.
Limit certain uses or disclosures of sensitive personal information where applicable.
Appeal a decision on a privacy request and receive equal service without unlawful discrimination for exercising a right.

To exercise a right, email support@tensoradmin.com or use /contact?subject=Privacy. Describe the right and the account, workspace, browser, telephone number, or email address involved. We may need to verify your identity and authority, and we will use verification information only for the request. An authorized agent may submit a request where law permits, but we may require proof of authorization and direct identity confirmation.

If the information is Customer Content, contact the relevant Tensor customer first. We assist customers with verified requests as required by contract and law. If we deny a request, you may appeal by replying to our response with the subject "Privacy appeal." You may also complain to your local data-protection authority where that right applies.

13. Regional disclosures

For people in the European Economic Area, United Kingdom, or another jurisdiction that requires a legal basis, our bases may include performance of a contract, steps requested before entering a contract, compliance with law, consent, and our or a customer's legitimate interests in operating, securing, supporting, and improving the Services. You can withdraw consent at any time without affecting earlier lawful processing. Where required, you may lodge a complaint with the supervisory authority where you live or work.

If the California Consumer Privacy Act or another U.S. state privacy law applies, the categories collected, sources, business purposes, and recipients are described in Sections 2 through 6. We do not sell personal information for money and do not currently share it for cross-context behavioral advertising. Rights to know, access, correct, delete, opt out, limit, and receive non-discriminatory treatment are handled through Section 12, subject to statutory scope and exceptions.

14. Children

The Services are designed for organizations and their authorized business users, not for children. We do not knowingly collect personal information directly from a child under 13 through a child-directed service. If you believe a child provided personal information to Tensor without appropriate authorization, contact support@tensoradmin.com so we can investigate and delete it where required. Customers must not configure the Services to collect children's information unless they have satisfied all applicable notice, consent, and protection requirements.

15. Changes to this Policy

We may update this Policy as the Services, providers, or legal requirements change. We will post the updated version and effective date at /privacy. If a change is material, we will provide additional notice through the website, workspace, email, or another appropriate channel when required. An updated Policy applies prospectively from its effective date unless law requires otherwise.

16. Contact

For privacy questions, requests, or complaints, contact Tensor Autonomous LLC at support@tensoradmin.com or use /contact?subject=Privacy. Please do not send passwords, full payment-card numbers, private keys, or other unnecessary secrets with a request.