Cookie-Richtlinie

This document explains how the Sellerviva website and application (sellerviva.com and its subdomains) use cookies and similar browser storage technologies. Service provider: Bays Trade LLC (the Sellerviva brand) · Contact: [email protected]

In short: Sellerviva is a business-to-business (B2B) software service. We use no analytics, advertising, tracking or marketing cookies of any kind. The technologies we use exist only to operate the service and to remember your interface preferences.

1. What are cookies and similar technologies?

• Cookie: a small record stored by your browser and sent to the server with requests.
• localStorage / sessionStorage: local storage kept only in your browser and never sent to the server automatically. sessionStorage is cleared when the tab closes.
• Third-party script: code loaded into the page from another provider (listed below).

2. Cookie inventory

Name	Type	Purpose	Duration	Essential?
sv_refresh	HTTP cookie (httpOnly, Secure, SameSite=Strict)	Securely maintaining your session (refresh token). Not readable by JavaScript.	30 days if "Remember me" on the sign-in screen is ticked; otherwise deleted when the browser closes	Essential — sign-in does not work without it
sv_remember	HTTP cookie (httpOnly, Secure, SameSite=Strict)	Storing your "Remember me" preference; holds only the value 1/0 and contains no personal data	Same as sv_refresh	Essential (part of session-duration handling)
NEXT_LOCALE	HTTP cookie	Your language preference (tr, en, de, es, fr)	Session cookie — deleted when the browser closes	No (functional — contains no personal data)
Access token	NOT a cookie — held in page memory only	Authenticating API requests	While the tab stays open, in memory	Essential (never written to disk)

3. Local storage inventory (localStorage / sessionStorage)

Name	Type	Purpose	Duration	Essential?
sv_cookie_consent	localStorage	Remembering that you dismissed the cookie notice banner	Until you delete it	Essential (functional — contains no personal data)
sellerviva-theme	localStorage	Your light/dark theme preference	Until you delete it	No (functional)
onbRedirected	sessionStorage	Preventing the setup redirect from repeating in the same session	Until the tab closes	No (functional)
Keys starting with sellerviva., sv., sv- or sv:	localStorage or sessionStorage	In-app interface preferences: table columns, page size, collapsed sidebar, wizard progress, selected store, dismissed announcements, dismissed page guide, support-session marker and reload protection after an error	Until you delete them (sessionStorage entries until the tab closes)	No (functional — they carry no account credentials)

These two tables are the complete inventory; an automated test verifies that every storage key in the source code is mentioned here. Sellerviva sets no cookie or storage key that is not listed here.

4. Third-party services

• "Sign in with Google" (Google Identity Services): Google's script loads only on the sign-in and sign-up pages. When it loads, your browser connects to Google's servers and Google may use its own cookies, which are governed by Google's privacy policy. If you do not use Google sign-in, your account works without this script.
• "Sign in with Apple": You are redirected to Apple only when you press the button; no Apple cookie is written on Sellerviva pages.
• Error monitoring (Sentry): Detects application errors and sets no cookies. Sending of personal data is disabled (sendDefaultPii off); error reports are scrubbed so they carry no personal content beyond a user identifier.
• Payments (Stripe): Checkout pages are hosted by Stripe; the fraud-prevention cookies Stripe uses on its own pages are governed by Stripe's policy.

5. What we do NOT use — explicit statement

Sellerviva has no:

• analytics/statistics cookies (no Google Analytics, PostHog or similar),
• advertising/marketing cookies, ad pixels or retargeting technology,
• cross-site tracking or client-side fingerprinting technology,
• sale or sharing of data with third parties via cookies.

For that reason no "Do not sell or share my data" option is needed: no sale or sharing takes place. Your browser's Global Privacy Control signal changes nothing on this site either, because there is no tracking to opt out of.

6. Why we do not ask for cookie consent, and what the preferences window does

Consent is meaningful only where non-essential cookies (such as analytics or advertising) are used. The Turkish Data Protection Board's cookie guidance, the EU ePrivacy Directive (2002/58/EC art. 5(3)) and the UK PECR all exempt cookies that are strictly necessary to run the service and preference records the user asked for. Because Sellerviva uses only technologies in that class, we do not ask you for cookie consent; instead we inform you through this policy and the on-page notice banner. We consider it dishonest to show a fake "accept/reject" screen for cookies that do not exist.

The "Cookie Preferences" link in the footer shows this inventory by category (essential, functional, analytics, marketing) and states the status of each. Because there is no optional cookie, there is no on/off switch there.

Our forward commitment: if we ever want to add any non-essential cookie or similar technology (for example analytics), then before enabling it we will (1) publish this policy as a new version, (2) ask for your explicit consent in the cookie preferences window and (3) not run the technology unless consent is given (default: off).

7. How to manage cookies

You can delete or block cookies in your browser settings, and clear localStorage/sessionStorage entries through your browser's site-data controls. Warning: if you block the sv_refresh cookie you will not be able to sign in to Sellerviva. If you block sv_remember, your session-duration preference cannot be stored and the session falls back to the default (30 days). Deleting the functional entries resets your theme, language and panel preferences and shows the notice banner again.

8. Notice banner

The "Got it" button on the site's notice banner only records that the banner was dismissed (sv_cookie_consent); it does not create, and is never claimed to create, any consent.

9. Changes and contact

Each version of this policy is published with its date and version number; material changes are announced in the application. For details of how we process personal data and your rights, see the Privacy Policy and Privacy Notice. Questions: [email protected]