Terms of Service & Sale
Last updated: 7 August 2026
Feedzy.ai comes in two halves. The browser extension is free, works with no account, and keeps everything on your machine — nothing below makes you pay for it. The Max Cloud subscription is a paid, monthly service you buy per person for one Espace. These terms describe both, and they describe them as the software is actually built.
Three product words are used throughout and are never translated: an Espace is the workspace an account owns (it is what gets billed); a Dossier is a shared folder of feedback inside it; a Feed is a stream of captured feedback.
1. Who you are contracting with
Feedzy.ai is operated by Anthony Fantinati, trading as Blazing Ideas, a sole trader (auto-entrepreneur) established in France. Postal address: 466 Bis chemin de Blazin, 30000 Nîmes, France. SIRET: 515 266 997 00037.
Where the service runs: the website you are reading and the web app are served by Cloudflare; the API runs on Scaleway Serverless Containers in the Paris (fr-par) region; the database is hosted by Neon; encrypted media is stored on Cloudflare R2 with EU jurisdiction.
Open point — publisher and hosting details
To be settled before publication: the exact legal form and wording of the seller's identity; whether a registration number beyond the SIRET must appear; the publication director; the commercial and support contact address — today the product publishes only privacy@feedzy.ai, which is a privacy mailbox, and no billing or support mailbox exists; and the full legal names, addresses and phone numbers of the hosting providers, which French law (LCEN) requires to be reachable from the site. The Neon database region is not pinned anywhere in the repository and must be confirmed before any claim of EU-only hosting is made.
2. What these terms cover, and when you accept them
They cover your use of the Feedzy.ai browser extension, the web app at app.feedzy.ai, and the optional Max Cloud subscription sold through this site. Companion pieces you install yourself — the VS Code bridge, the local MCP server, the database bridge script on your own server — run on your machine or your infrastructure and are covered only to the extent we supply them.
You accept them when you pay. The purchase screen states that paying accepts these terms and links to this page, right next to the buy button and next to the withdrawal tick box described in section 15; that tick box archives, with each order, the address of this page as the text it pointed at.
Open point — acceptance outside the checkout
The paid path now asks. Three gaps remain either side of it. Nothing asks at sign-up: the footer of every screen in the app links here, so the page is reachable — but a link is not an acceptance, and a free account is created, and the extension used, without anyone ever being asked to agree. Decide whether that matters, given the free offer takes no money and stores nothing on our servers. No version of these terms is stamped against the account: the version archived with an order is the version of the withdrawal wording, not of this page, so we can prove what someone acknowledged about their withdrawal right but not which revision of the contract they bought under. And nothing re-obtains acceptance when the terms change — that is the same hole as the notice mechanism in section 14, and it has to be built as well as decided.
3. The free offer
The extension is free and requires no account. It captures screenshots, elements, colours, JavaScript and network errors and voice notes, formats them into a prompt, and hands that prompt to the AI or IDE of your choice. Multi-device syncing through a folder you own (your own storage) is part of the free offer, as is the local MCP server. None of these are gated by our server — they keep working whether or not you ever pay us, and whether or not our server is up.
AI features run on your API keys (see section 10). We charge nothing for them and we do not resell provider capacity.
Free means free, not guaranteed forever: we may change or discontinue free features. We will not turn an existing free feature into a paid one without saying so in advance.
4. The paid offer — Max Cloud
There is one paid tier. It is sold per seat, billed monthly, and attached to one Espace. Each Espace has its own subscription and its own storage pool; there is no pool shared across Espaces. Only an administrator of an Espace can subscribe for it.
Price
The per-seat price falls as the seat count rises, and the lower price applies to every seat:
| Seats | Price per seat / month | Discount |
|---|---|---|
| 1 | €3.00 | — |
| 2–4 | €2.80 | −7% |
| 5–24 | €2.50 | −17% |
| 25–99 | €2.25 | −25% |
| 100+ | €2.00 | −33% |
Because the bracket price applies to all seats, a larger team can cost less in total than a slightly smaller one (24 seats bill more than 25). We do not silently re-bill you either way; the app points it out when a higher seat count would cost you less.
Storage
Each paid seat includes 5 GB of encrypted cloud storage, pooled across the Espace. Extra capacity is sold as packs at €0.03 per GB per month, added to the same subscription. A signed-in account that belongs to no Espace gets a personal allowance of 5 GB. When the pool is full, new uploads are refused; nothing already stored is deleted to make room.
What the subscription unlocks
Max adds, and only adds: real-time encrypted cloud sync across your devices, hosted encrypted storage for screenshots and voice, creating teams and Dossiers, inviting people, roles and permissions, encrypted sharing between accounts, the embeddable public widget, and the hosted MCP relay. Capture, prompt building, sending to an AI with your own key, export, folder sync and the local MCP stay free and are never checked against your plan.
Seats
A seat is one named person. You cannot reduce the seat count below the number of seats currently assigned, nor below the number of active members of the Espace — unassign the people first, then lower the count. This is enforced by the server, not by trust.
Tax
Prices are in euros. Feedzy.ai bills as a French micro-entreprise under the VAT franchise of article 293 B of the French tax code: no VAT is added, and the amount displayed is the amount charged.
Open point — tax
Confirm the exact legal mention required on invoices under the VAT franchise, what happens when the threshold is crossed mid-subscription (prices become VAT-inclusive or VAT-exclusive — that choice changes what customers pay), and the treatment of business and non-French EU customers. The code deliberately disables Stripe Managed Payments so that Stripe does not act as merchant of record and does not add VAT; that decision is what makes this section necessary.
5. Payment
- Payment runs through Stripe Checkout. Stripe is our payment processor, not the seller: we sell to you directly and Stripe collects on our behalf.
- We never see or store your card details. They are handled by Stripe.
- The subscription renews automatically every month until you cancel it.
- Invoices, payment method and cancellation all live in the Stripe billing portal, which the dashboard opens for you.
- Adding or removing seats or storage packs mid-month is prorated by Stripe on the next invoice.
- If a payment fails, Stripe retries. Your Espace stays fully active during those retries; if Stripe ends the subscription, section 7 applies.
Open point — failed payments
How many retries, over how many days, and what the customer is told, is Stripe dunning configuration rather than code — it is not pinned in the repository. Fix the policy, then state it here instead of the vague sentence above.
6. Duration and cancellation
The subscription is monthly with no minimum term. You can cancel at any time from the billing portal. Cancellation is scheduled, not immediate: your Espace keeps every paid feature until the end of the period you have already paid for, and the dashboard shows the date it ends. You are not charged again after that.
We never cancel a subscription on your behalf. That is why deleting an Espace whose subscription is still renewing is refused: cancel it, or schedule its cancellation, and the deletion goes through.
Open point — refunds
Nothing in the product issues a refund today; cancelling simply stops the next renewal and leaves the period in progress paid for. Whether that is the stated policy, and whether any pro-rata or goodwill refund is offered (and how it interacts with the withdrawal right in section 15), is a commercial and legal decision that has not been made.
7. What happens when a paid period ends
When a subscription ends — cancelled, or ended by Stripe after failed payments — the Espace returns to the free plan and, concretely:
- The storage pool closes: new encrypted uploads are refused. Nothing is deleted at that moment.
- Max features stop: creating Dossiers and teams, minting invites, the public widget, the hosted MCP relay.
- Your encrypted data is kept for 30 days. Licences, memberships and sharing grants are deliberately left intact during that window, so re-subscribing inside it restores the team exactly as it was.
- After those 30 days without re-subscribing, the encrypted media stored for that Espace is permanently deleted by a scheduled purge, along with its storage records. This is irreversible. Personal storage that belongs to an account rather than to the Espace is not touched by it.
- Everything on your own machine is untouched, and every free feature keeps working — including folder sync to storage you own.
The 30-day window is the value currently configured. If it changes, this page changes with it.
8. Your account, your keys, and what we cannot do for you
The cloud is zero-knowledge: your content is encrypted in your browser before it is uploaded, and our server only ever holds ciphertext. Your password is never transmitted, even at sign-in. That design has consequences you should read as terms, not as marketing:
- If you lose your password and your recovery key, your cloud content cannot be recovered. Not by support, not by us, not by anyone. There is no back door to ask for.
- Deleting your account destroys the keys attached to it. Anything still encrypted to you becomes permanently unreadable — that is how the deletion is made effective.
- You cannot delete your account while you own an Espace: delete the Espace first, because it carries billing and other people's shared data.
- An account may register up to 5 devices. Revoke one to free a slot.
- Your email address is your identifier and cannot be changed: it anchors the sign-in record and every key grant made to you.
- You are responsible for keeping your password, your recovery key and your devices safe.
9. Acceptable use
A seat is for one named person; seats are not to be shared, rotated or resold. Beyond that, do not use Feedzy.ai to capture, store or share content you have no right to, do not upload unlawful content, and do not attack the service or work around quotas, plan checks or rate limits.
Open point — suspension
No suspension or termination procedure exists in the product or on paper: what triggers it, what notice is given, whether the customer can respond, and what happens to the period already paid for. Draft it before claiming the right to suspend.
10. AI providers, and your own keys
Feedzy.ai builds a prompt; you decide who reads it. When you use an AI feature, the request goes from your browser straight to the provider (Anthropic, OpenAI, GitHub, or an AI website you open) using the key or account you entered. We are not a party to it: we do not see the content, we do not charge for it, and the provider's own terms, prices and data practices apply. The same is true of the "open in" destinations, which simply open that site and paste your prompt into it.
The extension redacts recognisable secrets — emails, card numbers, IBANs, tokens — before text is stored or sent. It reduces the risk of leaking a secret into a prompt; it does not eliminate it. Check what you send.
11. Availability
The paid service is provided on a best-effort basis. We do not commit to an uptime level, and there is no service-level agreement. Maintenance, incidents and interruptions happen. Free, local features are designed to keep working when our server does not.
Open point — availability commitment
Decide whether paying customers get any availability target or credit. Saying nothing is a valid choice; saying nothing while a customer assumes otherwise is not.
12. Liability
Open point — this whole section needs a lawyer
What is proposed, and what must be checked: liability limited to direct, foreseeable damage; a cap set at the amounts you paid over the twelve months before the event; no exclusion of liability that cannot lawfully be excluded (death, personal injury, fraud, gross negligence); and consumers' statutory guarantees for digital content and services left entirely intact, since they cannot be waived by contract. The cap, the exclusions and the wording are all legal decisions, not engineering ones.
13. Personal data
How data is handled is set out in full in the Privacy Policy, which forms part of these terms: local-first by default, zero-knowledge for the optional cloud, no analytics or tracking, and the GDPR rights you can exercise — including account deletion, which the product performs by destroying your keys.
14. Changes to the service and to these terms
We may change the service and these terms. Where a change affects a paid subscription, we will announce it before it applies to your next renewal, and you can cancel before it takes effect rather than accept it. Price changes never apply retroactively to a period you have already paid for.
Open point — notice period and channel
Fix how much notice is given (30 days is the usual figure), through which channel (email to the account address, in-app notice, or both), and what silence means. Nothing in the product sends such a notice today, so this has to be built as well as decided.
15. Right of withdrawal (consumers)
A consumer buying a digital service in the EU has 14 days to withdraw. That right falls away only if the buyer expressly asks for the service to start straight away and acknowledges losing it. Feedzy asks for both, at the moment of purchase, and refuses the sale without them — here is exactly how, because a paragraph that only promises this is worth nothing:
- The purchase screen carries a tick box, never pre-ticked, holding two statements: that you request Max Cloud to open immediately, and that you acknowledge losing your 14-day withdrawal right once it is open. They travel to us as two separate answers, not as one blanket "I agree" — asking for immediate delivery is not the same act as giving up a right.
- The buy button does not reach Stripe until the box is ticked, and it says why instead of sitting silently disabled.
- Our server refuses as well, before it creates any payment session: an order missing either statement is rejected outright. It also refuses a consent that points at a wording we never published, so a record can never refer to a text that did not exist.
- Each consent is recorded: who ticked it, for which Espace, in which of the seven languages it was read, which version of the wording, the address of this page, and the payment session it belongs to. It is written before the payment link is handed out — if that record cannot be written, the link is withheld and nobody can pay.
- The record is marked confirmed only once Stripe reports the payment actually went through. A box ticked on a basket that was then abandoned is never produced as proof of a sale.
Two consequences follow, and they cut both ways. If you ticked that box, you asked us to open the service and you no longer have the 14 days. If those statements were not collected — for any purchase made before this mechanism existed, or through any route that bypasses it — the 14-day right applies in full and you are refunded. Business customers are not concerned by any of it.
Open point — the wording, and the copy owed to the buyer
The mechanism exists; three things about it have not been settled. The wording of the tick box is an engineer's draft, in seven languages, and it is the single sentence the whole waiver rests on — it must be validated. (A version stamp travels with every consent for exactly that reason: rewriting the text later must not re-label the consents already collected.) Whether one box may carry the two statements, or whether each needs its own, is the same question and has to be answered with it. Finally, the trader also owes the consumer a confirmation of that consent on a durable medium: today it is stored on our side only, and nothing sends it to the buyer — the only mail this service can send is address verification, and a Stripe receipt is not that confirmation. Decide who sends it and in what form.
16. Governing law, disputes and mediation
Open point — law, court and mediator are all unresolved
To be settled: the governing law (French law is the natural candidate given the seller's establishment) and the competent court, remembering that a consumer cannot be deprived of the protection of their own country's law or of the right to sue where they live. Separately, a French seller selling to consumers must belong to a registered consumer mediation scheme and publish its name and address — none has been appointed. Also verify what the current EU-level online dispute resolution reference should be, if any, before citing one.
17. Miscellaneous
- If one clause turns out to be unenforceable, the rest stays in force.
- You may not transfer your subscription to someone else without our agreement. We may transfer these terms as part of a transfer of the business, without reducing your rights.
- These terms, the Privacy Policy and the order you place through Stripe are the whole agreement between us.
Open point — language
This page is written in English while the site's source and default language is French and the seller is established in France. Selling to French consumers in English only is a risk worth checking: decide whether a French version is required and, if so, which one prevails. Note that the Privacy Policy is English-only too, so the answer applies to both pages.
18. Contact
Questions about a subscription, an invoice or these terms: see the open point in section 1 — a commercial contact address has to be published before this page is presented as a contract.
← Back to Feedzy.ai