Privacy policy
Last updated 18 November 2026
Plugsight (plugsight.app) is operated by Nexgen Ventures LLC FZ (“we”, “us”), in the United Arab Emirates. This policy explains what we collect when you use Plugsight, how we use it and the choices you have. Questions: info@plugsight.app.
What Plugsight does
Plugsight lets you connect your own accounts (email, helpdesk, marketing and analytics, files, calendar and contacts) and make them available to AI assistants you choose, such as Claude or ChatGPT, through private endpoints (“MCP servers”) that you create and control.
Information we collect
- Your account: name, email address, a hashed password if you set one, and the identity you sign in with (Google or Microsoft).
- Connected accounts: for each account you connect, its email or login name, a label, and the credentials needed to reach it (OAuth refresh tokens, app passwords or API tokens). Credentials are encrypted at rest with AES-256-GCM.
- Settings: your MCP servers, which connections each includes, write-access switches, and which sites or ad accounts you hid.
- Activity records: a log of actions (sign-ins, settings changes, connections added or removed, and each AI tool call with its name and arguments) and, for emails you send through Plugsight, the recipients and subject. These records never include email bodies, attachments or report contents.
- Technical data: IP address and browser user agent for security, rate limiting and the activity log.
- Website analytics: on our public website (plugsight.app), Google Tag Manager and Google Analytics record which pages are visited, how visitors arrive and general device information, so we can improve the site. Website analytics never include data from your connected accounts.
- Product analytics (PostHog): we use PostHog, hosted in the EU, to see how the website, help centre and app are used: pages viewed, which buttons lead to sign-up, help-centre searches (how long the search was and how many articles matched, never the words), Ask AI use and ratings, and errors. In the app we also record product events such as signing up, adding or removing a connection (which service, never its contents), creating an MCP server, connecting an AI app, plan changes and payments (the amount and currency, never card details), the pages and endpoints of ours you use (which one, whether it worked and how long it took, never what was sent), and each AI tool call's name, timing and outcome. With a tool call, your AI app may also send a short description of what you asked it to do (for example "finding a customer's last order"), which we store with email addresses and quoted text removed, the name of the AI model it uses, the options it chose (such as page size, sort order or which fields a search filtered on, never the words, names or values searched for), and how much came back (its size and number of items, never the content). These app events (signing in included), and Ask AI questions asked while signed in, are recorded on our servers without cookies, so they are recorded whatever your cookie choice and always carry an internal account number, never your name or email address. Your visits in the browser carry that number only if you allow analytics cookies; if you choose Decline, they are counted without cookies and aren't linked to you. PostHog never receives your emails, tickets, orders, files, messages, what your AI app sends to a tool or gets back from it, or anything you type into Ask AI.
- Session replay: on the website, PostHog can record how a page is used (scrolling, clicks, what was on screen) for visitors who accept analytics cookies, with everything typed into forms hidden. In the app, only the sign-up and sign-in screens, and during your first week the setup screens (confirming your email, adding a connection, creating an MCP server and connecting an AI app), are recorded, again only with analytics cookies allowed, with every form field hidden (passwords, API keys and any other text you type) and images and embedded frames blocked. The help centre and the rest of the app are never recorded.
- Advertising measurement: only if you choose Accept all, we note the ad click identifier you arrived with (from Google, Meta or LinkedIn), and when you sign up or start a paid plan we tell that ad platform a conversion happened, with your email address only in hashed form (SHA-256), so it can match it to its own account holders. This is how we know which ads work. Choosing Analytics only or Decline keeps this off, and we never sell your data or use your connected accounts' data for advertising.
Data from your connected accounts
When you or your AI assistant ask, Plugsight reads data from your connected accounts and returns it to that assistant: for example emails from Gmail or Outlook, tickets from Zendesk, orders and products from Shopify, WooCommerce or Magento, or reports from Google Ads, Microsoft Advertising, Meta Ads, LinkedIn Ads, TikTok Ads, Google Search Console, Google Analytics, Google Tag Manager, YouTube and Google Merchant Center. It also includes data from APIs and MCP servers you connect yourself (Custom API and custom MCP server connections). This data is fetched live and is not stored by Plugsight; we keep short-lived caches (up to an hour) of lists such as which sites and ad accounts a connection reaches. Marketing, file and contact connections are read-only: Plugsight never creates, edits or pauses campaigns, bids or budgets. Sending email, helpdesk changes (replies, notes, new tickets, macros) and calendar bookings happen only when you have switched write access on and approved the specific action in the chat. On paid plans your assistant can also archive, label, move and mark emails read when you ask it to.
Data from advertising platforms
When you connect an advertising platform such as Meta Ads, LinkedIn Ads or TikTok Ads:
- We use its data only to answer your own questions about your own ad accounts, in the AI assistant you connected. Plugsight only reads: it never changes campaigns, ads, budgets or audiences.
- We never use it for advertising, for profiling you or anyone in your reports, or to build or enrich audiences, and we never sell it. It isn't combined with the advertising measurement described above.
- We don't share it with other Plugsight customers. Only you, and the people you invite to your own workspace on a team plan, can use your connections.
- It isn't stored beyond the short-lived lists described above (such as which ad accounts a connection reaches). Removing the connection deletes its stored credentials immediately, and deleting your account deletes all of your connections and their credentials (activity records are kept as described under Retention and deletion).
Google user data
Plugsight's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Each Google service is a separate connection you choose to add, and it asks only for the access that service needs.
What we access, and why
- Google Search Console (read-only): your verified sites and their search performance (queries, pages, clicks, impressions, positions), URL inspection results and sitemaps, to answer your questions about SEO.
- Google Analytics (read-only): your GA4 properties and their reports (traffic, conversions, revenue, funnels), to answer your questions about your website.
- Google Ads: your ad accounts and their performance reports (campaigns, keywords, search terms, costs, conversions). Google only offers this permission with edit rights, but Plugsight uses it for reports only and never creates, changes or deletes anything in your Ads accounts.
- Google Calendar: your calendars, events and free/busy times, to answer questions about your schedule. If you also grant "view and edit events", Plugsight creates, changes or cancels an event only when you approve that specific change in the chat.
- Google Contacts (read-only): names, email addresses, phone numbers and organisations of your contacts and "other contacts", so your assistant can look people up.
- Google Tag Manager (read-only): your containers and their published tags, triggers, variables, versions and unpublished workspace changes, to audit your tracking setup.
- YouTube (read-only): your channels, their videos and their YouTube Analytics reports (views, watch time, subscribers, traffic sources, audience), to answer questions about channel performance.
- Google Merchant Center: your Merchant Center accounts, products, product statuses and issues, and Shopping performance reports. Google only offers this permission with edit rights, but Plugsight uses it for reading only and never creates, changes or deletes products or settings.
- Google Sheets (read-only): the title, tabs and cell values of a spreadsheet only when you or your assistant give its link, to answer questions about that spreadsheet. Plugsight doesn't list or search your spreadsheets.
- Google Docs (read-only): the title and text of a document only when you or your assistant give its link. Plugsight doesn't list or search your documents.
- Google Forms (read-only): the questions of a form and the responses submitted to it, only when you or your assistant give the form's link, to summarise enquiries, surveys and sign-ups.
- Google Meet (read-only): the meetings you organise (times, participants' display names) and their transcripts when transcription was turned on, so your assistant can summarise what was said and agreed.
Plugsight can also check any public web page's speed with Google PageSpeed Insights. That uses no Google account and no user data.
How we use, share and protect it
- Use: only to provide the features you use, at your request: showing data to you and to the AI assistants you connect. We do not use Google user data for advertising, and we do not sell it.
- Sharing: we transfer Google user data only to the AI assistant you connected, only to answer your own request, and as required by law. We never share it with data brokers, advertisers or other third parties.
- Storage: Google data is fetched live when you ask and is not stored. We store only your connection's sign-in token, encrypted with AES-256-GCM, and short-lived lists (up to an hour) of which sites, properties, accounts, containers, channels and calendars it reaches.
- Protection: all traffic is encrypted with TLS, tokens are encrypted at rest, and access to production systems is restricted.
- People: we do not allow humans to read Google user data, except with your explicit consent for a specific item, where needed for security or to comply with law, or in aggregated, anonymised form for operations.
- Retention and deletion: when you remove a connection we delete its stored token immediately; deleting your account deletes all of your connections. You can also revoke access at any time in your Google Account (myaccount.google.com/permissions).
AI and machine learning
- Plugsight does not use Google user data, raw or aggregated, to develop, improve or train any AI or machine-learning model, and does not transfer it to any service for that purpose.
- Google user data reaches an AI model only when you ask your own connected assistant (for example Claude or ChatGPT) a question, and only the data needed to answer it. We recommend using an assistant or plan whose settings do not use your conversations for model training.
- The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
AI assistants you connect
Data returned to an AI assistant is processed by that assistant's provider (for example Anthropic or OpenAI) under its own terms and privacy policy. You decide which assistants to connect and which accounts each can reach, and you can revoke access at any time.
Ask AI (help assistant)
Ask AI answers questions about Plugsight on this website, in our help centre and in the app's Help panel. To write an answer, we send Anthropic's Claude your question, the last few messages of that conversation and the help-centre articles that match it, which are public. When you ask in the app while signed in, or on this website or in our help centre after you've chosen to use your account, we also send a short summary of your Plugsight settings so the answer can be about you: your plan and limits, the names you gave your connections and MCP servers, their switches and status, your pauses and daily email limit, and your AI's recent blocked or failed actions with the reason (never what they contained). Ask AI never receives data from your connected accounts (including Google user data and the accounts' email addresses) or your credentials, and when you're not signed in it can't see your account. Anthropic processes this under its commercial terms, which don't allow it to train its models on it.
We don't store your questions, the answers or the settings summary. To keep the service fair, we record your network (IP) address, or your account when you're signed in, with each question for rate limiting, and delete these records within a day. Please don't type passwords or other secrets into Ask AI; it never needs them.
Feedback you give (a thumbs up or down on an answer or a help-centre page, and any note you add) is stored anonymously with the article it's about, so we can fix what's wrong. It isn't linked to you or your account, and doesn't include your question or the answer. Each week, notes left with a thumbs down are sent with their article to Anthropic's Claude to check the article against our code; Anthropic doesn't use them to train its models.
How we use information
- To run Plugsight: sign-in, connecting accounts and answering your assistants' requests.
- To keep it secure: rate limits, fraud and abuse prevention, and the activity log shown to you.
- To send service emails such as sign-in links and password resets.
We do not sell personal data. We use it for advertising measurement only with your consent, as described above.
Service providers
We use providers that process data on our behalf: Railway (hosting and database), Resend (service emails), Stripe (payments and billing; we never see or store your card details), Anthropic (writing Ask AI answers from our help centre, as described above), PostHog (product analytics, error tracking and session replay, in the EU, as described above) and Google (website analytics, through Google Analytics and Tag Manager). With your consent, Google, Meta and LinkedIn receive the advertising conversions described above. Google, Microsoft, Zendesk and the other services you connect provide the data you ask for, under your own agreements with them.
Retention and deletion
- Removing a connection deletes its stored credentials immediately.
- Deleting your account deletes your profile, connections, credentials, MCP servers and sessions.
- Activity records are kept for one year, then deleted automatically; after an account is deleted they keep only the email address it had, for security.
- Ask AI questions and answers aren't stored; the network addresses used for its rate limits are deleted within a day.
- You can also revoke Plugsight's access at any time in your Google account (myaccount.google.com/permissions) or Microsoft account.
Security
All traffic is encrypted with TLS. Stored credentials are encrypted with AES-256-GCM. Passwords and access keys are stored only as hashes. Access to production systems is restricted.
Your rights
Under the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) and other laws that apply to you, you can ask to access, correct, delete or receive a copy of your personal data, and to object to or restrict its processing. Most of this you can do yourself in the app; otherwise contact info@plugsight.app. We reply within 30 days.
Children
Plugsight is a business tool and is not intended for anyone under 18.
Changes
If we change this policy materially, we'll tell you by email or in the app before the change takes effect.
Contact
Nexgen Ventures LLC FZ, United Arab Emirates. Email: info@plugsight.app.