Tab

Documented capabilities

Vendor statements, not verified task outcomes.

• Text, photos, screenshots, PDFs and video as task inputs; file and media creation Source · checked 2026-10-08
• Website browsing and requested use of connected accounts Source · checked 2026-10-08
• Outbound business calls, waiting on hold and returning a result in Messages Source · checked 2026-10-08
• Approved purchases and payments where wallet features are enabled Source · checked 2026-10-08
• Updates while work continues and context from earlier tasks Source · checked 2026-10-08
• Dated release notes describe timezone handling, browser changes and order follow-up; these are release claims, not tested outcomes Source · checked 2026-10-08
• Group chats: a separate Tab for each group, including people without their own Tab; money/password tasks move one-on-one Source · checked 2026-10-08
• Group-to-private requests: group Tab asks the personal Tab; vendor says nothing private is shared into the group without permission Source · checked 2026-10-08
• Reminders and recurring checks with optional active hours; vendor says it can report recent runs and check costs Source · checked 2026-10-08
• Delivery, flight, food-order and callback follow-up with status changes and arrival checks Source · checked 2026-10-08
• Named connected services in terms: Gmail, Calendar, Slack, GitHub, Linear and Notion, subject to selected provider scopes Source · checked 2026-10-08
• Contacts import via a secure Apple ID credential link and a six-digit verification code, as described in September 14 release notes Source · checked 2026-10-08
• Spreadsheets, PDFs, 3D files, ZIPs and published pages under sites.tab.bot, per September 11 release notes Source · checked 2026-10-08
• Outbound calls with up to an hour on hold, per September 9 release notes; duration is a vendor statement, not a measured guarantee Source · checked 2026-10-08

Permissions and human control

• A request authorizes steps reasonably necessary within the supplied scope, according to the terms. Ambiguous, sensitive, irreversible or materially changed requests may be paused for clarification; this is not a promise of a new approval for every action.
• Connected services use the access shown by the provider. The security page says write actions are denied by default unless the exact action is enabled; review the actual connection scope and settings.
• The homepage says spending waits until the user sees the purchase, total and payee and approves. Terms additionally bind merchant, cart, recipient, currency, payment destination and a short deadline; changed terms or uncertain outcomes are designed to stop, not silently retry.
• Payment and wallet features are limited beta. Bank or cardholder verification may require the user to take over. A successful demo does not establish that a particular merchant or payment works.
• Outbound calls and communications must be lawful and have any required permission. Tab may identify itself; the terms prohibit spam and emergency-service use.
• Card enrollment uses a single-purpose private link that expires after 10 minutes, per the security statement. Full card details must not be sent in Messages; this is a vendor-described control, not a test.
• Group work does not imply consent to expose private context: release notes say money/password jobs move into the personal thread and group-to-personal requests require permission before private data is shared.
• Apple contacts import is described as requiring saved Apple ID credentials through a secure link and a verification code. This is broader than uploading a contacts file; verify the actual scope, revocation and account-security implications first.
• Terms cap total liability at the greater of $100 or service fees paid in the preceding 12 months, subject to law. The reviewed terms contain no arbitration clause; that is a description of this version, not legal advice.

Documented controls do not prove that an agent always follows them.

Limits and open questions

• No official subscription price, per-task fee, usage allowance or numeric service limit was found on these pages. Unknown price does not mean free.
• Joining the waitlist does not guarantee beta access; calls, connections, media generation and payments may be incomplete, limited or unavailable.
• No hands-on test of task completion, call quality, response time, spending controls or reliability was run. No certification or independent security audit is claimed.
• The privacy policy gives purpose-based retention with legal, security, backup and fraud-prevention exceptions, not a fixed deletion window. Disconnecting account access is not an explicit promise to erase retained task data.
• No explicit model-training exclusion was established in the official privacy policy, terms or security page reviewed. A founder quote in press reporting is not a substitute for the applicable policy.
• The security page was reviewed 21 August and terms/privacy took effect 2 September, earlier than the October launch reporting. Confirm current beta behavior and terms before relying on them.
• Terms name Gmail, Calendar, Slack, GitHub, Linear and Notion. The competitor article also lists Drive, Docs, Sheets, Slides, Contacts and Tasks through one Google sign-in, but that exact bundle was not established by the official pages reviewed. Confirm the actual consent screen rather than assuming it.
• Microsoft 365/Outlook support was not established in the official pages reviewed. Absence from these pages is not proof that it is unsupported.
• Release notes dated September 10 say everyone wanting access gets in; the current homepage still says private beta/waitlist and the terms reserve staged access. Treat the current entry form and terms as controlling, not the older availability claim.
• The privacy notice confirms verified invite attribution and that neither participant receives the other's phone number. The competitor's claim that referrals move users up the waitlist was not established by the official pages reviewed.

Privacy and security

Vendor policy: messages, files, call results, browser activity and requested transaction data are processed to provide the service. Calls may include recordings or transcripts when configured and applicable consent requirements are addressed. Tab says it does not sell personal information. Its security statement describes encrypted saved credentials, private card enrollment and scoped account access; these are vendor statements, not an independent audit. Retention is as long as reasonably needed, with legal, security, backup and fraud-prevention exceptions and no fixed timetable. Users can ask to disconnect accounts, revoke credentials or request access, correction and deletion; identity checks may apply. The reviewed official policies do not establish a blanket no-model-training promise. Third-party services apply their own terms and privacy practices.