Your data.
Clear boundaries.

Liftaven is an SEO review and improvement workspace operated by Saeed Mashhadi. Questions or deletion requests can be sent to saeed@lindo.ai.

Website analytics

We use Google Analytics 4 and self-hosted Matomo, installed through Google Tag Manager, to understand visits to Liftaven’s public website and resource library. Google receives public page views, browser and device information, approximate location and cookie identifiers. We use these reports to understand which pages people find useful and improve the website. Google processes this information under its Privacy Policy. We exclude dashboard and OAuth callback page views, and we do not send connected marketing reports, chat messages or provider credentials to website analytics. Google signals and advertising personalisation are disabled by our tag setup. You can block analytics through your browser or the Google Analytics opt-out browser add-on.

Matomo runs at tracking2.lindoai.com and receives public page paths, browser and device information and network information needed to measure visits. Matomo tracking cookies are disabled. Both trackers omit URL query strings and fragments. Page titles contain only the public site name and path.

Website setup

When you enter a website to get started, we retrieve its public homepage title and description to help you confirm your business context. No account credentials or AI analysis are used for this preview. Preview metadata is cached briefly. Your setup answers remain in this browser tab until you sign in and save them to your workspace.

What we store

We store your account identity, provider connections, granted scopes, selected properties and authentication credentials needed to retrieve reports. Provider credentials remain on the server. Report responses and short-lived access tokens may be cached to reduce repeated provider requests. Authentication and operational logs may be retained by our Cloudflare infrastructure.

How we access and use Google user data

With your permission, Liftaven retrieves Google user data through Google’s APIs to provide your marketing dashboard and the reports you request through an authorised MCP client. We use the following data for these specific features:

Google account identity. We use your Google account identifier, name, email address and profile image, where provided, to create or recognise your Liftaven account, display your profile and associate your connected Google accounts with your workspace.

Google Search Console. We read the properties you can access, search queries, page URLs, clicks, impressions, click-through rates, average positions, country and device breakdowns, URL inspection results and sitemap information. We use these to display search performance, compare reporting periods, identify pages and queries to investigate, and show indexing and sitemap status. When you explicitly request sitemap submission, we send the selected property and sitemap URL to Google. This is why Liftaven requests Search Console access beyond the read-only scope.

Google Analytics 4. We read account and property information, reporting configuration and aggregated reports such as users, sessions, traffic sources, landing pages, engagement, events and conversions, including available device and geographic breakdowns. We use these to display website traffic and engagement, compare periods and help you understand how visitors reach and use your website. Analytics access is read-only.

Connection credentials. We use Google OAuth access tokens, refresh tokens and granted scopes to authenticate these requests and keep your approved connection working without asking you to sign in for every report. Google provider tokens remain on our servers and are not included in reports returned to MCP clients.

Other provider permissions

Bing supports search reporting and deliberate sitemap submission. Liftaven does not implement Analytics writes, property deletion or sitemap deletion.

AI agents and MCP

When you authorise a unified MCP client, it can retrieve permitted reports from the provider connections in your Liftaven workspace, including providers you connect later. You approve the client once in Liftaven; existing provider connections do not need separate consent for every agent. Disconnecting a provider in Liftaven removes its access through workspace MCP grants. Those reports are then available to that client and its AI provider under their own privacy terms. Choose a client you trust. Liftaven does not send your dashboard reports to AI merely because you sign in. If you enable AI analysis in workspace setup and ask a question in Liftaven chat, relevant reports, website content, your business context and conversation messages are processed by OpenRouter and its model providers to answer your request. Provider credentials are not sent to the model. Conversations and supporting evidence are stored in your Liftaven account; you can delete conversations in the workspace. Scheduled reviews can be paused in SEO setup. You can request removal of stored reviews and AI consent by contacting us; account deletion removes associated records.

Who receives Google user data

Cloudflare, our infrastructure provider. Liftaven uses Cloudflare Workers, D1 and KV to run the service, store account and connection records, process Google API requests and cache report responses. Cloudflare processes Google account information, connection credentials and reporting data on our behalf as needed to host and operate these features. Infrastructure logs may include request and error information.

MCP clients and AI services you authorise. When you approve an MCP connection and that client requests a Google report, Liftaven transfers the requested report data and relevant account or property identifiers to that client. If the client uses an external AI service, that service may receive the report to answer your question. The recipient is the client and AI service you choose; For built-in chat and SEO reviews, Liftaven uses OpenRouter and its model providers after you enable AI analysis and submit a question, request a review, or explicitly enable scheduled reviews. Relevant Google reports and account or property identifiers may be processed by OpenRouter and its model providers to produce that answer. Browsing ordinary dashboard reports does not invoke AI. Review your chosen service’s privacy, retention and model-training settings before connecting it. Disconnecting stops future access but does not erase reports already received by that service.

Support, security and legal disclosures. The Liftaven operator may access specific Google user data with your permission to investigate a support request, or where necessary to investigate security issues or comply with applicable law. We may disclose the necessary data to relevant authorities when legally required.

We do not sell or rent Google user data, disclose it to data brokers, or share it with advertising networks for ad targeting. Connecting Bing does not cause us to transfer your Google reports to Microsoft. We do not use Google user data to train general-purpose AI or machine-learning models, and we do not transfer it for that purpose. Authorised MCP reporting is provided to answer your requests.

Google API data commitments

Liftaven’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. These commitments also cover data derived from Google reports. We use this information to provide the features described above, not for unrelated profiling, serving personalised advertisements or credit decisions.

Website editing connections

If you connect Lindo, Webflow, WordPress or GitHub, Liftaven stores your connection credential encrypted and uses it to read permitted content and apply changes you review in Actions. Relevant content may be processed by OpenRouter and its model providers when you use chat. Proposed changes include the original and replacement content. Applying a CMS change may affect a live page; GitHub changes create a branch and pull request. These providers receive only the requests and content needed for a change you approve or a GitHub pull request you explicitly authorise through automation settings, not an automatic copy of your Google reports. Disconnecting removes the usable editing credential and its associated proposals.

Onboarding and product emails

Welcome and setup emails are optional. When you opt in, Cloudflare Email Service processes your email address and message content on our behalf. Promotional follow-up campaigns are not enabled. These emails do not include Google reporting data. You can unsubscribe using the link in each email or change your preference in workspace setup.

Payments

When you choose a paid plan, Stripe processes payments and subscriptions. We share your account email and a billing account identifier with Stripe. Liftaven stores subscription status and credit usage, but does not receive or store your full payment card number.

Security

Credentials are kept in server-side storage, connections use HTTPS, and application checks bind credentials to their account or authorisation grant. Session credentials are stored in your browser so you can stay signed in. We do not sell provider data.

Disconnecting and deletion

You can disconnect supported connections in the workspace or revoke access directly in Google, Meta, Bing or X. Disconnecting removes the usable connection from Liftaven; short-lived caches may remain until expiry. Contact us to request deletion of your Liftaven account and associated stored connections. Removing a Liftaven connection does not delete a property, campaign or account at a provider.

Separate from Searchlight

Liftaven and the Searchlight mobile product at gscmobile.app use separate deployments and account stores. Signing into one does not automatically connect the other. Existing Searchlight consent grants are not silently widened or transferred.

Changes

We will update this page when our handling of data changes. The date above identifies this version.

Public SEO research

When you request competitor, keyword, domain or backlink research in chat, Liftaven may send the public domain being researched and the selected country and language to DataForSEO. We do not send your Google user data, private reports, conversation text or provider credentials to DataForSEO. Its public search estimates are stored with the conversation evidence and may be cached for up to 24 hours. Relevant research results are processed by OpenRouter and its model providers to answer your question. These estimates are separate from your measured Search Console and Analytics performance.

GitHub website connections

When you connect the Liftaven GitHub App, GitHub shares your account identifier, username, accessible installations and selected repository information so you can choose a website. We temporarily store an encrypted user authorisation token while you select repositories; setup sessions expire after 30 minutes and are cleaned up periodically. For a saved connection, we store the installation and repository identifiers, selected branch and optional website folder. Liftaven generates short-lived credentials limited to that repository for background work. GitHub permissions apply to the repository; Liftaven enforces the selected folder on content reads and proposed changes. Repository source content may be processed by OpenRouter and its model providers when you request a relevant analysis or authorise an SEO review. Credentials are never sent to AI. Approved changes send file content and pull request details to GitHub. Disconnect in Liftaven to stop future use, or revoke the app in GitHub. Existing pull requests and commits remain in GitHub.

Setup progress

We record first-party setup milestones, such as completing a website check, matching Google properties and starting your first analysis, to identify setup problems. These records contain your account identifier, website, milestone and time, not report contents, conversation text or credentials. Setup records are retained for up to 90 days.

Saved conversations and documents

We store your conversations, project folders, saved documents and website preferences in your account. Your AI assistant can create, read and update private drafts when you ask it to. Relevant saved content may be sent to OpenRouter and its model providers to answer your request. Saving a document does not publish it to your website. These records are retained until deletion; contact us to request account data deletion.

Scheduled SEO reviews and website improvements

When you explicitly enable scheduled reviews, Liftaven checks the selected public website every three days and retrieves relevant Search Console queries and performance, Google Analytics traffic reports and Bing reports where available. You may also request a review manually. Relevant report data, website content and your business context are processed by OpenRouter and its model providers to identify issues, suggest metadata improvements and prepare unpublished article drafts. Provider credentials are never sent to the model. We store review findings, evidence, drafts and change records in your account until deletion; the dashboard displays recent reviews. Pausing stops future scheduled reviews but does not delete earlier records.

Website edits default to proposals requiring review. If you explicitly enable automatic GitHub pull requests, Liftaven can create a branch and pull request containing metadata changes to the exact homepage source you select, within your authorised repository folder. It does not merge pull requests. Article drafts remain unpublished. Updating or disconnecting the website connection prevents subsequent use of that credential. Google data is used only to provide these user-facing SEO features; it is not sold or used to train general-purpose models.