Privacy Policy
Mexant LLC ("Mexant") builds and operates custom software for its clients. This policy covers the data that software handles on a client's behalf — including any integration we operate with a third-party service such as Shopify, QuickBooks or an email provider.
Who the data belongs to
It belongs to the client, not to us. When a client connects their store or their accounting to software we operate, we are processing their business records on their instruction. We do not sell it, share it with other clients, or use it to train anything.
What we access, and why
- Product and inventory records — names, prices, unit costs, stock levels. Used to show the client their own catalogue and to work out what needs reordering.
- Order records — line items, quantities, totals, dates and status. Used for sales figures and revenue reporting.
- Accounting records, where a client connects them — chart of accounts, costs, invoices. Used to reconcile cost of goods against sales.
We request the narrowest access that does the job. Where an integration offers read-only and read-write permissions, we take read-only unless a specific feature the client has asked for requires more.
Customer personal data
Our integrations are configured not to request customer names, email addresses or phone numbers unless a client has explicitly asked for a feature that needs them. Where order data is analysed, customers are identified by an opaque reference rather than by name. If a client turns on a feature that does require identifying data, it is fetched only for that feature and only while it is in use.
Credentials
Access tokens and API secrets are encrypted at rest using AES-256-GCM, with the encryption key held separately from the database. Once stored, a secret is never returned to a browser — an interface can show that a credential exists and when it was saved, never its value. Credentials are held only for as long as the integration is connected, and are deleted when it is disconnected.
Changes to a client's systems
Software we build does not alter a client's live systems on its own initiative. Any change to a price, a stock level or a public-facing record is proposed as an exact difference that a person approves before it is applied, and every applied change is recorded in an append-only log with who approved it, when, and what the system reported afterwards.
Retention and deletion
We keep operational data for as long as we are engaged to run the software that uses it. On request, or when an engagement ends, we delete it and revoke our access to connected services. A client can disconnect any integration themselves at any time, which revokes our tokens with that provider and clears them from our storage.
Sub-processors
We host on third-party infrastructure and may use third-party model providers for features a client has asked for. These providers process data on our instruction under their own terms. We will name the current providers on request.
Security
Access to client systems is limited to the people working on that engagement. Interfaces holding client data require authentication. We do not put client data in public repositories, and secrets are never committed to source control.
Contact
Questions, access requests and deletion requests: mexantsoftware@gmail.com.
Mexant LLC · 8116 Viadana Bay Ave, Boynton Beach, FL 33473
← mexant.com