Sinyx POS Privacy Policy

Last updated: October 6, 2026

Sinyx POS is a Windows desktop point of sale application provided by SINYX for retailers, sweet shops and small businesses. This policy covers the Windows desktop application. The SINYX website and other products have separate privacy information.

Privacy and POS support contact: engineer.basitkhan@gmail.com

Local business records

Sinyx POS stores normal business records on your Windows device through its bundled local service. These can include business and receipt settings; staff accounts, roles, permissions and password hashes; product images, stock and pricing; customer and supplier names, contact details and balances; sales, purchases, payments, refunds, daily closing and reports; tax settings and fiscal delivery records; activation information and a machine identifier; audit records and local troubleshooting logs. Previously retained local records may also remain in recovery workspaces.

SINYX does not automatically receive your POS database, customer lists, ordinary business reports or backups. Sinyx POS does not include advertising trackers or generative AI features for creating user content. Core functions do not request location, camera, microphone, contacts, SMS, NFC or biometric data.

When information leaves the device

• Microsoft Store: Windows and Microsoft services handle app acquisition, purchases, applicable trials, licensing and Store-managed updates under Microsoft's terms and privacy policy. The app reads entitlement, expiry and product information to determine access. Microsoft handles Store account and payment processing.
• Optional FBR integration: When you configure and enable integration, invoice, seller/buyer tax and related transaction information is sent to your configured HTTPS FBR or tax endpoint. Queued invoices may be processed or retried in the background. Connectivity checks can also send configured fiscal information. Configure only an endpoint you trust. Disable integration to stop normal automatic submission; review queued records and any request already in progress.
• Printing: Receipt, label and report information goes to the Windows printer or configured network printer you choose. Other parties may operate that peripheral or network.
• Receipt sharing: The app creates an image locally and opens Windows Share. The destination application or service you select handles the shared information under its own terms and privacy policy. Sinyx POS does not provide a hosted messaging service.
• Backups and exports: Files go to the location you choose. A network folder, removable drive or cloud-synchronised location can transfer them to its provider. You control subsequent copying, uploading, sharing and deletion.
• Support: Information you choose to send, including screenshots, logs or files, may be used to investigate and answer your request. Review it first and avoid sending unnecessary customer information or credentials.

Licensing

The app reads Microsoft Store entitlement or validates a separately issued SPOS2 activation key. License information and a machine identifier may be stored locally. An inactive entitlement restricts business changes while allowing sign-in, activation, access to existing records and recovery functions. Microsoft handles Store purchases and refunds; SINYX handles support for separately issued licenses.

Fiscal credentials and restored invoices

FBR integration is optional. The app stores endpoint, POS ID and seller/tax settings locally. The security token is protected using Windows data protection for the current Windows account. Legacy readable tokens are migrated to that protection when possible. A token protected under another Windows account or computer may require re-entry; this protection does not encrypt the entire business database.

A normal manual database backup made by this version removes the FBR token and disables integration in the copy. Restoring prepares a checked copy and requires closing and reopening the app. It preserves a local recovery copy of the latest database before replacing records and settings. That recovery copy can retain the Windows-protected token. Older backups can contain unprotected integration credentials. Treat all backups as sensitive.

After a restore, re-enter fiscal credentials and review previously unfinished fiscal deliveries. These require confirmation with the tax service before an explicit retry because the selected backup cannot show submissions made after it was created.

Backups, exports and logs

Backups are manual; this version does not schedule automatic database backups. Backups and exports can contain staff account records, password hashes, customer/supplier details, financial transactions and configuration. These files and the business database are not generally encrypted by the app.

Audit records preserve business history. Troubleshooting logs remain local and may include technical paths, record identifiers, errors and fiscal diagnostic details. No automatic upload to SINYX is included. Review logs before sharing them with support.

Access, retention and deletion

Authorised users can view and change supported records and create backups or exports. Data remains until removed through supported functions, replaced by a restore, or removed from its application-data location. Some transaction and audit records remain to preserve business history. Uninstalling should not be assumed to delete every retained file, export or backup. Remove copies from external locations separately. SINYX cannot directly delete a database it does not host; contact support for help locating local files.

Security

The app uses password hashing, local authentication, current role permissions and a per-run token for its owned local backend. Protect your Windows account, device and administrator access; use disk encryption where appropriate; restrict access to business files, backups and exports; and protect tax credentials and printer/network access.

Children's privacy

Sinyx POS is intended for business use and is not directed at children. A Store content age rating describes content suitability and does not change its intended use.

Changes and contact

We may update this policy when features or data practices change. The current policy is available in the app and on the POS product privacy page. For privacy or POS support questions, contact engineer.basitkhan@gmail.com.