Privacy Policy

Effective August 17, 2026. Updated October 3, 2026 to describe product analytics, session recording and the choice to allow them. Contact: tame support on Discord↗

This Privacy Policy explains how tame handles personal information across the website, Web App, Desktop App, support, and related services. It should be read with the Terms of Service and EULA.

1. Who is responsible#

tame is responsible for the personal information described in this policy. For privacy questions, requests, or complaints, contact tame support on Discord↗.

For most Workspace and service information, tame acts as a controller because it decides why and how that information is used. A Customer may also submit information about its Operators, Clients, Accounts, or other people. The Customer is responsible for having authority and an appropriate legal basis to provide that information.

2. Information we collect#

Registration and identity#

We collect an Operator's name, email address, email-verification status, Workspace, Role, and accepted legal-policy version and time. For password registration, the authentication system stores a one-way password hash, not the original password. If an Operator chooses Google sign-in, we receive basic Google identity information and authentication records needed to complete and secure sign-in.

Workspace operations#

We process the information a Customer enters or synchronizes, which may include Workspace and Client names, public Platform handles, Platforms, Device pseudonyms and names, Mac installation identity and name, Account assignments, Warmup Schedules, Action Schedules, Posting Windows, Action Outcomes, Device State, Session records, failure causes, and other operational facts.

Content Library and Posts#

When a Customer uses the Content Library, we store uploaded media, filenames, captions, media metadata, ownership scope, fingerprints, Post instructions, schedules, preparation status, and publication results. Client-owned content is not written into application logs.

Subscription and billing#

Whop processes checkout and payment. We receive and store limited purchase and membership records such as the selected Subscription Tier, billing interval, membership identifier, status, renewal or end dates, provider-event identifiers, and checkout state. We do not receive or store full card numbers.

Technical, security, and support information#

We collect session identifiers, IP address, browser and Device information, request metadata, authentication-rate-limit records, application version, License Key status, installation heartbeats, diagnostics, error causes, and structured security and operational logs. If an Operator contacts support, we process the message and any files or diagnostics they deliberately provide.

Product analytics and session recording#

The website and Web App use PostHog to understand how they are used and to find what breaks. What PostHog does depends on the choice offered the first time a browser visits, described in section 5.

For every visitor, PostHog counts visits without cookies or browser storage, using a short-lived identifier computed on PostHog's servers from the IP address and browser that cannot recognize the same browser on a later day. It records pages viewed, clicks and other interactions (without the text or labels of what was clicked), referrer, browser and Device type, approximate location derived from IP address, a small number of named events such as completing registration or sign-in, and errors the browser reports.

Only if a visitor chooses Allow analytics, PostHog also sets a cookie so that later visits from the same browser are recognized, links a signed-in Operator's records to the Operator's account identifier, name and email address, and records sessions: a reconstruction of each page as it was displayed, including its text, and where the pointer moved and clicked, so that a problem can be seen rather than guessed at.

Because recordings include on-screen text, they can include what the page displays, such as Workspace, Client and Account names, captions, schedules and the signed-in Operator's name and email address. Everything typed into a form field is masked, and images and video are blocked, in the browser before anything is sent. Click records, for every visitor, do not include the text or labels of what was clicked. Password-reset tokens, sign-in codes and search terms are removed from recorded web addresses. Nothing is collected on invitation or team-management pages. On the Remote Control page, recordings show the page around the Devices, including Device and Account names, but never the Device screens themselves or anything typed for a Device. tame also counts connecting, opening a Device, taking control, and opening the live wall, with the number of Devices involved. The part of a web address after "#" is never sent.

Optional automatic failure reports#

Automatic failure sharing is off by default. If a Workspace Owner or Manager enables it in Settings, the Desktop App sends tame support a screenshot when automation fails, together with the reporting member’s name, email and Role, public Account handle, Device information, app version, workflow identifiers and a bounded technical step history. Screenshots may contain personal information visible on the Device. Reports are stored in private object storage and the scoped application database, accessible only to separately authorized support staff, for up to 30 days. Disabling sharing stops future reports and clears pending uploads when each Desktop App reconnects; it does not delete reports already received. Action inputs, OCR output, accessibility trees and full logs are not automatically included.

3. Information tame never asks for#

tame does not ask for, accept, or store a Platform password, Platform session secret, Platform authentication token, Apple ID password, or Proxy credential. There is no Platform credential field or import path in the product.

Raw Device frames used for Screen Recognition remain inside the Device worker process and do not cross a process boundary. tame does not sell personal information and does not use it for third-party targeted advertising.

4. Why we use information#

We use information to:

• create and secure Operator accounts and Workspaces;
• provide, synchronize, and support the Services;
• enforce Roles, Client separation, Subscription Tier allowances, and licences;
• store and deliver Customer-selected Content Items and Posts;
• process purchases, renewals, cancellations, refunds, and billing support;
• prevent fraud, abuse, credential attacks, and unauthorized access;
• diagnose failures and improve reliability, compatibility, and usability;
• communicate service, security, legal, and support information; and
• comply with law, enforce agreements, and protect rights and safety.

Where data-protection law requires a legal basis, we rely on performance of the Customer agreement, legitimate interests in operating and securing the Services, compliance with legal obligations, and consent where the law specifically requires it. An Operator may withdraw consent for consent-based processing, but that does not affect earlier lawful processing or processing based on another lawful basis.

5. Cookies and local browser storage#

The Web App uses essential authentication and security cookies to keep an Operator signed in and protect access. It also uses limited local or session storage to remember theme choice and preserve a billing handoff.

The first time a browser visits, tame asks whether analytics may use cookies and record sessions. Choosing Allow analytics lets PostHog set a first-party cookie and local storage entry so that visits from the same browser can be recognized as one visitor, and turns on session recording, as described in section 2. Choosing Only essential, or not choosing, keeps PostHog to counting visits without cookies or browser storage. The answer itself is remembered in local storage so the question is not repeated. This storage is not essential: declining it, or blocking PostHog in the browser, does not prevent sign-in or stop any feature working.

You can change your answer at any time here:

Cloudflare Turnstile may process limited browser and network information during registration or account recovery to distinguish legitimate requests from automated abuse. We do not currently use advertising cookies, cross-site behavioral tracking, or marketing analytics, and product analytics is not used for advertising. Disabling the essential storage may prevent sign-in or make a feature stop working.

6. When information is shared#

We share only what is reasonably necessary with service providers acting for us, including:

• Whop, for checkout, subscription state, payment, cancellation, and refunds;
• Google, when an Operator chooses Google sign-in;
• Resend, for verification, recovery, and service email;
• PostHog, hosted in the European Union, for product analytics, session recording and error reports;
• Cloudflare, for security checks and, when configured, Content Library object storage and delivery;
• hosting, database, infrastructure, and security providers needed to operate the Services; and
• professional advisers, authorities, or counterparties when needed for legal compliance, claims, security, financing, reorganization, merger, acquisition, or sale.

These providers may process information under their own terms where they act independently. We do not authorize a processor to use Customer information for its own advertising.

Information may also be disclosed when we reasonably believe disclosure is required by law, necessary to protect rights or safety, needed to investigate fraud or abuse, or connected with a business transaction. Client separation remains a product and database security boundary.

7. International processing#

tame and its providers may process information in countries other than the Operator's country. Where applicable law requires safeguards for an international transfer, we use recognized safeguards such as adequacy decisions, contractual protections, and technical and organizational measures.

8. Retention#

We keep information only as long as reasonably necessary for the purposes described above, including providing an active Workspace, resolving disputes, maintaining security records, enforcing agreements, and meeting accounting, tax, and legal obligations.

Retention depends on the information:

• active Workspace, Operator, Client, Account, schedule, activity, and Content Library information is generally retained while the Workspace uses the Services or until an authorized deletion;
• authentication sessions and verification records expire according to their security lifetime;
• billing and transaction records may be retained for the period required by financial, tax, fraud-prevention, and legal rules;
• support and security records are retained for a reasonable period after resolution; and
• backups and logs are deleted or overwritten on their normal cycles unless preservation is required for security or a legal claim.

Deletion from an active system may not immediately remove a record from a protected backup. We will not retain backup data for active use after it should otherwise be deleted.

9. Security#

We use technical and organizational safeguards appropriate to the Services, including encrypted network transport, access controls, scoped database roles, forced row-level security, transaction-scoped Workspace and Client separation, encryption of Google provider tokens at rest, pseudonymous Device identifiers, and data minimization.

No system is perfectly secure. Operators must protect their email account, password, browser session, License Key, Macs, Devices, and local network and must notify us promptly of suspected unauthorized access.

10. Privacy rights#

Depending on location, an Operator may have rights to request access, correction, deletion, restriction, objection, portability, withdrawal of consent, or information about disclosure. Some rights are subject to exceptions, including security, legal, billing, and the rights of others.

California residents may have rights to know, correct, or delete personal information and to receive equal service when exercising those rights. tame does not sell personal information or share it for cross-context behavioral advertising.

Residents of the EEA, United Kingdom, and similar jurisdictions may object to processing based on legitimate interests and may complain to their local data-protection authority.

Contact tame support on Discord↗ to make a request. Share the Operator email associated with the Workspace privately with tame support, not in a public channel. We may verify identity and authority before acting. We will respond within the period required by applicable law.

11. Customer responsibilities and other people#

Customers may process personal information through tame for their own business purposes. The Customer determines why it operates Client Accounts, schedules Posts, and stores content and is responsible for its own privacy notices, consents, contracts, and legal obligations. Privacy requests concerning a Customer's own content or Client relationship should first be directed to that Customer.

12. Children#

The Services are for business use by adults and are not directed to anyone under 18. Do not submit a minor's personal information or content without all authority and safeguards required by law. Contact us if you believe a minor registered directly with tame.

13. Automated decisions#

tame uses automation and Screen Recognition to carry out Customer-selected workflows and report operational state. We do not use personal information to make decisions about a person that produce legal or similarly significant effects.

14. Changes and contact#

We may update this policy as the Services or law changes. We will change the effective date and provide additional notice for material changes where required.

Questions, privacy requests, and complaints should be sent to tame support on Discord↗.