Skip to content
Book online to request your preferred appointment window.
Flying Flamingo Junk Removal
Serving the Seattle metro areaCheck your address

Legal resources

Cookie Policy

How optional technologies and privacy choices work on this website.

Effective date: July 26, 2026

Effective date: July 26, 2026

This Cookie Policy explains how Flying Flamingo Junk Removal (“Flying Flamingo,” “we,” “us,” or “our”) uses cookies, pixels, tags, local storage, software development kits, session-replay tools, and similar technologies on flyingflamingojunkremoval.com.

This Policy should be read with our Privacy Policy.

1. What cookies and similar technologies are

Cookies are small text files stored by a browser. Similar technologies include:

  • pixels and web beacons;
  • JavaScript tags;
  • local and session storage;
  • advertising and device identifiers;
  • server logs;
  • conversion APIs;
  • session-replay scripts; and
  • embedded third-party content.

These tools can remember choices, provide website features, measure traffic, detect problems, understand advertising, and personalize or target marketing.

We use four categories:

  1. Necessary
  2. Functional
  3. Analytics
  4. Advertising

Necessary technologies are always active because the website cannot securely or reliably provide core features without them.

Functional, Analytics, and Advertising technologies are nonessential. They should not load until you consent, except when a technology is activated at your request to provide a feature you specifically choose, such as opening an embedded map or payment service.

The cookie banner provides:

  • Accept All
  • Reject Non-Essential
  • Customize

The Accept All and Reject Non-Essential choices should be similarly prominent.

A permanent Privacy Choices link allows you to review or change your choice.

Consent is generally remembered for up to 12 months, unless:

  • you clear browser storage;
  • the website configuration materially changes;
  • applicable law requires an earlier renewal; or
  • you change your choice.

Withdrawing consent does not affect processing that occurred before withdrawal.

3. Necessary technologies

Necessary technologies support:

  • website delivery and security;
  • form submission and basic booking flow;
  • fraud and abuse prevention;
  • load balancing and technical routing;
  • consent-preference storage;
  • accessibility and display settings;
  • server and application diagnostics;
  • payment-session security when you choose to pay; and
  • other functions required to provide a service you request.

Necessary storage includes a tab-lifetime session identifier and, only after you actively begin entering the booking form, a draft identifier and random access token used to save or resume that incomplete draft. The draft identifier does not mean a request, lead, quote, booking, or appointment was created. Necessary autosave remains available without Analytics or Advertising consent.

Possible providers include Netlify, Supabase, Stripe, and our own website systems.

These technologies may process IP address, device information, security identifiers, form state, session information, consent choices, and transaction-security data.

Because names and durations vary by configuration, the website’s live cookie scanner or browser storage may display additional necessary identifiers.

4. Functional technologies

Functional technologies provide enhanced features such as:

  • Google Maps and service-area map display;
  • remembering map, chat, or interface preferences;
  • Flappy AI conversation state;
  • optional embedded content;
  • address or location features; and
  • convenience settings.

Google Maps

Google Maps may receive IP address, device and browser information, map interactions, and location or address information you submit.

Google may set cookies or local-storage identifiers whose names and duration vary by region, account status, browser, and Google configuration.

If Functional technologies are rejected, map or embedded features may show a placeholder or require you to activate them manually.

Flappy AI

Flappy may use first-party session or local storage to remember whether the panel is open and to preserve conversation state during a browser session.

OpenAI is normally contacted through our server-side integration rather than by placing OpenAI advertising cookies on your browser.

5. Analytics technologies

Analytics technologies help us understand:

  • visits and traffic sources;
  • pages viewed;
  • button and link interaction;
  • device and browser types;
  • website errors and performance;
  • booking-funnel activity;
  • scrolling and navigation; and
  • how the site can be improved.

Google Analytics

Representative Google Analytics cookies may include:

  • `_ga`
  • `_ga_*`

Google uses these identifiers to distinguish users and maintain session information. Typical duration may be up to two years, but configuration and duration can change.

Microsoft Clarity

Microsoft Clarity provides interaction analytics and session replay.

Representative Clarity cookies may include:

  • `_clck`
  • `_clsk`
  • `CLID`
  • `ANONCHK`
  • `MR`
  • `MUID`
  • `SM`

These identifiers may connect page views, maintain a pseudonymous user or session ID, and support analytics and related Microsoft functions. Duration varies by cookie and Microsoft configuration.

Clarity may collect clicks, scrolling, navigation, browser, device, approximate location, and page-interaction information.

Analytics technologies remain disabled when you reject Analytics consent.

After Analytics consent, the site may store a cryptographically random first-party visitor identifier and cross-session first-touch and last-touch attribution so return visits and permitted journey events can be measured. The visitor identifier represents a browser, not a verified person, and is not placed in public URLs.

6. Advertising technologies

Advertising technologies help us:

  • measure ad clicks and conversions;
  • understand whether advertising leads to a booking or inquiry;
  • create or measure advertising audiences;
  • limit or personalize advertising;
  • attribute traffic to campaigns; and
  • improve marketing performance.

Meta Pixel

Representative Meta cookies may include:

  • `_fbp`
  • `_fbc`

These may identify browsers, connect visits to advertising interactions, measure conversions, and support advertising or analytics. Meta states that `_fbp` and `_fbc` may remain for approximately 90 days, although practices can change.

Representative Google advertising cookies and identifiers may include:

  • `_gcl_au`
  • Google click identifiers;
  • Google tag and consent-state identifiers; and
  • other advertising or measurement cookies documented by Google.

These may measure advertising, attribute conversions, support remarketing, and communicate consent status.

Microsoft Advertising UET

Representative Microsoft Advertising cookies may include:

  • `_uetvid`
  • `_uetsid`
  • `_uetmsclkid`
  • `MUID`

These may identify a browser or session, preserve a Microsoft ad-click identifier, and measure conversions or audience activity.

Advertising technologies remain disabled when you reject Advertising consent.

When you open or use a Stripe payment interface, Stripe may use necessary fraud-prevention, authentication, security, and payment-session technologies.

These may collect browser, device, IP address, transaction, and risk information.

Payment-related technologies that are strictly required to complete a payment may operate as Necessary technologies after you choose to use the payment feature. Stripe may also use technologies under its own privacy and cookie notices.

8. Local storage and session storage

The website may use browser storage instead of a traditional cookie to save:

  • cookie choices;
  • chat state and conversation history;
  • booking progress;
  • form state;
  • interface preferences; and
  • security or duplicate-submission information.

Browser storage is covered by this Policy even when it is not technically a cookie.

Current first-party storage purposes and intended durations include:

  • Consent record (`ff_consent_v1`) — Necessary: remembers category choices, source, timestamp, policy/banner version, and withdrawal where applicable for up to 12 months.
  • Session ID (`ff_session_id_v1`) — Necessary: provides short-lived visit correlation for consent, requested autosave, and outbound contact actions for the current browser tab/session.
  • Draft pointer (`ff_booking_draft_v1`) — Necessary after active form entry: holds only the draft ID, random access token, revision, and expiry needed to save or resume the server-side draft for up to 30 days.
  • Session first/last touch (`ff_first_touch_v1`, `ff_last_touch_v1`) — Necessary session state: attaches attribution to a request you choose to submit during the current browser tab/session.
  • Persistent first/last touch — Analytics: provides return-visit and cross-session attribution for up to 180 days or until Analytics withdrawal.
  • Visitor ID (`ff_visitor_id_v1`) — Analytics: provides pseudonymous browser recognition and consented journey measurement for up to 12 months or until Analytics withdrawal, rotation, deletion, or browser clearing.
  • Approved links source (`ff_links_source_v1`) — Necessary session state: preserves a sanitized, allowlisted `/links` source during the current browser tab/session.

Server-side journey events use an explicit event and metadata allowlist and are retained for up to 180 days. They do not contain names, email addresses, phone numbers, full service addresses, free-form job descriptions, uploaded media, access codes, or payment information. Draft field values are not transmitted to Google Analytics, Meta Pixel, Microsoft UET, Microsoft Clarity, analytics event names, or URLs.

The site does not read Google, Chrome, Apple, or other browser-profile accounts and does not use canvas, font, audio, WebGL, or device fingerprinting.

9. How to manage your choices

You can manage nonessential technologies through:

  • the initial cookie banner;
  • the permanent Privacy Choices link;
  • browser cookie and site-data settings;
  • browser extensions and privacy tools; and
  • provider-specific advertising controls.

Rejecting or withdrawing consent may reduce analytics and advertising measurement. It may also disable optional maps, chat memory, embedded content, or convenience features.

Clearing browser cookies or storage may reset your choices and cause the banner to appear again.

10. Browser signals

Browsers may send “Do Not Track,” Global Privacy Control, or other preference signals.

Where applicable law requires us to recognize a supported opt-out preference signal and our consent system can reliably identify it, we will treat it as an opt-out of sale, sharing, or targeted advertising as required.

Because standards and browser support continue to change, you should also use the Privacy Choices link for a direct website-level selection.

11. Changes to this Policy

Providers may change cookie names, purposes, or durations without notice to us.

We may update this Policy when:

  • technology changes;
  • a provider is added or removed;
  • our consent process changes; or
  • legal requirements change.

The updated version will be posted with a revised effective date.

12. Contact

Questions or requests about cookies may be sent to:

Flying Flamingo Junk Removal

300 Lenora St

Seattle, WA 98121

Phone: (206) 474-7420

Privacy email: privacy@flyingflamingojunkremoval.com

Website: flyingflamingojunkremoval.com