Privacy at VOCO.

Google sign-in and Google Ads data

Google sign-in and Google Ads access are separate choices. If you sign in with Google, we use the basic identity information Google provides, such as your name, email address and profile image, to authenticate and maintain your VOCO account. This does not connect your advertising accounts.

If you choose to connect Google Ads, VOCO requests the Google Ads permission to read and manage advertising accounts you are authorised to use. We access account identifiers, account names, manager-account relationships, currency and timezone; campaign, ad-group, ad, keyword, budget and targeting settings; conversion-action settings and diagnostics; and advertising results such as spend, impressions, clicks, calls and reported conversions. Where you use a Google-hosted lead form connected to VOCO, form submissions can include the contact information and answers the person chooses to provide.

We use this data to show your accounts and campaigns, report results, check conversion setup, receive leads, prepare user-facing recommendations, and carry out the campaign changes you confirm. Google Ads account discovery and reporting may refresh in the background while connected. Connecting an account does not itself publish, pause or delete campaigns. Website conversion counts do not contain a person's contact information; receiving website-form leads requires a separate website lead connection.

We do not request Google Ads access to Gmail, Drive, Contacts or Calendar. Google passwords are entered only with Google and are not received by VOCO.

Facebook, Instagram and Meta advertising data

When you choose to connect Meta, we receive the Facebook identifier and name associated with the authorisation, the permissions granted and connection tokens. Depending on that access, we can discover available business portfolios, ad accounts, Facebook Pages and linked Instagram business identities. You select the assets to use in the workspace. We do not receive your Facebook or Instagram password.

For connected assets, we read campaign, ad-set and ad settings; creative content and identifiers; budgets and targeting; pixel or dataset identifiers and available conversion settings; and reporting such as spend, impressions, reach, clicks and reported actions or conversions. Connected lead forms can supply names, email addresses, phone numbers, answers, submission times and campaign or form attribution. We receive this data through Meta's APIs, scheduled synchronisation and authorised lead notifications.

We use it to display and manage your selected accounts, report campaign results, check available tracking settings, deliver leads to your workspace, suggest improvements to that advertiser's Meta campaigns and carry out changes you approve. Connecting Meta is not permission to launch or change advertising without your instruction. Choosing a pixel does not install tracking or reveal the identity of everyone who converts. Website-form contact details require a separate website lead connection.

Meta campaign data is kept within the relevant client workspace and used for that client's Meta advertising. We do not sell or license it, use it to build unrelated profiles, use one client's data to optimise another client's advertising, or use Meta-derived advice to optimise Google campaigns. Access is limited to the advertiser, people authorised to act for it, and service providers needed to deliver that service.

Optional AI explanations of Google Ads performance

Google Ads AI performance explanations are off by default. If an authorised workspace user enables this setting in Connected accounts, we send summary performance figures, such as spend, clicks and conversions, together with rule-based findings, to OpenRouter and its routed AI providers to write a plain-English summary for that workspace. Google connection tokens and lead contact details are not included in this feature's requests. These requests require no-training and zero-data-retention provider routing. If an eligible provider is unavailable, VOCO uses its rule-based summary instead.

You can turn the setting off at any time. Reports and rule-based suggestions remain available without it. We do not use Google user data to train or improve general-purpose AI models. Creating AI advertising content from business details and content you supply is a separate user-requested feature; review what you include in those inputs.

AI content and performance explanations

When you request copy, images or video, the business details, instructions and reference assets needed for that request are sent to the generation providers. Do not include passwords, government identifiers, sensitive personal information or lead contact lists in creative prompts or uploaded examples. Content you upload may contain personal information, so include only material you have authority to use.

Meta-only performance explanations can use summary campaign figures and rule-based findings to make results easier to understand. As with the optional Google explanations above, these requests go through OpenRouter using no-training and zero-data-retention routing, without connection tokens, lead names, email addresses or phone numbers. We do not send a combined Meta/Google performance brief to AI; rule-based checks remain specific to each platform and campaign.

VOCO Technologies does not use private connected-platform data or lead records to train shared or general-purpose AI models, or to improve another advertiser's campaigns. References to agency experience and creative playbooks describe our creative guidance, not permission to train on customers' private advertising data. AI can make mistakes. Recommendations are advisory; publishing and campaign changes require your confirmation. We do not make automated eligibility decisions about people for housing, employment, credit or other legally significant matters.

Storage, sharing and access

Google connection refresh tokens and Meta user and Page tokens are encrypted server-side using authenticated encryption. We use HTTPS for service traffic. Imported advertising settings, performance records and connected lead submissions are stored in VOCO's database and linked to the relevant organisation. Server-side permission checks and database access policies restrict access to the workspace and role involved. Tokens are not included in normal browser responses or AI performance requests.

Workspace members, agency staff and invited clients can access data according to their assigned permissions. Authorised staff may access specific information for support you authorise, security or abuse investigation, or legal obligations. Google data is not routinely read by people for unrelated purposes. No online service can guarantee absolute security; report a suspected vulnerability to hello@vocoads.com without including passwords or access tokens.

Our infrastructure providers, including Supabase and Vercel, process data to host, store and secure the service. Google receives requests needed for the advertising actions and reporting you use. OpenRouter and its routed AI providers receive Google-derived performance information only for the optional explanation feature described above. Resend processes recipient details and service-notification content where email delivery is needed. We do not sell Google user data, use it for unrelated advertising, cross-platform retargeting, data brokerage, creditworthiness or lending decisions, or transfer it to train general-purpose AI models.

VOCO's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Retention, disconnection and deletion

• Connection credentials: retained while the connection is in use. Disconnecting removes the stored tokens and selected-account access for that connection, including stored Meta Page credentials, and stops new requests through it. We also attempt to revoke the provider grant.
• Workspace, campaign, creative and lead records: kept while needed for the active customer's campaign management, lead follow-up and reporting, or until a valid deletion request is completed. Disconnecting alone does not delete imported reports, leads or drafts. They remain available for those existing workspace purposes, not unrelated reuse.
• Support and security records: kept only as needed to resolve the issue, investigate misuse or establish legal claims. Access is restricted and records are deleted when that need ends.
• Billing and statutory records: kept for the applicable accounting or legal period. Any exception to a deletion request is limited to the information and period actually required. Meta Platform Data is retained beyond required deletion only where applicable law requires it.

We delete data when it is no longer necessary for these purposes. Account closure, an authorised user or client deletion request, a platform deletion requirement, or cessation of the relevant service also triggers review and deletion of connected-platform data. Deletion is currently handled through our data deletion process, not an automatic account-deletion button. A request can cover specific platform data without closing the whole account. We aim to complete verified requests within 30 days and explain any lawful retention or permitted extension. A request is not treated as complete merely because a connection was disconnected.

You can independently revoke VOCO in your Google Account connections or Facebook Business Integrations settings. Provider-wide revocation can affect other workspaces authorised with the same identity. It does not pause or delete ads already running on Google or Meta. Where backup copies remain until the hosting provider's backup cycle expires, they are not used for ordinary service processing; deletion requests must also be respected if a backup is restored. Contact us for details of any retained copy affecting your request.

Why we may process personal information

Where VOCO Technologies is the controller, we rely on performing our contract with you to provide the service; our legitimate interests in secure operations, preventing abuse, responding to business enquiries and resolving faults; legal obligations for accounting and regulatory requirements; and consent where required, including optional website analytics, advertising tracking, promotional email and the Google AI setting. Where an account is provided by your employer or agency, administering that business relationship is a legitimate interest. You can object to legitimate-interest processing and withdraw consent without affecting earlier lawful processing.

Basic account information is needed to create and secure an account. Advertising connections and generation inputs are optional, but the corresponding features cannot operate without the necessary data and permissions. An OAuth permission is not a substitute for the advertiser's lawful basis or notices when collecting leads. Customers must not upload sensitive personal data that the service does not need.

Service providers

• Supabase and Vercel: authentication, application hosting, databases, asset storage and service operations.
• OpenRouter and the model providers used for your request: AI copy, image, video or the performance explanations described above. The information sent depends on the feature, not unrestricted access to your workspace.
• Meta and Google: account authorisation, advertising delivery, approved management actions, lead retrieval and reporting. These platforms also process information under their own terms and privacy policies.
• Google Analytics: optional measurement of visits to our public website, separate from Google sign-in and Google Ads connections. See Cookies and browser storage below for data, consent and controls.
• Stripe: payments, subscriptions and billing. We receive payment references and status; full card details are handled by Stripe.
• Cal.com: optional fit-call and onboarding bookings. The VOCO website loads an embedded Cal.com calendar when you approach its booking section, so you can book without leaving VOCO. Loading it connects your browser to Cal.com and shares technical information such as your IP address and browser details to display availability. If you book, Cal.com processes the contact details, business information, booking answers, time zone and appointment details you provide, and sends meeting confirmations. We do not prefill the calendar with private VOCO account data or send booking answers to our website advertising pixel. Booking does not require accepting advertising cookies, connect your Google Ads account or grant VOCO access to your calendar.
• Resend: transactional notifications, support-related emails and opted-in marketing. This includes recipients and the content needed to deliver the message.

We may also disclose information when legally required, or where necessary and permitted to address fraud or security. Any permitted business transfer must preserve applicable privacy protections; additional consent is obtained where required by law or platform policy. Access to one client's data is not sold or granted to other clients.

Service providers may process information outside Ireland and the European Economic Area, including in the United States. International transfers require an applicable adequacy decision or appropriate safeguards, such as the European Commission's Standard Contractual Clauses, with any necessary supplementary measures. Contact us for the providers, processing locations and transfer safeguards applicable to your data. A provider's availability does not remove our duty to put the required processing and transfer arrangements in place.

Referral offers and rewards

If you use Refer & save, VOCO Technologies records the referral code, the referring and referred billing accounts, the user claiming the code, timestamps, reward status, relevant subscription and payment references, and staff review decisions. We record copy-link, copy-code and share-button actions so you can see your sharing activity. These counts are not website visits or message opens, and we do not collect the recipients of your shares or access your address book.

We use these records to deliver the requested discount under the referral terms and, in our legitimate interests, prevent duplicate or self-referrals and payment abuse. Stripe handles discounts and payments. Eligibility checks can compare account ownership, subscription status, refunds, disputes and Stripe payment-method fingerprints; we do not store full card details or persist payment fingerprints in the referral tables. A matching payment method or failed check may put a reward on hold for staff review. You may contact support to contest a decision. Referrers see an anonymised referral reference and reward progress, not the other customer's name, email address, campaign data or payment details.

When you choose the referral offer while signing in or signing up, a first-party cookie named voco_referral_offer remembers that code for up to 30 days or until it is claimed. It is not set simply because you visit an invite link. You may untick the offer before continuing, clear the cookie through your browser, or enter a code manually in Billing & credits without this cookie. Email signup can temporarily retain the selected code with your account so it survives email confirmation; it is cleared when processed. Claiming a referral does not opt you into marketing.

Referral records are retained while needed to provide queued rewards, prevent repeat claims and resolve payment disputes. On account closure or an erasure request, we review and delete records no longer needed, retaining only information required for accounting, legal claims or a documented abuse investigation for the relevant period. Our retention and deletion process above applies. Connected Meta and Google advertising data is not used to run the referral program, and referral records are not used to train AI models.

Cookies and browser storage

VOCO campaign attribution: with Advertising consent, we store a signed Meta campaign reference in voco_campaign_attribution for up to 30 days. It contains the campaign and ad-account identifiers and visit time, not your contact details or the full page address. For a confirmed booking in our embedded calendar, we send its booking reference to VOCO and match it to Cal's signed booking confirmation. At service checkout, the campaign reference is saved with the Stripe subscription. Authorised VOCO staff can link these records to service bookings and actual payments to measure acquisition cost. This does not send your booking reference, contact details or payments to Meta. Declining Advertising, enabling Global Privacy Control or withdrawing consent stops new attribution and clears this browser entry. Earlier business records follow the retention and privacy-rights process above.

With the relevant cookie consent, we measure when the public campaign-results section is visible for at least one second: ViewContent in Meta and view_results in Google Analytics. This is a content view, not a lead or a booked call. Saved consent lets measurement start when the website code loads; you can reject or withdraw optional tracking at any time.

We use session cookies and browser storage for sign-in, security, workspace selection, interface preferences and saved progress. Disabling these can prevent those features from working. Connected advertising pixels on a customer's website are separate from VOCO's own website; selecting a customer pixel in VOCO does not install our website pixel or authorise marketing tracking.

Optional Google Analytics: only after you accept Analytics in Cookie settings, our public pages load Google Analytics 4 (measurement ID G-M4X6KZZYSD). This helps us understand page visits, traffic sources and engagement. With Analytics consent, a newly confirmed fit-call booking in the VOCO website's embedded calendar also sends a generate_lead event without contact details, booking answers or a booking identifier. Google receives the public page address and title, permitted campaign labels, a shortened referring address, event timing, browser/device details and analytics cookie identifiers; your browser also connects to Google using its IP address. We remove URL fragments, advertising click IDs and private query parameters from the page addresses we explicitly send. We do not send names, emails, phone numbers, form answers, private campaign content, account identifiers, OAuth credentials or payment details to website analytics.

Analytics is disabled on sign-in, signup, authentication, onboarding, payment-return, support, admin and private dashboard/client routes, and on development or preview hosts. We use explicit page_view events, with Google's standard session and engagement measurement; automatic form, outbound-link, site-search and history-change collection is disabled. Google Signals and advertising personalisation are disabled in this website tag. Accepting Analytics does not accept Meta advertising tracking, connect an advertising account or authorise AI processing. Google processes analytics under its Privacy Policy; learn how Google uses information from partner sites. The international-transfer safeguards described above also apply.

Optional Meta Pixel: only after you accept advertising tracking, our public marketing pages use Meta Pixel (ID 1235798736224314) to measure page visits, attribute visits to VOCO ads, and support relevant VOCO advertising and remarketing on Facebook and Instagram. Meta receives the public page URL, permitted campaign/click parameters, referring origin, time, IP address, browser/device information and applicable cookie identifiers. Meta may associate these events with your Meta account and use them under its Privacy Policy and Cookies Policy. Meta Platforms Ireland Limited is the relevant Meta entity for EEA users; Meta's policies explain its processing and international transfers.

We send explicit PageView events and, if advertising consent is active when Cal.com confirms a new fit-call booking in the VOCO website's embedded calendar, a Schedule event. Opening the calendar or clicking a button does not count as a booking. With the relevant advertising or analytics consent, we also measure fixed categories of public interactions: booking and pricing links, signup intent, contact links, feature and case-study links, industry and creative selectors, FAQ openings, video plays and calendar views. We do not collect their text or form-field contents. An InitiateCheckout event (begin_checkout in Analytics) is sent when a secure service checkout has been created, not on a failed attempt; it is not a purchase or a payment confirmation. Pending, cancelled and rescheduled bookings do not create a new Schedule event; neither do client onboarding calls. Repeat callbacks for the same booking are suppressed in memory for the current page. We do not provide your name, email, phone number, booking identifier, booking answers, lead details, private campaign content, OAuth credentials or payment information to this pixel. It is disabled on login, signup, authentication, onboarding, payment-return, support, admin and private client/dashboard routes, and on development or preview hosts. It does not run before consent or after rejection. Bookings made on the separate Cal.com website are not measured by this embedded-calendar integration. It is separate from the Meta account connections described above.

The first-party voco_marketing_consent and voco_analytics_consent browser-storage entries record your separate advertising and analytics choices, notice version and timestamp for up to 180 days; then we ask again. They contain no advertising identifier. Earlier Meta consent does not opt you into Analytics. When Analytics is enabled, Google may set _ga and _ga_M4X6KZZYSD cookies; our tag limits their lifetime to 180 days without automatic renewal. When advertising is enabled, Meta may set _fbp and _fbc cookies and use its own cookies; Meta determines their expiry and use as described in its Cookies Policy. Rejecting optional tracking does not limit access to VOCO. We honour a browser's Global Privacy Control signal by keeping advertising tracking off.

You can withdraw consent or change either choice at any time below or through Cookie settings on our public pages. Withdrawal stops the relevant future events, clears the corresponding analytics or Meta pixel cookies accessible on our domain and reloads the page to remove the tracking code. It does not undo earlier lawful processing or delete cookies held on Google's or Meta's own domains; use their controls or contact us about earlier data.

Public prices and new Managed subscriptions are in US dollars. We no longer use location or a currency-preference cookie to select prices. An old voco_managed_currency cookie is ignored and may be cleared in your browser. Existing subscription and advertising-account currencies remain unchanged. Booking and managed-service payment details are used to arrange the requested service and billing, not to opt you into promotional messages. Your private Managed client area stores your business brief, asset-sharing declarations, campaign approvals, progress history and support conversation. Authorised VOCO staff can access these to deliver the service. We link the area to a verified checkout email, keep internal staff notes separate from customer messages, and never ask you to send passwords or payment credentials in chat. Our retention and privacy-rights process applies to these records too.

Your choices and privacy rights

You can disconnect Meta or Google Ads, change email preferences, and request access to or deletion of your account data. See our data deletion instructions for the full process. Essential security, billing, and service messages are not marketing messages.

Subject to applicable law, you may request access, correction, erasure, restriction or portability of your personal information, object to processing based on legitimate interests, and withdraw consent. Requests are available to all users, including staff and invited clients, not only paying account owners. We may verify identity and authority without asking for more information than needed. We normally respond within one month; if a lawful extension is needed, we will explain it within that period.

If you submitted a lead to an advertiser using VOCO, contact that advertiser first about its use of your information. You can also contact us to help identify the responsible workspace and pass the request on; you do not need a VOCO login. A shared-workspace request must respect other people's rights and does not authorise deletion of unrelated clients' data.

You can complain to Ireland's Data Protection Commission or your local supervisory authority. Contacting us first is optional, not a condition of making a complaint.

Children and changes to this policy

VOCO is a business advertising service and is not intended for children. Tell us if a child's information has been supplied so we can investigate and remove it where appropriate. We update the date on this page when the policy changes and notify users of material changes in the service or by email. New uses of Google or Meta data require the relevant disclosure, consent and platform review before that new processing begins; posting a new policy alone does not grant new permission.