EvoShop Privacy Policy

Who we are

EvoShop is published and supported by EvoMaro (EVOMARO). It includes the public website, web application and services, and desktop and mobile applications. The business using an EvoShop installation is separate from EvoMaro.

Scope

This policy covers the EvoShop public website, web application and services, Windows and macOS applications, Android and iOS applications, and related subscription and support interactions. It is intended for use with the public website and the Microsoft Store, Google Play and Apple App Store listings. Each client currently has a separate application project and database. A business may provide its own notice explaining how it uses customer and employee information.

Controller and service-provider roles

For its customers, employees, sales and other business records, the EvoShop client/business is the data controller: it determines why and how those records are used. EvoMaro acts as processor/service provider for that business. EvoMaro may separately act as controller for its own subscription, support, account-security and operational records. EvoMaro does not decide how each business uses its customer data.

Data we process

Depending on enabled features, data includes staff names, emails, usernames, user IDs and permissions; customer names and optional phone, email and address; products, variants, references, images, prices and stock; orders, holds, returns, exchanges, payments, refunds, debts and customer-favor balances; notes, cashier/device/depot relationships, timestamps and audit records. Device, authentication and operational data are described below.

How information is collected

Information is entered by authorized staff, loaded from the configured business server, captured through an optional camera/gallery/scanner or NFC interaction, or generated when an operation is performed. Website contact forms receive contact and business details and a message to answer the inquiry. Website session/CSRF cookies support forms and security; connection IPs can be used for rate limiting.

Optional website analytics (Google Analytics 4)

EvoMaro uses Google Analytics 4 on the public evoshop.app website to understand visits and how visitors contact us. This website measurement is separate from the business data processed in client installations and from the POS applications. The Google tag loads only after you explicitly accept optional analytics. Refusing does not prevent browsing or using the contact form.

After acceptance, Google receives page views and interaction events, with browser/device information, language, timestamps and cookie-based visitor/session identifiers. Network requests also expose the connection IP address to Google; Google states that GA4 does not log or store IP addresses, although it can derive approximate location. Our implementation sends canonical page URLs without query strings and a blank referrer. It does not send contact-form contents, names, email addresses, telephone numbers, messages or client business records as analytics event parameters.

We measure clicks on WhatsApp and telephone links (whatsapp_click and phone_click). contact_form_submit records a request only after our mail transport accepts the submission; demo_request additionally identifies a demo request. These events do not prove that a call or conversation took place or that an email reached its recipient. Duplicate protection prevents the same submission confirmation from being counted again in the same browser tab.

Your choice is stored in browser localStorage. If you accept, Google Analytics uses first-party cookies such as _ga and _ga_* for visitor/session measurement. A random submission marker in sessionStorage prevents duplicate measurement. These analytics stores are separate from the session/CSRF cookies needed for forms and security. You can delete browser storage yourself; doing so can remove your saved choice.

Use Privacy preferences in the footer to change your choice or withdraw consent. Refusing stops our event tracking, removes the analytics cookies set by this integration and reloads the page to unload the Google tag. Withdrawal applies to future collection and does not automatically erase data already sent. Advertising consent stays denied; this integration does not enable Google Ads, Google signals or advertising personalization.

Google processes the consented analytics information to provide measurement and reports; processing may occur outside your country. Retention follows the settings of the EvoShop Analytics property and Google’s applicable service practices; no fixed period or legal compliance guarantee is asserted here. Contact support@evoshop.app about this website processing. Google’s privacy and cookie information is linked below.

Google — Privacy

Google Analytics — Cookies

Purposes

Processing supports authentication and authorized access, catalog and stock management, sales and settlement, accounting and customer balances, offline synchronization, history/audit integrity, subscription administration, support, service maintenance, abuse prevention and security. Where applicable, records may also be retained to meet legal obligations. SDK diagnostics have the separate purposes explained below.

Accounts, pairing, PIN and NFC

POS accounts are created/administered by the business; users cannot self-register. Authentication may use email/password, a PIN or an assigned NFC bracelet where supported. Passwords/PINs are hashed on the server; the app does not save plaintext passwords/PINs. Pairing uses a short-lived, single-use code/QR followed by a device credential. Device identifiers, name, platform, app version and session/activity timestamps support trusted access and revocation. Bracelet UIDs are transmitted for authentication/enrollment and stored server-side as keyed hashes, linked to the assigned employee.

Customers and business records

Customer records are business records, not EvoShop app accounts. Authorized users access them according to business permissions and depot/device restrictions. Transactions retain links between the original sale, returned/replacement items, payments/refunds and customer-balance movements. Recorded payments include amounts and payment methods, not card numbers, CVV or payment-gateway credentials in the current POS flows. Printed receipts contain the selected business/transaction information and require appropriate handling by the business.

Product photos and permissions

Camera/gallery access is optional and used for product photos or scanning. Selected product images can be cropped/resized and uploaded to the client application server. The current POS upload pipeline strips EXIF/GPS and unnecessary source metadata while preserving orientation. This does not rewrite previously uploaded images. The app does not request precise device location. Denying camera/gallery permission prevents the related feature, not all POS use.

Barcodes and QR codes

Barcode recognition processes camera frames on-device. Google ML Kit does not send those frames or recognition results to Google servers. Accepted barcode/reference values can be sent to the business server for lookup or product assignment. A pairing QR carries a temporary pairing credential and server address; it does not contain a cashier password/PIN or permanent device credential. Manual entry remains available where supported.

Local storage

The app uses local SQLite/cache/preferences for loaded catalog/customer/business data, settings, product drafts/images and queued sales. Tokens, device credentials and protected recovery attempts use secure platform storage, including Keychain on Apple devices. Not all local business records are encrypted. Logout/session revocation does not guarantee immediate deletion of every cached record. Businesses must protect devices and manage remaining local data appropriately, including after subscription termination.

Offline synchronization

Offline sales remain pending until the business server confirms them. When connectivity and authorization permit, queued records are sent to that configured server using their original identifiers. Unresolved/rejected records remain available for recovery or review; logout or changing server does not silently erase them. Resolve outstanding operations with the administrator before clearing app data.

Google ML Kit and other SDKs

mobile_scanner uses Google ML Kit for on-device recognition. ML Kit may send Google diagnostic/operational telemetry: installation identifiers, device/app information, performance/configuration data, events and errors. Google uses these metrics to operate, maintain, improve and secure its APIs and may contact its servers for updates or compatibility information. This is distinct from product-photo uploads to the client server. Local storage/image-processing libraries do not themselves provide a cloud upload service. The current integration has no advertising, ATT/cross-app tracking, Firebase Analytics or Crashlytics.

Google ML Kit terms and privacy

Google Privacy Policy

Hosting and service providers

Hosting currently varies across separate client deployments; there is no single provider or country for all installations. Product/media files stay on the client application server. Infrastructure, backup, maintenance and communication providers may process relevant data on behalf of EvoMaro or the business under the deployment arrangements. Access is for the services involved, authorized business users, support/security needs or applicable legal obligations. A future storage or hosting plan is not a current provider.

Security and transmission

Release app API/media connections use HTTPS with normal certificate validation. Legacy HTTP media links are upgraded to HTTPS, with no insecure release fallback. Authentication, permissions, device revocation, secure credential storage and separate deployment environments protect access; no system is completely risk-free. Limited private-network HTTP is available only in development/debug builds and is not a production transport exception.

Retention during service

While a subscription is active, business/customer/transaction data remains until the client edits/deletes it or the subscription ends, subject to applicable legal obligations. EvoMaro retains its own subscription, support and security records only for the relevant purposes and applicable obligations. Operational/security logs are server/local only, with no external logging/monitoring provider, and retained only as long as reasonably necessary under normal server rotation/maintenance. No fixed log-retention duration is promised.

Backups and subscription termination

Automatic backups exist. After subscription termination, EvoMaro may retain a recovery backup for up to 30 days. After that recovery period, remaining service data/backups are deleted, subject to normal infrastructure backup rotation and applicable legal obligations. Deleting a live record does not instantly erase every backup copy, and the 30-day recovery window is not a promise that every rotated infrastructure copy disappears at the same instant. Local device copies require separate management.

Business deletion and access controls

The client can create, edit and delete its customer/business records and history using authorized controls, subject to applicable obligations and transaction-integrity rules. Administrators manage employee permissions, PINs and devices and can revoke access. These controls do not create a public app-account signup/deletion flow and do not guarantee immediate erasure from backups, audit records or device caches.

Individual privacy requests

For customer/employee/business records, contact the relevant EvoShop business as controller first. EvoMaro may assist that business technically where required. For EvoMaro’s own subscription/support/security records, or help identifying the appropriate contact, write to support@evoshop.app; corporate fallback: info@evomaro.com. Identify the business and relevant records without sending passwords, PINs or payment credentials. Requests for access, correction, deletion or other rights are assessed according to applicable law, identity/authority checks and any legal retention obligations; no universal right or fixed response time is promised.

Children and minors

EvoShop POS is a professional business tool, not a service intended for children, and has no self-registration flow. If a business records information about minors, it is responsible for the lawful use of those records and any required notices/authorizations. Related requests should be directed to that business.

International processing

Processing locations depend on the client deployment, infrastructure and SDK/service providers. Information may be processed outside the country of the business or individual, including Google’s operational telemetry. We do not represent that all infrastructure is in one country or promise a specific transfer mechanism or certification. Contact us and the relevant business for deployment-specific information and any safeguards required by applicable law.

Changes to this policy

We may update this policy to reflect changes in features, practices or applicable requirements. The Last updated date identifies the current version. Significant changes will be communicated where required by applicable law. Business notices may be updated separately by their controllers.