Privacy and analytics
explained clearly.

Website analytics

We use Google Analytics 4 to understand visits, traffic sources, page use, and whether calls to action are useful. Google Analytics may process page paths, referral and campaign information, device and browser details, approximate region, and enhanced interactions such as page views, scrolls, and outbound clicks.

Our custom cta_click event records the page language, page path, CTA identifier, placement, displayed label, and destination type. We do not add names, email addresses, message contents, or other personal information to that custom event. Our funnel events (section_view, try_signal, form_invalid, try_tour, tour_start, contact_start, ask_submit and ask_source_click) record only the page language, the section or CTA identifier and its placement, and for questions whether a passage matched. The website address you type into the AI visibility diagnostic form is never sent to Analytics.

WEAVIST AI assistant

The “Ask WEAVIST AI” assistant at the bottom right of every page is WEAVIST ACE’s site-wide assistant. What you type in it is sent to WEAVIST and to our AI model provider (Google Vertex AI or OpenAI) to write the answer from this site’s pages.

Conversations are kept for up to 30 days and then deleted. De-identified records of questions and answers are used to improve the answers. Do not enter personal data, such as names, phone numbers or account details.

To have a conversation deleted earlier, email contact@weavist.ai with the date and time you used the assistant. Our analytics record only that one of our buttons opened the assistant (assistant_open), never what you type.

How we use the data

We use aggregated reporting to understand how people find the site, compare language and page performance, and improve the path from a visit to a conversation with WEAVIST AI.

Optional Analytics account sharing for modeling insights, technical support, and business recommendations is disabled. We do not configure this site for advertising personalization.

Google Analytics and Search Console in WEAVIST ACE

When you sign in to WEAVIST ACE with Google, we read your Google account’s email address and name and may save your name as your account’s display name. If you connect Google Analytics or Google Search Console to WEAVIST ACE (ace.weavist.ai), WEAVIST ACE accesses, with your permission and read-only: your Google account’s email address; the Analytics properties and Search Console sites that account can see; and, for the property and site you choose, daily report data. From Analytics that is sessions, engaged sessions, key events and revenue, by traffic source, medium and landing page; from Search Console, search clicks, impressions and position, by query and page.

We use this data only to show your WEAVIST ACE workspace how many visitors AI assistants send to your site, what those visitors convert, and which Google searches relate to the prompts you track. We retain the imported daily totals while the connection remains active and store an encrypted refresh token. The 90-day window applies only to the initial import, not to how long imported data is kept. Only members of your workspace see the data. We do not sell it, use it for advertising or use it to train AI models, and no one reads it except with your permission, for security, or as the law requires.

We do not share, transfer or disclose Google user data to any third party. It is stored and processed only on Google Cloud, which hosts WEAVIST ACE, and it is never sent to AI model providers.

Disconnecting a Google integration deletes that connection’s imported data and locally stored refresh token from the workspace. If another workspace still has an active connection for the same brand and Google account, we keep the Google authorization for that connection. Once the last such connection is removed, we request revocation from Google. You can also remove access at any time at myaccount.google.com/permissions.

WEAVIST ACE’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.

Google API Services User Data Policy↗

How WEAVIST ACE protects your data

WEAVIST ACE runs on Google Cloud in Taiwan (the asia-east1 region). All traffic between your browser and WEAVIST ACE, and between WEAVIST ACE and Google’s APIs, is encrypted in transit with HTTPS (TLS). Google Cloud encrypts our database at rest with AES-256.

Google refresh tokens are encrypted again with AES-256-GCM before they are stored, under a key kept in Google Cloud Secret Manager, apart from the database, and each token can be decrypted only for the workspace it belongs to. Data imported from Google is kept as daily totals for each property and site and contains nothing that identifies individual visitors.

Access is limited to the people who need it. In WEAVIST ACE, only a workspace’s owners and admins can connect or disconnect Google services, and only that workspace’s members can see the imported data. Inside WEAVIST, production systems and data are open only to authorized staff with company accounts, and Google Cloud records administrative access in audit logs.

When a connection or a workspace is deleted, its Google data is deleted with it. Encrypted database backups are kept for 7 days and then deleted. If a security incident affects your data, we will notify you and the authorities as the law requires.

WEAVIST ACE connector for Looker Studio

The WEAVIST ACE connector charts your own WEAVIST ACE brand reports in Looker Studio. It runs as a Google Apps Script under your Google account and asks Google for one permission, to connect to an external service (script.external_request), which it uses only to call the WEAVIST ACE API at ace.weavist.ai.

You give the connector a WEAVIST ACE API key with the Read scope. It keeps the key in your own Apps Script user properties and sends it only to the WEAVIST ACE API, to read the workspaces, brand reports, visibility, mentions, citations, sentiment and prompts that the key can read. It reads no data from your Google account, and sends WEAVIST nothing but the key and the report, market and dates you choose.

The connector does not share, transfer or disclose Google user data to anyone. It reads none from your Google account, and WEAVIST receives only the API key and the report, market and dates you choose.

The data appears in the Looker Studio reports you build. Google keeps those reports and their cached data under its own terms, not WEAVIST. To stop the connector, remove it from your Looker Studio data sources or revoke the key on the API keys page in WEAVIST ACE.

Contact and external services

With JavaScript enabled, the evaluation brief is saved in this browser tab’s session storage so you can return to it. Use “Clear this draft” to remove the text. Continuing to Google Forms sends the selected product and brief in a prefilled URL, which may remain in browser history; add your email and submit on Google Forms. This website does not receive the draft before that handoff.

Site search (/ask/) runs in your browser: it downloads an index of this website’s own pages and searches it on your device. What you type is not sent to WEAVIST AI or Google and is not stored. Analytics records only that a question was asked, where on the site, and whether any passage matched (ask_submit); it never includes the question or its words.

Our demo application form uses Google Forms on our company Google account. It collects your email, selected product and evaluation request to respond to your enquiry. Responses are private, not published to other applicants. Google processes the form under its service terms. Contact contact@weavist.ai to request access, correction or deletion of your enquiry. Do not submit passwords or customer personal data.

Form field values are not sent to our Analytics events. Opening the form is not proof of submission; received applications are counted in the private form response inbox, not inferred from CTA clicks.

Selecting an email link opens your email application. The CTA event is recorded before that handoff, but the address, subject, and message you send are not included in our Analytics event.

Demo links open separate product services, which may have their own access and data-processing notices. Google processes Analytics data under its own terms and privacy controls. You can use browser privacy controls or content blockers to limit Analytics collection.