Last updated: 28 October 2026
WebshopSensewise is a conversion-optimization platform for webshops. Two different groups of people show up in this policy, and they're treated differently:
For an Account Holder's own account data (section 3), WebshopSensewise is the data controller: we decide why and how that data is processed.
For visitor/shopper data collected on an Account Holder's store (section 4), the Account Holder is the data controller, and WebshopSensewise acts only as their data processor - we process it strictly to provide the service the Account Holder configured (analytics, on-site messages, cart-recovery/back-in-stock emails). If you're a shopper with a question about how a specific store uses your data, that store's own privacy policy and support contact is the right place to start; WebshopSensewise does not independently decide what happens to that data.
When you create a WebshopSensewise account, we collect and store:
| Data | Why |
|---|---|
| Email address | Login identifier, service notifications, password-reset/account emails. |
| Password | Stored only as a salted hash (never in plain text) - see section 8. |
| Two-factor authentication secret (optional) | Stored encrypted; only used to verify login codes if you enable 2FA. |
| Store name, domain, API key | Identifies which store's visitor data belongs to which account. |
| Login timestamps / login attempt records | Account security - rate-limiting repeated failed logins. |
| Email verification token, sign-up attempt record | Confirms the email address at registration (the token is stored only as a hash) and limits automated sign-ups per network (only a one-way hash of the IP address is stored, for 2 days). Accounts whose email is never confirmed are deleted after 7 days. |
| Billing status of each store | The plan, Stripe customer and subscription identifiers, subscription status and renewal date - needed to give you the plan you paid for. Card numbers are never stored by us (see 3.1). |
You can review and permanently delete this data yourself at any time from Account & Security → Danger zone - see section 9.
Paid plans are billed through Stripe (Stripe Payments Europe, Ltd. and its affiliates). You enter your card or other payment details on Stripe's own pages; we never see or store them. Stripe processes this data as an independent controller for payment processing, fraud prevention and its legal obligations - see Stripe's privacy policy. We receive and keep only the information described in the table above, and the invoices and receipts we must retain by law (section 6).
This section describes what the embeddable tracking script can collect - what it actually does collect for a given store depends entirely on how that store's owner has configured WebshopSensewise and their own consent banner (see Terms of Service, section 3).
By default, the tracking script collects nothing and creates no visitor identifier until the store's own consent-management banner calls a "grant consent" signal. Once active, it may record: page views, clicks, scroll depth, and cart-related events (e.g. add to cart) tied to a randomly generated, pseudonymous visitor ID (not your name or email). This identifier is stored in the browser's local storage, not in a tracking cookie. A visitor's IP address is never stored in raw form - it is one-way hashed (HMAC-SHA256 with a server-side secret) before it ever touches the database, purely to support basic fraud/abuse signals, not to identify individuals. A store owner can switch the consent gate off for a store; in that case tracking starts without waiting for a consent signal, and the store owner is responsible for having a lawful basis for it.
If a store owner's own checkout/account flow already has your email address and chooses to share it with WebshopSensewise (e.g. so an abandoned-cart email can be sent to you), it is linked to your visitor ID for exactly that purpose. This is separate from, and not gated by, the passive-analytics consent above - it only ever happens as a direct result of an action you took on that store (e.g. entering your email).
If a store owner enables these features, WebshopSensewise may send you: a reminder email if you added items to a cart and didn't complete checkout, or a one-time notification if you asked to be told when an out-of-stock product is available again. Every such email includes an unsubscribe link; unsubscribing (or being marked as bounced/complained) is recorded and future emails to that address are suppressed.
A store may show you a tailored on-site message (e.g. a shipping-threshold nudge, a trust badge, a time-limited offer) chosen automatically from the store's own configured rules based on your session's behavior. This selection happens automatically but only decides which pre-written message you see on the page - it doesn't make any decision that produces legal or similarly significant effects about you.
WebshopSensewise itself sets very little, and deliberately avoids third-party/advertising cookies entirely:
| Name | Where | Purpose | Type |
|---|---|---|---|
sensewise_session | Dashboard login | Keeps you logged in to your own WebshopSensewise account. | Strictly necessary - HttpOnly, not used for tracking, not shared with visitor-facing pages. |
| Visitor/session identifiers | A store's own storefront pages (via embed.js) | Distinguishes one visitor/session from another for analytics. | Browser local storage, not a cookie; created only after consent (see 4.1). |
Because the storefront-facing identifiers require the store's own consent signal before they're ever created, WebshopSensewise does not independently set analytics or advertising cookies on a store's visitors.
Visitor-level behavioral data (page views/clicks/scroll/cart events, session records, visitor identifiers, the visitor-to-email link used for cart recovery, and the cart-recovery email log) is automatically deleted after 14 months by default (configurable per install), matching common analytics-industry default retention windows. Back-in-stock subscriptions are kept only until they're fulfilled or cancelled, then follow the same 14-month clock - a still-pending subscription is never deleted early just because time has passed, since it reflects a request you're still waiting on.
Account data is kept for as long as the account exists. Sign-up attempt records are deleted after 2 days, never-confirmed accounts after 7 days, and payment-webhook logs after 90 days. Invoices and accounting records are kept for as long as accounting and tax law requires (in Hungary, generally 8 years), even after an account is deleted. An Account Holder can permanently and immediately delete their own account and every store they own - including all visitor/shopper data in those stores - at any time from Account & Security → Danger zone. This also removes any password-reset tokens or 2FA recovery codes tied to the account. Deleting an account only removes access to stores you're a team member of (not an owner of); that store and its data are unaffected and remain with its owner.
We don't sell personal data, and we don't share it for advertising purposes. Data is shared only with:
We apply the following measures across the platform:
No method of transmission or storage is 100% secure, but these are the concrete steps we take.
If you're an Account Holder, you can access and correct your account details from the dashboard, and permanently delete your account and owned stores yourself at any time (section 6) - no need to contact us for that specific request. For anything else (a copy of your data, a question about what's stored), contact webshopsensewise@ygsaas.com.
If you're a shopper/visitor on a store using WebshopSensewise, that store's owner is the data controller for your data (section 2) - start with their privacy policy/support contact for access, correction or deletion requests. If you're unable to reach them, contact us at webshopsensewise@ygsaas.com and we'll assist as the processor. Depending on applicable law (e.g. GDPR), you may have the right to access, correct, delete, restrict or object to processing of your data, receive a portable copy of it, and withdraw consent at any time (which, for passive analytics, you can also do directly via the store's own cookie/consent banner). You can also lodge a complaint with a data protection authority - in Hungary, the Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH, naih.hu).
WebshopSensewise is not directed at children, and we do not knowingly collect personal data from children under 16 through account registration. Because visitor tracking is configured by each store, we're not in a position to know a visitor's age - store owners are responsible for their own site's compliance with applicable rules about minors.
Account and visitor data is hosted by Dotroll.com. Payment data handled by Stripe may be transferred outside the European Economic Area, including to the United States; Stripe relies on safeguards such as the European Commission's Standard Contractual Clauses and, where available, the EU-U.S. Data Privacy Framework (see Stripe's privacy policy). We do not otherwise transfer personal data outside the EEA.
We may update this policy as the service changes. We'll update the "Last updated" date above, and for material changes we'll make reasonable efforts to notify Account Holders (e.g. by email) before the change takes effect.
Questions about this policy, or a data request: webshopsensewise@ygsaas.com.