Privacy Policy

This dashboard (the "App") is built and operated by Acutix LLC ("Acutix," "we," "us") as a private, internal analytics and customer service tool for The Little Rose Shop. It is not a public product: there is no public sign-up, and every account is created directly by The Little Rose Shop's owner for its own staff.

What data the App uses

The App reads business data from services The Little Rose Shop has connected, to display it on internal dashboards. Depending on what is connected, that includes:

• Shopify — orders, products, and customer records
• Meta Ads (read-only) — advertising performance by campaign and by day: spend, impressions, clicks, and conversions, with campaign names and identifiers and the ad account's currency
• Google Search Console (read-only) — search performance for the shop's own website: daily totals of clicks, impressions, average position, and click-through rate, and, for each day, the search queries that led to a page of the site, with that page's address and its clicks, impressions, and position. Google reports these in aggregate and does not identify the people who searched
• Google Ads (read-only) — advertising performance by campaign and by day: spend, impressions, clicks, and conversions, with campaign names and identifiers and the ad account's currency. Reported search terms are also read and stored with their campaign, date, spend, impressions, clicks, and conversions for the last 30 complete account days. Google withholds some terms for privacy, so this report does not account for every search. No audiences, user identifiers, or individual profiles are requested
• Amazon Ads (read-only) — Sponsored Products advertising performance by campaign and by day: spend, impressions, clicks, and purchases, with campaign names and identifiers and the ad account's currency. No audiences or information about the people who saw or clicked an ad is read or stored
• Pinterest organic access (read-only) — the connected business account's ID and username, and organic impressions, saves, Pin clicks, and outbound clicks for the last 30 complete UTC days. The stored report includes aggregate and daily counts, availability and estimate labels, and up to 25 top Pin IDs with their metrics. Only account and Pin read permissions are requested. No individual viewer identities are requested or stored, and Pins and ad campaigns are never changed
• Amazon SP-API (read-only) — Amazon marketplace orders (a second sales channel, separate from Shopify): order totals, statuses, fulfillment channel, and item counts by day, and current FBA inventory levels by seller SKU. No buyer names, addresses, or other information about the people who placed an order is read or stored
• Etsy (read-only, connected through its own OAuth2 authorization flow rather than a simple API key) — the shop's own Etsy shop info (name, currency, listing and review counts), its listing catalog (price, quantity, status, tags, materials, and favorers — never the "views" figure Etsy itself documents as unreliable), order receipts and their line items (status, totals, and coarse ship-to geography such as country or region — never a buyer name, email address, or street address), and shop reviews (rating and review text only, never the reviewer's identity)
• Printful — routine read-only synchronization keeps print-on-demand order status, shipping method, country, state and city, the synced product and variant catalog, and fulfillment costs used to compute margin. Separately, when authorized support staff review an address correction, the App reads the recipient name, email, phone and shipping address to verify the linked order. After staff confirmation it sends the corrected recipient address to Printful and reads it back. Original and verified addresses are retained in the access-controlled support task with the staff member, timestamps and outcome. It never confirms, releases, cancels or pays for a Printful order.
• Judge.me (read-only): the shop's product reviews. For each review the App keeps the star rating, the product it is about, when it was written and last changed, Judge.me's review id, how Judge.me verified the reviewer (for example buyer, email, or not verified), how the review was submitted (for example web, email, or import), whether it has photos, how many characters its title and text have, and Judge.me's moderation state (approved, spam, or awaiting review) and hidden flag. Reviews Judge.me marks as spam are left out of the review figures. The review title and text are read only to count their length and are not stored. The reviewer's name, email address, and other identity, their IP address, and review photos are not stored. Nothing is ever written back to Judge.me
• GA4 (Google Analytics, read-only) — daily website traffic totals: sessions, users, page views, engaged sessions, and Google's "key event" counts, broken down by day, by traffic channel (both how a visitor ultimately converted and how they first arrived, shown separately), by page, by device type, and by country. All figures are pre-aggregated by Google to the day level; no individual visitor is identified
• Customer Service Hub archive (read-only) — data from the shop's connected help desk: support tickets and every message in them (including internal notes), customers' names, email addresses, and phone numbers as the connected help desk holds them, staff accounts, tags, saved replies, satisfaction survey answers, each ticket's activity history, and attachments. The App keeps a copy in its own database and private file storage so the shop's support history is preserved, and shows it only to signed-in owners and staff. Nothing is ever written back to the connected help desk, and this data is not sent to Rose or to the connected AI assistant tools: they receive aggregate counts only
• Gmail (Google Workspace; during the trial it sends only to a test address): the shop's support mailbox, where customers write to the shop. The App reads the email that arrives there through Google's Gmail API and shows it in the App's Customer Service inbox, and, once the shop switches replies on, sends the shop's replies from the same mailbox through Gmail. What is read and kept, who can see it, and what the App can and cannot do in the mailbox are described in the section on support email below
• Klaviyo (read-only) — campaign and flow names, statuses, send times, email subject lines, and aggregate results (recipients, opens, clicks, conversions, revenue, unsubscribes, bounces), plus list and segment names and how many members each has over time. No subscriber, profile, email address, phone number, or message content is read or stored
• Ahrefs — SEO and site performance data, retrieved when the SEO page is used, and a connection check
• QuickBooks Online — profit & loss, balance sheet, chart of accounts, and item data, read-only

For signed-in users, the App also stores account information needed to sign in (name, email, and role).

QuickBooks Online, specifically

The App's QuickBooks connection requests only read access to accounting data (com.intuit.quickbooks.accounting) — it never requests access to payments, and it never sends QuickBooks any data, only reads it. The refresh token used to maintain that connection is encrypted before it is stored. An authorized user can disconnect QuickBooks at any time; disconnecting stops new data from syncing but does not delete data already synced — that is a separate, explicit action.

Support email, specifically

The shop's support mailbox, hello@thelittleroseshop.com, is a Gmail mailbox on The Little Rose Shop's own Google Workspace, so Google is the source of the support email the App reads. The App is connected to Google as that mailbox, and refuses a connection to any other account, so it never reads a person's own mailbox. It reads the mailbox through Google's Gmail API, with access the shop grants in its own Google Workspace.

Before the App answers any customer, it runs a trial alongside the shop's connected help desk. For that trial the App holds Google's read-only Gmail permission (gmail.readonly), which lets it read mail, and Gmail's send permission (gmail.send), which lets it send mail from the support mailbox but not change anything in it. During the trial the App sends only to a test address the shop chose, never to a customer. Once the shop switches replies on, the replies the shop's staff write in the App, and any automatic replies the shop has switched on, are sent from the support mailbox through Gmail and appear in that mailbox's sent mail like any other reply. Customer email is only ever sent through the shop's own Gmail mailbox, never through Resend or any other mail service. Even with the send permission, the App cannot delete, archive, relabel, or mark mail as read in the mailbox.

For each email it reads, the App keeps a copy in its own database and private file storage: the sender's name and email address, the addresses it was sent or copied to, the subject, the date, the message text as plain text, the identifiers email uses to keep a conversation together, and, in private file storage only, the complete original message and its attachments. It also keeps technical details about each email: each attachment's name, type and size, Gmail's ids and labels for it, whether it was sent automatically, in bulk or to a mailing list, whether it came through a relay such as a contact form, and the results of Google's checks on the sender. It keeps the same for the replies sent from the support mailbox, and it links each conversation to the shop's own customer record with the same email address, so the customer's orders show beside it. During the trial it also records which of the App's rules, modelled on the ones the shop's current help desk runs, would have applied to each email (the rules are only simulated, and send nothing). Once the shop works in the App, it records how the shop handled each conversation: its status, tags, who it is assigned to, internal notes (which are never sent to the customer), and a history of those changes. Mail copied during the trial run is kept apart from the shop's working inbox and its figures.

Support email is shown only to signed-in owners and staff: the shop's owners, and staff members the owner has added to the Biz Ops workspace, which includes Customer Service. The database applies the same rule, and every sign-in to the App requires two-step verification, so viewers and staff outside Biz Ops cannot read it. Files are served only through the signed-in App, never from a public link. The key that keeps the connection to the mailbox open is encrypted before it is stored, and only the App's server can read it. Acutix, which operates the App, holds an owner account for account recovery and reaches this data only to run, secure, and support the App.

When the shop enables request sorting, the App sends a limited excerpt of a new incoming email or an explicitly approved existing email to TypeSafe's Jev model to suggest a category and workflow. Before sending, the App removes known sender names, email addresses, phone numbers, links and recognizable order references or addresses. This filtering is imperfect: the remaining excerpt may still contain personal information. Attachments, raw email, quoted history and contact records are not deliberately sent. Messages that appear incomplete or contain obvious payment, security or medical information are held for a person instead. The App keeps the original email locally and stores the category, confidence and processing record; it does not keep another copy of the excerpt in the sorting record. The model does not write replies, send messages, or change orders. The App does not send support email to Anthropic, Rose or connected AI assistant tools, which receive aggregate counts at most. If the shop switches automatic replies on, they will be chosen by rules the shop sets, never written by a model.

Support email is kept as the shop's support record for as long as the shop uses the App for customer service, unless the shop asks for it to be deleted sooner (see below). Mail copied during the trial run will be deleted when the shop moves its customer service to the App. Deleting email in the App does not delete it from the Gmail mailbox, whose own retention the shop manages in Google Workspace.

Where data is stored, and who else handles it

Data is stored in Supabase (a hosted Postgres database and private file storage provider, which also runs sign-in) and the App itself is hosted on Vercel. Three further providers handle limited data to provide specific features:

• Resend delivers the App's own emails to the people who use it, such as the weekly report email, which contains summary business figures, to the recipients set up to receive it. Resend is never used to email the shop's customers, and customers' emails are not sent to it.
• Anthropic provides the AI model behind Rose, the App's built-in assistant. When someone asks Rose a question, the App sends their chat messages, together with a summary of current business figures (revenue, orders, top products, sales channels, shipments, and low-stock items), to Anthropic to produce the reply. That summary does not include customer names or contact details.
• Cloudflare runs a bot check (Turnstile) on the sign-in page to tell people from automated traffic. It runs in the visitor's browser, and Cloudflare receives the information the check needs to work.

All of these are service providers Acutix uses to operate the App, not independent recipients of the data.

What we don't do

We do not sell this data, and we do not share it with any third party except the service providers named above, which are needed to operate the App, and the platforms the data already comes from (Shopify, Meta Ads, Google Ads, Amazon Ads, Amazon SP-API, Etsy, Printful, Judge.me, Pinterest organic access, Ahrefs, Google Search Console, GA4, the Customer Service Hub archive (connected help desk), Gmail, Klaviyo, QuickBooks Online), each under that platform's own terms.

Deleting data

The Little Rose Shop can request deletion of any data stored by the App, including previously synced QuickBooks data and support email with its attachments, by contacting us at the address below.

Contact

Acutix LLC — info@acutixmarketing.com