Cookie Policy

1. What we use today

The ArcPixel marketing website and the ArcPixel application both use Google Analytics, and only after you choose “Allow analytics” in the consent banner shown on each of them. If measurement is not configured, or you decline, the analytics library is not loaded and analytics cookies are not set. Your choice is recorded separately on each of the two, so declining on one does not enable analytics on the other. We do not use advertising cookies anywhere.

The application also uses cookies and local storage that are strictly necessary to keep you signed in. Those are described in section 4 and are not optional, because the application cannot work without them.

2. Local storage on the marketing website

Instead of cookies, this marketing site uses your browser's local storage for a few functional purposes:

• Theme preference — remembers your light or dark mode choice (via next-themes).
• Brand intro — remembers whether you have seen the introductory animation this session, so it does not replay on every page load.
• Session hint— a lightweight flag that lets the navigation show "Log in" or "Dashboard" without a flash, based on whether you have an active session in the ArcPixel app.
• Analytics consent — records whether you allowed or declined optional analytics so the site can respect that choice on later visits.

These functional values do not track you across other websites.

3. Optional analytics

After consent, Google Analytics may set first-party cookies such as _ga and a property-specific _ga_* cookie to distinguish visits and sessions. Both the marketing website and the application report to the same Google Analytics property, so a visit that begins on the website and continues into the application is not counted twice.

On the marketing website we send page views and a small set of content events with non-personal labels such as content topic, page family, locale, CTA placement, and target product.

In the application we send page views and a small set of product events that record that a step happened, never what it contained: starting a workspace, importing a résumé, creating a portfolio draft, viewing pricing, starting checkout, activating a paid plan, exporting a PDF, and publishing a portfolio. The only labels attached are non-identifying ones such as the plan identifier, the type of document, and the file extension of an imported file. Addresses are reduced to the page path before they are sent, with query strings, fragments, and document identifiers removed, so a report cannot be traced back to an individual document.

Document content, résumé and portfolio data, file names, names, email addresses, and form entries are never analytics properties. Advertising storage, ad personalization, and Google signals are disabled in our configuration.

4. Strictly necessary storage in the ArcPixel app

The ArcPixelproduct application (used by signed-in customers) uses session cookies and local storage necessary for authentication — including an HttpOnly refresh-token cookie and session management. It also stores your theme preference and your two banner choices: the acknowledgement of this notice and your analytics decision. Our payment processor Paddle may set cookies during its checkout flow. Paddle's cookies are governed by our Privacy Policyand Paddle's own privacy policy, not this page.

5. Managing cookies

Choose “No thanks” in the banner to keep optional analytics disabled. Because the choice is stored separately on the marketing website and in the application, you can decide differently on each. You can reset a choice by deleting that site's local storage and cookies in your browser settings. If you withdraw consent after previously allowing analytics, the analytics library is removed and the analytics cookies it set are deleted; your sign-in cookies are left untouched.

6. Contact

Questions about this policy can be sent to support@arcpixel.io.