What tame never does

How tame handles credentials, content and access, including remote control.

It never holds a Platform password#

tame does not save social Platform login credentials. You log in on the Device; tame records the Account handle and Platform. Your tame sign-in credentials are separate. Remote control forwards your input to the Device without storing the typed content.

It never logs your content#

Not captions, not the video, not what an Account posted.

Operational logs record status and errors without including your captions or media.

It never lets one Client see another#

Each Client's Accounts and content stay separate. Operators can access only the Clients allowed by their Workspace permissions. Assign those permissions before inviting someone to manage a Client's work.

Optional failure screenshots#

Automatic failure sharing is off by default. An Owner or Manager can enable it in Settings in either the Desktop App or Web App. It sends tame support an failure screenshot, reporting member identity, Device and Account information, versions and technical execution steps. The screenshot can contain personal information visible on the Device. Private reports expire after 30 days. Turning sharing off stops future uploads and clears pending reports when each Desktop App next connects.

What remote control transmits#

Remote control lets authorized Operators see the Device screen and provide input from their browser. The live screen images and typed input are not stored by the remote control service. This is live screen access, so an Operator can see all visible apps, Accounts and notifications on an assigned Device. It is not limited to one social Account, and tame cannot prevent a viewer from capturing what their computer displays.

The Web App also receives the Fleet, Account and Activity information it needs to show your Workspace. Content deliberately uploaded to the Content Library is stored in cloud storage. Sending an item to Photos leaves a copy on the Device. These saved media files are separate from transient remote screen images.

Devices are identified to the service by a Workspace-specific pseudonym rather than their raw hardware identifier. Remote access requires an eligible customer subscription, permission in that Workspace and explicit sharing from the Mac. See Remote control and VA permissions.

And two about how tame talks to you#

A cause you can understand. When work stops, tame explains the cause in plain language so you know what to check.

Never a promise about your Account's safety. Nobody outside the Platform can know that. tame tells you what it did and what happened.

Two severity levels, and only two#

Needs attention and Account exposed. There is no third anywhere. If Account exposed becomes routine, the answer is to fix what produces it rather than invent a quieter tier.