Effective date: servicewebbuilder.com
This Cookie Pservicewebbuilder.com, doing business as EstimateFlow Pro (“we,” “us,” or “our”), may use cookies and similar technologies on the EstimateFlow Pro website. It should be read with our Privacy Policy.
This is a publication framework, not a completed cookie declaration or legal advice. The live website must be scanned after its hosting, analytics, checkout, security, support, embedded-content, and consent tools are configured. Complete every bracketed item and verify the resulting inventory before publication.
EstimateFlow Pro Cookie Policy
What Cookies Are
Cookies are small data files stored by a website or service in a visitor’s browser or device. They can support functions such as maintaining a session, remembering preferences, protecting a checkout, measuring website use, or recognizing whether a consent choice has already been made.
Similar technologies may include local storage, session storage, pixels, tags, software development kits, server logs, device identifiers, or scripts that read or write information on a device. In this policy, “cookies” may refer to these technologies collectively where appropriate.
Scope of This Policy
This policy applies to cookies and similar technologies used on the EstimateFlow Pro marketing, documentation, support, account, licensing, and purchase pages operated by us. It does not automatically govern cookies placed on independent customer websites that install the EstimateFlow Pro plugin.
Each plugin customer controls its own WordPress website, theme, plugins, analytics, estimator configuration, hosting, and consent tools. Customers must scan their own websites, identify technologies actually used, provide an appropriate notice, and obtain consent where required.
Cookies and Similar Technologies We May Use
The live website may use first-party cookies set through our domain and third-party cookies set or accessed by service providers. Potential purposes include essential website operation, security, user preferences, traffic measurement, checkout, license administration, support, embedded content, attribution, and advertising.
Listing a category here does not mean that category is currently active. [VERIFY EVERY ACTIVE TECHNOLOGY THROUGH A COOKIE SCAN, BROWSER TESTING, PROVIDER DOCUMENTATION, AND CONSENT-BANNER CONFIGURATION.]
Strictly Necessary Cookies
Strictly necessary cookies support functions the website cannot reasonably provide without them. Examples may include secure sessions, load balancing, consent records, shopping-cart status, checkout protection, account authentication, fraud prevention, and requested form submission.
These technologies are normally enabled because they are needed to provide a requested service or protect the website. They should not be repurposed for unrelated analytics or advertising. [LIST THE ACTUAL ESSENTIAL COOKIE NAMES, PROVIDERS, PURPOSES, AND DURATIONS.]
Preference and Functionality Cookies
Preference cookies may remember choices such as language, display settings, dismissed notices, region, form progress, or other optional functionality. They can make later visits more convenient but may not be necessary for the basic website to work.
[CONFIRM WHETHER PREFERENCE COOKIES ARE USED AND WHETHER CONSENT IS REQUIRED.] If a visitor declines them, the website should explain which conveniences may not persist without preventing access to unrelated content.
Analytics and Performance Cookies
Analytics technologies may help measure page visits, navigation paths, referring sources, device categories, errors, performance, and general use patterns. They should be configured to collect only what is reasonably necessary and to respect consent requirements.
[INSERT THE ACTUAL ANALYTICS PROVIDER, PROPERTY, DATA-SHARING SETTINGS, IP HANDLING, RETENTION, CROSS-SITE FEATURES, AND CONSENT MODE.] Do not state that analytics is anonymous unless the configured provider and data truly support that claim.
Checkout and License Cookies
A checkout, account, download, or license system may use cookies to maintain a cart or session, secure payment flow, verify delivery, remember an account login, prevent fraud, and administer a purchased license. Payment providers may also use their own technologies under their policies.
[INSERT THE ACTUAL ECOMMERCE, PAYMENT, TAX, ACCOUNT, DOWNLOAD, AND LICENSE PROVIDERS.] Identify which cookies are essential, which are optional, whether the payment page is hosted elsewhere, and how long each technology remains.
Security and Fraud-Prevention Technologies
Security services may process IP addresses, request characteristics, browser signals, login attempts, rate-limit information, and cookies used to distinguish legitimate visitors from automated abuse. These controls can protect forms, accounts, downloads, checkout, and license systems.
[INSERT THE ACTUAL HOST, FIREWALL, CAPTCHA, CDN, SPAM-PROTECTION, AND FRAUD-PREVENTION PROVIDERS.] Security tools should be configured proportionately and described accurately. Basic EstimateFlow Pro form rate limiting does not replace full website security.
Marketing and Advertising Cookies
Marketing technologies may measure campaigns, remember referrals, build audiences, personalize advertising, or report conversions across websites or devices. These technologies can trigger additional consent, disclosure, opt-out, or “sale” and “sharing” obligations depending on the location and configuration.
[STATE WHETHER ANY ADVERTISING, RETARGETING, AFFILIATE, OR CROSS-SITE TRACKING IS USED.] If none is used, remove this category or state that clearly after verification. Do not load optional marketing tags before valid consent where consent is required.
Embedded Content and Third-Party Features
Embedded videos, maps, social posts, chat tools, support widgets, fonts, payment buttons, or other third-party features may make requests to outside services and place or read cookies. Clicking or loading an embed may send the visitor’s IP address and technical details to that provider.
[LIST EVERY EMBEDDED OR THIRD-PARTY FEATURE AND TEST ITS PRE-CONSENT BEHAVIOR.] Consider a consent-gated placeholder for optional embeds so content is not contacted until the visitor chooses to load it.
Current Cookie Inventory
[REPLACE THIS PLACEHOLDER WITH THE VERIFIED COOKIE INVENTORY.]
| Name | Provider | Category | Purpose | Duration | First/Third Party |
|---|---|---|---|---|---|
| [COOKIE NAME] | [PROVIDER] | [CATEGORY] | [PURPOSE] | [SESSION OR PERIOD] | [TYPE] |
Scan logged-out pages, estimator demos, contact and support forms, documentation, account pages, cart, checkout, thank-you pages, license management, and embedded content. Repeat the scan after major plugin, theme, checkout, analytics, security, or consent changes.
How Consent Is Collected
Where required, the website should display a clear consent interface before optional cookies load. Visitors should be able to accept all optional categories, reject them as easily as accepting, or choose categories individually. Necessary cookies should be explained separately.
[INSERT THE CONSENT PLATFORM, REGIONS WHERE IT APPEARS, CATEGORIES, RECORD-RETENTION METHOD, AND BANNER LINK.] Consent must be informed, specific, freely given where required, and capable of being withdrawn. Preselected optional categories and manipulative button designs should be avoided.
How to Change or Withdraw Consent
A persistent “Cookie Settings” link should allow visitors to revisit choices and withdraw consent as easily as it was given. Withdrawal should stop future optional processing; it may not remove information lawfully processed before withdrawal.
[CONNECT THIS SECTION TO THE LIVE CONSENT-PREFERENCE CENTER BEFORE PUBLISHING.] When a provider cannot be disabled immediately, explain the limitation accurately and provide the available opt-out method.
Browser and Device Controls
Most browsers allow visitors to view, delete, block, or limit cookies and clear local storage. Blocking all cookies may prevent cart, checkout, login, consent, security, or preference functions from working correctly. Browser instructions vary by product and version.
Visitors may also use operating-system privacy settings, provider opt-out pages, or device controls. Deleting cookies can remove saved preferences and may cause the consent banner to appear again. Browser controls do not necessarily stop server logs or every similar technology.
Do Not Track and Privacy Signals
Some browsers send “Do Not Track,” Global Privacy Control, or other privacy preference signals. Legal requirements and technical standards vary. [VERIFY WHETHER AND HOW THE LIVE WEBSITE, CONSENT PLATFORM, ANALYTICS, AND ADVERTISING SERVICES RECOGNIZE EACH SIGNAL.]
Do not claim the site honors or ignores a signal without testing. Where applicable law requires recognition of an opt-out preference signal, the website and enabled providers should be configured accordingly.
How Long Cookies Remain
Session cookies generally expire when the browser session ends, while persistent cookies remain until their stated expiration or deletion. Similar technologies and server-side records may use different retention periods.
The verified inventory should state each duration rather than relying only on broad categories. Retention must match the provider configuration and business need. Consent records, fraud records, transaction sessions, analytics identifiers, and marketing tags may have different periods.
Updates to This Cookie Policy
We may revise this Cookie Policy when the website, plugin, providers, consent requirements, or legal obligations change. The page should display a new effective date, and material changes may require renewed consent.
Automated scans are useful but may miss conditional, geographic, logged-in, checkout, or interaction-triggered technologies. Review the inventory regularly and after material website changes. Preserve prior versions where practical.
Related Policies and Support
Review the Privacy Policy to learn how personal information is handled and the Terms and Conditions for the rules governing use of this website and EstimateFlow Pro. If you have questions about cookies or privacy, contact EstimateFlow Pro support.