# CCPA Published articles for CCPA. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Privacy-First Analytics API: One Facade, A Provider SPI, And A Consent Gate DevFeed: [A Privacy-First Analytics API: One Facade, A Provider SPI, And A Consent Gate]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-29T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [API](), [Framework](), [Google Analytics](), [Open Source]() Tags: [analytics](), [api](), [ccpa](), [framework](), [gdpr](), [google-analytics](), [open-source](), [privacy]() ### AI overview This article explains a new analytics facade with a provider SPI and an opt-in consent gate. Reporting calls are withheld until consent is granted, and the design supports multiple analytics providers and granular consent categories. ### Source excerpt A new analytics facade with a provider SPI you can point at any backend and a consent gate that is opt-in by default, so nothing leaves the device until the user agrees. ## How Merchant of Record reduces your Legal & Compliance risk DevFeed: [How Merchant of Record reduces your Legal & Compliance risk]() Original publisher: [Read original article]() Author: Ishani Sahai Published: 2025-11-17T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Security, Privacy and Abuse Prevention](), [Transactions]() Tags: [ccpa](), [chargebacks](), [compliance](), [data-privacy](), [gdpr](), [global](), [invoicing](), [legal](), [merchant-of-record](), [payments](), [regulatory](), [saas](), [tax](), [time]() ### AI overview This article explains how a Merchant of Record can reduce legal and compliance risks for SaaS companies selling globally. It covers tax remittance, invoicing, refunds, consumer-protection rules, KYC and AML checks, data privacy, chargebacks, and related regulatory obligations. ### Source excerpt Understand how a Merchant of Record lowers legal and compliance risk by handling tax remittance, invoicing, disputes, and global regulatory obligations. ## Ensure compliant and secure third-party access using GraphOS DevFeed: [Ensure compliant and secure third-party access using GraphOS]() Original publisher: [Read original article]() Author: Matthew Ratzke Published: 2023-03-20T09:00:00Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [GraphQL](), [Security](), [Authentication]() Tags: [authentication](), [ccpa](), [data-privacy](), [gdpr](), [graphos](), [graphql](), [how-to](), [jwt](), [security](), [third-party-applications]() ### AI overview This post explains how financial services companies can use Apollo GraphOS to provide compliant and secure third-party access to sensitive data. It describes schema contracts for limiting exposed fields and types, separating customer use cases, supporting data minimization, and applying access controls and authentication through Apollo Studio and Apollo Router. ### Source excerpt This post is a part of our "How to power modern financial services apps with Apollo GraphOS" series. Also in this series: - Deliver a personalized customer experience with GraphQL - Securing APIs declaratively with GraphQL - Adopt a Customer 360 approach to prevent fraud with GraphQL In recent years, GraphQL has gained popularity as a powerful alternative to REST APIs for building modern web applications. ## How Artsy Preserved Cookie Preferences Beyond Safari's 7-Day Limit DevFeed: [How Artsy Preserved Cookie Preferences Beyond Safari's 7-Day Limit]() Original publisher: [Read original article]() Published: 2022-08-23T00:00:00Z Content type: tutorial Language: en Sources: [Artsy]() Topics: [browser](), [WebKit](), [User experience (UX)](), [client]() Tags: [apple](), [browser](), [ccpa](), [cookies](), [gdpr](), [privacy](), [safari](), [server](), [ux](), [wwdc]() ### AI overview This article explains how Artsy addressed Safari's seven-day limit on client-side cookies, which caused cookie-consent preferences to be repeatedly requested. It describes replacing the client-side cookie with a same-domain, secure, server-side cookie so the preferences persist beyond seven days. ### Source excerpt Amongst the many, many things that organizations have to contend with around cookie consent laws is Apple's very own browser, Safari. Did you know that Safari will only retain a client-side cookie for 7 days? This is in support of Apple's Intelligent Tracking Prevention (ITP) feature, designed to protect a user's privacy. These privacy efforts are great but, in hand with laws like GDPR and CCPA, their rollout often creates a UX nightmare for users without some extra care. Here at Artsy, we've landed on a way to make things slightly less bad and want to share our approach. Scenario: Imagine that as a EU resident you visit artsy.net for the first time. A banner appears asking you to Accept or Deny tracking cookies from our site. You don't like tracking cookies, so you click the "Deny" button and the banner disappears. All good, right? Nope! You visit Artsy a week later and again, a banner appears asking you to choose your preferences. This happens again and again until you switch browsers and realize that what you were experiencing was Apple's ITP feature in action. After choosing your preferences, the cookie we use to store them is erased after 7 days, necessitating another interaction. We thrashed around in this vicious cycle for months until we found a simple, elegant solution thanks to a WebKit engineer's prompt (during Apple's open lab calls at WWDC - which you too can schedule!) She mentioned that the 7-day cookie limitation only applies to client-side cookies and that same-domain, secure, server-side cookies are not limited to these constraints. This got us thinking. Our third-party cookie consent management service sets a client-side cookie, not a server-side cookie. Could we perhaps overwrite the client-side cookie with a server-side cookie of the same name and trick Safari into persisting the user preferences beyond the 7-day limit? We gave it a try and... Yes. We. Can! And this means that you can too (and it's also real easy to implement). First, define an AP