TabTasker Privacy Policy
Version: 1.0 · Effective date: 6 November 2026
This Privacy Policy explains how Vehicularis Limited, trading as TabTasker (we, us, our), uses personal data as a controller, as required by the UK General Data Protection Regulation (UK GDPR) and, where it applies, the EU General Data Protection Regulation.
1. Who we are
- Controller: Vehicularis Limited, company number 15804590, Unit 501 Leroy House, 434-436 Essex Road, London, England, N1 3FY.
- Contact: info@vehicularis.com.
2. Scope
This policy does not cover content that our business customers put into their workspaces (Workspace Content). For Workspace Content the customer is the controller and we process it on its behalf, so the customer's own privacy notice applies. Please direct requests about it to that customer.
3. Personal data we process and where it comes from
- Account data: name, email address, password, profile image and profile details you add, organisation membership and role, notification settings, and your choice about sharing data with AI providers (the version of the notice you accepted). We receive it from you, from your organisation's administrators when they invite you, or from Google, Microsoft or GitHub if you sign in with them.
- Security data: sign-in, session and device records, IP address and security-check results.
- Billing data: billing contact details, VAT number, purchases and payment history. Card details are handled by our payment processor.
- AI usage data: records that you used an AI feature: which agent or feature, when, the Credits used and the size of the request. The content of what you asked is Workspace Content (section 2).
- Service performance data: information about how the Service is used and performs, including IP address, device and browser information. When we turn it into anonymous statistics, it is no longer personal data and becomes Usage Data under our Terms.
- Mobile app analytics: only if you allow it in the mobile app: which screens you open, your sessions and how long they last, when you first open the app and when it is updated, an identifier for the app on your device, the kind of device, its operating system and app version, and your approximate location (at most your city), derived from your IP address. Nothing is collected until you allow it, and it never includes your messages, files, contacts or name.
- Integration and notification data: tokens for services you connect and for push notifications.
- Communications: messages you send us and our replies.
- Reports you make: the message you reported, your reason and details, and that you reported it.
- Business contact data: name, business email address, job title and employer of people at current and prospective customers, received from them, at events, from their colleagues or from publicly available sources.
4. Purposes and legal bases
| Purpose | Legal basis (UK GDPR Article 6) |
|---|---|
| Providing the Service and managing accounts | Contract, where you contract with us yourself; otherwise our legitimate interest in providing the Service to our customers |
| Billing and keeping tax and accounting records | Contract or our legitimate interest in managing customer relationships; legal obligation for records the law requires |
| Security, preventing fraud and abuse, and investigating incidents | Our legitimate interest in protecting the Service, its users and our business |
| Enforcing our terms and establishing, exercising or defending legal claims | Our legitimate interest in protecting our rights |
| Service messages and support | Contract or our legitimate interest in operating the Service |
| Operating and improving the Service | Our legitimate interest in running and developing the Service |
| Understanding how the mobile app is used (mobile app analytics) | Consent, which you give or refuse when the app asks and can withdraw at any time in the app under Settings, Privacy |
| Business-to-business marketing | Our legitimate interest in promoting our services, for contacts at companies; for sole traders and partnerships, consent, or our legitimate interest where the "soft opt-in" applies (Privacy and Electronic Communications Regulations 2003, regulation 22) |
| A financing, merger, acquisition or sale of our business | Our legitimate interest in financing and organising our business |
| Complying with law and lawful requests from authorities | Legal obligation, or our legitimate interest where a request is not binding |
We need account and billing data to provide the Service under our contract. Without it we cannot provide the Service.
We do not make decisions about you based solely on automated processing that have legal or similarly significant effects on you.
4A. Your right to object
Where we rely on our legitimate interests (section 4), you can object at any time, on grounds relating to your particular situation, by emailing info@vehicularis.com. We will then stop unless we have compelling legitimate grounds that override your interests, rights and freedoms, or need the data to establish, exercise or defend legal claims. You can object to direct marketing at any time, for any reason, and we will stop.
5. AI features
- AI agents and the meeting assistant process Workspace Content on our customers' behalf (see section 2).
- We keep records that you used an AI feature (which agent or feature, when, the Credits used and the size of the request) for billing and security. The content of what you asked is Workspace Content (section 2).
- AI agents may keep notes about how you prefer to work, which you can view and delete in the Service.
- To decide which AI agent handles a request, sort workspace events for AI agents and guide in-app walkthroughs, the message or event, the recent conversation lines and the on-screen labels needed to decide are sent to TypeSafe AI, Inc. in the United States. It does not use them to train or fine-tune its models.
- If you connect workspace agents to the browser in TabTasker Desktop, they can read and interact with tabs you share while answering your desktop chat requests. URLs, page text, screenshots and interaction results may be sent to the workspace's AI provider, and answers may be visible to everyone in the requesting conversation. Tabs opened by an agent are shared automatically; existing private tabs remain private. Agents use your existing website sessions; the connection provides no cookie or password export tools. Stop sharing revokes access to that tab; disconnecting revokes workspace browser access. Neither action retracts information already returned to a conversation or AI provider.
- When a member of your organisation invites the meeting assistant (Maya) into a call, while present it continuously receives the audio of participants who are not muted, and reads the call's chat, so it can respond; that audio and chat are sent to OpenAI and Cloudflare. Any participant can also switch transcription on; without the meeting assistant, the audio of participants who are not muted is then sent to Cloudflare to transcribe it. A saved transcript is created only if a participant switches transcription on. Everyone in the call sees a notice while the meeting assistant is present or transcription is on.
- Before AI features send personal data to our AI providers at your request, we ask for your permission, and we ask again if those providers change. You can withdraw it at any time in Settings. While it is off, AI features do not run at your request. Content you share in the workspace can still be included when a colleague uses AI features, and processing your organisation has configured without anyone's request, such as search indexing, still runs; and if a colleague brings the meeting assistant into a call or switches transcription on, your audio while you are not muted is still sent as described above. Your organisation controls that.
- Where you are a workspace owner and export the workspace, the export leaves out other members' private conversations, personal tasks you cannot open and other items shared only with others, and private AI notes.
- We do not use these features to make decisions about you with legal or similarly significant effect.
6. Recipients
We share personal data with these categories of recipients:
- service providers who host and deliver the Service, send email and notifications, and provide AI features (listed at https://business.tabtasker.com/sub-processors);
- our payment processor;
- Functional Software, Inc. (Sentry), which receives error and crash diagnostics from our apps, processed in the EU (Germany);
- Google LLC (Google Analytics for Firebase), which receives mobile app analytics only if you allow it, to provide us with usage reports; we do not use its advertising features or collect advertising identifiers;
- GIPHY, Inc. (United States), which receives only the search terms when you search for a GIF;
- providers of public company information (Logo.dev, Wikidata and, if Logo.dev is not in use, DuckDuckGo, which your browser contacts directly for company icons and which therefore also receives your IP address), which receive a company name or website domain and no account identifier;
- GitHub, from which the desktop app checks for and downloads updates, and which receives your device's IP address when it does;
- third-party services you choose to connect;
- professional advisers;
- courts, regulators, law enforcement and other authorities, where required or permitted by law; and
- a buyer, investor or successor in a financing, merger, acquisition or sale of our business.
Dictation in the mobile app uses your phone's own speech recognition (Apple on iOS, Google on Android) under your device's terms; the audio is processed on your device or by that service, not by us, and only the resulting text reaches the Service.
When you connect a third-party service, we, not its provider, are responsible for the personal data the Service receives from it.
6A. Google user data
TabTasker's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.
- What we access: if you sign in with Google, your name, email address and profile image. If you connect Google Calendar, the events on your calendars and your calendars' names and time zones. We ask only for the Calendar permissions needed for that:
calendar.eventsandcalendar.calendars.readonly. - How we use it: only to sign you in, to keep your Google Calendar and your TabTasker calendar in step in both directions, and to provide features you use with those events, such as an AI agent or the meeting assistant reading your agenda when you, or a colleague you share your calendar with, ask it to.
- Who can see it: you, and members of your workspace as far as your calendar sharing setting allows (nothing, busy times only, or full details).
- AI providers: when an AI feature needs your calendar, the events it reads are sent to our AI providers: Cloudflare, Inc. (Workers AI) for AI agents, and OpenAI OpCo, LLC for the meeting assistant. Event details that appear in a conversation can also reach TypeSafe AI, Inc., which reads recent conversation lines to decide which AI agent handles a request. Cloudflare and OpenAI do not use data we send to train or improve their models, and TypeSafe does not use it to train or fine-tune its models. Cloudflare keeps nothing once it has answered a request, OpenAI deletes meeting assistant data after 30 days, and TypeSafe processes data only to provide its service to us, under its published data processing addendum.
- What we never do: we do not sell Google user data, use it for advertising, or use it to build profiles beyond the features above. We do not use it, whether raw, aggregated, anonymised or derived, to create, train or improve foundational or generalised AI or machine-learning models, and we do not transfer it to anyone who does. Nobody at TabTasker reads it unless you ask us to, or we need to for security or to comply with the law.
- How we protect it: it is encrypted in transit (TLS) and at rest (database encryption with managed keys). Google access and refresh tokens are encrypted again by our own service before they are stored. Every request is checked against the signed-in member and their organisation, and each component of the Service runs under its own service role. Access is role-based, with two-factor or passkey sign-in, and administrative actions are logged.
- Keeping and deleting it: we keep Google Calendar data while your calendar is connected. When you disconnect Google Calendar in TabTasker, we stop syncing, delete the stored Google tokens and remove the events we imported from the Service. Deleting your account deletes your calendar connections and tokens too (section 8). You can also revoke TabTasker's access at any time at https://myaccount.google.com/connections, or ask us to delete your Google user data at info@vehicularis.com.
7. International transfers
Some recipients process personal data outside the United Kingdom and the European Economic Area, including in the United States and in other countries where our hosting provider operates. We rely on UK adequacy regulations (including the UK Extension to the EU-US Data Privacy Framework) where they apply, and otherwise on the International Data Transfer Agreement or the International Data Transfer Addendum to the EU Standard Contractual Clauses. Where the EU GDPR applies, we rely on EU adequacy decisions (including the EU-US Data Privacy Framework) or the EU Standard Contractual Clauses. You can ask us for a copy of the relevant safeguard at info@vehicularis.com.
8. Retention
| Data | Retention |
|---|---|
| Account data | While the account is open. When you delete your account we delete your profile, sign-in data, profile image, notification settings, device tokens, calendar connections, connected-service tokens and AI agent notes about you. Most content you created stays with the workspace, with your profile-based author attribution removed; names and other personal data written into retained content may remain. Your private views, and personal tasks that belong only to you with their attached images, are deleted. Private items in a workspace that only you could open are not opened by anyone: they stay with the workspace, and an owner may transfer them to a colleague they choose; your organisation, as controller, may obtain them from us only on a written, lawful instruction. Deleted data is removed from backups within 180 days |
| Records kept by our payment processor and by connected services | Records our payment processor keeps (such as invoices) and access granted to some connected services (for example Microsoft or Figma, which offer no way for us to revoke it) are governed by those providers and lapse on their own terms |
| Integration and notification data | Until you disconnect the service, sign the device out, switch notifications off, or ask us to delete it; a device's notification token is deleted once the app has not been opened on that device for 60 days |
| AI usage data | While the workspace exists, and as part of billing data for as long as billing data is kept |
| Security data | Up to 13 months, or longer where needed for a specific incident or claim |
| Service performance data | Up to 13 months |
| Mobile app analytics | Up to 14 months after you last use the app with analytics on. Google deletes expired data in a monthly cycle, so deletion can take up to a month longer, and aggregated reports that do not identify you may be kept after that. Switching analytics off stops new collection; because this data is not linked to your account, we cannot normally find one person's data to delete it sooner |
| Billing data | 6 years after the end of the financial year it relates to |
| Communications | Up to 3 years after the matter is closed |
| Reports you make | Until your account is deleted |
| Business contact data | Until you opt out, or 2 years without contact; after an opt-out we keep a record so we do not contact you again |
| Anti-abuse record that free Credits were granted (a one-way hash that does not identify you by name) | Kept after account deletion, to stop the same grant being claimed again |
| Data needed for a legal claim | Until the claim and any limitation period end |
9. Your rights
You have the right to access, rectify and erase your personal data, to restrict or object to its processing, and to data portability, in each case as the law provides. You can object to direct marketing at any time. Where we rely on consent, you can withdraw it at any time without affecting earlier processing; for mobile app analytics, switch it off in the app under Settings, Privacy. To exercise these rights, email info@vehicularis.com. You can also delete your account yourself, in the apps or on the web; https://business.tabtasker.com/delete-account explains how, and what happens to your data.
10. Complaints
You can complain to us at info@vehicularis.com. We will investigate your complaint without undue delay, and tell you the outcome. You also have the right to complain to the Information Commissioner's Office at https://ico.org.uk/make-a-complaint/ or on 0303 123 1113. If you are in the European Economic Area, you can also complain to the data protection authority where you live or work.
11. Cookies and similar technologies
| Technology | Purpose | Duration |
|---|---|---|
| Sign-in cookies | Keep you signed in and complete two-factor or passkey sign-in | Until you sign out or the session ends |
| Trusted-device cookie | Remembers that you chose to trust a device for two-factor sign-in | 30 days, renewed when you sign in on that device |
| Security check (Cloudflare Turnstile) and Cloudflare security cookies | Protect our sites and forms from automated abuse | While the protected screen is open, or as set by Cloudflare for security |
| Browser storage for your theme and cookie choices | Remember the display theme and cookie choices you selected | Until you change them or clear your browser storage |
| Browser or desktop app storage for features you use | Keep interface preferences, drafts (such as call notes) and in-progress work (such as imports and call recovery) | Until overwritten, the feature clears it, the browser session ends, or you clear your browser storage |
| Mobile app analytics identifier (Google Analytics for Firebase), only if you allow analytics | Measure how the app is used: sessions, time spent and screens viewed | Until you remove the app; not used while analytics is off |
Apart from mobile app analytics, which runs only if you allow it, these are strictly necessary for the Service you use or its security, or only remember choices you made. You can remove stored choices at any time by clearing your browser storage for our sites.