Vee3
Privacy Policy
This policy explains how Vee3 handles information when you visit vee3.ai, use a workspace, connect a service or contact us. It also covers SalesPilot, our sales outreach application, as described below.
Effective November 5, 2026
1. Who operates Vee3
Vee3 is operated by The Marketing Agency Inc., 88 Palace Pier Crt, Ontario, Canada. Contact moe@themarketingagency.ca for privacy questions or requests.
We determine how information is used to operate and secure Vee3. Customers are responsible for the information they submit and their instructions to analyze, share or publish it. Only connect accounts and websites you are authorized to use.
2. Information we collect and access
- Account and workspace information: email, display name, account identifiers, sign-in and guest sessions, membership, permissions, settings and workspace sharing records. Google sign-in through Clerk can provide the identity information shown on its consent screen.
- Website and content information: domains, public pages and sitemaps you ask us to inspect; keywords, competitors, roadmaps, briefs, drafts, images, edits, instructions and publication history.
- Google Search Console and Analytics information: the accessible properties needed for selection, the property identifiers you choose, and imported search queries, page URLs, dates, clicks, impressions, click-through rates, average positions, organic sessions, key events, conversion rates and revenue where available. We store the OAuth credentials needed to maintain the connection.
- Connected CMS information: site configuration, the WordPress application password, Webflow token or Shopify token you provide, and content, media, categories and publication results needed for your requested actions.
- Support and operational information: feedback, incident reports, relevant diagnostic context, service activity, timestamps, network and browser information, security events, and usage, cost and credit records. The operator's Google Sheets connection reads and updates the designated feedback and incident queue. It uses Google account identity to restrict access to the configured administrator.
Information comes from you, authorized workspace members, connected services, public sources you ask Vee3 to analyze, our service providers and your use of Vee3. Analysis and generated content can also create derived information.
3. Why we use information
We use information to authenticate users, maintain guest and saved workspaces, enforce permissions, analyze websites, research keywords, prepare and prioritize content, provide requested AI features, publish at your instruction, and show performance. We also use information to provide support, diagnose failures, secure the service, prevent abuse, administer usage and credits, and meet legal obligations.
The Google website connection requests read-only Search Console and Analytics permissions together so you can select the properties to use. It does not authorize changes to those services. The separate administrator-only Sheets permission allows queue entries and statuses to be read and updated; ordinary website connections do not request that Sheets permission.
4. AI processing and Google Limited Use
AI features send the instructions, content and relevant workspace context needed for the requested feature to our AI providers. Anthropic processes text generation and analysis. During automatic site scans, Anthropic receives selected and alternative search queries and relevant Search Console performance evidence to classify pages and validate keyword choices. This processing happens automatically as part of the scan. Google processes prompts and relevant content for requested image generation. Do not include information you do not want processed by these features.
The Copilot beta answers typed and spoken requests. What you type, the transcript of what you say, the relevant workspace context and what Vee3 shows on your screen go to Anthropic, which writes the Copilot's replies. When you turn on voice, your microphone audio streams to ElevenLabs, which runs the call, turns your speech into text and turns the Copilot's replies into speech. The microphone is used only while voice is on, and you can mute it or end voice at any time.
The AI Editor's request queue temporarily retains request text and relevant edit metadata in session storage for this browser tab so waiting requests can be reviewed after a reload. This queue is separated by signed-in user and does not automatically repeat an interrupted operation.
The Copilot remembers the goals, preferences and facts you ask it to keep, in the brand's Knowledge Hub inside Vee3. Your preferences are visible only to you; goals and facts are visible to the people who can edit the brand. You can ask the Copilot to show, correct or forget any of it. Forgetting stops the Copilot using it at once, and the forgotten memory is deleted after 30 days. Unless you forget it sooner, a memory is kept for up to 12 months by default.
Automatic scans may send Search Console query terms to the configured SEO data provider, Ahrefs or DataForSEO, to check keyword demand and validate keyword choices. These lookups support the page and keyword analysis displayed in your workspace.
We use Google API information only to provide or improve the user-facing features described here. We do not sell Google user data, use it for advertising, credit decisions or data brokerage, or use it to train general-purpose AI models. AI processing of Google data is limited to providing the relevant Vee3 feature.
Vee3 follows the Google API Services User Data Policy, including its Limited Use requirements. Those restrictions also apply to data derived from Google information.
Transfers of Google data are limited to delivering or improving appropriate user-facing features with your consent, security purposes, applicable law, or an acquisition or asset transfer with your prior explicit consent. People may access Google data only with your affirmative agreement for specific information, for necessary security or legal reasons, or for internal operations involving aggregated and anonymized data as permitted by Google's policy.
5. When information is shared
Workspace members can see information according to the access you grant. Publishing sends content and related details to your selected CMS, and live publication can make them public. Shared workspace links can give access to their recipients under the permissions you select.
Authorized Vee3 staff may access a workspace's data, read-only, to provide support, investigate problems and keep the service secure. This access is limited in time and logged. Staff do not see passwords, API keys, publishing credentials or payment details this way. Google data in a workspace is viewed only with your agreement for that request, or when needed for security or legal reasons, as section 4 describes.
We use service providers to operate features: Vercel for hosting, delivery, queues and demo measurement; Neon for the PostgreSQL database; Clerk for authentication; Anthropic for text AI, scan classification, research and the Copilot's replies; ElevenLabs for the Copilot's voice calls, speech recognition and speech; OpenAI for the embeddings behind Cluster Fit, Brand Fit, category review and Knowledge Hub search, and for text models an administrator selects; Google for OAuth, connected metrics, Sheets, PageSpeed and image generation; DataForSEO and Ahrefs for SEO research, including Search Console query terms used in keyword validation; and Thum.io for screenshots of public pages. The information sent depends on the feature, such as a domain or keyword for SEO research, a page URL for a screenshot, or relevant content and performance evidence for AI processing.
Service providers process information needed for their role. Connected services also have their own privacy policies. We may disclose other information when required by law, to protect rights or security, to professional advisers, or as part of a business transfer with appropriate safeguards. The stricter Google data limits in section 4 continue to apply.
6. Storage, security and retention
We use access controls, workspace authorization checks, HTTPS and authenticated encryption for stored Google and CMS credentials. No system can guarantee complete security. Vee3 operates from Canada and uses service providers whose systems may process information in the United States and other countries, where privacy laws may differ.
Workspace content, imported metrics and derived analysis are generally retained while the workspace is maintained, until you delete the relevant records or request deletion. Credentials are retained while a connection is maintained, unless replaced, disconnected or removed through an authorized deletion. Support, security, usage and diagnostic records may be retained longer where needed to resolve incidents, prevent abuse, address disputes or meet legal requirements.
Vee3 does not record live Copilot conversations. Guided tour narration is different: it is generated from the page's data, can include page titles and keywords, goes to ElevenLabs to be turned into speech, and is stored as audio so it can be replayed. For the Copilot, Vee3 keeps a working record for each person and brand, such as the current objective, decisions, references and tasks, and clears it after 30 days without use. A record unused for 90 days is deleted. It keeps a session's recent turns as redacted text for up to two hours after the session's last activity, details of ended sessions, such as times, device type and why they ended, for 30 days, and records of the actions the Copilot carried out for up to 90 days. Usage counts kept for the Copilot's daily limits, and the usage and cost records we keep per workspace and person (voice minutes, typed requests, tokens and characters), contain no content.
Our ElevenLabs agent is configured not to record voice, with zero days of conversation retention and deletion of audio and transcripts. ElevenLabs' zero-retention mode is not on, so ElevenLabs may still keep transcripts until its scheduled deletion runs.
Deletion from active systems does not necessarily remove backup copies immediately. Copies may remain until the applicable backup retention cycle ends and are not used to resume ordinary processing of deleted information. We do not promise an automatic deletion deadline that applies to every record.
7. Disconnecting, deletion and your choices
You can disconnect Google in Brand Configuration. Vee3 attempts to revoke the Google tokens and removes its stored connection credentials even if remote revocation fails. You can also remove access in your Google Account connections. Disconnecting stops future authorized imports through that connection; previously imported metrics, drafts and analysis remain in your workspace until separately deleted.
Disconnecting a CMS removes its stored credential from Vee3. Revoke or rotate the credential with the CMS as well. Disconnecting does not delete content already published on your website. Brand deletion removes the brand from your workspace and clears its stored Google connection. Cached import snapshots and operational records may remain and require a separate deletion request. Brand deletion does not remove third-party copies or published pages.
To request access, correction, export or deletion of personal information, email moe@themarketingagency.ca. Include the relevant account or workspace and what you want us to do. Do not send passwords or access tokens. We may need to verify your identity and authority, and will explain any records we must retain or requests we cannot fulfill.
Depending on applicable law, you may also withdraw consent, object to or restrict processing, request portability, or complain to your privacy regulator. Where consent is required, withdrawing it affects future processing and may limit the connected feature. For customer-controlled workspace information, you can also contact the workspace owner.
8. Cookies and browser storage
Vee3 and its authentication provider use cookies and browser storage for sessions, security, workspace continuity, preferences and recovery of requested work. Blocking them can prevent sign-in or saved workspace access.
Vee3 counts page views across the application, and demo-video opens and viewing progress, with Vercel Web Analytics, which sets no cookies. Each address is reduced to its page's route before it leaves your browser, keeping only which workspace view is open, so workspace identifiers, share links and other query parameters are never sent.
Our website at vee3.ai uses Google Analytics only if you accept analytics cookies in its cookie banner. The Cookie Policy lists each cookie, its purpose and how long it lasts, and the Cookie settings link at the foot of every vee3.ai page changes your choice at any time.
The app at app.vee3.ai runs no advertising measurement. It loads no advertising cookies, pixels or similar technologies, and it sends no visit, account or workspace information to advertising providers.
9. SalesPilot
SalesPilot is operated by the same The Marketing Agency Inc., at the address and privacy contact above. This section supplements the policy for SalesPilot. Customers choose which business contacts to import, research and contact, and are responsible for lawful instructions, permissions, outreach and opt-outs.
SalesPilot stores brands, campaign settings, prospect lists, uploaded files, business contact names, roles, emails and profile links, research evidence, notes, generated drafts and offer assets. It also stores sender names and addresses, authorized email copy, sequence and provider identifiers, delivery results, replies, bounces, opt-outs and tracked open and click events. Open tracking can include automatic image loading and does not establish that a person read a message.
Information comes from customers, people with workspace access, public company websites, research providers and connected services. Vercel hosts the application and workflows; Neon stores its database; DataForSEO supplies public search and SEO research; Hunter finds and verifies business emails. The configured Anthropic, OpenAI or Vercel AI Gateway provider receives instructions and relevant company evidence and campaign context for requested AI research and writing. Optional website captures use DataForSEO or Browserless. Research, generated copy and profile matches can be inaccurate and need review.
LinkPilot, operated by the same company, supplies shared email transport, mailbox connections, warmup, suppression and reply protection. Recipients and email providers receive authorized messages and associated delivery information. SalesPilot retains its own campaigns, queues, Autopilot settings and workflow controls.
LinkedIn and X: customers may import or confirm personal profile URLs and maintain assisted social tasks. Optional LinkedIn OpenID Connect reads the connecting account's identifier and display name. It does not grant access to connections or inboxes, or permission to send invitations or messages. Optional X OAuth reads the connecting account's identifier, display name and handle. An explicit follow-back check asks X for the selected contact's relationship to that account. Offline access permits token refresh for a later requested check. There is no background social inbox polling, social posting, automatic following, invitation sending or automated DM sending. Users review and complete actions in the provider; acceptance or follow-back does not constitute consent for automated messages.
Social profile matching should use links published by the person or their company, links the person supplied directly, or matching for which the customer has permission. Public availability alone does not authorize unrestricted use. SalesPilot does not send connected social API identity or relationship responses to AI providers for generation or model training, sell that API information or use it for advertising targeting. LinkedIn and X apply their own policies: LinkedIn privacy policy and X privacy policy.
SalesPilot uses encrypted server-side storage for integration tokens, HTTPS, browser-write origin checks and a separate HttpOnly browser cookie to control social connections. That cookie lasts up to 180 days and temporary OAuth state lasts 10 minutes. Clearing it can remove assisted-account management. Browser storage also retains workspace preferences and unfinished campaign drafts.
Current console access: SalesPilot's operator sign-in is disabled at its owner's request. Anyone with the app URL can access ordinary brand, prospect and campaign information. Do not submit confidential customer information or assume these workspace records are private. Social connection controls are not authenticated team membership. This policy does not change that access setting.
Disconnecting a social account removes its stored OAuth credentials and pauses its tasks. Also revoke SalesPilot in LinkedIn permitted services or X connected apps. Disconnecting cannot recall messages or delete provider copies. Previously imported prospect records, independently entered notes and manual task history require separate deletion. Workspace records generally remain until deleted or a deletion request is fulfilled; suppression, security, operational and financial records may remain where needed to prevent unwanted outreach or meet legal obligations.
To request access, correction, export, deletion of SalesPilot information or withdrawal of connection consent, email moe@themarketingagency.ca with the relevant brand or account. Do not send passwords or tokens. We verify authority and explain any required retention. We remove connected LinkedIn API information when required on account closure or a verified request. We update or delete restricted X API information as required by X, including within 24 hours of a qualifying request. Backup limitations, international processing and applicable privacy rights described above also apply.
10. Children and policy updates
Vee3 is intended for business users and is not directed to children. Please do not submit children's personal information.
We may update this policy as Vee3 changes. We will update the effective date and provide additional notice or seek consent for material changes when required. For questions, contact moe@themarketingagency.ca.