How to Handle Consent When a Visitor Uses Multiple Devices
Almost everyone browses on more than one device, and almost every consent system stores its answer in a cookie or local storage on the device where the choice was made. The result is familiar: a visitor spends a minute setting careful preferences on a laptop, then opens the same site on a phone and faces the banner again. It feels broken, but it is the privacy model working as designed. Consent is tied to a context the site can verify, not to a person it thinks it recognizes.
That does not mean nothing can be done. There are honest ways to reduce repeat friction, and there are dishonest shortcuts that amount to inventing consent. This guide separates the two, and explains what account based sync, preference centers, and plain good banner design each contribute.
Why consent stays on one device
Browsers isolate storage by device and by browser, and privacy law treats a stored choice as evidence about that browsing context. A site has no reliable, permission free way to know the phone opening a page belongs to the same person who set preferences on a laptop. Fingerprinting tricks that try to bridge the gap are themselves tracking, and using them to import a consent choice would be self defeating: collecting data in order to claim permission to collect data. So each new device starts unconsented, and the banner appears.
What account sync can legitimately do
When a visitor signs in, the picture changes. An account gives the site a first party relationship in which a stored preference can be attached to the account and applied on any device where that same account signs in. This is how large platforms remember choices across a phone, a tablet, and a work machine. The limits matter: sync only covers signed in use, the preference applied must be the one the account holder actually set, and a later change on any device should update the record everywhere, with the newest timestamp winning.
Designing the repeat banner so it costs seconds
For anonymous visitors, the answer is a banner that respects a returning device and makes a fresh choice fast on a new one. Keep the stored choice valid for a sensible period so the same device is not re-asked weekly. On a new device, present the same plain language, the same category structure, and a reject path as easy as accept, so a visitor who already decided elsewhere can repeat the decision in two taps. Consistency across devices is what makes repeat choices feel routine instead of adversarial.
What never to do across devices
Never pre tick choices on a new device because an account or another device accepted. Never treat an email click, an app install, or a Wi-Fi match as consent to web tracking. And never hide the banner on mobile because the account accepted on desktop: the person holding the phone may not be the account holder at all, especially on shared family devices. Each of these shortcuts manufactures a record that will not survive the simplest audit question: show me where this visitor made this choice.
Related reading
These earlier guides cover connected questions in more depth: Consent Banner Audits for Redesigns: What Breaks When a Site Relaunches, Consent Mode Signals When a Visitor Declines: What Your Tags Should Actually Do, and Reading your consent string: how to confirm vendors honor what the banner recorded.
Frequently asked questions
Why does a site ask for consent again on my phone?
Because the choice was stored on your other device or browser, and the site has no permission based way to carry it over. Storage is per browser, so a new device starts with no recorded choice and the banner appears until you make one there.
Can consent sync across devices for signed in users?
Yes, when the preference is attached to the account and applied wherever that account signs in. The sync must reflect the account holders actual latest choice, update everywhere when it changes, and it cannot cover anonymous browsing before sign in.
How long should a stored consent choice last?
Common practice is six to twelve months, after which visitors are asked again. Shorter periods annoy visitors and inflate accept rates through fatigue. Longer periods risk choices outliving the purposes and vendors they were given for, which is its own compliance problem.
Does deleting cookies reset consent?
Yes. If the record lives in a cookie or local storage, clearing it removes the evidence of the choice and the banner returns. That is expected behavior, and it is one reason consent records kept server side, tied to an identifier the visitor controls, are more durable.