Privacy policy

Who operates WeaverData

WeaverData is operated by GodMode Labs, Inc. This policy covers our public website, demo, account and workspace services, and the integrations you choose to connect. Contact godmodelabs.xyz@gmail.com for support or privacy requests.

Our default website analytics are cookieless and do not retain visitor IP addresses in analytics records. The tracker honors Global Privacy Control and Do Not Track. These choices do not prevent us from receiving information you deliberately send through a contact form or from processing account activity needed to provide the service.

Analytics on this website

This site runs our own first-party tracker. During your visit it records:

• Pages you view, links and buttons you click, how far you scroll and which sections you see.
• When you start or submit a form — never what you type into it.
• Page speed measurements (Web Vitals).
• The referring website and campaign tags in the link you followed.
• Coarse device details: device type, browser, operating system, screen size, language and time zone.

This information is stored in your own browser’s local storage (under the key plainsight-you) so the live demo can show you your own visit. It is not a cookie. You can delete it at any time from the “Your visit” panel on the home page or the tag debugger on the Tracking page, or by clearing your browser’s site data.

Separately, when enabled, our public-site collector sends page activity to WeaverData for business analytics. The local demo data is not uploaded by that collector. Hosting page-view analytics also honor your opt-out and browser privacy signals.

Optional behavior recording measures click positions, scrolling and time in public page sections. When enabled, it also creates a masked reconstruction of the public page for visual replay. Reviewed public page copy and selected public images and 3D scenes may be visible. Text is otherwise masked; input values, forms, private regions and embedded frames are excluded. Public visuals use bounded image samples. Selected customer websites may also record up to 60 seconds of designated public canvas animation as private video, without audio or screen recording. Account and dashboard pages are excluded. Ordinary recordings are retained for up to seven days. Video recordings and their matching page data stay until the business deletes the visit; new video capture stops at its storage or recording cap.

Information you send us

When you use the Contact us form we receive your name, email, business name, website and message. We use this information to respond, discuss the service and manage the resulting business relationship. A copy is also saved in your browser so it appears in the demo inbox.

When you use an account or workspace, we process your sign-in identity, workspace membership and role, settings, and the business records you create or connect, such as inquiries, contacts, bookings, invoices and reports. Workspace permissions determine which members can access or manage those records.

The live demo

The demo uses sample data and stores demo edits in your browser’s local storage. Those edits do not change a live customer workspace. Public-site analytics and information you deliberately submit through the contact form are handled as described separately above. Use “Reset” in the demo to restore the original sample data.

Our customers’ data

When a business uses WeaverData, it controls the data collected on its own website and we process it on its behalf. By default, visitor data is collected without cookies, IP addresses are discarded after country lookup, and privacy signals are honored.

A business can turn on ad attribution. In that mode a first-party identifier is stored on its own site to recognize returning visitors and ad click identifiers are kept with the visit, after the visitor agrees when the business uses a consent banner or its own consent tool. The business is responsible for asking for consent where the law requires it. If the business connects an ad platform, it can choose to send that platform hashed contact details of people who bought, so the platform can measure its ads.

We use these service providers to run WeaverData: Railway (application hosting and database), Vercel and Cloudflare (website hosting and delivery), Clerk (sign-in), Stripe (payments), Amazon Web Services (email delivery), Cloudflare R2 (encrypted backups), Google (only the Google services a business chooses to connect) and, where enabled, AI features. Information is shared only as needed for the features you use. A payment provider processes payment details through its own payment interface.

Google account connections

Google integrations are optional. You authorize the requested permissions on Google’s consent screen. We receive the connected account’s email address and Google account identifier to identify the connection, together with authorization tokens that allow the chosen integration to work. We do not receive your Google password.

• Search Console: we read the properties your account can access and the selected property’s search reports, including queries, pages, dates, clicks, impressions, click-through rates and average position. We store returned reporting data for the selected website, watched queries and any queries you import into SEO research. This permission does not let WeaverData change your website or Search Console property settings.
• Calendar: we read calendar names, identifiers, time zones and access roles so you can choose calendars. We read availability and selected event details, such as times, titles, status and your attendance response, to show conflicts and avoid double booking. When you enable booking synchronization, we create and update booking events in the selected writable calendar and remove those events when the corresponding booking is canceled. Event content can include the booking’s service, customer, contact details, location and attendees according to your settings.
• Gmail: the send-only integration sends the business messages you compose or configure, such as inquiry replies, booking notices, invoices and reports. We process their recipients, subjects, bodies and delivery records. It does not read your Gmail inbox.
• Sheets: we create and update an app-created reporting spreadsheet in your Google account. We store its identifier and link and write the workspace’s reporting figures to its reporting tab. This integration does not request access to all of your Drive files.

Stored Google authorization tokens are encrypted on our server. We use Google data to provide the connected features you request. Workspace members with the relevant permissions can see the resulting reports and business records. Data sent to Google, including calendar events, outgoing messages and reporting spreadsheets, is also governed by your Google account and sharing settings.

How Google data is used and shared

WeaverData’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. We do not sell Google user data, use it for advertising, or use it to train generalized AI or machine-learning models.

We share Google data only to provide the features you authorize, with service providers needed to operate those features, for security, or as required by law. Human access to Google data is limited to your affirmative agreement to view specific data, necessary security investigations, legal requirements, or permitted internal use of aggregated data.

You can separately authorize an external assistant connection to read supported workspace reports and business summaries. Google connection tokens are not returned through those reporting tools. Authorizing a Google integration does not by itself authorize an external assistant. Review the information you choose to share and the external provider’s terms before connecting it.

Disconnecting Google and deleting connected data

Workspace administrators can disconnect an integration in Settings. For Gmail, switch the workspace sender away from the connected account or disable that sender. This removes the stored authorization for that connection and stops its future use. You can also revoke WeaverData’s access in your Google Account connections.

Disconnecting is separate from deleting data. Previously saved reports, imported research, bookings and message delivery records can remain in your workspace. It does not delete messages, events or spreadsheets already created in Google. Use the applicable workspace controls or contact godmodelabs.xyz@gmail.com to request deletion of retained connected data. Manage copies in Google through Google’s controls.

Retention

We retain inquiries and business records as needed to provide the service and maintain the business relationship, subject to deletion requests and applicable legal obligations. Analytics retention depends on the workspace’s plan and configured retention period. Behavior-recording retention is described above. A reporting window does not mean all stored records are automatically deleted at its end.

Authorization tokens remain stored while a connection is active and are removed when it is disconnected. Owners can delete a workspace; administrators can delete supported website and business records. Contact godmodelabs.xyz@gmail.com for data that is not covered by a self-service deletion control. Deleting records from the active service does not recall copies already exported or sent to another provider.

Your choices and rights

You can ask us to access, correct, export or delete your personal information. Depending on where you live you may have additional rights. Contact us at godmodelabs.xyz@gmail.com.

Changes

We’ll update this page when our practices change and revise the date at the top.