Website privacy information

This website presents Softwexa products and services. Request forms collect your name, email, optional company, product or project context, subject and message, together with your consent and a submission identifier. The request service first saves the submission in a private request store and returns a receipt that states how it was handled. When the Dolibarr connection is enabled, enquiries, demo requests, quote requests and support requests are recorded separately in Softwexa's CRM. Its database and application documents are stored on Softwexa's server. The receipt distinguishes local storage from confirmed recording in the CRM.

Request records and receipts

The development preview keeps its request store on the development computer. A private receipt key permits a recording-status check and, after confirmed CRM recording, a check of the ticket number and current status. The check does not return your name, email address, message or internal support notes. Keep the key private. The latest opaque request ID and key are kept in this browser tab's session storage so you can move from the form to the support page. No form contents are stored in the browser, and the receipt key is never included in a page URL.

Submitting an email address does not grant access to a client account or existing support records. Authorised staff review enquiries before associating them with customer records or preparing a commercial proposal. Business request records and shared documents follow the retention arrangements agreed with Softwexa. Do not include passwords, credentials, payment information or sensitive customer records in these forms.

Email enquiries and support

General enquiries go to [email protected]; support email goes to [email protected]. Email is handled through Purelymail and the sender's email provider. When the support mailbox collector is enabled, incoming support messages are saved in the CRM as ticket records or as replies to an existing ticket. The CRM's outgoing email connection also uses Purelymail. A website request receipt confirms recording status; it does not confirm that an email was sent or delivered. Include the business information needed to discuss your enquiry and avoid sending credentials or sensitive production data.

Your invited client account

Softwexa staff create client invitations and link each account to its authorised business records. The client area uses an HTTP-only session cookie for sign-in. A client account can retrieve its shared ticket conversations, projects, proposals and documents. Internal staff notes are excluded from the public ticket conversation. Invitation codes are kept only in the current page's memory during activation and removed from the address bar. Passwords, account records and conversations are not saved in local storage or session storage. The client area and document downloads do not send website measurement events.

Website measurement

When enabled, Softwexa's own measurement service counts public page views, product views, demo and enquiry link clicks, form starts and confirmed request records. Bounded campaign source, medium, campaign label, referring hostname and the public landing-page path provide context for a request. Full page URLs, query strings, search text, form contents, email addresses, IP addresses and client credentials are not stored in the measurement database. Campaign values should contain business campaign labels rather than personal information. Validators reject email-like values, full URLs and obvious phone or UUID identifiers; validation cannot identify every possible personal label.

The first public source context is kept only in this browser tab's session storage. No measurement cookie or persistent browser identifier is created, and no third-party analytics script is loaded. Do Not Track and Global Privacy Control signals disable browser measurement. The private measurement store keeps aggregate counts and hashed event and request identifiers for at most 90 days. CRM sales records provide the actual discussion, proposal and project stages; a page view alone does not count as a sale. Local preview counts are separated from production website activity. Hosting and network providers may process their own access logs.

Your shopping basket

Adding a product to the basket creates an HTTP-only shopping session cookie and saves your product selection, displayed prices and catalogue version in the private shopping store. In the development preview this store stays on the development computer. A basket does not require an account and does not create an order or payment. The basket can be updated or cleared by removing its items, and its session expires automatically. Downloads require a separately fulfilled order.

Questions

For questions about information you share with Softwexa, contact [email protected].