E-Commerce · head to head
BackToMe vs Immuta

BackToMe
E-Commerce
Right-of-withdrawal handling for European e-commerce
- From
- €25/month
- Free plan
- No

Immuta
Databases
Attribute-based access control and masking applied inside Snowflake, Databricks and BigQuery
- From
- On request
- Free plan
- No
The short version
- BackToMe starts at €25/mo; Immuta prices on request.
- Only BackToMe lists floating withdrawal button; only Immuta lists attribute-based policy.
- Where BackToMe falls short: the scope is European consumer law. A merchant selling outside the EU has no use for it.
- Prices and features on this page were last checked on 17 September 2026.
Where they differ
Only the attributes on which BackToMe and Immuta actually diverge.
Identical on both: free tier (No).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in BackToMe
- Floating withdrawal button
- Automatic acknowledgement
- Sealed archiving
- Withdrawal dashboard
- One-click proof export
- Multi-store from one account
Only in Immuta
- Attribute-based policy
- Native enforcement
- Dynamic masking
- Row-level filtering
- Purpose-based access
- Sensitive data tagging
- Audit logging
- Multi-platform
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot Immuta
- Producing dated proof of a cancellation in a customer disputenot Immuta
- Handling withdrawal requests across several EU languagesnot Immuta
- Running one withdrawal process across multiple storefrontsnot Immuta
- Passing a consumer-protection audit with exportable recordsnot Immuta
Immuta
- A bank whose Snowflake estate has grown to tens of thousands of roles that no one can review before an auditnot BackToMe
- A healthcare analytics team that must let researchers query patient data with identifiers masked unless a specific purpose is recordednot BackToMe
- A multinational applying different residency and access rules per jurisdiction to the same tables without duplicating datasetsnot BackToMe
- An organisation running both Snowflake and Databricks that wants one policy set rather than two divergent implementationsnot BackToMe
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
BackToMe
- The scope is European consumer law. A merchant selling outside the EU has no use for it
- The site and dashboard are French. The customer-facing button covers 24 EU languages, but the merchant side is not multilingual
- One price, one feature set. There is no tier for a shop that wants only the archive or only the button
- It runs as an injected script on the storefront, so a shop with a strict content security policy has an extra step before the button will render
- A young French vendor with no independent review coverage, so there is nothing outside the vendor's own material to corroborate the archive's evidentiary weight
Immuta
- Contracts commonly start around one hundred to two hundred thousand US dollars a year for mid-market deployments and exceed five hundred thousand at enterprise scale, which excludes most data teams without a regulatory mandate
- Policy is only as good as the data classification underneath it, so an organisation with poorly tagged columns will spend months on classification before Immuta enforces anything useful
- Native enforcement means capability varies by platform, and a feature available on Snowflake may be absent or behave differently on BigQuery, which undermines the promise of one policy set everywhere
- Adding an access governance layer creates a new dependency in the path to data: a misconfigured policy silently returns fewer rows rather than erroring, and analysts can act on incomplete results without noticing
- It governs cloud data platforms, so personal data in operational databases, files and SaaS applications sits outside its scope and needs separate controls, meaning Immuta is rarely the whole answer
Pricing, plan by plan
BackToMe
€25/month- Monthly€25/mo
- Per active store, excluding VAT
- Unlimited withdrawal requests
- 24 EU languages
- Annual€250/yr
- Per store, excluding VAT
- Two months free against the monthly rate
- Everything in the monthly plan
Immuta
On request- Immuta PlatformOn request
- Attribute-based policy authoring
- Native enforcement in supported data platforms
- Dynamic masking and row-level security
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose Immuta if
- You need attribute-based policy.
- You work on Web, API.
- You also want native enforcement.
Questions people ask
- Is BackToMe or Immuta better?
- Neither clearly leads. BackToMe starts at €25/month and Immuta at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or Immuta?
- BackToMe starts at €25/month and Immuta at On request.
- Does BackToMe or Immuta run on more platforms?
- BackToMe runs on Web. Immuta runs on Web, API.
- What is BackToMe best used for?
- BackToMe is most often used for meeting eu directive 2023/2673 withdrawal obligations, producing dated proof of a cancellation in a customer dispute, handling withdrawal requests across several eu languages, running one withdrawal process across multiple storefronts. Of those, meeting eu directive 2023/2673 withdrawal obligations and producing dated proof of a cancellation in a customer dispute are not what Immuta is typically brought in for.
- What can BackToMe do that Immuta cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. Immuta covers Attribute-based policy, Native enforcement, Dynamic masking, Row-level filtering.
Answered from the vendors’ own pages
BackToMe: What does BackToMe cost?
25 euros excluding VAT per month per active store, or 250 euros excluding VAT per year, which works out at two months free. The price does not change with the number of withdrawal requests.
SourceImmuta: Does Immuta sit in the query path?
No. It compiles policies into the data platform's own native controls, so queries run at normal speed through your existing tools.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceImmuta: What does it cost?
Not published. Market data suggests roughly 100,000 to 200,000 US dollars a year for mid-market deployments and considerably more at enterprise scale.
BackToMe: Is there a free trial?
Seven days. A card is required to start it but nothing is charged upfront, and cancelling before day seven costs nothing. There is also a 30-day money-back guarantee.
SourceImmuta: Is Immuta still independent?
Yes. It remains independently owned, unlike several competitors in data access governance that have been acquired.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceImmuta: Does it work across more than one warehouse?
Yes, one policy set can target Snowflake, Databricks, BigQuery and Starburst, though enforcement capability varies by platform.
BackToMe: What happens to the archive if I cancel?
Cancellation is available at any time with no commitment, premium access runs to the end of the paid period, and the account stays open with archived withdrawals and proofs accessible indefinitely. Reactivation is self-service.
SourceBackToMe: Which e-commerce platforms does it support?
Shopify, WordPress, WooCommerce, PrestaShop, Wix, Webflow, WiziShop and Squarespace, plus custom builds through a single line of script. The vendor puts installation at five minutes on any platform.
SourceRelated pages
Other head to heads
- BackToMe vs Temu
- BackToMe vs Amazon Shopping
- BackToMe vs Mailchimp
- BackToMe vs Shein
- BackToMe vs CJ Dropshipping
- BackToMe vs Memberful
- BackToMe vs Wish
- BackToMe vs Zendrop
- BackToMe vs Heartland Retail
- BackToMe vs Vinted
- BackToMe vs Mollie
- BackToMe vs TikTok Shop
- BackToMe vs SamCart
- BackToMe vs Sellfy
- BackToMe vs Shopware
- BackToMe vs Spree Commerce
- BackToMe vs Swell Commerce
- BackToMe vs Toast
- BackToMe vs Privacera
- BackToMe vs BigQuery
- BackToMe vs Teradata
- BackToMe vs Dgraph
- BackToMe vs Knack
- BackToMe vs Elasticsearch
- BackToMe vs Apache Druid
- BackToMe vs DuckDB
- BackToMe vs DynamoDB
- BackToMe vs Oracle Database
- BackToMe vs Microsoft SQL Server
- BackToMe vs QuestDB
- BackToMe vs Vitess
- BackToMe vs Aiven
- BackToMe vs DataStax
- BackToMe vs Cassandra
- BackToMe vs Amazon Redshift
- BackToMe vs CosmosDB
- Immuta vs Temu
- Immuta vs Amazon Shopping
- Immuta vs Mailchimp
- Immuta vs Shein
- Immuta vs CJ Dropshipping
- Immuta vs Memberful
- Immuta vs Wish
- Immuta vs Zendrop
- Immuta vs Heartland Retail
- Immuta vs Vinted
- Immuta vs Mollie
- Immuta vs TikTok Shop
- Immuta vs SamCart
- Immuta vs Sellfy
- Immuta vs Shopware
- Immuta vs Spree Commerce
- Immuta vs Swell Commerce
- Immuta vs Toast
- Immuta vs Privacera
- Immuta vs BigQuery
- Immuta vs Teradata
- Immuta vs Dgraph
- Immuta vs Knack
- Immuta vs Elasticsearch
- Immuta vs Apache Druid
- Immuta vs DuckDB
- Immuta vs DynamoDB
- Immuta vs Oracle Database
- Immuta vs Microsoft SQL Server
- Immuta vs QuestDB
- Immuta vs Vitess
- Immuta vs Aiven
- Immuta vs DataStax
- Immuta vs Cassandra
- Immuta vs Amazon Redshift
- Immuta vs CosmosDB
