Privacy Policy · v2026-10-03
Privacy Policy for Formahand
Formahand is operated by Macro Conquer. This page is the plain summary of what applies to a Formahand store; the full document is published by Macro Conquer. Where the two differ, the full document applies.
1. Who is responsible
Macro Conquer runs Formahand and is the controller of merchant accounts and of the platform's own records. For the personal data inside a store (its buyers, orders and customer list) the merchant is the controller and Formahand the processor, under the terms.
2. What is recorded
- Merchant accounts: name and email from sign-in (Google, or an emailed sign-in link), the stores and organisations you belong to, API tokens (only a hash is stored), the dates and versions of the terms you accepted with the country the acceptance came from, and your marketing opt-in (off by default).
- Store records: catalog, pages, theme, orders, buyers' names, emails, phone numbers and shipping addresses as entered at checkout, tracking numbers, customer list and tags, email templates, flows and events. A shopper's cart lives in a cookie (`fh_cart`) on the store's own hostname.
- Billing: your plan, promotions and referral code, a card reference held by Stripe (Formahand stores the brand and last four digits only), monthly usage meters (emails sent, automation runs, API calls, media size, domains, labels) and the statements issued.
- Operations: request logs at our infrastructure provider, webhook events from our payment processor and our shipping partner, delivery results from our email delivery provider, and the activity clock behind the idle-store policy (90 and 180 days).
Formahand runs no advertising pixels of its own on storefronts or in the dashboard. A merchant may switch pixels on for their own store; what those collect goes to the merchant's own account with that provider. The dashboard, sign-in and merchants' storefronts are never recorded; the one exception is a showcase store Formahand itself built, which asks you to agree before it shows anything (section 7).
3. Data isolation
Each store's data is kept separate from every other store's. One store cannot read another's data, and a merchant's API token reaches only their own store.
4. Processors
| Infrastructure provider | hosting and storage; request logs |
|---|---|
| Payment processor (Stripe) | checkout on the merchant's connected account, refunds, plan subscriptions, the card on file and monthly statements |
| Email delivery provider | order, shipping, platform and marketing email; bounce and complaint counts per store |
| Shipping partner | shipping labels and tracking for Formahand Shipping (ship-to name and address on the label) |
| AI model provider | only when a merchant runs the optional built-in setup assistant: the store's catalog text is sent to generate products |
| Analytics provider | page visits and replays of formahand.com's public pages and of Formahand's own showcase stores (section 7); never the dashboard, sign-in or a merchant's storefront |
A merchant who connects their own courier platform or PayPal shares order data with that provider under the merchant's own account and agreement. Section 9 says how a merchant gets the companies behind each role.
5. Email
Transactional mail (order confirmation, shipping updates, statements, idle-store notices) is sent because it is part of running the store. Marketing mail from a store goes only from the merchant's own verified domain to people who opted in, and every message carries an unsubscribe link that Formahand honours immediately. Formahand's own product updates go only to merchants who ticked the optional box, at most monthly.
6. Retention and deletion
Store data is kept as long as the store exists; an idle store keeps all of it. Orders and statements are kept for as long as accounting rules require after a store closes. Consent records are kept as evidence of the acceptance. To delete an account or a store, or to exercise access, correction, portability or objection rights, contact Macro Conquer. Shoppers should ask the store they bought from, which can export or delete their customer record.
7. Cookies
The dashboard uses a session cookie for sign-in; storefronts use fh_cart for the cart; fh_ref (30 days) remembers a referral link. None is used for tracking across sites.
On formahand.com's public pages we count page visits, note which site linked you here, and may replay how a page was used, to see which pages help. Anything you type is masked, no profile of you is built, and the dashboard, sign-in and merchants' storefronts are never recorded. A browser that sends a do-not-track or Global Privacy Control signal is not counted, and "Analytics settings" in the footer turns it all off for good.
A showcase store is a demo store Formahand built and links to. It shows nothing until you agree, on the page itself, that your visit there is measured and may be replayed the same way, with anything you type masked; the choice is kept for 180 days in a cookie on that store alone.
8. Changes
Material changes bump the version above and are shown to every merchant once in the dashboard before they continue.
9. Sub-processors
A merchant who needs the companies behind the roles in section 4, as the controller of their buyers' data, can ask for the current list from Macro Conquer. It is sent to the address on the merchant account. Merchants are told of a change to that list through a version bump of this policy.
Version 2026-10-03.