Privacy choices in plain language.

This page explains what George Digital collects when you ask about a service, choose analytics, or become a client.

Information you provide

Inquiry forms, email, booking tools, and the client portal may collect your name, email address, phone number, website, business type, actual service area, site status, needed features, content readiness, project needs, billing details, and files you choose to send.

Why it is used: to review fit, answer questions, prepare an order, deliver services, process payments, and support active work.

Client information: project files, messages, and reports are used to provide the requested service.

Contact: privacy questions can be sent through the contact page.

Next SEO Fix review applications

The Next SEO Fix review application collects your name, operational email, website URL, whether you are the owner or authorized operator, your concrete goal, platform, ability to edit and publish, optional implementation preference, optional Search Console status, optional context, plus two independent, optional consent choices.

Application administration: AgencyHandy receives the submitted application, contact, and fit details only to administer and assess the review application. The applicant is not marked as converted. An operational application email is required for application administration and is distinct from optional marketing-email consent.

Independent choices: Marketing-email consent and public-case consent are separate, optional, and unchecked choices. Public-case consent does not affect selection. Applications are private by default; any public case or sanitized group use requires the separate public-case consent.

No transaction or guaranteed outcome: A review application is not an order, purchase, payment, sale, confirmed service lead, service engagement, delivered review, Skool payment, or paid founder. Selection and outcomes are not guaranteed.

Campaign attribution and analytics

If you accept analytics, this site stores a random attribution ID and first, last, first-paid, and last-paid visit details in first-party cookies for no more than 90 days. Those details can include the landing path, the referring site's scheme and host only (never its path or query string), sanitized UTM campaign fields, provider-format Google or Meta click IDs, and capture times. Campaign values that resemble contact details, phone sequences, IP addresses, full URLs, credentials, UUIDs, or other direct identifiers are discarded. Landing or source paths with identifier-like segments are replaced with a generic 404 path.

Google Analytics and Ads: Google Analytics loads only after acceptance. Google Ads conversion tracking may also load when a campaign is configured. Google receives a sanitized same-origin page location without the page query string and a blank page referrer. Form contents, email addresses, phone numbers, and click IDs are not added to GA4 event parameters.

Meta Pixel: Meta Pixel loads only after analytics acceptance. It may record a page view and, after the application endpoint confirms a newly created Next SEO Fix application, one Lead event. That event identifies the review offer and uses an opaque submission reference for deduplication; it does not receive the applicant's name, email, website, form answers, qualification status, purchase status, or promised outcome.

AgencyHandy: receives the inquiry details you submit, including the website fit context, plus opaque attribution and submission references and short campaign labels so the lead can be reconciled.

Supabase: receives the opaque references, campaign touch data, AgencyHandy lead ID, selected non-PII fit categories, whether a service area was provided, and qualification or payment outcomes. The attribution ledger does not receive the form's name, email, phone number, website entry, exact service area, or message.

Review application measurement

GA4: GA4 records a review application only after analytics acceptance and only after a server-confirmed application. seo_review_application is secondary measurement and receives approved non-PII event and page fields: the form name, secondary role, sanitized same-origin page location, and blank page referrer. It does not receive form contents, contact details, click IDs, or the application's submission reference. It does not use Ads conversion or generate_lead semantics.

Meta: Meta records a standard Lead only after analytics acceptance and a server-confirmed newly created application. This means an application was received; it does not mean the site qualified, was selected, received a review, made a purchase, or produced revenue.

Supabase: After AgencyHandy confirms the application, Supabase may receive a secondary record limited to approved non-PII categories and opaque references, including the CRM lead ID, qualification categories, source path and offer slug, and consented, sanitized attribution when present. Secondary recording is not required for the application to be accepted. The record never includes the application name, operational email, website URL, goal, free-text context, or form contents.

Your analytics choice: If you reject analytics, attribution is absent but the application still works.

Google Ads: Review applications never trigger Google Ads confirmed-service conversion reporting. Only the existing, separately server-confirmed service-lead flow can trigger Google Ads confirmed-service conversion reporting after analytics consent.

Your choice

You can accept or reject analytics in the on-site control. If you reject, Google Analytics, Google Ads measurement, and Meta Pixel do not load, campaign attribution cookies are not kept, and the inquiry form and checkout links still work. Your choice is saved in your browser. Use Privacy choices in the footer to clear that choice and decide again.