Privacy policy

StoreFleet (Jose James, LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, USA) operates this website, the StoreFleet: Inventory Sync app for Shopify, the web dashboard at <your-workspace>.getstorefleet.com, the StoreFleet Agent desktop app, and the connections they make to e-commerce platforms. This policy covers all of them. Contact: hello@reply.getstorefleet.com.

For your own account and workspace, StoreFleet decides how that data is used. For the data of your shops’ customers, you, the merchant, decide; we handle it only to run the screens and actions you use.

Today StoreFleet connects to Shopify. Connections to Etsy and WooCommerce are in development and limited to a preview; they are not available to every workspace.

When you connect a shop, StoreFleet receives only what that platform’s API returns for the permissions you grant, and only when a screen, an action or a job you set up asks for it. The rules on this page apply to every platform you connect.

• From a platform when you connect a shop: the shop’s domain and name, the owner’s email address, the shop’s primary language, whether it is a development store, and an access token (plus a refresh token where the platform issues one).
• While you work: the orders, products, customers and other shop records a screen or action needs, read from the platform at the moment you use it.
• From you: your name, email address and password when you create a dashboard account, the members you invite, settings you change, and messages you send to support.
• From a waitlist or early access form on this website (for an app, platform or feature that is not available yet): your email address, the time you signed up, and the answers that form asks for. Depending on the form these are your shop’s address (we keep only its domain) or your Etsy shop’s name, the country your business is based in, the other stores you run, how many stores you would use it on, the AI tool you use, the invoice app you use today and its biggest problem, and your optional notes, such as what your current app misses. We use them only to email you about what you signed up for and to decide what to build. We do not record your IP address or browser for a waitlist sign-up.
• From a support form on this website (for example the Ledger theme’s support page): your name, email address, your store’s address if you give it, the topic you choose and your message. They go to our support inbox like an email you sent us, and we use them only to answer you. We do not record your IP address or browser with the message.
• From your browser or device when you sign in: IP address and browser user agent, recorded with your session and in the workspace audit log.

• Your account and workspace: members, roles, password (hashed with bcrypt), two-factor settings, sessions and the audit log.
• Each connected shop: its domain and name, owner email, language, and its access tokens, encrypted at rest.
• Order identity: the internal id, the platform’s id and the order number, so notes, returns, shipments and links to an order keep working.
• Records you create in StoreFleet: order notes, return records, shipment tracking numbers and carriers, products in your StoreFleet catalogue and their links to products in your shops, and pending changes with their approval history.
• Draft orders you build in StoreFleet, including the recipient’s email, phone and addresses you enter. This is the one place we store a shop customer’s contact details.
• Settings for any Discord, Telegram or Google Sheets connection you add, encrypted at rest.
• Support conversations you start from the app or dashboard.

We do not keep a copy of your customer list, of order contents (status, totals, line items, customer details), or of your shops’ product data: those are read live from the platform each time a screen shows them. StoreFleet never receives card or bank details.

• To show your shops’ data and to make the changes you, your team or the approval rules you set ask for.
• To keep your account secure: sign-in, two-factor checks and the audit log.
• To answer support requests.
• To send account emails (verification, invitations, password resets) and service emails to a shop owner about the app: welcome, setup help, tips, a feedback request and a note after uninstall. Development stores are never sent service emails. Reply STOP to any service email to opt out.

We do not sell, rent or trade your data or your customers’ data, and we do not use it for advertising.

Platform access tokens, refresh tokens and integration settings are encrypted at rest with AES-256-GCM. Passwords are stored only as bcrypt hashes. Traffic to StoreFleet is served over HTTPS. Workspaces can require two-factor sign-in, limit staff to chosen screens and shops, and review an audit log. See Security for the details.

• Uninstalling the Shopify app: the stored access and refresh tokens are wiped at once and the shop is marked disconnected, so StoreFleet can no longer reach it.
• Disconnecting or removing an Etsy or WooCommerce store (preview): the stored Etsy tokens or WooCommerce API keys are wiped at once, and the webhooks StoreFleet added to a WooCommerce store are removed. From these stores StoreFleet keeps only order identifiers (the platform’s order ID and order number), never the buyer’s name, email or address. You can also revoke access on the platform itself: in your Etsy account settings, or in WooCommerce under Settings → Advanced → REST API.
• Shopify’s erasure request (sent 48 hours after uninstall): the shop’s details, tokens, settings, order and draft-order records and support conversations are deleted. The workspace is deleted too, unless another shop or a dashboard user still uses it; then only that shop’s data goes.
• A shop customer’s erasure request sent through the platform: any data-request record naming that customer is deleted.
• Removing a shop in the dashboard stops StoreFleet from using it. To have its stored data deleted straight away, or to delete your account or workspace, write to hello@reply.getstorefleet.com.
• Website chat and visit statistics (see below): the full IP address is kept for 30 days and then shortened in place (the last part removed); chat conversations and visit records are deleted 12 months after their last activity, or sooner when you ask at hello@reply.getstorefleet.com.
• Customer account at my.getstorefleet.com (see below): a sign-up whose email is never confirmed is deleted after 7 days, signed-in sessions end after 14 days (7 days unused), failed-attempt and email counters are deleted after a day, and the security log is deleted after 12 months; the account itself stays until you ask us to delete it.
• Waitlist sign-ups are deleted 12 months after you sign up at the latest, or sooner when you ask at hello@reply.getstorefleet.com.

Otherwise we keep data while your account or shop connection exists.

• Cloudflare hosts this website and carries traffic to our servers, terminating TLS.
• Our account and service emails are sent from our own mail server; no outside email delivery provider handles them.
• Anthropic provides the AI model that drafts answers in the support chat, including the chat on this website, so your support messages are sent to it.
• Slack is where our team is notified about support conversations that need a person, and where it reads and answers chats from this website.
• When we turn them on, Google Analytics measures visits to this website only, not the app or dashboard. Google Ads counts how many visitors who came from one of our ads go on to open an app's Shopify App Store listing, so we can measure our ads. Both start with analytics storage, ad storage, ad user data and ad personalisation turned off for every visitor (Google Consent Mode), so Google sets no cookies until you choose "Accept" in the cookie banner; until then Google receives only cookieless measurements. "Cookie settings" at the bottom of every page changes your choice, and choosing "Reject" removes the cookies these tools set. Your choice is kept in your browser for a year. When you arrive from an ad or a tagged link, the campaign tags and the ad click ID in the address are kept in that browser tab's session storage until you close it, so a later click on an App Store link is counted for that campaign.
• Microsoft Clarity records how visitors use this website (clicks, scrolling and the pages they view, shown as heatmaps and session replays) so we can improve it; not the app or dashboard. It runs without cookies unless you accept cookies in the banner, and what you type into forms is masked.
• Discord, Telegram or Google Sheets, only if you connect one, to deliver the notifications you set up. Alerts carry no buyer name, email or address.

The platforms you connect (Shopify, and Etsy or WooCommerce when available) receive the requests StoreFleet makes on your behalf under their own privacy policies.

The StoreFleet Agent desktop app runs on your own computer and uses the AI model you configure in it. What it reads is sent to that model’s provider under your own account with them.

You can ask us for a copy of the data we hold about you, to correct it, or to delete it, by writing to hello@reply.getstorefleet.com. A shopper who wants to know what a shop holds about them should ask that shop; requests sent through Shopify’s own mechanism reach us automatically.

StoreFleet is a business tool and is not directed at children.

When this policy changes, we update this page and its date.

This website has its own live chat and counts its own visits. Both are stored on our own servers and neither sets a cookie. Three service providers process this data for us: Cloudflare, which hosts the site and passes chat messages and visit records to our servers; Slack, where our team reads and answers website chats; and Anthropic, whose AI model drafts the first answers in the chat. We do not sell this data or use it for advertising.

• What the chat keeps: your messages and our replies (including any contact details you choose to write in them), the page you wrote from, and for each message your IP address, the approximate location and network Cloudflare derives from it (country, region, city, time zone, network operator), your browser’s user agent (device, browser and operating system) and the referring site or campaign link that brought you. An AI assistant (Anthropic’s model) answers first and a person from our team can read the conversation and take over. Our team gets one short notice per chat in Slack with the start of your first message, without your IP address; the conversation itself is read and answered in our internal customer system.
• Talking to the chat: on wide screens a small fox (Kit) walks around the site and opens the chat when you click it. If you press its Talk button or the microphone in the chat, your browser asks for access to your microphone and Kit records what you say until you stop talking. The recording is sent to our website and turned into text by Cloudflare Workers AI (the speech model runs on Cloudflare’s network, which already serves this site); the text is sent as an ordinary chat message, and the recording is not kept by us or used for training. The answers are read aloud with a voice generated by Cloudflare Workers AI from the answer’s text. In browsers that cannot record, your browser’s own speech service turns your words into text instead (in Chrome this is Google, in Edge Microsoft, in Safari Apple) and its built-in voice reads the answers. The microphone is used only after you press the button, during a spoken conversation, and is released when the conversation ends: when you press the button again, close the chat or stay silent twice. Hiding the fox is remembered in your browser’s local storage (sf-pet-off), and that it already greeted you in this visit in session storage.
• How the chat remembers you: your browser keeps a random visitor ID and the conversation’s ID and secret key in local storage, so you can come back to the same conversation, plus a note that the chat’s welcome bubble was already shown so it does not show again. The new-conversation button in the chat forgets the conversation. We never use your IP address to find or reopen a conversation.
• Visit statistics: for each page view we record the page, its title, the time, the referring site or campaign link, how long the page was open, how far it was scrolled, links to other sites you clicked (such as the Shopify App Store), your IP address, the approximate location and network derived from it, the user agent and, when your browser allows it, the random visitor ID above, so we can tell new from returning visits and link a chat to the visits around it. Visits without a visitor ID are grouped under a key computed from your IP address and user agent with a secret only we hold, so the key on its own does not reveal the address. Known bots are left out.
• Why: to answer your questions (the chat, at your request), to protect the site and the chat from abuse (rate limits use the IP address), and to understand which pages help visitors, on the basis of our legitimate interest in running and improving this website.
• Do Not Track and Global Privacy Control: when your browser sends either signal, visits are still counted, but no visitor ID is linked to them and only a shortened IP address is stored.
• How long: the full IP address for 30 days, then it is shortened in place (the last part of an IPv4 address, everything after the first three groups of an IPv6 address); conversations and visit records are deleted 12 months after their last activity, and at the same time we delete our copy of that conversation in Slack (the messages our system posted there).
• Your choices: ask for a copy or for deletion of your chats and visit records at hello@reply.getstorefleet.com (tell us the email you gave in the chat, or the visitor ID shown in your browser’s local storage as sf-vid), or clear this site’s data in your browser to drop the visitor ID.

For data about your Etsy shop and its buyers, StoreFleet acts as your service provider: it processes that data only to run the screens and actions you use in StoreFleet. Concretely:

• What StoreFleet reads: your shop's name and ID, shipping profiles, orders (receipts) with their items, totals and shipping status, and your listings with their price and stock. StoreFleet does not request buyers' email addresses.
• What it keeps: your encrypted Etsy access tokens, and for orders only the Etsy order ID, number, status, totals and dates. Buyer names and addresses are read from Etsy when you open an order and are not stored. Listings are read live and not stored.
• Freshness: listing details are never shown more than 6 hours and other Etsy data never more than 24 hours older than on Etsy.
• Who else gets it: nobody. Etsy data is not sold, not shared with advertising or marketing platforms, not sent to AI or machine-learning providers, and not used for analytics beyond the reports you see about your own shop. AI agents connected to your workspace cannot access Etsy shops.
• Security: tokens are encrypted at rest and all traffic uses HTTPS. If Etsy data handled by StoreFleet is compromised, we notify Etsy and you within 24 hours of discovering it.
• Your controls: disconnect the shop in StoreFleet to delete the tokens at once, revoke StoreFleet in your Etsy account under Apps, or ask us to delete the rest at hello@reply.getstorefleet.com.

The term 'Etsy' is a trademark of Etsy, Inc. This Application uses Etsy's API, but is not endorsed or certified by Etsy.

The customer account is one place for customers of any StoreFleet app, waitlist or website chat to see what we have under their email and to manage how they sign in. You can sign in with an email and password or with Google (see Google sign-in).

• What the account keeps: your email address and when you confirmed it, your password as a one-way hash (never the password itself), your name if you signed in with Google, your Google account ID if you linked Google, and, if you turn on two-factor sign-in, either your authenticator key (encrypted) and one-way hashes of your recovery codes, or that you chose email codes. Codes we email you are stored only as one-way hashes and stop working after 10 minutes. We do not store your Google profile picture.
• Sessions and security log: for each signed-in browser, its IP address, browser user agent, how you signed in and when it was last used, so you can see and end your sessions on the Security page. Sign-ins, failed attempts, password and two-factor changes are written to a security log with the IP address, and failed attempts are counted per IP address (or IPv6 network), per email and per recognized browser to slow down password guessing; these counters are deleted after a day without use.
• What it shows you: matched only by the email address you confirmed, the StoreFleet apps and workspaces where that email is a user, your waitlist sign-ups (above) and a summary of website chats where you left that email (above): their status, number of messages, the page they started on and dates, not the messages themselves.
• Emails: we send the confirmation and password reset links, a link to confirm your email after a Google sign-in when Google does not manage that address, a code to turn on email-code sign-in and, with it on, a sign-in code when you ask for one, and a notice when your password, two-factor sign-in or Google sign-in changes, from our own mail server. They are not marketing emails.
• Cookies: my.getstorefleet.com sets only the cookies sign-in needs: your session, a pending two-factor step, a short-lived Google sign-in state, a cookie that ties an email confirmation link to the browser where you signed in with Google (up to 24 hours), and a signed random ID that recognizes a browser you signed in from (90 days), so failed sign-ins elsewhere cannot lock you out of it. It runs no analytics or advertising scripts.
• Who sees it: our team can see your account's status, how you sign in, whether two-factor sign-in is on and which kind, when you last signed in and the accounts matched to your email, and can disable the account if it is misused. Nobody at StoreFleet can see your password, authenticator key or recovery codes.
• Why: to provide the account you asked for and to keep it secure, on the basis of providing that service and our legitimate interest in protecting it.
• Your choices: sign out of any browser on the Security page, turn two-factor sign-in on or off, or ask us to delete the account at hello@reply.getstorefleet.com from the email it uses.

StoreFleet uses Google in two places, and only when you choose to:

• Signing in with Google to your StoreFleet customer account at my.getstorefleet.com. We receive your name, email address, profile picture and Google account ID (scopes openid, email, profile). We use them only to sign you in, to show your name on your account and to match your account with the stores and support conversations under the same email.
• Connecting Google Sheets in Columna: Order Export & Sheets, to send order exports to a spreadsheet. The app asks only for access to the spreadsheets it creates or that you open with it (scope drive.file), plus your email address to show which Google account is connected. Details are in the Order Export privacy policy.

Data received from Google is not sold, not used for advertising, not shared with anyone except the service providers needed to run the feature you use, and not used to train AI or machine-learning models. StoreFleet's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can disconnect at any time: remove StoreFleet under your Google account's third-party connections, disconnect Google Sheets in Columna: Order Export & Sheets, or ask us to delete your data at hello@reply.getstorefleet.com.