Service-specific terms

1. Product Hunter: claims, holds and exclusivity

1.1 A hold is temporary and expires. It reserves a product while you look at the offer and build a store around it; it is not a claim and confers no exclusivity.

1.2 A claim records the product against your account and removes it from the pool offered to other FlowFinds accounts, for as long as the claim stands.

1.3 Exclusivity is within FlowFinds only. It says nothing about whether another seller, on another platform, sells the same item. We make no representation about the wider market and none about how long a product stays viable.

1.4 Passing a product releases it. A released product may be offered to another account immediately, and cannot be reserved back.

1.5 Evidence shown with a find — observed listings, market movement since the claim — is a record of what was observed at a stated time. It is not a warranty about the present state of the market.

2. Store engine: generated storefronts

2.1 The store engine generates a storefront, its pages, its copy and the order of its sections, and records the reason it chose that order. Regeneration may change any of it; keep your own copy of anything you have edited by hand and want to preserve.

2.2 You publish the store; we generate it. You are responsible for its legal pages, its consumer-facing information, its cookie disclosure and its tax treatment, as clause 3 of the commercial terms sets out.

2.3 Payments on a generated store run in a sandbox until live payments are explicitly enabled for that store. A store in sandbox mode must not be presented to real buyers as able to take real money.

2.4 A generated store is a set of files served to the public. No credential, key or secret is ever written into one, and you must not add one — a secret in a published store is a published secret.

2.5 Where you connect a domain, you are the registrant and are responsible for its renewal and its use. We check availability and price from public sources and warrant neither.

3. Supplier and sourcing figures

3.1 Sourcing terms, the lowest observed listing price, the margin basis and the expected unit cost and profit are observations and derivations, each shown with the source row it came from. They are not quotations, and no supplier is bound by them.

3.2 Verify price, availability, lead time, duties and compliance documentation with the supplier before you commit money.

3.3 We are not a party to your contract with a supplier and take no commission on it unless we tell you otherwise in writing.

4. Growth: advertising artefacts and organic campaigns

4.1 An advertising artefact is generated with its own pass criteria attached. Those criteria are a measurement standard we apply to the artefact, not a prediction of the performance you will achieve.

4.2 The organic campaign tool researches, drafts and logs approvals. It publishes nothing. It holds no account on any social platform and posts on none. Every piece of material it produces is published by you, in your own account, under that platform’s rules.

4.3 You are responsible for advertising law compliance in the markets you target, including disclosure of paid promotion, claim substantiation and any rules on disclosing that material was generated with AI.

4.4 Advertising money and funded launch spend are governed by clauses 4 and 5 of the billing and refund terms.

5. Activity: orders, satisfaction and the support agent

5.1 The product issues your store a support email address and can route inbound messages through rules you configure. Mail sent to that address is Customer Personal Data processed under the data processing addendum.

5.2 The support agent answers within the rules and canned responses you have approved, and is bound to the record it is answering about. It does not invent order facts, and it does not issue refunds or make commitments on your behalf unless you have configured a rule that says so — in which case that commitment is yours.

5.3 Satisfaction sampling contacts a sample of your buyers on your behalf. You are the sender for the purposes of marketing and electronic communications law, and must have a lawful basis for that contact.

5.4 Order and revenue figures shown in the product are derived from what the store and the payment provider report. They are an operational view, not a set of accounts, and your accountant’s records govern.

6. The API

6.1 API keys authenticate as your account. Keep them server-side, rotate them if exposed, and revoke them when a person leaves. Calls made with your key are your calls.

6.2 Rate limits and quotas are published in the documentation and enforced. Repeatedly working around them is a breach of the acceptable use policy.

6.3 Breaking changes follow the deprecation notice period published in the documentation. Undocumented endpoints and fields are not part of the interface and may change without notice.

7. Beta and preview features

7.1 A feature labelled beta, preview or experimental is provided as is, may be changed or withdrawn at any time, and is excluded from the availability commitment at availability.

7.2 Do not rely on a beta feature for anything you cannot afford to lose, and keep your own copy of output it produces.

7.3 Feedback you send us about a beta feature may be used freely to improve the product. Tell us at [email protected] if you need that treated as confidential instead.