Last updated: September 11, 2026
This page describes the information enspire processes when you visit the site, run a public AI-visibility check, create an account, or use a workspace. It also explains which outside services are involved.
Requests to enspire pass through Vercel, our hosting provider. As with other hosted services, Vercel may process request information such as an IP address, browser and device details, the requested URL, referrer, approximate location, and timestamps.
We use Vercel Web Analytics for aggregate traffic and product-usage measurement. It records page views and limited custom events such as a call-to-action location, sign-in method, selected plan, or check/scan score. A public check event may include the submitted site or repository target. We do not attach an account ID or email address to these events. Vercel describes Web Analytics as cookie-free and says it creates a short-lived hash from request data rather than storing a visitor’s IP address. See Vercel’s Web Analytics privacy documentation for its current technical details.
New accounts can sign in through Google or GitHub OAuth. Those providers send Supabase Auth the identity information you authorize, which may include your name, username, email address, avatar, and a provider identifier. Existing users can request an email magic link; this requires processing the submitted email address. Supabase manages the authentication session, and enspire keeps the profile and session information needed to associate you with your workspace.
A public check accepts a website domain or public GitHub repository. To build the product profile, enspire may fetch the public homepage text or the repository’s public metadata, README, and package.json. It then generates buyer questions and stores the resulting profile, AI answer excerpts, named products and ranks, and provider-returned source metadata and URLs, along with the visibility score, indexing observations, and suggested actions.
Public-check reports are not private. A report can be opened by anyone who has or discovers its URL, and a recent result may be reused when someone checks the same target. Do not submit a private repository, secret URL, or confidential material to the public checker.
To limit automated use, enspire derives a SHA-256 hash from the request IP address and stores that hash with the check for rate limiting. The public-check record does not store the raw address, although Vercel may still process request information as described above. Hashing reduces exposure but does not make the value impossible to associate with repeated requests.
Installing the enspire GitHub App is separate from signing in. You choose which repositories the App can access. Enspire stores repository metadata such as the full name, installation identifier, default branch, and homepage. The current AEO workflow reads the repository README and limited files needed to understand the product or prepare a requested pull request; it does not clone the complete repository into the enspire application database.
A workspace can contain your product profile and description, domain, approved buyer questions, selected answer engines, scan history, answer excerpts, recommended products and ranks, provider-returned source metadata and URLs, scores, suggested action plans, outreach or listing drafts, and drafted comparison, alternatives, or answer pages. We also store the status and identifiers needed to review, publish, or create and track a GitHub pull request. If you publish a hosted page, its content and public URL are public by design.
If you buy a plan, Stripe hosts checkout and processes your payment details. Enspire sends Stripe the details needed to start checkout, such as the selected plan, email address, and internal user reference, and stores Stripe customer/subscription identifiers, plan, and subscription status. We do not receive or store full card details.
When service or digest email is enabled, enspire sends the recipient, sender, subject, and message content to Resend for delivery. We also process information you include when contacting support.
We use this information to:
Anthropic is used for product profiling, interpreting scan answers, suggesting actions, and generating drafts. Depending on which answer engines are configured and selected, a buyer question is also sent to OpenAI (ChatGPT), Google (Gemini), Anthropic (Claude), or Perplexity. Their returned answers and source metadata may then be processed by Anthropic to identify recommendations. The material sent varies by operation and may include relevant profile details, public homepage or README excerpts, buyer questions, AI answers, source metadata, and drafting context. A returned source link is not necessarily a verified inline citation for the stored excerpt. Do not place secrets or unnecessary personal information in those fields.
Enspire does not use analytics cookies. Vercel Web Analytics is cookie-free. The site does use cookies that are necessary to sign you in and continue a requested flow: Supabase authentication cookies maintain your session, and an HttpOnly enspire_check cookie can hold a public-report reference for up to seven days while you sign in and connect a matching repository. It is removed after a successful import. Google, GitHub, Stripe, and other services may use their own cookies when you visit or are redirected to their sites; their policies govern that activity.
We disclose information to service providers only for the functions described here. Which providers receive data depends on the features you use and the answer engines configured for a scan.
These providers operate under their own terms and privacy notices, which may change independently of this page. We may also disclose information when required to respond to a valid legal request or to protect users and the service.
Workspace records are intended for the signed-in account unless you choose an action that makes content public. Public checks, hosted pages, and GitHub pull requests in public repositories can be seen and copied by others. Search engines and other third parties may retain copies of material after it is changed or removed from enspire.
Retention varies by the type of information and how the service is used. Public checks may remain cached and be reused. Account and workspace records are kept while they are needed to provide the service; billing and service records, provider logs, and backups may follow different schedules. We do not promise that deleting enspire data removes public copies held by GitHub, search engines, AI providers, or other third parties.
To request access, correction, export, or deletion of account data, email support@enspire.co. The options available can depend on the applicable law and whether some information must be kept for security, billing, dispute, or other operational reasons.
Enspire uses measures such as account-scoped database access controls, server-side service credentials, signed webhook verification, and separately granted GitHub App access. Public reports and content you choose to publish are excluded from those privacy expectations. No internet service can guarantee absolute security.
You choose the sign-in provider, repositories, buyer questions, answer engines, and whether to publish or create a pull request. You can revoke the GitHub App’s repository access in GitHub. Revoking access stops future repository access but does not by itself delete workspace records already stored by enspire. Depending on applicable law, you may also have rights to object to or restrict certain processing or to complain to a competent data-protection authority. Contact us to make a request.
We may update this page as the product or its providers change. Questions or privacy requests can be sent to support@enspire.co.