§1Who runs this server
This Shopworthy server is run by [operator name: set AGENTREADY_OPERATOR]. Everything described here happens on that server: reports, accounts and uploads are kept in the server's database, which runs on Heroku (Salesforce), with the database on Amazon Web Services in the United States, and nothing is sent to any analytics service.
Write to support@getcarve.app with any question about your data. [Legal entity, postal address and, where required, a data protection contact]
§2When you check a site
When you check a site we store what you entered (the address, any competitors and the category) with the report, in the server's database. The report holds what we measured: the pages we fetched, the checks, the score and, when assistants were asked, their answers.
A report started from the public form is public. Anyone with its link can open it, and it appears in the dashboard, the leaderboard, the site's history and the data study. A report run from an account (Run now, scheduled checks, the Shopify app) is private to that workspace until a member shares it.
To build a report we fetch public pages of the site you named, read-only, as a browser and as each assistant's agent. We never submit forms, sign in or buy anything on that site.
§3Questions sent to AI assistants
When the server has assistant API keys (live mode), it sends buyer questions to OpenAI, Anthropic, Google or Perplexity through their APIs. The questions come from fixed templates, the category you picked and the store's brand name. Your email address and IP address are not sent. Those providers handle the questions under their own terms and privacy policies. This server currently asks OpenAI, Anthropic, Google and Perplexity.
Without keys, no assistant is asked anything. The demo stores use scripted sample answers, labeled SAMPLE.
§4Your IP address
Your IP address is never written into a report. To limit how often one visitor can run costly checks, the server counts requests per visitor using a hash of the IP address mixed with a random salt. The salt changes every UTC day and old salts are deleted, and the counting records are deleted after two days. After that, nobody can link a count back to an address. IPv6 addresses are grouped by their first 64 bits for these limits.
The app writes no access log of its own. If the server sits behind a proxy or CDN, that service may keep logs under its own policy (this server runs on Heroku (Salesforce), with the database on Amazon Web Services in the United States).
§5Accounts, sign-in and email
Sign-in is passwordless. When you ask for a sign-in link, we store your email address and a hash of the link's one-time token, which expires after 15 minutes. Once you sign in we store your account: email address, workspace name, the stores and competitors you track, fixes you record, alerts, and plan changes. These live in a SQLite file (accounts.db) on the server.
One cookie keeps you signed in: ar_session, HttpOnly, for 30 days. The server keeps only a hash of it. There are no other cookies.
Sign-in links, alerts and digests are sent by email through Resend, which receives your address and each message in order to deliver it, under its own privacy policy.
§6Logs and orders you upload
On the proof pages you can upload server logs and an orders export for a store you have verified you own. Logs are reduced to daily counts per assistant and per AI referral source; the raw lines and IP addresses are not stored. From an orders export we keep each order's ID, time, total, currency, AI source and landing page, and nothing about the customer. This evidence is stored in a SQLite file (proof.db), scoped to the workspace that verified the store.
The free log checker, AI traffic tool and feed checker read what you paste in memory and store none of it.
§7The snippet on your store
If you add the first-party snippet to your store, it sends the referrer and page address only when a visit came from an AI assistant. It stores nothing on your shopper's device and reads no identifiers. The server turns each event into a daily count and keeps no raw events and no IP addresses. The edge snippet's IP is checked against the assistant vendor's published ranges in memory and then dropped. You are responsible for telling your own shoppers about the snippet [add guidance for store owners if needed].
§8Billing
Payments are handled by Stripe. You pay on Stripe's own checkout page, and your card details go to Stripe, never to this server. This server keeps your plan, the billing status and Stripe's references for your customer record and subscription. Stripe processes payment details under its own privacy policy.
§9No trackers
No analytics services, advertising pixels, web fonts or third-party scripts. Pages load only from this server. To see how the site is used, the server itself keeps anonymous daily totals: which pages were opened, the name of the site a visit came from, campaign tags in the address (utm_source, utm_medium, utm_campaign), forms that went through (such as checks started), and how many distinct visitors there were that day. Distinct visitors are counted with a hash of the IP address and browser name mixed with a random salt that changes every UTC day; those hashes are deleted after two days. No cookie is set for this, and no IP address, full address or referring page is stored. The totals are kept for 400 days.
One exception the operator can turn on: if the Cloudflare Turnstile bot check is enabled, pages that show it load a script from challenges.cloudflare.com, under Cloudflare's privacy policy.
§10How long data is kept
Reports, accounts and proof data are kept until the operator deletes them; this build deletes nothing automatically except the visitor-limit records (after two days), expired sign-in links and sessions, and expired shared answer snapshots. [Retention periods to be set before launch]
§11Your choices
You can stop tracking a store from your account. To see, correct or delete what is stored about you, including your account, write to support@getcarve.app. [Your legal basis for processing and your rights under the law that applies, for example GDPR or CCPA]
When this policy changes, the date and what changed will be noted on this page.
Questions about this privacy policy: support@getcarve.app.