Who we are
SearchWeave is operated by FIT Innovations LLC, Florida, United States. This policy explains how we handle personal information when you visit our website, create an account or use our content and publishing services. Contact support@searchweave.ai with privacy questions.
Business mailing address: FIT Innovations LLC, 400 N Tampa St Ste 1550, PMB 194755, Tampa, Florida 33602-4719 US.
FIT Innovations LLC determines how account, billing, security and operational information is used to run SearchWeave. For customer content, we carry out workspace instructions, including research, generation and authorized publishing. Your organization is responsible for the information it supplies and the instructions and access it authorizes. This notice does not replace any applicable data-processing agreement.
Information we process
We process account and organization details; business descriptions, websites, corrections and files you provide; public pages collected for research; article drafts, revisions and publishing records; connected-service permissions; and support communications. Operational records include request routes, status codes, timing, errors and workflow identifiers. Payment services, when enabled, supply billing and subscription records. Do not submit patient records, confidential third-party information or sensitive personal data that is unnecessary for the service.
How we use information
We use information to authenticate users, manage workspaces, understand your business, research topics, generate and revise content, perform authorized publishing, display performance results, provide support, administer billing and protect the service. Where applicable law requires a legal basis, processing depends on the purpose: performing our agreement, legitimate interests in operating and securing the service, legal obligations, or consent for optional processing.
AI and service providers
Relevant business descriptions, supplied instructions, research excerpts and drafts are sent to OpenAI for content tasks such as research, writing, verification and image generation. We have disabled OpenAI account options that share API inputs and outputs, feedback, and evaluation or fine-tuning data for model improvement and training. Processing inputs to produce a response is different from using them to train a general-purpose model. Provider retention and processing depend on the endpoint, contract and account settings; this policy does not promise zero provider retention.
Supabase supports authentication, databases and file storage, and Railway supports hosting. Our observability stack runs on Railway using Grafana, Loki, Tempo and Prometheus software; using that software does not itself send application telemetry to Grafana Labs. Google provides Search Console functionality and externally hosted fonts. Stripe handles checkout and subscription payments when enabled. Email and support providers process recipient details and communications when their integrations are enabled. Publishing sends selected content and media to your connected WordPress site. Providers receive information needed for their functions; their processing is also governed by their applicable terms.
Google Search Console
Connecting Google is optional. Performance reporting initially requests webmasters.readonly. If you enable automatic sitemap submission and indexing monitoring, we ask you to authorize the broader webmasters permission. Google permissions can cover properties accessible to your account, not just one blog path. SearchWeave requires a selected property that covers your blog and restricts its operations to that blog.
Imported performance records include dates, page URLs, search queries, clicks, impressions, click-through rates and positions. Optional discovery monitoring sends your existing sitemap URL and public article URLs to Google and stores submission metadata, indexing observations, crawl dates and canonical URLs. We retain indexing observations for up to 400 days and store encrypted access and refresh credentials. Stopping monitoring cancels future checks; disconnecting removes local Google credentials. Historical observations remain subject to retention and deletion requests. This feature does not edit WordPress content, access Gmail, Ads or Google Analytics, or guarantee indexing or rankings.
Google data use and disconnection
The current Search Console integration uses imported data for performance reporting and, when enabled, sitemap registration and indexing-status reporting. It does not send imported queries, page URLs, metrics or derived reporting summaries to AI providers. Public website content collected separately for research may still be processed by AI as described above. A future feature that uses Google data for AI recommendations would require updated disclosures and any required consent before that use begins.
Google data, including derived data, is subject to the Google API Services User Data Policy and its Limited Use requirements. It is not sold or used for advertising, credit decisions or general-purpose model training. Transfers are limited to consented user-facing features, security purposes, legal obligations, or a business transfer with prior explicit user consent. Human access is limited to your affirmative permission, necessary security or legal purposes, or aggregated internal operations permitted by those rules.
Disconnecting in Connections stops synchronization and removes local credentials. SearchWeave also attempts remote revocation; if that fails, the Google grant may remain active even though the local integration is disconnected. You can revoke access in your Google Account. Disconnection does not itself erase historical imported results; contact us to request deletion.
Cookies, browser storage and diagnostics
Authentication cookies maintain your sign-in session and are refreshed as the session changes. Tab-local session storage retains unfinished onboarding information, the selected workspace and payment-request identifiers; it normally lasts for the browser tab session and may be restored by the browser. Local storage retains your theme preference until changed or cleared. You can clear these items through browser controls, but doing so may sign you out or discard unfinished work.
Operational telemetry records service performance and failures. Application telemetry is designed to exclude credentials, cookies and request bodies; infrastructure providers may separately process network information such as IP addresses. Loading Google Fonts sends a request from your browser to Google. Browser storage disclosures do not replace consent or other controls where those are required.
Retention, security and international processing
Active account and workspace records are retained to provide the service and preserve shared work. Retention also depends on support needs, security investigations, contractual disputes and applicable billing or legal obligations. Deleting an individual account is different from deleting an organization and its shared content. Cancellation or disconnection is not a request to erase all records.
The Search Console cleanup process removes observations older than 400 days and superseded datasets after 30 days, in scheduled batches; historical results are not erased immediately on disconnection. Our hosted observability stores are configured for 30 days of routine logs and metrics and seven days of traces. These are operational retention settings, not a promise that every copy disappears at the exact cutoff. Our Supabase Pro database service provides daily backups with a seven-day recovery window. Database backups do not include uploaded files stored through the Storage service. Backup copies and provider-held records follow separate retention processes; deletion from the active service does not immediately erase every backup copy. Contact us for a deletion request and the scope and timing applicable to your records. Content already published to WordPress remains on that website unless separately removed there.
We use access controls and encrypted integration credentials, but no system is completely secure. FIT Innovations LLC operates from the United States, and our primary Supabase database is hosted in Oregon, United States. Using SearchWeave from another country involves transferring information to the United States. Other service providers and authorized support personnel may process information in additional countries. Contact support@searchweave.ai for information about the providers and transfer arrangements applicable to your information.
Your choices and rights
Depending on your location and applicable law, you may request access, correction, deletion or a copy of your personal information, object to or restrict processing, withdraw consent, or complain to a data-protection authority. Send requests to support@searchweave.ai. We may need to verify your identity and authority for the relevant workspace. Some records may need to be retained for legal or security reasons. Revoking an integration does not remove content already published on your website.
Children and policy updates
SearchWeave is a business service and is not directed to children. Contact us if you believe a child has provided personal information. We will update this page when our practices change and provide additional notice or obtain consent where required.
Optional website analytics
On our public landing pages, Google Analytics and our own presentation measurement may operate automatically for visitors approximately located in the United States or Brazil unless they opt out. Elsewhere, or when location is unknown, we request consent. Previous refusals and Global Privacy Control stop both systems. We determine approximate country on our server using a local IP-country database; this lookup does not send your IP to a geolocation provider or retain it as an analytics field. On our public landing pages, your analytics choice also controls Google Analytics. A separate host-only preference cookie remembers this choice for up to 180 days. Google Analytics can operate while our presentation experiment is disabled. When analytics operates, Google receives page-view and technical browser/device information and may process it internationally. We configure host-only analytics cookies for up to 180 days, omit URL query strings, fragments and referrers from configured page views, and disable Google signals and advertising personalization. We do not send account IDs, payment records or form values to Google Analytics. Withdrawal stops this tag and removes its cookies on the current host. Google Analytics retention is controlled separately in our Google property; the experiment retention periods below apply to our own experiment records.
Under the regional collection rules above, we use first-party analytics to compare presentation alternatives and understand progression from our website through account creation, paid-trial activation and completion of a first article. Choosing not to allow analytics does not affect account creation, payment or the service you receive. Results distinguish automatically enrolled and consenting visitors and may be inconclusive.
We store your analytics preference in a host-only cookie for up to 180 days. A separate secure host-only assignment cookie lasts up to 30 days. A signed, short-lived handoff connects our marketing and application websites. We record the presented page, trial-button and sample engagement, entry language and a coarse device category. After you sign in with a verified account, we may link these records to confirmed signup, the organization's first paid trial, first completed article and refunds. Payment and workflow records, rather than browser claims, establish those outcomes.
These analytics do not collect form contents, email addresses, full website URLs, advertising identifiers, fingerprints or session recordings. We keep experiment-level records for no more than 90 days and non-identifying daily aggregates for 13 months. Unknown attribution is reported in aggregate without creating an analytics identity for people who declined. Existing account, payment and security records have their own purposes and retention periods described elsewhere in this policy.
Change your choice using Analytics preferences in the website footer. Withdrawal stops collection, clears the assignment on that website and removes the experiment linkage to your account and payments; it does not delete records needed to provide the service or maintain required payment records. A cookie on another SearchWeave website is invalidated centrally and stops working on its next check; we cannot remove another website's cookie until you visit it. Non-identifying aggregates already finalized may remain. If our service cannot acknowledge withdrawal, the page pauses analytics and offers a retry. A temporary, host-only pending-withdrawal cookie, lasting no more than 24 hours, is used only to complete that request. An essential short-lived security cookie protects preference changes. Backup copies expire under the backup lifecycle described above.