Clear handling for the information behind the work.

We handle information that is needed to respond to an inquiry, operate an AnswerLift workspace, or complete a purchase.

• Snapshot and sales inquiries. Name, work email, agency or company, agency website, optional client URL, and the freeform visibility concern you submit.
• Account and workspace information. Information associated with authenticated users, workspaces, membership, and team invitations.
• Work product entered in the service. Audit details, evidence observations, sources and URLs, remediation tasks, notes, and related review information entered by authenticated users.
• Usage and attribution information. Basic, aggregated site-use and attribution dimensions described below.
• Transaction information. Information handled through the platform checkout flow when you purchase an offering. AnswerLift does not add payment-card fields to its public intake form.

Account and workspace information is kept for as long as your account is open, and is deleted when you delete your account (see the account deletion page below). Billing and payment records are retained for six years from the end of the accounting period the record falls in, which is the retention HMRC requires of a UK limited company. Snapshot and sales-inquiry information is kept only as long as needed to respond to the inquiry it relates to.

AnswerLift runs on the publisher’s own virtual private server, hosted by OVHcloud in France, and the application database and backend functions run on that same server. Hosting therefore keeps information inside the EEA. Some service providers do process information outside the UK/EEA, including in the United States: Stripe, which takes payment for the Visibility Sprint; the Perplexity and OpenAI APIs, where a workspace has scheduled prompt collection and those provider keys are configured; and PostHog, only where browser analytics is configured and you have consented to it. Where that happens, we rely on the UK International Data Transfer Addendum to the EU Standard Contractual Clauses as the transfer safeguard.

AnswerLift is hosted on the publisher’s own virtual private server at OVHcloud in France. The application database, the backend functions and the sign-in service for workspace accounts all run on that server as a self-hosted Convex instance, so there is no third-party backend platform holding this data. Payments for the Visibility Sprint are taken by Stripe on their own hosted checkout page; the application records the resulting order but never receives or stores card details. Snapshot and sales inquiries are stored in that same self-hosted database and are not passed to any marketing or advertising service.

Where a workspace schedules prompt collection and the provider keys are configured on the deployment, the prompt text is sent to the two paid APIs described on the methodology page — the Perplexity Sonar API and the OpenAI Responses API — and their answers are stored as evidence. Nothing else is sent to them, and with no key configured no request is made at all.

When browser analytics is configured, the application uses PostHog for site analytics and event capture. The specific browser-storage and attribution behavior is described in the next section.

We may disclose information when needed to operate these services, complete a purchase, respond to a request, protect the service, or meet legal obligations. This notice does not describe providers that are not evidenced by the current application implementation.

The public site records aggregate daily attribution counts for landing pages and high-level source classifications, such as direct, search, social, referral, or AI answer engine. The application classifies a browser referrer on the device and sends the classification rather than a raw referrer URL. Its aggregate attribution reporting does not send IP addresses or persistent visitor IDs to the AnswerLift attribution table.

Attribution and analytics storage are switched off by default and run only if you accept them on the banner. If you accept, the site keeps first-touch and current-session attribution information in browser local storage and session storage, including UTM values when present, and PostHog is initialized for page views, event capture and checkout attribution, using local storage and a first-party cookie for its persistence. Checkout links carry no identifiers: the Stripe Checkout Session is created by our own server, and the link we hand your browser is the one Stripe returned, unmodified.

If you reject, or have not answered, none of that runs: no PostHog request is made, no attribution entry is written or read, and nothing is stored on your device except the record of your own choice, which is strictly necessary. The session cookie used to keep you signed in is also strictly necessary and is not covered by the banner. You can change your choice at any time:

To ask about access, correction, deletion, or another privacy matter, email support@answer-lift.com. We may need to verify your identity before acting on a request.

You can delete your account and its data yourself from inside the app, without contacting us. The public account deletion page sets out exactly what is deleted, what is kept and why. If you are in the UK or the EEA you also have rights of access, correction, restriction, objection and portability, and the right to withdraw analytics consent at any time; we answer data-rights requests within one month, and you can complain to the Information Commissioner's Office.

California residents may use the same contact path to submit a privacy-related request. The availability and scope of any request depend on the information involved and applicable law.

We may update this notice as the service or its operational practices change. When we do, we will post the updated version here and revise the effective date.

Questions about this notice can be sent to support@answer-lift.com.

Looking for a Snapshot? Request one here.