Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Portfolio website builder included with Adobe Creative Cloud that injects Adobe Analytics and Audience Manager tags on published sites.
Adobe Portfolio is a portfolio website builder bundled with every Adobe Creative Cloud subscription. It lets photographers, designers and illustrators publish responsive portfolio sites that sync with Behance projects and Lightroom albums. The hosted service is operated by Adobe Inc. from servers in the United States and delivered globally through Amazon CloudFront. Published sites carry a Powered by Adobe Portfolio badge and, by default, embed the Adobe Marketing Cloud measurement stack.
On a published Adobe Portfolio site, Adobe Analytics drops cookies such as s_cc, s_sq, s_vi and s_fid to identify visitors and reconstruct sessions. Adobe Audience Manager adds aam_uuid and AAMC_publishers_0 for cross site audience segments, and Adobe Target uses the mbox cookie for personalisation tests. The scripts also report IP address, user agent, referrer, pages viewed, clicks and viewport size to omtrdc.net and demdex.net, allowing Adobe to link visitors across other Adobe powered properties.
Because Adobe Portfolio pages load Adobe Analytics, Audience Manager and Target without any built in consent gate, every visit stores identifiers in the visitor terminal and transfers personal data to Adobe as processor. Under the GDPR this is processing of personal data, and under Art. 5(3) of the ePrivacy Directive (transposed into the German TDDDG and similar national laws) the prior storage and reading of these cookies requires informed consent. The audience profiling layer also raises transparency duties under Art. 13 GDPR.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Strictly necessary cookies for serving the portfolio site itself can rely on Art. 6(1)(f) GDPR and the technical exemption of Art. 5(3) ePrivacy, but the Adobe Analytics, Audience Manager and Target cookies cannot. They require freely given, specific, informed and unambiguous opt in consent under Art. 6(1)(a) GDPR before any tag fires. In practice the portfolio owner must place a consent banner in front of the Adobe scripts, block them until acceptance, and offer an equally easy reject option as recommended by the EDPB and the CNIL.
All data collected by the embedded Adobe tags is transferred to Adobe Inc. in the United States and may be processed in other Adobe Experience Cloud regions. Adobe relies on the EU US Data Privacy Framework and Standard Contractual Clauses. The portfolio owner should document the transfer in the Art. 30 record, link to Adobes DPF certification, update the cookie policy with the cookies listed above, deploy a consent platform that blocks omtrdc.net and demdex.net until opt in, and consider disabling Adobe Analytics in the Portfolio dashboard.
Websites using Adobe Portfolio must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is advisable when the portfolio site receives large traffic or targets EU minors, because the embedded Adobe Marketing Cloud stack combines analytics, audience segmentation and cross domain identifiers that enable profiling under Art. 35 GDPR.
Sample consent text
We use Adobe Analytics, Adobe Audience Manager and Adobe Target on this Adobe Portfolio site to measure audience and personalise content. These tools set cookies and transfer data to Adobe Inc. in the United States. Click Accept to allow, or Reject to keep only strictly necessary cookies.
Third-party domains contacted
myportfolio.comcdn.myportfolio.comassets.myportfolio.comadobe.combehance.netomtrdc.netdemdex.neteveresttech.netCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| s_vi | third_party | 2 years | Adobe Analytics persistent visitor identifier used to recognise the same browser across visits to the Adobe Portfolio site. |
| s_cc | third_party | session | Adobe Analytics cookie that checks whether cookies are enabled in the browser. |
| s_sq | third_party | session | Adobe Analytics cookie that stores the previous link clicked, used for ClickMap and link tracking. |
| aam_uuid | third_party | 6 months | Adobe Audience Manager unique identifier used to build cross site audience segments. |
| AAMC_publishers_0 | third_party | 1 year | Adobe Audience Manager cookie that supports synchronisation of the audience identifier with publisher domains. |
| mbox | third_party | 2 years | Adobe Target cookie that stores test and personalisation experience assignments for the visitor. |
Adobe Portfolio collects user analytics data — you legally need a consent banner. Try FlowConsent free.
By default it loads Adobe Analytics (s_cc, s_sq, s_vi, s_fid), Adobe Audience Manager (aam_uuid, AAMC_publishers_0) and Adobe Target (mbox). Exact names depend on the Marketing Cloud configuration of the account.
Yes. The Adobe Analytics, Audience Manager and Target tags are not strictly necessary, so under Art. 5(3) ePrivacy and the GDPR they need prior, freely given opt in consent before they fire on the visitor browser.
Consent under Art. 6(1)(a) GDPR for the embedded Adobe tags. Strictly necessary cookies for serving the static portfolio can rely on legitimate interest (Art. 6(1)(f)) and the technical exemption of Art. 5(3) ePrivacy.
Yes. Data is sent to Adobe Inc. in the United States and may be processed in other Adobe Experience Cloud regions. Adobe relies on the EU US Data Privacy Framework and on Standard Contractual Clauses for covered transfers.
A DPIA is advisable when the site receives large traffic, addresses EU minors, or hosts sensitive creative content, because the Adobe stack combines analytics, audience segments and personalisation that enable profiling under Art. 35 GDPR.
Deploy a consent management platform that blocks omtrdc.net and demdex.net until opt in, disable Adobe Analytics in the Portfolio dashboard when measurement is not essential, link to Adobe DPF certification, and document the transfer in the Art. 30 record.
Yes. Squarespace, Format, Wix, Carbonmade and Cargo offer hosted portfolios. Self hosted Hugo or Eleventy on Netlify minimises tracking. EU based options include Pixpa and Webnode for creators who prefer European hosting.
List each Adobe cookie (s_cc, s_sq, s_vi, s_fid, aam_uuid, AAMC_publishers_0, mbox) with purpose, duration and provider. Identify Adobe Inc. as recipient, note the United States transfer, and link to the Adobe privacy centre.