# Privacy Policy — POS SoftSolvIT

## 1. Overview

POS SoftSolvIT is a business point-of-sale (POS) application for merchants who runtheir own [Odoo](https://www.odoo.com) back-office system. The app lets a merchant'sstaff sell products, take payments, and sync those transactions to **the merchant's ownOdoo server**.

**Important — who controls your data.** SoftSolvit provides the app software. The**merchant** (the business that installs and configures the app) operates their ownOdoo server and is the **data controller** for all business and customer data processedthrough it. SoftSolvit does **not** receive your sales, customer or payment data, neverreceives an employee PIN, and does **not** have access to the merchant's Odoo instance.

**One exception about credentials, added 2026-08-15.** SoftSolvit never *stores* an Odoopassword or API key. The single moment one reaches SoftSolvit is **device linking**: thefirst time a given device is linked to a database, the login and password entered on thesign-in screen are sent to `softsolvit.com`, which uses them once — immediately — to askthe merchant's *own* Odoo server whether that account exists and is allowed to use thepoint of sale. The answer decides whether that device may be issued a licence key. Thepassword is not written to a database, not written to a log, and is discarded as soon asthe check returns. It happens once per device, not at every sign-in.

This exists because a device that has never been seen before cannot otherwise bedistinguished from an unauthorised one, and a database URL is not a secret — anyone whoguessed it could otherwise claim a licence seat in the merchant's shop.

SoftSolvit operates a **registration/licensing server** (`softsolvit.com`). It receives,and only for licensing: the **Odoo database URL**, a **contact phone number** andoptional **contact email** given at registration, and — each time the app signs in — a**device identifier**, the **Odoo login name** used to sign in, a **device/platformlabel**, and the **date and time that device was last used**. The device identifier andlogin name are what make the per-business device limit enforceable and a licence questionanswerable; see §2 and §4. Business data flows only between the device and thedestinations the merchant configures.

**Egyptian eReceipts.** A merchant who switches them on reports each sale directly tothe **Egyptian Tax Authority** from their own till, with credentials the Authorityissued to them. SoftSolvit is not in that path and receives nothing from it. No buyeridentity is ever sent: every receipt this app issues is anonymous, which is why itrefuses a sale of 150,000 EGP or more — at that value the Authority requires buyeridentification, and this app does not collect any. See §2 and §4.

**Presented and accepted in the app, from this build on.** The list above is no longeronly published here: on first run the app shows two agreements — the data-collectionagreement and a terms-of-use/liability agreement — each as a full-screen, scrollabletext that must be read to the end and ticked before it can be accepted. **The app cannotbe used until both are accepted**, and the gate is decided on the device, so it appearswhether or not the device is online. The data-collection agreement states the same listdescribed in §2 and §4; it restates rather than extends what this policy already says.Each agreement carries a version number: if either text changes materially, its versionis raised and every device is asked again. The accepted versions and the acceptance timeare recorded on the device, and are reported once to the merchant's registration recordon `softsolvit.com` so we hold a record of which terms that business accepted and when.

## 2. Data the app handles and where it goes

Network communication goes to the following destinations:

1.**The merchant's Odoo server** — the server URL is entered by the merchant at login   (chosen and controlled by the merchant). Almost all data flows here.2.**Thermal receipt printers on the merchant's local network (LAN)** — for printing   receipts and reports (local network only).3.**The Egyptian Tax Authority (`invoicing.eta.gov.eg`)** — contacted **only** when   the merchant has switched eReceipts on and entered their own ETA credentials. The   app then reports each sale to the Tax Authority as the law requires. This is a   direct connection between the merchant's till and the Tax Authority: **SoftSolvit   receives nothing from it and cannot see it.** See the eReceipt rows below.4.**SoftSolvit's registration server (`softsolvit.com`)** — contacted for licensing   only: to register the merchant's database for a licence/free trial, to verify that   the database's subscription is active (an access gate), and **to register this device   against the licence's device limit each time the app signs in**. This is the only   data SoftSolvit itself receives; the exact fields are in the table below and in §4.

The app contains **no advertising, analytics, tracking, or crash-reporting SDKs**.

| Data | Why it is handled | Where it goes ||---|---|---|| **Odoo login credentials** (server URL, username/email, password or API key) | To authenticate the app to the merchant's Odoo server, and once per device to prove that device may be licensed | Sent to the merchant's Odoo server; stored locally on the device (see §3). **The password / API key is never stored by SoftSolvit.** It is transmitted to `softsolvit.com` exactly once per device, for the device-linking check described above, and discarded after that single use. The server URL and the login name are sent for licensing — see the device-registration row below. || **Employee identifiers and PINs** | Downloaded from Odoo so cashiers can log in with a PIN while offline | Downloaded from the merchant's Odoo server; cached on the device || **Sales, orders, payments, cash movements** | Core POS function — recording and syncing sales | Sent to the merchant's Odoo server; cached on the device until synced || **Customer details** (name, phone, email, tax/VAT id, address) | To attach a customer to a sale, or to create a customer record the merchant requested | Downloaded from / uploaded to the merchant's Odoo server || **Receipt logo image** | Branding on printed receipts | Chosen by the merchant from the device gallery; stored **locally only** — never uploaded off the device || **Receipt content** (item names, prices, cashier/customer name) | To print receipts and kitchen tickets | Sent to the merchant's LAN printer over the local network || **Registration details** (the merchant's Odoo database URL, a contact phone number, and optionally a contact email, entered when registering) | To register the database for a licence/free trial and to check that its subscription is active before allowing access | Sent to **SoftSolvit's registration server (`softsolvit.com`)**. The database URL is also re-sent on periodic subscription checks. || **eReceipt documents** (the sale's own lines, prices, taxes, totals and payment kind, the shop's tax registration number, registered name, activity code and branch address, and this till's registered serial) | To issue the electronic receipt the Egyptian Tax Authority requires for each sale, and to send the matching return receipt for a refund | Sent to the **Egyptian Tax Authority** (`invoicing.eta.gov.eg`) from the merchant's own till, using the merchant's own ETA credentials. **No buyer identity is ever sent**: every receipt this app issues is anonymous (`buyer.type = P` with no name and no id), which is also why it refuses to take a sale of 150,000 EGP or more — the Authority requires buyer identification at that value and this app does not collect it. Nothing is sent to SoftSolvit. || **ETA credentials** (the client id and client secret the Tax Authority issues per registered till, and an optional pre-shared key) | To authenticate this till to the Tax Authority | Entered by the merchant, stored **only in the device's secure keystore** — never in the app's settings file, never in a backup of it, and never sent anywhere but the Tax Authority. || **Device registration** (a device identifier generated by the app, the Odoo login name used to sign in, a device/platform label such as "iOS 18.1 – iPad13,4", the database URL, and the date/time the device was last used) | To enforce the licence's limit on how many devices a business may use at once, and to show the licence holder which devices are active | Sent to **SoftSolvit's registration server (`softsolvit.com`)** each time the app signs in, and refreshed periodically while it is open. The identifier is generated by the app for this purpose; it is not an advertising identifier and is never used as one. No sales, customer or payment data and no employee PIN is sent here. Each device holds a **licence key issued to that device**, which is what identifies it on later calls; the key is stored in the device's secure keystore. |

The app does **not** collect location, contacts, microphone, phone/SMS, or health data.

Two device permissions are used, and neither sends anything to SoftSolvit:

-**Photo library** — accessed only when the merchant picks a receipt logo, which is  stored on the device and never uploaded.-**Camera** — used to scan product barcodes at the till, and to photograph a receipt  logo if the merchant chooses the camera instead of the gallery. Barcode frames are  read **on the device** and are never stored or transmitted; only the decoded barcode  number is used, and only to look the product up in the merchant's own catalogue.

## 3. Data stored on the device

For offline selling, the app caches data in the app's private storage:

- Catalog (products, taxes, payment methods, categories).- Employees (names and PINs) and customers (contact details) downloaded from Odoo.- Orders and session data awaiting sync.- App settings, including the last-used Odoo URL/login and the receipt logo.-**Where eReceipts are switched on**: for each sale, the receipt document exactly as it  was sent to the Egyptian Tax Authority, its identifier, the QR text printed on the  paper, the Authority's answer and a log of the attempts. It is kept for the same reason  and the same length of time as the order itself, and is removed with the app's data.  The Tax Authority credentials are **not** part of this cache — they are held in the  device's secure store (Keychain on iOS, the keystore on Android).- A **device identifier** the app generates once per install — a random UUID, held in  the device's secure storage (Keychain on iOS, the encrypted keystore on Android). It  is not a hardware or advertising identifier and reveals nothing about the device; it  exists so the licence's device limit can count this till. It is sent to SoftSolvit's  licensing server as described in §2 and §4.

This local cache is stored in the app's private area of the device. It is removed whenthe app's data is cleared or the app is uninstalled (Android Settings → Apps → POSSoftSolvIT → Storage → Clear data / Uninstall). Signing out clears the stored passwordfrom the device.

One exception: on iOS the **device identifier** is held in the system Keychain, whichApple does not erase when an app is deleted, so reinstalling the app on the same iPhoneor iPad reuses the same identifier rather than consuming a second device slot. It holdsno personal information. To have it cleared from the licence, see §6.

## 4. Data sharing

We do **not** sell your data or share it with advertising or data-broker third parties.Business data (sales, customers, passwords, employee PINs, catalog) is transmitted only tothe merchant's own Odoo server and the merchant's own LAN printer(s), as described above —**SoftSolvit does not receive any of it.**

A second destination exists only where the merchant has enabled it: the **Egyptian TaxAuthority**. eReceipt documents go from the merchant's till to`invoicing.eta.gov.eg` under the merchant's own Tax Authority credentials, becauseEgyptian law requires each sale to be reported. **SoftSolvit is not a party to thatexchange and receives no copy of it.** No buyer identity is included in any receipt theapp issues.

The exception is **licensing**, which reaches SoftSolvit's own server(`softsolvit.com`) in two ways:

-**Registration and subscription checks** — the **database URL**, and at registration a**contact phone number** and optional **contact email**.-**Device registration**, each time the app signs in — a **device identifier** generated  by the app, the **Odoo login name** used to sign in, a **device/platform label**, the  database URL, and the **date/time the device was last used**.

SoftSolvit uses all of this solely to manage the licence/free trial, the subscriptiongate, and the limit on how many devices a business may use at once — a limit that cannotbe enforced without identifying the device, and a licence question that cannot be answeredwithout recording which login activated it. None of it is sold or shared for advertising,and it is never joined to data from other apps or websites.

## 5. Security

- Data transmitted to the merchant's Odoo server is encrypted in transit **when the  merchant configures an `https://` server URL**. If a merchant uses a plain `http://`  server (e.g. an on-premises LAN server), that traffic is not encrypted; merchants are  responsible for securing their own network and are advised to use HTTPS.- Local device data relies on the device's own security (screen lock, app sandboxing,  and device/OS encryption). The receipt-printer connection uses the standard  unencrypted ESC/POS protocol over the local network, as required by thermal printers.

## 6. User accounts

The app does **not** create consumer user accounts and has no in-app sign-up. Staffauthenticate with credentials for the merchant's pre-existing Odoo system. Because noapp-managed account is created, account/data deletion is handled through the merchant'sOdoo system and by clearing the app's local data on the device (§3).

The one record SoftSolvit itself holds is the **device registration** described in §2and §4. To have a device's record (its identifier, login name, platform label andlast-used timestamps) deleted from the licence, email **info@softsolvit.com** from thelicence-holder's contact address. Removing it frees that device's slot, so the app willregister the device again the next time it signs in.

## 7. Children

The app is a business tool intended for merchant staff (adults). It is not directed tochildren.

## 8. Changes

We may update this policy; material changes will be reflected by the "Last updated"date above and posted at the policy URL.

## 9. Contact

Fintech for Software Solutions — info@softsolvit.com9 Ibn Elmoataz, El Hegaz Square, Heliopolis, Cairo 11351, Egypt