The Roma Sposa bridal shop site uses one storage key of its own and, with your permission, the tags of three advertising platforms. Here is each one, who sets it and how long it stays.
Effective · Version 2.0
Roma Sposa Tags declared
The short answersEight questions · full text below
Who holds the data
Romasposa, trading as Roma Sposa, 722 N Old Woodward Ave, Birmingham, Michigan 48009, United States.
What our own site stores
One key, site_consent_v2, holding your cookie choice. The chat keeps a token if you open it.
Who else sees a click
Google Ads, Microsoft Advertising and Meta Ads, through gclid, msclkid and fbclid. Only after you allow it.
Default state
All four Consent Mode v2 signals denied. Nothing for advertising is written to your browser.
How long it lasts
Your choice: 12 months. Google ad cookies: 90 days. Microsoft: up to 13 months. Meta: 90 days.
How to change your mind
The Cookie choices button at the foot of every page. It reopens the bar. Decline switches everything off again.
If you decline
Every page, the collection, the appointment form and the chat still work. Only ad measurement stops.
Who to write to
[email protected] or +1 248-723-4300. A person answers, within 7 days for a data request.
This notice takes effect on and was last updated that day. It sits beside the privacy policy, which covers what the inquiry form and chat keep. This page covers only what is stored in your browser and what the ad tags read.
Three kinds of storage
Strictly necessary. The key that remembers your cookie choice, and the chat token if you start a conversation with the atelier. Without the first, the bar would ask you again on every page. These run without consent because they exist to respect it.
Analytics. Counts of visits and which pages lead to an appointment request. Governed by the analytics_storage signal and off until you allow it. We look at totals, such as how many people read the Lace Mermaid Gown section before booking. Not at individuals.
Advertising. Cookies set by Google Ads, Microsoft Advertising and Meta Ads that tie a paid click to a later inquiry. Off until you allow them. This is how we learn whether an ad for a bridal shop in Birmingham, Michigan brought anyone through the door, or just cost money.
There are no social share buttons, no embedded videos and no map widget on this site, so none of their cookies arrive either.
Every cookie and key, listed
Durations are the maximum. Clearing your browser removes all of them sooner.
Cookies and storage keys on romasposa.us
Name
Set by
Purpose
Lasts
Needs consent
site_consent_v2
Roma Sposa, local storage
Records whether you pressed Allow or Decline
12 months
No
chat token
Roma Sposa, local storage
Lets you return to your conversation with the atelier
Until you clear it; transcript deleted after 12 months
No, set only when you start a chat
_gcl_au
Google Ads
Stores the gclid so a later inquiry can be matched to the ad click
90 days
Yes, ad_storage
_ga, _ga_*
Google
Distinguishes visits for aggregate analytics
Up to 13 months
Yes, analytics_storage
_uetsid
Microsoft Advertising
Holds the session for Microsoft conversion tracking
1 day
Yes
_uetvid
Microsoft Advertising
Recognizes a returning visitor for conversion tracking
Up to 13 months
Yes
_uetmsclkid
Microsoft Advertising
Stores the msclkid from the ad link
90 days
Yes
_fbp
Meta Ads
Identifies the browser for Meta conversion reporting
90 days
Yes
_fbc
Meta Ads
Stores the fbclid from the ad link
90 days
Yes
The Meta cookies appear only while a Meta campaign is running. Google and Microsoft campaigns run continuously.
Paid clicks and their identifiers
This site receives paid traffic now. When someone searches for couture wedding dresses in Birmingham, MI or a private bridal appointment in Michigan, an ad may bring them here. Each platform tags the link:
Google Adsgclid
Microsoft Advertisingmsclkid
Meta Adsfbclid
Read by our tagsAfter Allow
The identifier is in the web address because the platform put it there before you arrived. Our tags leave it alone until you consent. After that, the matching tag stores it in the cookie listed above so an inquiry sent next week can be counted against the right ad. None of these platforms has reviewed or approved this site, and we do not say otherwise.
Consent Mode v2, signal by signal
Google Consent Mode v2 runs on every page. Before any tag loads, four signals are set:
ad_storageDenied
ad_user_dataDenied
ad_personalizationDenied
analytics_storageDenied
They hold at denied until you press Allow. Then all four become granted. Press Decline, now or later, and they return to denied that moment, on the page you are on. While denied, Google tags can send a cookieless ping that carries no identifier. No cookie is read or written.
If your browser sends Global Privacy Control, the signals stay denied and the bar does not ask you to change that.
Giving and withdrawing consent
The bar at the bottom of the screen appears on your first visit. It never covers the page and you can scroll past it. Allow switches on analytics and advertising. Decline keeps them off. Ignoring it counts as Decline.
To change your answer, press Cookie choices in the footer of any page, or the button in the panel above. The bar opens again with both options. Your new answer replaces the old one in site_consent_v2 straight away. Cookies already set by a platform stay in your browser until they expire or you delete them in your browser settings, but our tags stop reading them the moment you decline.
What declining changes
Very little that you would notice. The collection pages, the atelier page, the appointment form and the chat all work exactly the same. We still receive your inquiry and still call you back.
What stops: no advertising or analytics cookie is set, the click identifier is not stored, and the platforms get no conversion from your visit. We lose the ability to tell which ad brought you. That is our problem, not yours.
The platforms' own documents
Each platform decides for itself what it does with the data its tags receive. Read their terms directly:
Found a cookie on romasposa.us that is not in the table? Tell us its name. Email [email protected], call +1 248-723-4300, or write to Romasposa, 722 N Old Woodward Ave, Birmingham, Michigan 48009, United States.
