Terms of Service

1. Publisher, host and contact

Publisher and operator: Yanis FAHEM, entrepreneur individuel, Tour Ariane, 5 Place de la Pyramide, 92800 Puteaux – La Défense, France, SIREN 920 580 404. Publication director: Yanis FAHEM. Email: support@getlusca.com. Professional telephone: +33 7 83 88 19 47.

Technical host: Scalingo SAS, RCS Strasbourg 808 665 483, 13 rue Jacques Peirotes, 67000 Strasbourg, France; contact: support@scalingo.com. Lusca does not invent or publish a host telephone because the official Scalingo notice used here provides none.

2. Acceptance, eligibility and language

These Terms apply to adult professional users acting for a merchant or organization. Signup requires active acceptance of Terms v2.4.0 and acknowledgment of Privacy v2.4.0 through a control that is not preselected. New public accounts may use a supported identity provider with a stable subject and verified email, or email/password followed by Lusca email verification. Google, GitHub and Apple remain supported when configured; Google and GitHub are exposed on the current public signup screen. An email/password account, organization and membership remain non-operational until the approximately 20-minute, single-use link is confirmed by Lusca. Historical accounts receive no silent verification. Existing accounts must accept the current version when the service requires reacceptance before access resumes.

The experimental public beta permits one workspace per organization. This release limit is not a promise of a paid plan or future multi-workspace entitlement.

The French version is the governing text. This English version is provided for convenience; if the texts differ, the French version prevails.

3. Current service

Lusca provides the supported Shopify, Google Ads, Merchant Center, Search Console and GA4 reads listed in the Privacy Policy. Installing Lusca and actually granting read_orders enables Shopify order-derived analysis for the exact verified store, limited to the last 60 days. Uninstalling, revoking the scope or losing the proven store binding closes that access.

Lusca supports exactly six protected changes: Shopify variant price, exact inventory quantity at one selected location and product status; Google Ads campaign status, daily budget and asset-group status. Merchant Center, Search Console and GA4 remain read-only. Price and daily-budget changes are EUR-only in this pilot and perform no currency conversion.

Google Ads production changes remain unavailable until the exact customer and developer-token eligibility, ad-management permissible use and applicable Required Minimum Functionality status are evidenced; a configured token alone is insufficient.

4. Protected action rules

One review covers one action for 15 minutes and displays the live current state and exact target. Only an authenticated active owner/admin may approve or reject through the Lusca card. A chat message, recommendation or support exchange is not approval.

Approval rechecks live state, reserves the effect and attempts at most one provider write. No automatic retry follows a timeout or ambiguous provider response. Recheck is read-only. A further attempt requires a new review and a new human decision; autonomous, scheduled and batch provider changes are outside this beta.

5. AI client disclosure

Provider connection and acceptance of these Terms do not activate delivery to ChatGPT. The separate, initially unchecked and versioned service activation described in the Privacy Policy binds the exact user/tenant/workspace/client/resource/scopes to the closed Shopify, Google Ads, Merchant Center, Search Console and GA4 scope, its categories, purpose, recipient and retention policy. Adding a covered provider later requires no new activation. A new provider, category, purpose, recipient or retention policy requires revalidation.

ChatGPT Data Controls, Memory and sync settings are controlled by the user in their ChatGPT account. Lusca cannot read or alter them. Depending on those settings and the applicable OpenAI terms, ChatGPT may retain results or use them to improve its models. Withdrawal stops future Lusca transfers but does not erase content already retained in ChatGPT. The user must have authority to disclose the data. Google-derived results remain subject to Google API Services User Data Policy Limited Use requirements.

The activation never approves a provider write. Every supported write still requires a separate protected card, a fresh human click and at most one provider attempt.

6. Accounts and authority

The user supplies accurate information, secures authentication methods and reports suspected compromise. Email verification proves only control of the address at confirmation time, not authority over an organization or provider account. The user represents that they may bind the relevant organization, connect each store/account/property and request the selected reads or protected actions.

Verification and password-reset links are short-lived and single-use. A resend invalidates older verification links. A password reset revokes the relevant active Lusca sessions and token families. Support never asks for or manually consumes a raw link or token.

Passwords, OAuth tokens, API secrets, private keys, private card capabilities, unnecessary customer data and sensitive data must not be sent by prompt or support message.

7. Prohibited use

• Do not connect or act on an account without authority or infringe third-party rights.
• Do not bypass tenant/workspace isolation, roles, scopes, private card controls, rate limits, price or budget limits, or attempt an autonomous or batch mutation.
• Do not submit secrets or unnecessary personal data, misuse Limited Use data, or present a Lusca result as guaranteed.

8. Results and third-party services

Results may be incomplete, delayed or inaccurate because source data, APIs, authorization and business context change. Lusca guarantees no revenue, profitability, ranking, advertising outcome, stock state or error-free result. The merchant verifies current provider state and remains responsible for business judgment.

Shopify, Google, identity providers, Brevo and AI clients are independent services governed by their own terms and availability. Brevo transports transactional account messages but does not activate accounts. Lusca does not guarantee that an external API, message delivery, account authorization or feature will remain available.

9. Beta availability and support

The beta is experimental and may be paused, limited or unavailable for maintenance, security, provider failure, capacity, quota or law. If Brevo is absent, misconfigured, unavailable or out of the Lusca delivery budget, email/password signup and recovery fail closed without disabling supported identity-provider signup. No contractual uptime, message-delivery, first-response or resolution SLA applies. Internal targets are operational only.

10. Pricing and future billing

The current experimental public beta is free and requires no payment card. Lusca will not charge under these Terms. Any future paid service requires a separate offer stating price, taxes, period, renewal and cancellation and a separate affirmative acceptance before billing. No Shopify or other billing mechanism is promised.

11. Data and intellectual property

Users and relevant rights holders retain their rights in connected data and permit its processing only to provide, secure and support the service and comply with law. Lusca retains its rights in software, interface, documentation and marks; merchant/provider data ownership is not transferred.

12. Privacy and Article 28

Processing, AI disclosure, rights and retention limits are described in the Privacy Policy. The Shopify installation and actual read_orders grant provide the technical authorization to access orders for the requested service. Where Lusca acts as processor for merchant-controlled personal data, any applicable Article 28 data-processing agreement remains a separate legal obligation; neither the installation nor these Terms replace it.

13. Suspension and termination

The user may stop using Lusca, disconnect providers or request closure. Lusca may suspend access for illegal or unauthorized use, material breach, credible security risk, provider revocation, abuse, capacity or legal duty. Notice and an opportunity to respond are provided when reasonably possible; suspension may be immediate when delay would increase risk.

Closure and disconnection follow the manual, fail-closed rights process described in the Privacy and Support pages and do not create an unverified backup-deletion or completion deadline.

14. Liability

Each party is responsible under applicable French law for loss caused by its breach or fault. No monetary liability cap applies in this version. Nothing excludes liability that cannot lawfully be excluded, excuses intentional or gross fault or deprives an essential obligation of its substance. Causation, foreseeability and recoverable loss follow French law.

The merchant’s responsibility for final business decisions does not exclude Lusca’s responsibility for its own obligations.

15. Changes, French law, courts and contact

A substantive version requires renewed acceptance before access resumes where enforced by the service. French law governs. Disputes fall within the French courts legally competent under applicable procedural rules; no city or particular court is designated. The French text prevails. Legal and support contact: support@getlusca.com.

Privacy · Terms · Support