In short
- Ecomify serves two audiences: merchants who install the “Ecomify” Shopify app on their store, and the team, who sign in by invitation.
- The Shopify app reads the store read-only, mostly totals, never its customer list. It keeps no customer’s name, email, phone number or address.
- Access to Shopify, Meta and Juicy is stored encrypted.
- 48 hours after the app is uninstalled, everything that came from the store is deleted.
- No advertising, no trackers, no selling of data. Ever.
- To see, correct or delete your data, write to [email protected].
Who is responsible
Ecomify is a service by William Blais (“we”), who runs it in his own name.
The person in charge of the protection of personal information is William Blais. You can reach him at [email protected].
Who this policy covers
It explains what Ecomify does with information about:
- merchants, owners or staff of a Shopify store, who install the “Ecomify” Shopify app;
- people on the team who use the app, at app.ecomify.cc;
- store owners who connect their Meta, Shopify or Juicy accounts to it;
- customers and visitors of those stores, of whom Ecomify mostly sees totals;
- visitors to this site, ecomify.cc.
It follows Québec’s Act respecting the protection of personal information in the private sector, as amended by Law 25.
This site, ecomify.cc
This site keeps nothing about you. It has no cookies, no analytics, no trackers, no forms and no JavaScript. Its fonts are served from here, with no call to Google.
As with any website, our host Cloudflare receives your IP address to send you the pages and block attacks. It handles it under its own policy.
The Shopify app, for merchants
You install the “Ecomify” app from Shopify. It only asks for read permissions and changes nothing in your store.
Installing and signing in
At install, Shopify shows you the permissions requested, then sends Ecomify a signed address that proves you work in the store. Ecomify then opens your session, with no password and no Google account. After that, the link to Ecomify in your Shopify admin does the same.
Ecomify does not ask Shopify for your name or email. It keeps:
- the store’s domain (
your-store.myshopify.com), its name, currency, time zone and public domain; - the install date and the permissions granted;
- Shopify’s access token, valid for 1 hour, and its refresh token, valid for 90 days, both encrypted (AES-GCM). Ecomify refreshes them when it needs them.
You only see your store. Other merchants do not see it.
What the app offers merchants
Sales, sessions, today’s live sales and, if you use Juicy, profitability. What the app reads for this is described in Connected accounts, under Shopify and Juicy.
- Meta is optional, and not yet available to merchants who install the app. Nothing from your store is sent to Meta.
- Claude, the team’s artificial intelligence, is not available to merchants for now.
- The store script (the click map and live presence, see On the stores) is not added by the Shopify app.
If we ever offer Meta or Claude to merchants, we will update this policy first.
Shopify’s compliance webhooks
Shopify sends Ecomify signed notices (“webhooks”). Ecomify checks their signature and rejects any that do not come from Shopify.
customers/data_request: a customer of your store asks for their data. Ecomify lists what it keeps about that customer (only customer service records, if any), and we give it to you within 30 days.customers/redact: a customer asks for deletion. Ecomify deletes the customer service records that name them, the live sales rows of their orders, and any Claude questions or agent tasks that mention their email.shop/redact: sent 48 hours after uninstall (see below).
Ecomify keeps a record of each notice: the date, the store, the Shopify customer ID if any, and what was done. It is proof that we handled the request; it contains no name or email.
Uninstalling
Right away, Shopify sends app/uninstalled. Ecomify deletes the access tokens, disconnects the store and deletes the figures kept for display. Shopify itself removes the order notifications used for live sales.
48 hours later, Shopify sends shop/redact. Ecomify then deletes everything that came from the store: its installation, live sales, the figures kept for display, the click map and live presence if any, and the customer service records of the brand linked to the store through the app.
Your space in Ecomify (your brand’s name and what you wrote there) remains, with no data from the store. To delete it too, write to [email protected].
Team sign-in
People on the team sign in to the app with their Google account. They can then add a passkey (Face ID, Touch ID or the device’s fingerprint reader).
Your Google account
When you sign in, Google sends us your email address, your name and your profile picture. Ecomify only reads the email address verified by Google, and checks it against the list of authorized people. Your name and picture are not kept.
The access list maps each address to a first name. It is stored as a secret at Cloudflare, not in the database. In the app, you are identified by that first name.
Ecomify asks for no other access to your Google account: not your email, your calendar or your files.
Ecomify’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. This information is used only to let you sign in. It is never sold, never passed on to anyone, and never used for advertising or to train an artificial intelligence model.
Your passkey
If you create a passkey, Ecomify keeps its public key, the device name, and the dates it was created and last used. Your face and fingerprint never leave your device: Ecomify never sees them.
Your session
Once you are in, a signed cookie keeps your session open for 14 days, or 30 days if you choose. You can close a session remotely, one device at a time. Ecomify also keeps your security choices, such as the new-device alert.
Your device remembers your first name and email address to suggest the right account next time. The “Pas toi ?” (“Not you?”) button on the sign-in page erases them.
The sign-in log
Every sign-in attempt is logged: the date, the first name if known, the method (Google, passkey or recovery link), the browser and system (for example “Safari · iPhone”), the country the connection comes from, whether it succeeded, and if not, why. This log is used to spot suspicious access and to show you your devices. It does not contain the IP address.
The attempt limit
To block attacks, Ecomify counts sign-in attempts per IP address: at most 20 in 10 minutes. This counter keeps the IP address for one hour, then deletes it at the next sign-in attempt.
The team’s work
What the team creates in Ecomify is kept there: brands, ads and their versions, videos and images, comments, the rules and knowledge given to Claude, sample portraits of the target customers (not real people), and research notes.
Important actions, such as approving or publishing an ad, are logged with the person’s first name, to know who did what.
The research section keeps public information about other businesses: links to public ads, the public product lists of online stores, and notes. It does not target individuals.
Videos, images and screenshots are stored at Cloudflare.
Connected accounts
Meta (Facebook and Instagram)
When someone connects their Meta business portfolio with “Connecter avec Meta” (“Connect with Meta”), Meta gives Ecomify an access token. Ecomify keeps it encrypted (AES-GCM), along with the ID and name of the system user Meta creates, and the portfolio name.
The permissions requested are ads_management, ads_read, business_management, pages_show_list, pages_read_engagement, pages_manage_ads and instagram_basic. Ecomify uses them to:
- read ad accounts, campaigns, ad sets, ads and their thumbnails;
- read their daily statistics: spend, impressions, reach, clicks, video views, add-to-carts, purchases and purchase value;
- choose the Facebook Page and Instagram account an ad is published under;
- publish the ads the team has approved. They are always published paused: only a person on the team can switch one on.
Meta only provides totals: Ecomify receives nothing about the people who see the ads. This data is used only to run Ecomify for the brand that connected it.
Shopify
A store is connected read-only, in one of these two ways. Ecomify changes nothing in the store.
- The “Ecomify” Shopify app, the one merchants install (see The Shopify app). Its access tokens (1 hour) and refresh tokens (90 days) are stored encrypted.
- The advanced method, for the team’s stores: a Shopify app specific to the store. Its ID, its secret and its access token, valid for 24 hours, are stored encrypted.
The permissions are read_reports and read_orders. Three others, also read-only, are optional: read_products, read_returns and read_shopify_payments_disputes, only if the store grants them. The advanced method may also have read_all_orders. Ecomify reads:
- once, when connecting: the store’s name, currency, time zone and public domain;
- reports as totals (ShopifyQL): sales, cost of goods, sessions, landing pages, channels, campaigns, devices, countries and regions, hours, products, and the share of new customers;
- the period’s orders, to compute refund and return rates: the number, date, amount, refunds and return status. Not the customer’s name or email;
- payment disputes: the order number, status, reason and amount;
- when someone clicks “Préremplir” (“Prefill”) on a brand’s product sheet: the title and description of 10 active products. A person accepts or rejects what is drawn from them; only what they accept is kept in the sheet;
- when a person looks up an order by its number or the customer’s email: the order, its items, its tracking, and the shipping first name, last-name initial and city, to recognize the parcel. This is displayed, never kept, and the typed email is only used for the search at Shopify;
- for the globe in En direct (“Live”): the city and a point rounded to about 10 km from the shipping address of today’s orders, grouped by city, with no name or street (see On the stores).
These Shopify responses are used for 10 minutes at most (2 minutes for the globe), then replaced at the next read. They are deleted when the store is disconnected or the app uninstalled. Ecomify does not copy the store’s customer list.
For live sales, Ecomify also subscribes to Shopify’s order notifications (“webhooks”), using the same read_orders permission. This is the only setting it makes in Shopify. As soon as an order is placed, cancelled or refunded, Shopify sends it to Ecomify, signed to prove it comes from Shopify. Ecomify only asks for and keeps:
- the order’s ID and number, its time, total, subtotal, shipping, taxes and currency;
- the payment status, the cancellation and the refunded amount;
- the ad campaign the visit came from: the
utm_campaignparameter of the landing page, and nothing else from its address.
Never the customer’s name, email, phone number, address or IP address, nor anything they wrote in their order. Test orders are not kept. These rows are deleted after 7 days.
Juicy
If a brand connects Juicy, an attribution and profit tool, Ecomify keeps the tokens Juicy issues (or the key pasted instead) encrypted, along with the list of stores that Juicy account can see. Ecomify reads attribution and profit figures from Juicy, read-only, to display them. It does not keep them.
Customer service
The tool that answers a store’s customer emails, or a Claude agent of the team, can send Ecomify one record per request: the customer’s name or email, the order number, the subject, a summary, the reason (delivery, return, refund…), the status, and, if a person has to decide, the reason why and the decision made.
These records are used to follow customer service and the decisions to make. They are the only data kept by Ecomify that names a store’s customer. They do not come from the Shopify app.
On the stores
A team store can add a small Ecomify script to its theme. The Shopify app does not add it. It follows the store’s consent choice, meaning its cookie banner, through Shopify’s Customer Privacy API: if the visitor declines analytics, the script measures nothing. It sets no cookies.
The click map
Once per page view, the script counts:
- clicks, reduced to a 20 × 20 cell of the clicked element;
- how far down the page was scrolled, in tenths;
- clicks on elements that do not respond, and repeated clicks out of frustration.
Each measurement adds 1 to a counter, per page, per day and per screen width. Ecomify also keeps the visible name of clicked buttons and links, such as “Add to cart”. There is no identifier, no IP address, no time of day and no typed text: no person or visit can be traced.
Live presence
The same script says “I’m here” when a page opens, then every minute while the tab is visible. Ecomify then keeps:
- a random number drawn by the tab, which disappears when the tab closes. It is used only to avoid counting the same visit twice;
- the page viewed, and the step reached: product, cart or checkout;
- the city, region and country, as Cloudflare infers them from the connection, with a point rounded to about 10 km.
Never the IP address, never the postal code. Each row is deleted after 30 minutes.
The store remains responsible
Ecomify takes these measurements on the store’s behalf. The store must inform its visitors of them in its own privacy policy.
Claude
Claude is the artificial intelligence made by Anthropic. It advises; people on the team decide.
For now, Claude is only available to the team, not to merchants who install the Shopify app.
Questions asked in the app
When you ask Claude a question in Ecomify, it goes through your team’s Mac. That Mac uses Claude Code, Anthropic’s software, with the Claude subscription of the person who owns it. It receives:
- your question and the latest turns of the conversation, 6 at most;
- useful context: the brand’s figures as totals, its ads, its rules, the team’s knowledge, its store sheet, its sample customer portraits and passages from the course.
While it answers, Claude may read other brand data in Ecomify, read-only: it cannot change anything, and it does not read customer service records. This context contains no customer’s name or email. On the Mac, Claude does not search the web. Do not write personal information in your questions.
Until the Mac picks it up, your question is kept on Ecomify’s server. The question and its answer are deleted from it as soon as the answer is shown, and at the latest 1 hour after the question. The server then keeps only the record: the date, the duration and whether Claude answered. Conversations stay in your browser.
These exchanges go through Anthropic, under the Claude account of the person who owns the Mac, under that account’s terms.
The API key fallback
If no Mac is on, Ecomify can send the question straight to Anthropic with its API key. This fallback is off by default: only the account owner can turn it on. We then send your question, the earlier turns of the conversation (8 at most) and the same context, and Claude may run a few web searches. Ecomify’s server only keeps the number of questions in the month and their cost. Under its commercial terms, Anthropic does not use this data to train its models and keeps it only for a limited time.
Connected Claude agents
Each person on the team can connect their own Claude (the Claude app or Claude Code) to Ecomify with a personal key. The agent reads and writes what that key allows, in that person’s brands, including customer service records. These exchanges go through Anthropic, under that person’s Claude account.
Ecomify does not keep the key itself, only its fingerprint, its name and when it was last used. A key can be revoked in one click.
What we never do
- Sell, rent or trade personal information.
- Put a tracker, an advertising pixel or an analytics tool on this site or in the app.
- Use your data for targeted advertising, or give it to a data broker.
- Make a decision about a person through fully automated processing. Claude and the app’s rules make suggestions about ads, not about people.
- Use your Google data for anything other than letting you sign in.
Providers and Québec
To run Ecomify, information goes through these companies. Each one handles it under its own terms.
- Cloudflare (United States) hosts this site and the app, the database and the files. Its policy.
- Google (United States) handles sign-in. The app also loads its fonts from Google Fonts: your browser then contacts Google, which sees your IP address. Its policy.
- Anthropic (United States) runs Claude for the team, on the team’s Mac (Claude Code) or, as a fallback, through its API key. Its policy.
- Meta (United States) provides the ads and their statistics, for brands that connect it. The app shows ad thumbnails from Meta’s servers. Its policy.
- Shopify (Canada) provides the store data and installs the app. Its policy.
- Juicy, by Easyapps, only for brands that connect it.
These companies may store or process information outside Québec, mainly in the United States, where privacy laws are different.
Security
- Everything goes over HTTPS, and both this site and the app enforce HTTPS (HSTS).
- Meta, Shopify and Juicy tokens and secrets are encrypted in the database (AES-GCM).
- Without a valid session, the app shows nothing, not even its code.
- Sessions are signed and can be closed remotely. Sign-in attempts are limited.
- Agent keys are kept only as fingerprints.
- Shopify and Juicy are accessed read-only.
- The Shopify app’s tokens expire after 1 hour and are refreshed; they are deleted at uninstall.
- Requests from Shopify (install, webhooks) are checked by their signature; those not signed by Shopify are rejected.
- Each merchant only has access to their own store.
- Every read of a store’s sales, orders or customer service data is recorded in an access log: who read it (a team member’s first name, or the store), when, and what kind of data. Never any customer data.
If a confidentiality incident presents a risk of serious injury, we notify the Commission d’accès à l’information and the people affected, as the law requires. We keep a register of these incidents.
How long we keep data
| What we keep | For how long |
|---|---|
| IP address, for the attempt limit | 1 hour |
| A visitor’s live presence | 30 minutes |
| Shopify responses (reports, orders, disputes; the globe in En direct) | 10 minutes at most (2 minutes for the globe), then replaced at the next read; deleted at uninstall |
| Orders sent by Shopify for live sales (amounts, times, statuses, campaign; nothing about the customer) | 7 days; at the latest 48 hours after uninstall |
| Shopify app tokens (access: 1 hour; refresh: 90 days) | Until uninstall, then deleted right away |
| Store installation (domain, name, currency, time zone, date, permissions) | Until 48 hours after uninstall |
| Record of Shopify compliance notices (date, store, Shopify customer ID, what was done) | As long as needed to prove we handled the request |
| Failed sign-in attempts | 30 days |
| Access log for store data (who, when, what kind of read) | 12 months; a store’s entries no later than 48 hours after uninstalling |
| Session | 14 days, or 30 if you choose |
| Account remembered by your device (first name and email) | 400 days, or until “Pas toi ?” |
| Click map counters | 400 days |
| Successful sign-ins, passkeys, security choices | As long as your access exists; deleted within 30 days after your access ends |
| Meta, Shopify and Juicy tokens | Until the account is disconnected or the brand removed |
| Ads, statistics, customer service records, the team’s work | As long as the brand is in Ecomify, or until a deletion request |
| Conversations with Claude | In your browser, until you erase them |
| A question asked to Claude and its answer, on the server | Until the answer is shown, 1 hour at most |
| Record of questions to Claude (date, duration, answered or not) | As long as your access exists |
| Database backups | 30 days at most |
Cookies and your browser
This site uses no cookies. The app only uses cookies needed to sign in, none for advertising or analytics:
| Cookie | What it does | Duration |
|---|---|---|
__Host-ecomify_session | Keeps your session open | 14 or 30 days |
__Host-ecomify_compte | Remembers your first name and email to suggest the right account | 400 days |
__Host-ecomify_google, __Host-ecomify_meta, __Host-ecomify_juicy | Protect the connection to Google, Meta or Juicy while it happens | 10 to 15 minutes |
__Host-ecomify_shopify | Holds the store during an install started from Shopify | 10 minutes |
The app also keeps your conversations with Claude, the chosen brand and your display preferences in your browser. They stay on your device; only the current conversation is sent with your question (see Claude).
On the stores, live presence keeps its random number in the tab, erased when the tab closes. The team’s browsers are marked “internal” there so they are not counted.
Your rights
Free of charge, you can:
- know what information we hold about you and get a copy, in a structured, commonly used technological format if you ask;
- have anything inaccurate, incomplete or ambiguous corrected;
- have your information deleted, or have its dissemination stopped;
- withdraw your consent, for example by disconnecting an account;
- file a complaint with the Commission d’accès à l’information du Québec.
Write to [email protected]. We answer within 30 days. We may ask you to confirm your identity before acting. To delete your data, the Data deletion page explains the steps.
If you are a store customer
If you bought from or browsed a store that uses Ecomify, the store decides what is done with your information; Ecomify processes it on the store’s behalf. Write to the store first: if it uses the Shopify app, Shopify forwards your access or deletion request to us, and we handle it within 30 days (see The Shopify app). You can also write to us at [email protected]: we will delete the customer service records that name you. For live sales, Ecomify keeps only your order’s amounts, time and status, for 7 days, without your name or address.
Minors
Ecomify is a work tool. It is not meant for people under 14 and does not knowingly collect their information.
Changes
If we change this policy, the date at the top of the page changes too. If the change is significant, we announce it in Ecomify before it applies.
This is a translation of the French policy. If the two versions differ, the French version prevails.
Contact us
William Blais, person in charge of the protection of personal information
Ecomify
[email protected]
Effective November 20, 2026.