Skip to content
Adorn
Compare Docs Pricing Log in
Start free

Privacy Policy

How the Adorn service, operated by Avocado Blvd LLC, collects, uses, and protects data.

Last updated: November 8, 2026.

On this page

  • 1. Introduction & Scope
  • 2. Who We Are (Controller)
  • 3. Controller and Processor Roles
  • 4. Data We Collect, Why, and Where It Lives
  • 4b. Your Shopify Orders
  • 5. Sub-Processors
  • 5b. Product and Catalog Data Vendors
  • 6. Legal Bases for Processing
  • 7. How We Use Data
  • 8. Data Sharing & Disclosure
  • 9. International Transfers
  • 10. Data Retention
  • 10b. Bill Credit Uploads
  • 11. Security
  • 12. Your Rights
  • 13. Platform-Initiated Deletion
  • 14. California Privacy (CCPA/CPRA)
  • 15. Analytics and Cookies
  • 16. Children's Privacy
  • 17. Changes & Contact

1. Introduction & Scope

This Privacy Policy explains how Avocado Blvd LLC ("we" or "us") handles data in connection with the Adorn service (the "Service"), a platform that renders branded product images and emits a prioritized product catalog feed for merchants. It covers the merchants and their authorized users who sign in to and connect accounts with the Service, visitors to our public website at useadorn.com, and anyone who uploads a bill for the bill credit offer, whether or not they have an Adorn account. It takes effect on the last-updated date shown above.

A workspace is where we keep one catalog in Adorn: its products, the templates and brand settings made for it, its connections and its team. A workspace connects to at most one Shopify store. You sign in to Adorn with your own account, and one account can belong to more than one workspace.

2. Who We Are (Controller)

Avocado Blvd LLC is the entity responsible for the Service and is governed by the laws of the State of California, United States. You can reach us about privacy through our support form.

3. Controller and Processor Roles

Under the GDPR, we act as a controller for the account and identity data we hold about merchants and their users, and as a processor for the product, catalog, and platform data we process on a merchant's behalf and under its instructions. This split reflects that a merchant decides which stores, ad accounts, and product data to connect, while we operate the platform that processes them. We also act as a controller for the data we collect about visitors to our public website and about anyone who uploads a bill for the bill credit offer.

4. Data We Collect, Why, and Where It Lives

We collect only what the Service needs to operate. The table below maps each category to the real technology that stores or processes it.

DataWhyWhere it lives
DataAccount & identity (email, name, user id)WhySign-in, membership, access controlWhere it livesHandled by Clerk, our authentication sub-processor
DataConnected-platform OAuth access tokens (Shopify, Meta, TikTok, Pinterest, Snapchat)WhyRead your catalog and register your feed on your behalfWhere it livesA per-workspace secret store, envelope-encrypted at rest under a platform key (never stored in reversible form)
DataBilling identifiers and subscription stateWhyRun your subscription and trialWhere it livesYour name, billing address, and card are entered on Stripe's hosted checkout and are held by Stripe. We store only your Stripe customer and subscription identifiers, plan, status, and renewal date in Cloudflare D1
DataRendered product images (Output)WhyDeliver the designed creative into your feedWhere it livesCloudflare R2 object storage
DataWorkspace configuration, product/catalog data, and an operational error logWhyRun the rule engine, render, and serve the feedWhere it livesCloudflare D1; the error log holds only classified, opaque tokens, no raw personal data
DataProduct data ingested at your directionWhySource the catalog we design and feedWhere it livesFrom your chosen source, Shopify, a pasted feed URL, or DataFeedWatch
DataDaily unit counts for each product, split between first-time and returning buyers, if a store on a custom Shopify app turns on Sales from Shopify orders (Section 4b)WhyShow that split on the Product spend tabWhere it livesCloudflare D1, with no order id, name, email address, phone number or postal address
DataSupport messages you send usWhyRespond to your requestWhere it livesBot-checked with Cloudflare Turnstile and delivered by email via Resend
DataBills you upload for the bill credit offer, with the email and store you giveWhyCheck your claim and add your creditWhere it livesBot-checked with Cloudflare Turnstile. The bill is kept privately in Cloudflare R2, never at a public address, and the claim record in Cloudflare D1

A Shopify store connects to Adorn through Adorn's public Shopify app, which is not built for any one store, or through a custom Shopify app built for that store alone.

When you install Adorn's public Shopify app or connect a store to it, we ask Shopify for four permissions: to read your products, your inventory levels, your markets (the countries you sell in, with their currencies and prices), and your storefront's product listings, which also let us read the logo, colors and slogan your store shows. We use them to design your product images, build your feeds and suggest your brand settings. None of them lets us change anything in your store.

Some features ask Shopify for one more permission, and only when an owner of the store turns the feature on in Settings under Data sources: Shopify discounts on designs asks to read your discounts; Designs saved to your Shopify products asks to edit your products, so we can save Adorn's designs to them; and Sales reports in Shopify asks to add your Adorn campaigns to Shopify's Marketing page and to read and add notes on your sales charts. We only add our own notes there and keep nothing from your charts. Adorn's public Shopify app does not ask for permission to read your orders or customers, or to add a web pixel to your store.

A store on a custom Shopify app gives us the permissions set in that app, which can include reading its orders and customers and editing its products. We read those orders and customers only when an owner turns on Sales from Shopify orders, which Section 4b describes.

4b. Your Shopify Orders

A store on Adorn's public Shopify app cannot turn on Sales from Shopify orders today. We read none of that store's Shopify orders, so we keep nothing from them.

We offer Sales from Shopify orders today only to a store on a custom Shopify app. An owner of that store turns it on or off in Settings under Data sources. While it is on, we keep, for each product and day, how many units first-time buyers bought and how many returning buyers bought. Those counts hold no order id, name, email address, phone number or postal address, and we delete them 60 days after the day they cover. Turning the feature off stops new counts, and the counts already kept are deleted on the same schedule.

If Adorn's public Shopify app offers Sales from Shopify orders later, we will also keep, for a store that turns it on, one row for each product in an order: Shopify's ids for the order and the product, the product page the visit landed on, the ad tracking values for source, medium and campaign, the time of the order, and the amount spent on that product with its currency. These rows will hold no name, email address, phone number or postal address. No store has these rows today.

5. Sub-Processors

We use the following sub-processors, each for the purpose named in its entry below. Each one may handle personal data on your behalf. We remain responsible for their handling of data processed on your behalf and bind them to appropriate data-protection obligations (GDPR Art. 28).

  • Clerk, authentication and account identity.
  • Cloudflare, compute, R2 storage for images and for bills you upload for the bill credit offer, D1 database, Turnstile bot mitigation on the support and bill credit forms, and the container that encodes video.
  • Resend, transactional, support and bill credit email delivery.
  • Stripe, subscription checkout and card payment. Your name, email, billing address and card details are entered on Stripe's own hosted checkout page and are held by Stripe. They never reach the Service.
  • Shopify, connected commerce platform and product source.
  • Meta, connected advertising platform and feed destination.
  • TikTok, connected advertising platform and catalog destination, if you choose to connect it.
  • Pinterest, connected advertising platform and catalog destination, if you choose to connect it.
  • Snapchat, connected advertising platform and catalog destination, if you choose to connect it.
  • DataFeedWatch, optional product feed source.
  • Figma, design file access, used to bring brand artwork into the Service. We store the Figma access token, refresh token and Figma account id against the email address of the person who authorized the connection.
  • Sentry, error monitoring. It receives error reports from the Adorn app, with a recording of the app screen leading up to an error, and records of requests to our servers, so we can find and fix problems.

5b. Product and Catalog Data Vendors

The vendors below run parts of the image, copy, and video pipeline. They receive product and catalog data only, meaning a product image address and product text. They receive no name, no email address, no billing detail, and no account credential, which is why they are listed separately from the sub-processors above rather than alongside them. They are named here because Sections 8 and 15 describe every vendor that touches your data, not only the ones that handle personal data.

  • Modal, the graphics hardware that removes a product photo's background. It receives the image address and returns the cut image.
  • Anthropic, generates campaign and element wording. It receives a short brief, your store identifier, and product title, type, brand and collection text.
  • Bria, background removal and product scene generation. It receives the product image address and a short product description hint.
  • fal.ai, background removal. It receives the product image address. Engaged on your own account, using an API key you supply.
  • Photoroom, background removal and product scenes. It receives the product image address. Engaged on your own account, using an API key you supply.
  • Higgsfield, turns a finished product image into a short video. It receives the address of that image. Engaged on your own account, using an API key you supply.

6. Legal Bases for Processing

Where the GDPR applies, we rely on: performance of our contract with you (to provide the Service); our legitimate interests (to secure, maintain, and improve the Service and prevent abuse), balanced against your rights; and your consent where it is specifically required. Merchants are responsible for the legal basis for any data they connect and process through the Service.

7. How We Use Data

We use data to provide and operate the Service: to authenticate accounts, ingest your product data, render designed images, generate and serve your catalog feed, respond to support requests, and to secure the Service and prevent abuse. We do not use your product data or connected-account tokens for any purpose other than operating the Service for you.

8. Data Sharing & Disclosure

We share data only with the vendors named in Section 5, in both of the lists there, and with Google through the Google Analytics on our public website described in Section 15. We share it only as needed to operate the Service, or where disclosure is required by law or to protect rights and safety. We do not sell personal information. We do not share personal information for cross-context behavioral advertising.

9. International Transfers

The Service is operated using US-based processing. Where data is transferred from other regions, we rely on appropriate safeguards, such as standard contractual clauses where relevant. For personal data from the European Economic Area, the United Kingdom or Switzerland, that safeguard is the European Commission's standard contractual clauses, with the United Kingdom's addendum and the Swiss amendments where they apply.

10. Data Retention

We keep account and identity data for the life of the account. Rendered images stay in Cloudflare R2 while your workspace is active, unless we delete them when Shopify asks us to erase its store. Our operational error log retains only classified, opaque tokens and never raw personal data.

When Shopify asks us to erase a store that has uninstalled Adorn and not installed it again, we delete everything we hold that came from that store, including its stored credential. Because we do not record which source each product came from, we also delete every other product in that store's workspace, including products from the other sources Section 4 lists, with their rendered images, AI work and performance history. Your other workspaces stay as they are.

If someone signed in to finish setting up that workspace, we keep what you made yourself, such as your templates, brand settings and uploaded images. We also keep its team, its other connections, your billing and audit records, and records of what AI and video work cost, without saying which products the work was for. A source other than Shopify adds its products back on its next sync, but their past performance history does not come back.

If nobody ever signed in to finish setting up the workspace the install created, we delete that whole workspace, apart from billing and audit records and the record of dates below, which no longer names the store.

We erase nothing for Shopify's erase request in these cases:

  • the workspace is one our own team set up and protects from automatic deletion (no workspace created by installing Adorn is one of these)
  • the store is connected through a custom Shopify app built for that store alone
  • our access to the store came through a different Shopify app than the one Shopify sent the request for
  • the store has installed Adorn again, and Shopify confirms that access still works

The workspace then stays as it is until you ask us to delete it, as our data deletion instructions describe.

When we delete a workspace, for any reason, we keep the dates it signed up, installed Adorn, connected a platform, first published, started a trial, paid and canceled, with its plan and what it paid. We keep them as dates with no time of day, and without the store's name, its address or any email address.

We keep information about a store's Shopify orders only as Section 4b describes. A cleanup that runs every day deletes each daily unit count 60 days after the day it covers. No store has order rows today. If we keep any later, that cleanup will delete each one 60 days after its order.

10b. Bill Credit Uploads

We delete a bill you upload for the bill credit offer 30 days after we add your credit, decline your claim or tell you we could not add the credit. If your claim ends without a credit, we delete the bill when it ends.

A claim ends without a credit 180 days after upload in any of these cases:

  • no Adorn store is owned by your email by then
  • we have approved the claim for your store, and by then 30 days have not passed since your store's first paid Adorn bill
  • we have approved the claim for your store, and by then we have not added any of the credit for a reason on your side, such as a failed payment

If we reopen your claim, those 180 days count from the day we reopen it. If we have not added the credit because of a problem on our side, such as our connection to Shopify or to our payment processor, the claim does not end on its own, and we keep the bill while it waits. While we are still reviewing a claim for a store, or have added part of its credit, we keep the bill until the claim ends.

We keep a record of each bill credit claim, including the amount and our decision, permanently, so each store and each email address gets one bill credit, whether or not you become a customer.

If we delete your workspace at your request, or Shopify asks us to erase your store, we delete the store name you typed on that store's claim and replace your email address and the bill's invoice number with a scrambled fingerprint, which only lets us recognize a repeat claim. We keep the rest of the claim record with our billing records. That includes your store's Adorn ID (based on its myshopify.com address), the Shopify store ID or Stripe customer ID we added the credit to, and any note our staff wrote when declining the claim.

11. Security

Connected-account OAuth tokens are envelope-encrypted at rest under a platform key held outside the database. Workspaces are isolated so one merchant cannot reach another's data, images, or feed. Inbound platform webhooks are verified by HMAC before any action. Secrets are read by name at runtime and are never written into code or logs.

12. Your Rights

Subject to applicable law, you have rights to access, correct, delete, port, restrict, and object to the processing of your personal data, and to withdraw consent where processing relies on it. You can exercise these rights, or ask a question, through our support form. Our data deletion instructions say how to ask for full account deletion. Where we act as a processor for a merchant, we will refer or assist with a data-subject request as that merchant directs.

13. Platform-Initiated Deletion

We honor platform-initiated erasure. Our compliance endpoint at /webhooks/shopify/compliance verifies and acts on Shopify's customers/data_request, customers/redact, and shop/redact compliance webhooks. We have given Meta our data deletion instructions as the way to ask us to delete data that came through Meta.

Section 4b describes the daily unit counts we keep and the order rows we would keep about a store's Shopify orders. When Shopify sends customers/redact, we delete the rows for the orders it names in that store. When Shopify sends customers/data_request, our team is told which rows we hold for the orders it names, and gives them to the store owner within 30 days of the request. No store has order rows today, so both requests find nothing to delete or send. The daily unit counts name no order, and neither request reaches them.

When Shopify asks us to erase a store after it uninstalls Adorn (its shop/redact request), Section 10 says what we delete and keep, and when we delete nothing.

Our data deletion instructions explain step by step how to disconnect a single connected platform and how to request full account deletion.

14. California Privacy (CCPA/CPRA)

If you are a California resident, you have the right to know the categories of personal information we collect and the purposes for using them, and the rights to delete, correct, and opt out. As stated above, we do not sell or share personal information for cross-context behavioral advertising, and we will not discriminate against you for exercising your rights. The Google Analytics on our public website, described in Section 15, measures visits to it and is not used to show you ads on other websites. Requests can be made through our support form.

15. Analytics and Cookies

Our public website at useadorn.com loads Google Analytics 4 and Cloudflare Web Analytics on its pages, except on shared design links (addresses that begin useadorn.com/p/), the docs search, and the switch offer form and its confirmation page, and it loads neither when your browser sends a Do Not Track signal. Together they record the pages you view, the page that sent you, your browser and device, and an approximate location worked out from your IP address. Google Analytics sets its own cookies on useadorn.com, and Google receives what it records. Cloudflare Web Analytics sets no cookies. The Adorn app at app.useadorn.com loads neither. Apart from these two, the third parties that receive any data are the vendors named in Section 5, in both of the lists there.

We do set a few cookies of our own, and we state them here rather than leave you to find them. If you arrive on our home page from a link that carries campaign tags or an ad click identifier, and your browser does not send a Do Not Track signal, we store an ac cookie for 30 days on the .useadorn.com domain, marked Secure, HttpOnly, and SameSite=Lax, so our marketing site and our app can recognize that they are the same visit and we can tell which link or ad brought you here. It is a first-party cookie shared only between our own two subdomains. It is never sent to another company and cannot be used to follow you across other websites. It holds the campaign tags from the link you followed and, if the link carried one, the click identifier Google, Meta or Microsoft added to it.

When you connect another service to Adorn, such as a Shopify store, a sales channel or Figma, or install Adorn from Shopify, we set a short-lived cookie that ties that sign-in to the browser you started it in. A sign-in finished in any other browser is refused.

When you install Adorn from Shopify, we set a short-lived adorn_claim cookie on the .useadorn.com domain, so the account you create can claim your store.

These cookies are marked Secure, HttpOnly, and SameSite=Lax. They are first-party, they are never sent to another company, and they are not used to follow you across other websites.

16. Children's Privacy

The Service is a business-to-business product for merchants and is not directed to children. We do not knowingly collect personal information from children.

17. Changes & Contact

We may update this Policy; the last-updated date at the top reflects the latest version, and material changes will be notified through the Service. Questions or requests can be sent to the controller, Avocado Blvd LLC, through our support form.

Last updated November 8, 2026.

On-brand catalog creative that auto-refreshes as prices and sales change, with zero per-product manual work.

Product

Home Pricing Docs

Company

Support Status

Legal

Privacy Terms

Compare

Adorn vs Marpipe Adorn vs Confect All comparisons
Adorn

© 2026 Adorn. All rights reserved.