Cookie Policy

We use first-party cookies for sign-in and security, a non-essential first-touch attribution cookie (ap_attr), optional Google Analytics cookies, and Meta ad-measurement cookies. Google Analytics is off until you choose Allow analytics; declining, closing the notice, or pressing Escape does not enable it. Meta ad measurement is on by default in the United States and other places outside the European Economic Area, the United Kingdom, Switzerland and Quebec, and you can opt out at any time with Opt out in the cookie notice, Cookie settings → Turn off Meta, the Your privacy choices link, or the control under “Your privacy choices” below. Global Privacy Control: if your browser sends it, we treat it as an opt-out; if you choose Allow Meta while it is on, we honor that choice, and an Allow Meta chosen before you turned it on no longer applies. Opt-in places: in the EEA, the UK, Switzerland and Quebec, and whenever we cannot determine where a visit comes from (including a visit from Canada whose province we cannot tell), Meta ad measurement stays off until you choose Allow Meta. Checkout links opened directly (for example from an email) without a visit to one of our pages in the previous 24 hours are not measured for Meta unless you have chosen Allow Meta. Your choice is saved by our server for 400 days so that browser storage limits cannot silently undo an opt-out. You can change your choices with the Cookie settings button on any page. Google Analytics runs with its advertising features disabled.

Our Google Analytics integration measures allowlisted public marketing pages only, not sign-in, registration, customer/admin dashboards, the extension, or tools that accept dealership text. The page-view fields we send contain a fixed page label and canonical public path without query strings, URL fragments, or referring URLs. We do not send account identifiers, email addresses, phone numbers, vehicle records, or buyer conversations to Google Analytics. If you allow it, Google receives standard request information such as your IP address and browser/device information, plus pseudonymous analytics identifiers and usage events. Google processes that data under its own terms and Privacy Policy; it is not anonymous simply because we omit account details. Google Signals, advertising personalization and automatic user-provided data collection are disabled.

Optional Google measurement includes scrolling and eligible public demo-video engagement, plus application-controlled events for selected calls to action, extension/download links, phone/email links, pricing and billing choices, FAQ openings, sections viewed, and checkout attempts or checkout-page creation. Our application-controlled event fields use fixed labels, plan/billing choices, and a coarse source category such as search, social or direct—not typed form values, contact details, raw campaign text, full clicked URLs or error messages. Approved embedded-video measurement can include the public demo’s title, URL, provider, duration and playback progress. Automatic search, form, outbound-link and file-download collection is disabled in favor of these controlled events.

These events describe website interactions, not necessarily business outcomes: a phone/email click does not prove contact, an extension/download click does not prove installation, a request to open the demo does not prove it played, and checkout creation does not prove payment. This Google integration does not send a purchase or successful-registration event. Confirmed payment records remain in our billing systems.

Meta ad measurement (Meta Pixel and Conversions API). We advertise on Facebook and Instagram and use Meta’s measurement tools to learn which ads lead to sign-ups and paid subscriptions. While Meta ad measurement is on for you under the rules above: (1) the Meta Pixel loads on our public marketing pages and on the welcome page after checkout (there only in the browser that started that checkout)—never on sign-in, the registration form, customer/admin dashboards, the extension or free-text tools—and sends Meta the page address you view (including campaign parameters such as utm_* and Meta’s fbclid), page views, a view of our homepage, an ad landing page or pricing, a Lead (with no form contents) on the thank-you page after you send us a question from our ad landing page, checkout starts with the plan you picked, and, after a paid checkout, a Purchase with the amount actually charged, currency and plan; Meta’s script also receives your IP address, browser details and its _fbp/_fbc identifiers; (2) when you start checkout and our server connection to Meta is active, we store your _fbp/_fbc identifiers, IP address and browser user agent with your Stripe checkout session so our server can tell Meta about the completed purchase; and (3) our server sends Meta that purchase, the confirmation of a free account’s email address, or a Lead when you send us a question or choose Continue with Facebook on our ad landing page, with your email address and account ID in SHA-256 hashed form, those identifiers, the amount paid and the plan. The welcome page reports a purchase only in the browser that started that checkout, within 24 hours, and only once our billing system has accepted the payment. We switch off Meta’s automatic button-click, page-metadata and history-change events. If you opt out, send Global Privacy Control, or are in the EEA, UK or Switzerland and have not chosen Allow Meta, our site and servers send Meta nothing. Renewal payments are not sent to Meta. Meta processes this data under its own Privacy Policy and business terms, which can include measuring, delivering and improving our ads and letting us reach people who visited our site. Opting out stops further sending by our site and servers and removes the accessible _fbp/_fbc cookies, but cannot recall data already sent.

Separately, we measure site traffic with Vercel Web Analytics, which is cookieless: it reports aggregate page views, referrers, country, device class, and fixed interaction events such as CTA clicks, demo plays, plan choices and sections viewed. Those events contain labels chosen by us—not anything a visitor typed—and do not create a cross-site profile or store an identifier on the visitor’s device. The Google Analytics choice does not change this existing Vercel measurement or the first-touch attribution described below.

After Stripe accepts a request to create a hosted checkout, AutoPosting Pro attempts to keep one server-side acquisition checkpoint so a browser click is not mistaken for a working checkout. That checkpoint contains only the selected plan and billing interval, a coarse fixed first-touch source category, and the landing-page version when present. Dynamic campaign and referrer text is not stored in this checkpoint. It contains no name, email, IP address, raw URL or referrer, Stripe session or customer ID, account ID, or visitor identifier, and it is not directly linked to an account. If that best-effort checkpoint cannot be recorded, checkout continues; aggregate checkpoint counts are therefore a lower bound, not a complete count of Stripe sessions.

When someone activates a phone or email link on one of our public marketing pages, the page also attempts a best-effort server checkpoint containing only the fixed channel (phone or email) and a coarse source category derived in the browser from ap_attr, if present. The request omits cookies and the browser referrer, and the product audit record stores no name, email address, phone number, destination, message, page, link position, raw URL, referrer, UTM text, account, organization, visitor identifier, or IP address. The server may use the request IP transiently for abuse limiting, and ordinary Vercel infrastructure logs still apply as described below. This activation count is not a lead: repeats, accidental or automated clicks, and clicks whose phone or email handler fails may count, while copied contact details or blocked requests may not.

For an exact campaign link registered by AutoPosting Pro, the normal site client may submit a best-effort first-party campaign-arrival checkpoint after a visible page matches a registered path and all four campaign parameters. The application payload contains only one fixed campaign code; the server derives the fixed source and landing labels from its own registry. This request is separate from the first-touch ap_attr cookie, does not read that cookie, and explicitly omits all cookies and the browser referrer. The application table stores only the UTC day, fixed registered code, and a count bounded at 5,000 per code per day. It stores no per-event timestamp, full URL, raw UTM value, name, account, organization, visitor or device identifier, or IP address. The request IP may be processed transiently into a short-lived HMAC rate-limit key, and ordinary Vercel infrastructure logs still apply outside this application counter. A recorded checkpoint means only that the endpoint incremented the registered key’s daily counter; it does not prove the URL rendered, a link click, referring site, unique or human visitor, dealership, lead, signup, purchase, or customer. Direct or replayed requests, copied links, reloads, multiple tabs, automation, and previews may count; blockers, hidden pages, network failures, request limits, and write failures may be missed. A count of 5,000 means at least 5,000 recorded submissions because the counter stops increasing at that cap. The admin report reads a rolling 90-day window; older daily aggregate rows follow the service’s general retention practice rather than being automatically deleted when they leave that report.

Cookies we set

The cookies below are first-party (stored for this website). That does not mean all data stays with us: the optional Google Analytics cookies support measurement sent to Google, and the optional Meta cookies support ad measurement sent to Meta. Sign-in cookies are marked HttpOnly and Secure where supported and generally appear only during sign-in. Google Analytics cookies, Meta cookies, ap_meta_consent and ap_attr are script-readable. Unlike opt-in Google Analytics, ap_attr is written on your first visit to an allowlisted public marketing page. A deliberately source-tagged link to the signed-out login page may also establish the campaign source, but the login path itself is not retained as marketing landing evidence; signed-in, operational, legal and arbitrary missing routes do not write it. It stores bounded arrival information: a classified source, referring host and path without the query string, landing path, campaign labels supplied in UTM parameters, first-touch time, and the homepage version when applicable. AutoPosting Pro does not intentionally put personal information in those fields, but an outside link publisher can place personal text in a campaign label or referring path. Campaign links should never contain personal information. On non-HTTPS local development the __Secure-/__Host- prefixes are dropped.

Browser storage (not cookies)

We also use your browser’s localStorage for small UI and consent preferences. These preference values are not sent to our servers:

• autopostingpro:setup:progress — remembers which steps of the portal setup checklist you have completed.
• ap_google_analytics_consent_v1 — remembers your explicit Google Analytics choice until you change it or clear browser storage. If storage is blocked, your choice applies only in the current tab.
• ap_cookie_notice_v1 — an older notice-dismissal preference. It is not permission for Google Analytics and is no longer used to make that choice.
• ap_meta_ads_consent_v1 — remembers your explicit Meta ad-measurement choice until you change it or clear browser storage (mirrored for the server in the ap_meta_consent cookie above).
• ap_meta_notice_seen_v1 — remembers that you pressed OK on the short Meta notice, so it does not reappear. It is not a consent choice.
• ap_meta_purchase_sent:<id> — set only after an allowed Meta Purchase was sent from the welcome page, so reloading that page does not send it twice. The id is a one-way code, not your order number.

What we do not use

• No advertising cookies other than Meta ad measurement as described above.
• No session recording or analytics collection of typed messages, customer account details, or dealership inventory.
• No Google advertising signals, advertising personalization, or cross-domain analytics linking enabled by this integration.
• We do not sell your data for money. Meta ad measurement shares website and purchase data with Meta for advertising, which California law can treat as “sharing”; you can opt out at any time as described above, and we honor Global Privacy Control.

Third-party services

• Google Analytics — optional website measurement after your consent, with Google’s processing described above. Data retention in Google Analytics is controlled by the property settings and is separate from our 30-day browser-cookie expiration.
• Meta (Facebook/Instagram) — ad measurement as described above (opt-out; opt-in in the EEA, UK, Switzerland and Quebec). The Meta Pixel script loads from connect.facebook.net and sends to facebook.com.
• Stripe — payments happen on Stripe’s own hosted checkout page (checkout.stripe.com). Stripe sets its own cookies there under its own privacy policy; card details never touch our servers.
• Iconify CDN — the site loads its icon graphics from the Iconify CDN. Those requests carry standard web-request data (IP address, browser info) like any resource load, and set no AutoPosting Pro cookies.
• Infrastructure logs — our hosting provider (Vercel) keeps standard server logs (IP address, user agent, timestamps) for security and operations, and the domain’s DNS and email routing run through Cloudflare. These are ordinary infrastructure records, not tracking cookies.

Managing cookies

Your privacy choices

Use Opt out (cookie notice), Cookie settings → Turn off Meta, the Your privacy choices link or the control above to opt out of Meta ad measurement; it stops further Meta sending by our site and servers and removes the accessible _fbp/_fbc cookies. Use Cookie settings → Turn off analytics to withdraw Google Analytics permission. This disables further collection by our integration and removes its accessible host-only analytics cookies; it does not recall requests already sent or automatically delete data Google has already received. Requests in flight may finish. You can also block or delete cookies in your browser settings. Blocking sign-in cookies prevents portal sign-in; public marketing pages still work. Blocking or deleting ap_attr changes nothing about how the site works for you and prevents durable first-touch attribution. The separate fixed-code campaign-arrival checkpoint does not use that cookie; browser privacy controls or content blockers can block its first-party request. If you start checkout or sign up directly from a current AutoPosting Pro page whose same-origin URL still contains campaign or click information, that current-page source may still be classified for that one request.

Changes & contact

If we ever add a new cookie, we will list it here and update the date above. Questions: founder@autopostingpro.com. See also our Privacy Policy.

This document is provided as a general template and does not constitute legal advice. Have counsel review it before relying on it.