Privacy Policy

FeCommerce ("we", "us") runs fecommerce.co and makes plugins, templates and components for Framer: the FeCommerce plugin and storefront components with the FeCommerce Bridge for WooCommerce plugin for WordPress, StripeKit, RazorpayKit, Shopify Connect, Calendly Booking, SEO Toolkit, and our Framer templates and components (together, "FeCommerce"). This policy explains what information FeCommerce processes, why, and for how long. Some sections only apply if you use that product.

1. Who is responsible

• For visitors to fecommerce.co, buyers of our products, plugin accounts and licenses, and the merchant information described below, FeCommerce is responsible.
• Merchants who build a store or booking page with our products decide what their site collects from their own shoppers and visitors. For that information the merchant is responsible, and where it passes through FeCommerce, we process it on the merchant's behalf.

Contact: [email protected]

2. Information we process

a) When you visit fecommerce.co

• We use Google Tag Manager, Google Analytics and Microsoft Clarity to understand how the site is used. They collect information such as pages visited, clicks and scrolling, device and browser type, approximate location and your IP address, and set cookies to do so.
• Your browser remembers your light or dark theme and whether you've seen the intro animation. This stays on your device.
• Fonts load from Google Fonts, and some product pages embed videos from YouTube, which receive your IP address when they load.

b) When you contact us

• The contact form sends your name, email and message to us through Web3Forms, our form-delivery provider.
• To stop spam, Cloudflare Turnstile checks the form, which involves your IP address.
• If you choose to book a call, your name, email and message are filled into Calendly's booking page for you.

c) When you buy a template or component

• Checkout happens on Stripe. We never receive your card details.
• Stripe tells us your name, email and what you bought, and we use them to email you your download or remix link through Resend. A copy goes to our support inbox as the record of the sale.

d) Plugin accounts and licenses

Some plugins ask you to sign in or enter a license key. For this we process:

• your email address and name, and the sign-in method you used (email code or Google). One-time codes are stored only in a scrambled (hashed) form;
• your license key, the plugin and its version, the Framer project's id and name, the site's domain, a hashed form of the IP address, and when the license was first and last checked;
• support tickets and messages you send us.

e) FeCommerce for WooCommerce

When a merchant connects a store:

• The store's web address, to find the store and confirm that the merchant controls it.
• A short pairing code and a one-time check read from the merchant's website, to confirm the connection.
• A random connection id created by the plugin. We don't receive the Framer project's name or Framer's own project id for this connection.
• The published web addresses of the Framer site, so the connection works only on the merchant's own site.

While a merchant works in Framer:

• Requests to read the store's products, variations, reviews and categories, used to show and sync products in Framer.
• Each editor's access credential, kept in that editor's own browser. We store only a one-way fingerprint of it, never the credential itself.

On the merchant's published site, requests from shoppers' browsers pass through FeCommerce to the merchant's store, so the store can answer them: product and stock lookups, searches and filters; cart contents and coupon codes; at checkout, the details the shopper enters (such as name, email, phone and addresses) and the chosen delivery option; and reviews a shopper submits.

We pass these to the merchant's store and return the store's answer. We don't store products, carts, orders, checkout details or reviews. We also pass the shopper's IP address to the store, so the store can calculate tax and shipping and run its own fraud checks.

Security and fraud prevention: to protect stores from abuse, such as automated card testing, we keep short-lived records of failed payment attempts, linked to a hashed form of the IP address and never the address itself, and of temporary blocks.

f) StripeKit

• The merchant's Stripe keys are saved in the Framer project's plugin storage, where the project's editors can access them. We recommend a restricted key.
• The plugin talks to Stripe directly from the editor's browser to list and create products, prices and Payment Links. These requests don't pass through us.
• On the published site, buttons link to Stripe Payment Links, and shoppers pay on Stripe. No shopper information reaches us.

g) RazorpayKit

• The merchant's Razorpay keys are saved in the editor's own browser.
• Requests from the plugin to Razorpay pass through our relay server, because Razorpay doesn't accept them straight from a browser. The relay forwards them without storing or logging them and doesn't pass on the editor's IP address.
• On the published site, shoppers pay in Razorpay's own checkout. No shopper information reaches us.

h) Shopify Connect

• The plugin talks to the merchant's Shopify store directly. Nothing passes through us.
• The Storefront access token is kept in the editor's browser: for the session, or for up to 30 days if they choose to be remembered.
• On the published site, the shopper's cart is remembered in their own browser, and checkout details (such as email, phone and delivery address) go straight to Shopify.

i) Calendly Booking

• The simple embed only uses the merchant's public Calendly link. Nothing passes through us.
• The advanced booking components run through our server. We store the merchant's Calendly access token encrypted, together with their Calendly account address and email, for up to 90 days.
• When a visitor books through these components, their name, email, time zone, notes and any guests pass through our server to Calendly. We don't keep them.

j) SEO Toolkit

• Speed audits send the page address you choose to Google PageSpeed Insights, which then loads that page. Search previews fetch the site's icon from Google.
• If you turn on AI alt text, the plugin sends your images to OpenAI using your own OpenAI key. The key and your SEO settings are kept in your browser.
• Nothing passes through our servers.

k) Templates and components

Our templates and components run inside your own Framer site and don't send information to FeCommerce. Templates built for a store or booking tool work through the matching plugin above.

3. What we keep, and for how long

Information kept only in your browser or in your Framer project stays there until you remove it or sign out.

4. What we don't do

• We don't sell or rent personal information.
• We don't use shopper information for advertising or profiling.
• We don't receive card details. Card payments go directly to Stripe, Razorpay, Shopify or the payment provider the merchant chose.

5. Service providers

• Cloudflare runs our servers, database and relays, protects our forms with Turnstile, and processes the requests described above on our behalf.
• Framer hosts merchants' sites, plugin storage and the product images copied into a Framer project.
• Stripe handles purchases on fecommerce.co and payments made through StripeKit.
• Resend sends purchase and sign-in emails.
• Web3Forms delivers contact-form messages to us.
• Google (Analytics, Tag Manager, Fonts, PageSpeed Insights, sign-in) and Microsoft Clarity provide analytics, fonts, audits and sign-in.
• Razorpay, Shopify, Calendly, WooCommerce stores and OpenAI receive information only when you use the matching plugin, and on your instruction.
• Payment providers chosen by the merchant (for example Stripe or Paystack) receive payment details directly from the shopper.

Information may be processed in countries other than yours. Our providers apply appropriate safeguards.

6. Cookies

fecommerce.co uses cookies from Google Analytics and Microsoft Clarity for analytics, and a sign-in cookie for plugin accounts. You can block or delete cookies in your browser settings. The site still works without analytics cookies.

7. Security

• Encryption in transit: all traffic is encrypted (HTTPS).
• On our servers: FeCommerce editor credentials are stored only as one-way fingerprints, sign-in codes and IP addresses are hashed, and secrets shared with stores and Calendly tokens are encrypted.
• On your side: keys that StripeKit, RazorpayKit, Shopify Connect and SEO Toolkit keep in your browser or Framer project are protected by that browser and project. Share project edit access carefully, and use restricted or limited keys where your provider offers them.
• Access control: each FeCommerce connection works only for its own Framer project and its own website addresses.

8. Choices and control

• Merchants can disconnect FeCommerce at any time, either from the plugin in Framer or from WooCommerce → FeCommerce in WordPress. Disconnecting stops all requests for that site.
• Signing out of a plugin removes the keys and tokens it saved.
• Shoppers and visitors should contact the store or site they used about their personal information. We'll support merchants with any request.
• Depending on where you live, you may have the right to access, correct, delete or object to the processing of your information. Contact [email protected].

9. Children

FeCommerce isn't directed at children. We don't knowingly collect children's information.

10. Changes

We'll update this page when how we handle information changes, and change the date at the top.

11. Contact

[email protected]