Simple Seller Privacy Policy

1. Operator and business responsibilities

Operator’s legal name

Not provided — to be completed

Contact address

Not provided — to be completed

Privacy contact

Not confirmed — to be completed

Each business determines the lawful sources, business purposes and staff permissions for the customer, supplier and employee information it enters. The service provider supplies technical processing as agreed. The parties’ controller and processor responsibilities, and any necessary data processing agreement, must be defined before the formal service begins. This notice does not replace the information a business must give its customers or employees, and it does not adopt another company’s privacy policy as our own.

2. Information we process

Registration, sign-in and approval

We process the business name, username, contact name or telephone number, password and registration time you provide to create accounts, verify access and review applications manually. The contact field is not a mandatory email field. Current registration does not request business licences, identity documents or social accounts. Passwords for accounts created through registration are verified using salted hashes. Approval status, review notes and security actions are recorded.

Employees and device binding

We process the salesperson name, permissions and enabled status set by the owner, binding-code validation records, binding time and a random browser binding identifier to manage authorisation, binding and unbinding. Codes can be used once and expire after 10 minutes. The device credential is not a phone hardware serial number, and we do not read the address book. Social sign-in is not currently provided.

Business records

Depending on the features used, we process products and images, customer and supplier details, orders, held drafts, inventory, prices, payments and receipts, outstanding balances, invoices and exports. Only enter information you are authorised to process and need for your business. Electronic catalogues show information according to the business’s settings and sharing authorisations; the person sharing a catalogue should check its content and recipients.

Voice and AI

When you choose voice ordering, the website requests microphone permission and sends the audio through the server to the enabled speech service. The current integration uses OpenAI and may include a small selection of customer names and product codes as recognition hints. Results help match products, quantities and prices and update the current order. Current application code does not save original recordings in the business database, COS or long-term disk storage. Temporary audio still exists in memory and in transit during processing. Third-party retention and processing locations must be checked under the actual service agreement; we cannot promise immediate deletion by a third party.

When you choose a configured AI try-on or other generation service, selected garment images, model images you provide, scene options and necessary prompts are sent to that feature’s provider. The provider, purpose and required permissions must be explained before use. An unconfigured service is not called merely because you visit this page. Do not upload someone’s likeness without permission. Manual ordering remains available without AI; microphone or camera permission is not blanket authorisation to share all business records.

Camera, photos and files

Camera or file permissions are requested when you use QR scanning, barcode scanning, photography or image selection. Employee QR scanning recognises the code in the browser and submits the binding code, rather than uploading camera frames as product images. Image and file features upload only items you select or confirm; they do not grant continuing access to your whole photo library.

Feedback, diagnostics and operations

When you submit feedback, we process its category, text, up to 3 selected images, account and business association, version, device category, operating system and submission time. Additional client diagnostics are off by default and require a separate confirmation. Technical diagnostics are limited to controlled error codes, modules, versions, device categories, status codes, timings and timestamps. They do not automatically collect business request bodies, full URLs, recordings, passwords or cookie contents. The server retains necessary interface-error, security-audit and connection records. Infrastructure may process IP addresses and request times; this does not read precise GPS location.

Mobile faults are grouped by business, platform, version, build, device category and operating-system version, with occurrence counts and event identifiers. Authorised diagnostic uploads may contribute to these groups; raw error text is not stored as the fault content.

Service payments and notifications

The administration system processes manually confirmed payment references, amounts, methods, purposes, quota additions and refunds. This does not mean automatic card charging or Apple in-app purchases are integrated. Registration-review and operational notifications send necessary business, account, contact and application information to operators, without sending registration passwords. An internal notification address is not automatically a public privacy contact.

3. Purposes and legal bases

• Registration, approval, sign-in, binding and business-management services: where applicable, performance of a service contract or necessary pre-contractual steps. Business data processed on behalf of a customer follows its authorised instructions and agreement.
• Preventing misuse, investigating faults and protecting data: where applicable, legitimate interests in secure operations, with consideration of the impact on individuals’ rights.
• Applicable statutory retention, tax duties and lawful requests: the relevant legal obligation or other applicable basis.
• Optional diagnostics, disclosure of personal data to third-party AI and other non-essential processing that requires consent: separate information and the required permission before processing begins, rather than treating this page as consent.

Missing necessary information may prevent the related operation. Optional information should not be made a condition for unrelated features. Business registration is reviewed by management personnel, not decided automatically from speech-recognition results.

4. Cookies and browser storage

The website uses necessary session and security cookies, local storage, session storage, IndexedDB and Service Worker caches to support sign-in, settings, drafts and offline use. The current sign-in page does not integrate advertising trackers or marketing analytics cookies. Adding this privacy link does not add tracking scripts.

• ss_session: business sign-in session, normally 7 days in the production website, renewable with continued use. Sign-out, replacement sessions or permission changes may invalidate it sooner.
• ss_employee_device: random employee binding credential, with a browser lifetime of up to approximately one year. Unbinding invalidates the binding; clearing the credential may require a new binding.
• ss_unlock: unlock credential when a screen passcode is enabled, up to approximately 8 hours.
• ss_developer: administration-only session, up to approximately 8 hours, also subject to inactivity expiry, reauthentication and revocation.
• Business caches, offline drafts, images, language and sorting preferences: stored in the current browser as needed by the feature. Retention depends on the feature and browser cleanup. Signing out or closing a page is not guaranteed to clear every local copy.
• Client technical events: up to 80 controlled events from the last 24 hours are temporarily held within the current session. A voluntary diagnostic upload includes the latest 20 error or failed-operation records.

You can manage cookies and website data in your browser. Sync offline records before clearing storage: clearing it may sign you out, lose unsynced content or require employee rebinding. On shared devices, use separate browser profiles and sign out promptly. Any future non-essential tracking requires a fresh assessment of notice and consent; ordinary sign-in is not consent to marketing.

5. Recipients and processing locations

Necessary information is disclosed for the service, features you initiate, lawful requests and authorised support. Business customer lists are not sold or traded for advertising. Owners and authorised staff access their own business’s records according to permissions. Operators and technical staff access necessary management information for approval, support, payments and security, with management audit records.

• Tencent Cloud: infrastructure for the current servers, private COS object storage and encrypted backups.
• OpenAI: audio, input and limited recognition hints required by enabled voice or AI features. Signing in or reading this notice does not send the whole business database.
• Google / Gmail: review and operational notifications to operators, including the necessary email content and delivery information.
• Optional business providers: invoicing, tax-number checks and image generation receive necessary information only for the relevant feature and authorisation. The actual recipient must be identified during configuration or activation.
• Resource providers: barcode, OCR and similar components may load from resource services when needed. Their servers may receive IP addresses and necessary request information, which does not authorise access to all business records.

Infrastructure and providers may process data outside the European Economic Area. Before formal adoption, confirm: actual server, storage and provider locations, data processing agreements and applicable international-transfer arrangements, such as adequacy decisions or standard contractual clauses. Displaying this notice or obtaining a single blanket agreement cannot replace necessary transfer measures. This draft does not claim they are all in place.

6. Retention, deletion and backups

• Accounts and business information are kept for service delivery and lawful business needs. Orders, invoices and accounts may be subject to statutory retention or dispute requirements. Specific periods and bases must be defined before formal adoption; no universal period is invented here.
• Feedback and selected attachments are normally kept for up to 90 days, limited to 500 submissions and approximately 20 MB per business. Ordinary diagnostics are normally kept for up to 30 days, limited to 200 records and approximately 8 MB per business. Capacity limits may remove older records earlier.
• Mobile fault groups are retained for up to 30 days, limited to the latest 5,000 groups. Deduplication event identifiers are retained for up to 24 hours, limited to 20,000 records. Security audits, data-request handling and service-payment records do not yet have a uniform automatic expiry policy; their periods and bases must be specified before formal adoption.
• Original audio is not stored long-term on disk by the current application code. Recognised text, product lines, held drafts and orders follow business-record retention. Third-party retention must be checked under the applicable agreements.
• Databases, images and related configuration have backup copies. Deleting an online record does not immediately delete backups; automatic expiry of cloud recovery points is not currently enabled. Retention, deletion and access restrictions must be defined before formal adoption. Restores should take account of accepted deletion or restriction requests.

Scheduled cleanup or a record no longer appearing in a page does not mean every backup copy has been physically erased. Account suspension, employee unbinding and account deletion are different actions. Suspension or unbinding does not automatically delete business records.

7. Security

HTTPS, business-data isolation, permission checks, salted password hashes, random sessions, developer multi-factor authentication, auditing and encryption of some storage and backups help reduce risk. No measure guarantees absolute security. Backup verification does not mean every disaster-recovery or cross-region capability is complete. Protect passwords, binding codes and devices; do not put keys, full payment-card details or unrelated sensitive information in feedback or images.

8. Your rights and requests

Depending on applicable law and the processing basis, you may request access, correction, erasure, restriction, portability and objection, and withdraw consent where processing relies on it. Withdrawal does not affect lawful prior processing or automatically stop necessary processing based on another valid ground.

Business customers, suppliers and employees may first contact the business that entered their information. Account owners can make requests through configured Help and Feedback channels; identity and authority are checked before processing. The formal notice will provide a privacy contact usable without signing in. Current administrative request-status management does not amount to one-click account deletion or automatic deletion of all data.

Proportionate identity and scope checks may be needed to protect others. Where statutory retention or others’ rights prevent deletion, the reason should be explained. Where EU data protection rules apply, you may complain to the competent supervisory authority. In Italy this is the Garante per la protezione dei dati personali.

9. Children

This service is intended for business users with business needs and appropriate authority, not for children. Do not enter children’s information unnecessarily. Suspected unauthorised information about a minor should be checked and handled through the relevant request process.

10. Changes and effective date

The formal notice will state its version and effective date. Important changes to purposes, disclosures or rights should be communicated through the relevant pages or another effective channel. Where new permission is required, obtain it before processing begins; continued sign-in is not agreement to every change. This draft does not replace future iOS permission notices, App Store privacy disclosures, data processing agreements or a formal legal review.