Legal
Terms & Conditions
These terms govern your use of Loomaru's revenue recovery service. They include our Data Processing Agreement and CCPA Service Provider Addendum — no separate documents needed.
Effective date: April 21, 2026 · Last updated: April 22, 2026
1Definitions
"Loomaru," "we," "us" — Vadim Sharapov, sole proprietor, operating as Loomaru, with registered address at Zikova 1023, Prague, Czech Republic.
"Merchant," "you" — the business entity or individual that subscribes to the Service.
"Service" — the managed revenue-recovery service Loomaru operates on the Merchant's behalf to reconcile measurement signal between the Merchant's online store and the advertising and analytics destinations the Merchant has authorized.
"Store" — the Merchant's e-commerce website or platform where commercial transactions occur.
"Ad Destinations" — the third-party advertising and measurement destinations the Merchant has authorized Loomaru to send conversion data to, as specified in each Merchant's onboarding configuration.
"Customer Data" — personal data contained in Store transaction records that the Service processes on the Merchant's behalf, which may include: contact identifiers (such as email or phone), name, address fields, network identifiers, referring click identifiers, and order details (value, currency, products). The exact fields processed are determined per-Merchant by the Ad Destinations the Merchant has authorized.
"Pseudonymized Data" — Customer Data that has been normalized and transformed using industry-standard one-way cryptographic hashing consistent with the receiving Ad Destination's published specification. Pseudonymized Data is still personal data under GDPR.
2Service Description
Loomaru operates a managed revenue-recovery service that reconciles order and conversion data between the Merchant's Store and the Ad Destinations the Merchant has authorized. The specific destinations, event types, and integration profile are determined per-Merchant and documented in each Merchant's onboarding brief.
The Service is destination-agnostic. Loomaru may add, remove, or modify supported Ad Destinations over time as those destinations change their interfaces or as new destinations become commercially viable.
No Customer Data is persistently stored. Customer Data is processed transiently during reconciliation (typically under a few seconds) and is not written to any durable store, database, queue, or log.
No PII is logged. Operational logs record only non-personal telemetry: timestamps, event types, Merchant identifiers, order identifiers, upstream response codes, and processing duration. Identity fields, network identifiers, and payload bodies are never logged.
2.1Tier Revenue Bands and Ceiling Fallback
The Service is sold in revenue-banded tiers. Each tier corresponds to a band of the Merchant's monthly store revenue, as published on the pricing page. The Merchant selects a tier appropriate to the Merchant's current monthly revenue at onboarding.
Automatic ceiling fallback.When the Merchant's monthly store revenue in a given calendar month reaches ninety percent (90%) of the upper bound of the Merchant's selected tier, the Service automatically reverts — for the remainder of that calendar month — to whatever measurement configuration the Merchant had in place prior to Loomaru's deployment (the "pre-install baseline"). Reconciliation and forwarding by Loomaru pauses; the Merchant is not billed an overage, is not upgraded without consent, and is not pushed past the tier purchased. At the end of the calendar month Loomaru will contact the Merchant to discuss moving to a higher tier before the next billing cycle.
The purpose of this fallback is to prevent mid-month revenue events (such as subscription renewals, post-purchase upsells, or promotional spikes) from silently carrying the Merchant past the capacity the Merchant has paid for. Service for the balance of the month operates at the pre-install baseline; no additional fee is charged.
2.2Small-Business Program
Loomaru offers the full recovery layer free of charge, on a permanent basis, to stores whose monthly revenue is below fifteen thousand United States dollars (USD $15,000 / month) at the time of onboarding (the "Small-Business Program"). Eligibility is determined by the Merchant's self-reported monthly revenue at onboarding, subject to reasonable verification.
Merchants in the Small-Business Program receive the same deployment, monitoring, and the Service obligations set out in Section 4 (Data Processing Terms), Section 5 (CCPA), and Section 7 (Security) as paying Merchants. Section 9 (Service Level), Section 8.5 (Refunds — which does not apply because no Fee is paid), and Section 9.6 (Support Response Targets) apply at the Starter-tier response levels.
Ceiling fallback for the Small-Business Program.The Small-Business Program is subject to the same ceiling fallback described in Section 2.1, measured against the USD $15,000 / month threshold. When the Merchant's monthly store revenue in a given calendar month reaches ninety percent (90%) of that threshold (i.e., USD $13,500 / month), the Service automatically reverts to the Merchant's pre-install baseline for the remainder of that calendar month. Before the next calendar month, Loomaru will contact the Merchant to offer a transition to a paid tier (Starter or higher). The Merchant is under no obligation to accept; if the Merchant declines or does not respond, the Small-Business Program ends at the close of the calendar month and no charge is raised.
The Small-Business Program may be withdrawn for any individual Merchant who is found to have misrepresented revenue eligibility, or globally on thirty (30) days' public notice on the pricing page; the fallback behavior above applies in all cases while the Program is active.
2.3Scale-Tier Deliverables
The Scale tier includes, in addition to the recovery layer common to all tiers:
- Priority email support with the response target set out in Section 9.6; and
- Video calls on demand for operational and performance matters, scheduled at mutually convenient times through Loomaru's scheduling provider.
The Scale tier does not include periodic performance reviews, dedicated account management, or any other ongoing deliverable not expressly listed above or on the pricing page.
2.4Wix-Store Tier
The Wix-Store Tier is a managed-recovery service offered by Loomaru to e-commerce stores hosted on the Wix platform. Under this tier, the Merchant authorizes Loomaru to reconcile order data from the Merchant's Wix-hosted Store and forward conversion signal to a single Ad Destination — Meta (Facebook and Instagram , as a single advertising destination of the Merchant's Meta Business account). No other Ad Destination is included under this tier; if the Merchant wishes to add a further Ad Destination (such asGoogle Ads,TikTok Ads, orPinterest Ads), the Merchant must transition to the Starter, Growth, or Scale tier as published on the pricing page.
Eligibility.Any Merchant operating a Wix-hosted Store may subscribe to the Wix-Store Tier, subject to the same revenue-eligibility threshold described in §2.2 (the “Small-Business Program threshold”): the Wix-Store Tier is intended for Wix-hosted Stores whose monthly Store revenue is below the threshold described in §2.2 at the time of onboarding. The automatic ceiling fallback described in §2.1, measured against that same threshold, applies in identical terms to the Wix-Store Tier. A Merchant whose monthly Store revenue exceeds the threshold on a sustained basis will be invited to transition to the Starter, Growth, or Scale tier; the Merchant is under no obligation to accept and may continue at the Wix-Store Tier subject to the ceiling fallback.
Fees. The Fee for the Wix-Store Tier is published on the pricing page and is billed annually in advance, in United States dollars, exclusive of applicable sales tax or VAT, which is added at checkout based on the billing address the Merchant provides. The annual-billing mechanics, including auto-renewal on the anniversary of the first paid charge, are governed by §8.6.
Refunds. The unconditional 30-day money-back commitment in §8.5 applies to the Wix-Store Tier in identical terms: the Merchant may request a full refund of the first paid annual Fee at any time within thirty (30) days of that first paid charge, for any reason, with the refund processed within five (5) business days of the request to vadim@loomaru.com. After the close of the 30-day window, no pro-rata refund is owed for the unused portion of the paid year (see §8.6 and §12.2 as adapted by §8.6).
Service Level. The Wix-Store Tier inherits the uptime commitment in §9.1, the measurement methodology in §9.2, the exclusions in §9.3, and the service-credit mechanism in §9.4. The Merchant-support first-response target for the Wix-Store Tier is the Starter-tier target described in §9.6(a): twenty-four (24) hours on business days (Monday–Friday, excluding Czech public holidays).
Out-of-scope deliverables. The Wix-Store Tier does not include: (a) the Scale-tier deliverables described in §2.3; (b) any Ad Destination other than Meta ; (c) any agency-tier features, multi-store consolidation, or white-label arrangements; or (d) periodic performance reviews, dedicated account management, or any other ongoing deliverable not expressly listed in these Terms or on the pricing page.
Statutory consumer rights.For Merchants who qualify as “consumers” under Directive 2011/83/EU (typically sole traders contracting outside the scope of their business), nothing in this Section limits the 14-day right of withdrawal under Article 9 of that Directive. The 30-day commercial money-back commitment in §8.5 is offered in addition to, and does not replace, the statutory right. Merchants who wish to exercise the statutory withdrawal right may do so by emailing vadim@loomaru.com within 14 calendar days of the conclusion of the contract.
Trademark disclaimer. “Wix” is a trademark of Wix.com Ltd. Loomaruis an independent service provider and is not affiliated with, endorsed by, sponsored by, or otherwise officially connected to Wix.com Ltd. References to Wix in these Terms and on the Loomaru website identify the platform on which the Merchant's Store is hosted; they do not assert any commercial relationship between Loomaru and Wix.com Ltd.
3Merchant Obligations
By activating the Service, you represent and warrant that:
3.1Legal Basis for Data Collection
You have obtained all necessary consents, authorizations, and legal bases required under applicable law — including GDPR, ePrivacy Directive, CCPA/CPRA, and any other applicable privacy legislation — for the collection and processing of Customer Data before it is transmitted to Loomaru.
For customers located in the EU, EEA, UK, or Switzerland: you have implemented a consent management mechanism that obtains prior, informed, freely-given, specific, and unambiguous opt-in consent for marketing tracking and ad attribution before the Service processes their data.
For customers located in US states with comprehensive privacy laws (including California, Colorado, Connecticut, Texas, Virginia, and others): you provide a "Do Not Sell or Share My Personal Information" link and honor Global Privacy Control (GPC) browser signals where required by law.
3.2Privacy Notice
Your privacy policy identifies Loomaru as a service provider / processor acting on your behalf, or provides a link to your sub-processor list that includes Loomaru.
3.3Ad Destination Relationship
You maintain direct, valid advertising relationships with each Ad Destination you authorize the Service to send events to. Any access tokens, identifiers, or credentials provided to Loomaru are yours and are authorized for the stated purpose. Each Ad Destination is your separate data controller — not Loomaru's sub-processor.
3.4Pre-Activation Compliance Checklist
Before the Service is activated for production traffic, you must confirm:
- Completion of the reconciliation verification procedure (matched conversion identifiers on the receiving Ad Destination, so no double-counting occurs).
- Deactivation of any duplicate Store-native integrations that would cause double-counted conversions on any Ad Destination you authorize.
- Review and acceptance of these Terms, including the Data Processing Terms and CCPA Addendum.
- Confirmation that your privacy policy and consent mechanisms satisfy applicable law for all regions where you operate.
3.5Ongoing Obligations
You are responsible for: handling data subject access requests (DSARs), deletion requests, and objection requests from your customers; maintaining a compliant cookie consent mechanism; keeping your privacy policy current; and notifying Loomaru if you become aware of any unauthorized access to credentials provided to us.
4Data Processing Terms
This section constitutes the Data Processing Agreement between you (Controller) and Loomaru (Processor) as required by GDPR Article 28. These terms are binding upon acceptance of these Terms & Conditions.
4.1Roles
You are the Controller. You determine the purposes and means of processing Customer Data. You instruct Loomaru to process Customer Data solely for the purpose of reconciling and forwarding conversion signal to the advertising destinations you have designated, on your behalf.
Loomaru is the Processor. We process Customer Data only on your documented instructions as described in Section 2. We do not determine purposes independently, do not combine Customer Data with data from other sources, and do not use Customer Data for any purpose beyond performing the Service.
4.2Scope of Processing
| Subject matter | Reconciliation and forwarding of the Merchant's order data to the Merchant's designated advertising destinations as conversion signal. Source storefront and destinations are configured per Merchant during onboarding and disclosed in the Merchant's Configuration Record. |
| Duration | For the duration of the service agreement; processing per event is transient (typically under 3 seconds). |
| Nature & purpose | Normalization, pseudonymization via industry-standard one-way hashing, and transmission of identity and order fields to the Merchant's designated Ad Destinations for attribution. |
| Data categories | Pseudonymized (before transmission): email, phone, first name, last name, city, state, postal code, country. Raw (where the destination's interface requires raw form): IP address, user agent, click identifiers. Order fields (non-personal): value, currency, product identifiers, quantities. The exact subset is determined by the destination's published interface and the Merchant's configured profile. |
| Data subjects | Merchant's end-customers who complete purchases on the Merchant's e-commerce storefront. |
| Storage | None. Customer Data exists only in transient processing memory. No database, no queue, no persistent store retains Customer Data. |
4.3Processor Obligations
Loomaru shall:
- Process Customer Data only on your documented instructions as described in these Terms. If EU/EEA law requires processing beyond your instructions, we will inform you before such processing unless prohibited by law.
- Ensure that persons authorized to process Customer Data have committed to confidentiality obligations.
- Implement appropriate technical and organizational security measures as described in Section 7.
- Not engage additional sub-processors without prior notice to you. The current categories of sub-processors are described in Section 6. We will notify you of any intended material change, giving you the opportunity to object, in accordance with Section 6.
- Assist you, taking into account the nature of processing, in responding to data subject requests (access, rectification, erasure, restriction, portability, objection) insofar as this is possible given our transient-processing architecture.
- Assist you in ensuring compliance with your obligations under GDPR Articles 32–36 (security, breach notification, DPIAs, prior consultation), taking into account the nature of processing and information available to us.
- At the end of the service agreement, delete all Customer Data — which, given our transient-processing architecture, is automatic for event data. Configuration records are deleted on termination. We will confirm deletion upon written request.
- Make available to you all information necessary to demonstrate compliance with Article 28 obligations, and allow for and contribute to audits and inspections conducted by you or an auditor mandated by you, subject to reasonable confidentiality safeguards. The practical scope of an audit includes: review of these Terms, review of non-PII operational logs, and review of our sub-processors' published security documentation under confidentiality.
- Notify you without undue delay (and in any event within 72 hours) after becoming aware of a personal data breach affecting Customer Data.
4.4International Transfers
Customer Data may be processed at the nearest available compute location of our infrastructure providers, some of which may be outside the EU/EEA. Every such transfer is covered by one of the following safeguards, each bound into our sub-processor agreements:
- European Commission Standard Contractual Clauses (Module Two: controller-to-processor; Module Three: processor-to-processor), the UK Addendum, and the Swiss Addendum, where applicable.
- Adequacy decisions and approved frameworks (including the EU-US Data Privacy Framework and UK Extension, where our counter-party is self-certified).
- Onward transfers to Ad Destinations— any onward transfer from Loomaru to the advertising destinations you designate is covered by each destination's own cross-border transfer mechanism and by that destination's terms of service with you. These onward transfers occur under your direct controller relationship with each destination, not under Loomaru's processing.
Loomaru is established in the European Union (Czech Republic) and is directly subject to GDPR. No separate EU representative under Article 27 is required. The current list of named sub-processors is available to Controllers on written request under a confidentiality undertaking; see Section 6.
4.5Data Subject Rights Assistance
Given our transient-processing architecture, Customer Data cannot be individually retrieved, modified, or deleted after processing because it is not retained. If you receive a data subject request that requires our assistance, contact us at vadim@loomaru.com and we will:
- Confirm that no Customer Data is stored by the Service.
- Provide operational-log excerpts (containing no PII) if required for audit purposes.
- Assist you in contacting your designated advertising destination(s) regarding data already transmitted to them, if applicable.
5US Privacy Laws — CCPA Service Provider Addendum
For purposes of the California Consumer Privacy Act (CCPA/CPRA) and similar US state privacy laws (including CPA, CTDPA, VCDPA, TDPSA, and others), Loomaru acts as a "Service Provider" (as defined in Cal. Civ. Code §1798.140(ag)) with respect to Customer Data received from you.
Loomaru certifies that it:
- Shall not sell or share Customer Data. Loomaru does not sell, rent, release, disclose, disseminate, make available, transfer, or otherwise communicate Customer Data to a third party for monetary or other valuable consideration, or for cross-context behavioral advertising.
- Shall not process outside the business purpose. Loomaru processes Customer Data solely for the purpose of performing the Service as described in Section 2 and as instructed by you. Loomaru does not retain, use, or disclose Customer Data for any commercial purpose other than providing the Service.
- Shall not combine with other data. Loomaru does not combine Customer Data received from you with personal information received from any other source or collected from its own interactions with consumers.
- Shall assist with consumer rights. Loomaru will assist you in responding to verifiable consumer requests for access, deletion, correction, or opt-out, to the extent applicable given our transient processing architecture.
- Shall honor opt-out signals. Where a consumer has exercised a right to opt out of the sale or sharing of personal information — whether through your "Do Not Sell or Share" link, a Global Privacy Control browser signal, or an equivalent mechanism you support — Loomaru will apply destination-supported limited-data-use flags to the forwarded signal, consistent with the opt-out preference you communicate to us and with each Ad Destination's published specification.
- Grants audit rights. You may, upon reasonable notice, take reasonable and appropriate steps to help ensure that Loomaru uses Customer Data in a manner consistent with your obligations under applicable law.
Your obligation:For consumers who opt out of the sale or sharing of personal information (via "Do Not Sell or Share" link or Global Privacy Control signal), you must either (a) configure the opt-out preference in your Loomaru store settings, or (b) ensure that your consent mechanism prevents the Service from being triggered for opted-out consumers.
6Sub-Processors
Loomaru engages sub-processors from the following categories to provide the Service. By accepting these Terms, you provide general authorization for sub-processors within these categories. We will notify you of any intended material change, giving you a reasonable opportunity to object.
| Category | Purpose | Region | Safeguard |
|---|---|---|---|
| Managed compute & configuration infrastructure | Transient event processing, configuration storage, and non-PII operational telemetry. | Global with EU processing available | Written DPA with EU SCCs and approved framework safeguards. |
| Managed application hosting | Hosting of the loomaru.com website and the merchant-facing dashboard. | EU & US regions | Written DPA with EU SCCs and approved framework safeguards. |
| Managed data & identity platform | Merchant-account database and authentication for the dashboard; consent audit log. | EU region | Written DPA with EU SCCs. |
| Embedded scheduling provider | Calendar availability and meeting booking for prospective and active merchants. | EU & US regions | Written DPA with EU SCCs and approved framework safeguards. |
Named sub-processor list.The current list of named sub-processors, their addresses, and their individual DPA references are available to Controllers on written request under a confidentiality undertaking. Controllers receive not less than thirty (30) days' advance written notice of any intended material change to that list, including any addition, and may object in writing during the notice period; an unresolved objection entitles the Controller to terminate the affected portion of the Service without penalty.
Advertising destinations are not Loomaru sub-processors. Each Ad Destination you designate is a separate data controller with which you maintain a direct advertising relationship. Loomaru forwards data to those destinations on your instruction, under your existing terms with each destination. Loomaru does not have an independent data relationship with any advertising destination regarding your Customer Data.
7Security Measures
Loomaru implements technical and organizational measures appropriate to the risk, as required by GDPR Article 32, to protect Customer Data during processing:
- Authenticated intake.Inbound event submissions from the Merchant's Store are verified using industry-standard signed-integrity verification before any processing occurs. Submissions failing verification are rejected at intake.
- Encryption in transit.All communication between the Merchant's Store, Loomaru, and the Merchant's designated Ad Destinations uses TLS 1.2 or higher.
- Encryption at rest. Merchant configuration (including destination credentials and integrity secrets) is stored in managed encrypted-at-rest key storage provided by our infrastructure sub-processor, isolated per Merchant.
- Data minimization.Only the fields required by the Merchant's designated Ad Destinations are extracted. Identity fields are pseudonymized via industry-standard one-way hashing before transmission. Null or empty fields are omitted entirely — never sent as empty hashes.
- No persistent storage of Customer Data. Customer Data exists only in transient processing memory during the processing window. No database, queue, file, or cache retains Customer Data.
- Log sanitization. Operational logs are filtered through a strict allowlist. PII, network identifiers, user agents, payload bodies, and credential material are never logged. In non-production environments, attempts to log disallowed fields fail fast.
- Access control.Merchant credentials are isolated per Merchant under the principle of least privilege. No Merchant can access another Merchant's configuration or data.
- Reconciliation gate.Conversion signal is not forwarded until reconciliation has been verified and explicitly enabled in the Merchant's Configuration Record, preventing double-counted conversions.
8Fees & Payment
8.1Billing and Auto-Renewal
Service fees are as published on the pricing page at the time of your subscription, or as agreed in writing. Fees are billed monthly in advance, in United States dollars unless otherwise agreed. All fees are exclusive of applicable sales tax or VAT, which is added at checkout based on the billing address the Merchant provides.
Automatic renewal.The subscription renews automatically each calendar month on the anniversary of the first paid charge, at the then-current Fee for the Merchant's tier (subject to the price-stability commitment in §8.2), until the Merchant cancels in accordance with Section 12. There is no fixed contract term or minimum commitment; the Merchant may cancel at any time and the cancellation takes effect at the end of the then-current paid month.
No free trial.The Service does not include a free trial period. The Merchant pays the first month's Fee in advance at the start of service. The 30-day money-back commitment in §8.5 is the commercial safety net that runs from the first paid charge.
8.2Price Stability for Active Subscriptions
Fees for any active Subscription remain fixed for the lifetime of that Subscription. Loomaru will not increase the Fee payable by an existing Subscription while it remains active and in good standing. This commitment is published and tracked on the pricing page.
8.3Pricing Adjustments for New Subscriptions
Loomaru may adjust pricing for new Subscriptions at any time with 30 days' public notice on the pricing page. Adjusted pricing applies only to Subscriptions initiated on or after the adjustment effective date. Adjustments do not affect Fees for existing Subscriptions, which are governed by §8.2.
8.4Cancellation and Re-subscription
If the Merchant cancels and later re-subscribes, the new Subscription is treated as a new Subscription and the then-current pricing applies. The Price Stability Commitment in §8.2 does not carry over across cancellations.
8.5Refunds and Measurement Methodology
The Merchant may request a full refund of the first paid Fee at any time within 30 days of that first paid charge, for any reason, including (but not limited to) dissatisfaction with measured performance (for example, a measured lift inside the published range that the Merchant nonetheless considers insufficient). The refund is unconditional, carries no outcome threshold, and is processed within 5 business days of the request. Request a refund by emailing vadim@loomaru.com. No call is required, no form to complete.
Measurement methodology.Whether the Service has produced a meaningful revenue lift is measured by the Merchant, in the Merchant's own e-commerce admin sales report, comparing the post-install period to the Merchant's pre-install baseline. Loomaru does not operate a Merchant-facing analytics dashboard and does not report lift numbers. The decision whether the observed lift justifies continuing the subscription rests solely with the Merchant; the 30-day money-back window in this Section is the contractual mechanism through which the Merchant acts on that decision.
8.6Annual Billing — Wix-Store Tier
The Wix-Store Tier is the only Loomaru tier billed annually. The first Fee is charged in advance at the start of service. The subscription renews automatically each calendar year on the anniversary of the first paid charge, at the then-current Wix-Store Tier Fee (subject to the price-stability commitment in §8.2), until the Merchant cancels in accordance with Section 12. There is no fixed contract term beyond the paid year and no minimum commitment beyond the current paid year; the Merchant may cancel at any time and the cancellation takes effect at the end of the then-current paid year (the year for which the Fee has already been paid in advance under this Section). No pro-rata refund is owed for the unused portion of the then-current paid year after the 30-day money-back window in §8.5 has closed; the 30-day window in §8.5 is the contractual mechanism for the Merchant to obtain a refund of the annual Fee. For the avoidance of doubt, the cancellation-effect language in §12.2 is read, for the Wix-Store Tier only, as “end of the then-current paid year” in place of “end of the then-current paid month.”
Pre-renewal notice.No fewer than thirty (30) days before each annual auto-renewal, Loomaru will send the Merchant an email reminder to the account email address, identifying the upcoming renewal date, the Fee that will be charged, and the cancellation method. The pre-renewal notice is sent in addition to (and does not replace) the Merchant's right to cancel at any time under §12.2 as adapted by this Section.
9Service Level
9.1Target
Loomaru targets 99.9% monthly uptime for the Service (approximately 43 minutes of unplanned downtime per calendar month).
9.2Measurement
Uptime is measured by third-party external monitoring checking Service endpoints every 60 seconds from at least two geographically distinct locations.
9.3Exclusions
The 99.9%target does not apply to: scheduled maintenance (announced at least 48 hours in advance); force majeure events; Merchant-side misconfiguration; outages of third-party systems outside Loomaru's direct control (including advertising destinations and the Merchant's e-commerce host); and events occurring during the Merchant's first 7 days of onboarding.
9.4Service Credits
If measured uptime in a calendar month falls below 99.9%, the Merchant is eligible for a service credit of 10% of that month's Fee per full 0.1% below target, capped at one month's Fee. Credits must be requested within 30 days of the affected month via vadim@loomaru.com.
9.5Deployment Target
Service activation is typically live within 48 hoursof Merchant kickoff. “Typically” denotes target, not contractual commitment — §9.1 is the contractual uptime commitment.
9.6Support Response Targets
Loomaru targets the following first-response times for Merchant-initiated email support enquiries, measured from receipt at vadim@loomaru.com:
- Starter and Growth tiers: first response within twenty-four (24) hours, on business days (Monday–Friday, excluding Czech public holidays).
- Scale tier: first response within eight (8) hours, on business days.
These targets apply to substantive first response, not to issue resolution, which depends on the nature of the enquiry and on any third-party systems involved. Failure to meet a response target in an individual instance is not a breach of these Terms and does not trigger service credits; the contractual service-level commitment is the uptime target in §9.1.
9.7Performance Targets Are Not Contractual Commitments
The pricing page and other Loomaru marketing materials publish expected revenue-lift ranges (for example, +3% to +10% monthly revenue lift across the Merchant's target ICP envelope, with narrower ranges within that envelope and Scale-tier dampening to +2% to +7%), together with a week-by-week ramp curve. These ranges are derived from published per-platform benchmarks and are presented as targets, estimates, and illustrative outcomes, not as contractual commitments or warranties.
Actual outcomes for any individual Merchant depend on traffic mix, paid-share of revenue, audience maturity, creative, seasonality, promotional calendar, baseline measurement quality, and many other factors outside Loomaru's control. Loomaru does not guarantee any specific revenue lift, conversion volume, return on ad spend, or other performance outcome.
The Merchant's contractual remedy if measured performance is unsatisfactory during the first month is the unconditional 30-day money-back commitment in §8.5. The Merchant's remedy thereafter is to cancel in accordance with Section 12; no performance-based refund applies beyond the first paid month.
9.8Visibility Milestone
Measurable revenue lift, as defined in §8.5, is typically visible in the Merchant's own e-commerce admin sales report by day 30 of deployment, which is the final day of the money-back window under §8.5. The ramp curve published on the pricing page describes the expected shape of that visibility — first recovered events flowing within hours of deployment, meaningful uplift in ad-platform reporting within 5–7 days, measurable lift in the Merchant's own sales report around day 30, and steady state reached by weeks 5–8.
The day-30 visibility milestone is a target, not a contractual commitment, and is subject to the factors described in §9.7. If by the close of the money-back window the Merchant has not observed a lift the Merchant considers meaningful, the Merchant's remedy is the unconditional refund under §8.5.
10Limitation of Liability
To the maximum extent permitted by applicable law, Loomaru's aggregate liability for all claims arising out of or related to these Terms shall not exceed the total fees paid by you to Loomaru in the twelve (12) months preceding the event giving rise to the claim.
Carve-outs. This limitation does not apply to:
- Loomaru's indemnification obligations under Section 11.
- Loomaru's breach of the Data Processing Terms (Section 4).
- Loomaru's gross negligence or willful misconduct.
- Liability that cannot be excluded or limited under applicable law.
Neither party shall be liable for indirect, incidental, special, consequential, or punitive damages, or loss of profits or revenue, except where such exclusion is prohibited by applicable law.
11Indemnification
11.1Merchant Indemnifies Loomaru
You will indemnify, defend, and hold harmless Loomaru from and against claims, losses, and expenses (including reasonable legal fees) arising from:
- Your failure to obtain required consent or legal basis for data collection.
- Your privacy policy failing to disclose the Service or Loomaru's processing.
- Your failure to honor data subject rights requests.
- Your failure to implement required opt-out mechanisms (CCPA/GPC).
- Your breach of any representation or warranty in Section 3.
11.2Loomaru Indemnifies Merchant
Loomaru will indemnify, defend, and hold harmless you from and against claims, losses, and expenses (including reasonable legal fees) arising from:
- Loomaru's breach of the Data Processing Terms (Section 4).
- Loomaru's unauthorized processing of Customer Data outside your documented instructions.
- Loomaru's failure to implement the security measures described in Section 7.
- Loomaru's failure to notify you of a data breach within 72 hours.
12Term & Termination
12.1Term
These Terms are effective upon the Merchant's first use of the Service and continue for as long as the subscription is active under §8.1. There is no fixed contract term, no minimum commitment, and no renewal lock-in.
12.2Cancellation by the Merchant
Cancel at any time. The Merchant may cancel the subscription at any time, for any reason, by emailing vadim@loomaru.com. No notice period applies. Cancellation takes effect at the end of the then-current paid month (the month for which the Fee has already been paid in advance under §8.1); no further Fees are billed after that point, and no pro-rata refund is owed for the remainder of the paid month (the 30-day money-back commitment in §8.5 governs refunds in the first paid month).
12.3Termination for Cause
Either party may terminate immediately upon written notice if the other party materially breaches these Terms and fails to cure within fourteen (14) days of receiving notice of breach.
12.4Post-Cancellation Cleanup
On cancellation, Loomaru will deactivate the Merchant's configuration and cease all processing. Because Customer Data is not persistently stored (§2, §4), deletion of event data is automatic; configuration records are deleted on termination and written confirmation is provided on request.
Restoration of the pre-install state. At the Merchant's choice, Loomaru will either:
- Assisted restore (no-cost). If the Merchant provides the necessary access, the engineer who deployed the recovery layer will reverse the deployment, returning the Store to the measurement configuration that was in place before onboarding. The Merchant does not run a checklist, uninstall a snippet, or coordinate across vendors — the deployment mechanism is the removal mechanism; or
- Documented reversal procedure.If the Merchant prefers not to grant access for the reversal, Loomaru will provide written, Merchant-specific documentation of each configuration change made at onboarding, sufficient for the Merchant (or the Merchant's own staff or contractor) to reverse the deployment on the Merchant's own timeline.
Either option is available at no additional cost for up to thirty (30) days after the effective cancellation date. After that window, Loomaru will still provide the written reversal documentation on request, but assisted restore may be subject to reasonable reactivation fees to cover engineer time.
12.5Survival
Sections 4 (DPA), 5 (CCPA), 9 (Service Level — for the duration of any paid month remaining at cancellation), 10 (Limitation of Liability), 11 (Indemnification), and 13 (Governing Law) survive termination.
13Governing Law
These Terms are governed by and construed in accordance with the laws of the Czech Republic, without regard to its conflict-of-law provisions.
Any disputes arising from or relating to these Terms shall be submitted to the exclusive jurisdiction of the courts of Prague, Czech Republic — except where mandatory consumer protection or data protection law grants jurisdiction to courts in another jurisdiction (including GDPR Article 79 and Brussels I Recast Regulation Article 18).
For EU/EEA data subjects: nothing in these Terms limits your right to lodge a complaint with a supervisory authority in your member state of habitual residence, place of work, or place of the alleged infringement (GDPR Article 77).
14Contact
Loomaru
Vadim Sharapov, sole proprietor
Zikova 1023, Prague, Czech Republic
Privacy & legal inquiries: vadim@loomaru.com