Tensor AdminTry it live
00 · Security

It asks before it acts. And it shows its work.

You are letting something new near your inbox, your calendar and your customers. Here is what Tensor will and will not do, in plain words, and how you would know.

Try it live See the product
01 · The first question

“Will it do something I didn’t ask for?”

No. Tensor carries out only the automations you set up. Each one repeats the steps you described or showed. Anything it would send or change waits for you, until you decide otherwise.

Your OK comes first

  • By default, Tensor asks before it sends or changes anything. It shows you what it plans to do, and waits.
  • Set limits it can work within, and routine work inside them goes ahead without asking each time. You decide where that line sits.
  • Anything outside your limits waits for your approval. Each approval goes into that job’s record.

Only the work you gave it

  • Tensor carries out only the automations you have set up. Each one repeats the steps you described or showed. It doesn’t take on open-ended work.
  • When information is missing or conflicts, Tensor stops and asks instead of guessing.
  • Sign-in details stay hidden from the AI doing the work.
02 · The second question

“Who can see my customers and my data?”

Your workspace, your people. Your data is encrypted in transit and kept inside your workspace, apart from every other business on Tensor.

Your people, by role

  • Each workspace is kept separate from every other workspace.
  • Workspace roles and permissions control who can see the job history, approve work and change settings.
  • The AI services that do the work process it only for that job.
  • Demo data is kept separate from your real records. Advertising and site analytics are on only if you opt in. We keep basic first-party records of how visitors arrive.

Passwords stay out of sight

  • Gmail, Google Calendar and Google Sheets connect through Google sign-in, so Tensor never sees that password.
  • Any sign-in an automation needs is hidden from people in your workspace and from the AI doing the work.
03 · The third question

“What if something goes wrong?”

You can see exactly what happened, and you can put it back. You can check work done for you afterwards, not just in the moment.

A record of every job

  • Each record shows what started the job, each step, the approvals and how it turned out. You can still check finished work after the job ends.
  • Admin changes are recorded too: what changed, who did it, and when.
  • A job’s working content, including any email it read, is deleted 30 days after it finishes. Its steps and result stay for as long as the workspace does. Records stay visible to the roles allowed to see them.

Versions you can go back to

  • Each automation keeps its earlier versions. If a change goes wrong, go back to an earlier one.
  • You can delete supported records from your workspace. Deleting affects only your own workspace.
04 · The fourth question

“Where does it live, and who is behind it?”

Tensor is a service we operate. There is nothing to install, nothing for your staff to maintain, and one company to hold to account: ours.

One service, operated by Tensor

  • Nothing to install. Tensor is a service we operate, and team roles and permissions are part of every plan.
  • Start small and expand as trust grows. Larger plans add team controls.

A security review on request

  • On Enterprise, a security review maps these controls to your requirements before rollout. Retention and data-processing terms are agreed with you before you start.
  • For your vendor review, email support@tensoradmin.com.

In one line: Tensor does only the work you gave it. It checks with you before it sends or changes anything, unless you’ve set limits it can work within. It keeps your sign-ins out of sight, and leaves a record you can check and a version you can go back to.

05 · Questions

Security questions, answered plainly.

  • Can Tensor act without my approval?

    Tensor checks with you before it sends or changes anything. If you set limits it can work within, routine work inside them goes ahead without asking each time. You decide where that line sits.

  • Who can see our data?

    Your data stays yours: encrypted in transit and kept inside your workspace, separate from every other workspace. The AI services that do the work process it only for that job. You can delete supported records there. Demo data is kept separate from your real records.

  • Do you store our logins and passwords?

    Gmail, Google Calendar and Google Sheets connect through Google sign-in, so Tensor never sees that password. Any sign-in details an automation needs stay hidden from people in your workspace and from the AI doing the work.

  • Can we delete our data and control retention?

    You can delete supported records from your workspace. A job’s working content, including any email it read, is deleted 30 days after it finishes. Its steps and result stay for as long as the workspace does. Enterprise terms are agreed with you.

  • What record do we get?

    Every job leaves a record of what started it, each step, the approvals and how it turned out. Each automation keeps earlier versions you can go back to. Admin changes are recorded too: who changed what, and when.

  • Where is our data processed, and what about GDPR or a DPA?

    Advertising and site analytics are on only if you opt in. We keep basic first-party records of how visitors arrive. Tensor is a service we operate. We review sub-processors and data-processing terms with you before an Enterprise agreement.