Enriched reading of the catalogue (once)
- Sent
- Product designations, the category from your software, brand
- Never sent
- Prices, stock, customers, suppliers
Last updated: September 2026
We ask a distributor to let our software read the database their business runs on. That is an unusual thing to ask. This page says exactly what we read, what we send, and what we never do.
Each client company has its own data. Isolation is enforced by the database itself, row by row, not only by application code: a query that forgot to filter returns nothing rather than someone else’s data.
Data is encrypted in transit and at rest. Uploaded files — voice notes, photos, PDFs — are stored under a key that belongs to your company alone.
The account we use to read your database has no write permission. That is not a promise made by our code, which can have bugs: it is a property of your database, which our code cannot work around.
Qotora AI never writes into the software you already use. When a write is useful, it goes through a supported door: the vendor’s official API, its import format, or an order sheet a person keys in.
Connection credentials stay in the keychain of the machine the connector runs on, encrypted by the operating system. They never reach us, and they appear in no log and in no mapping template.
No purchase price and no margin is ever sent to a model: the assistant has no legitimate use for either, and both are role-gated data.
A supplier request never names your end customer or their project. Disclosing it would cost you the deal; that is a commercial risk as much as a privacy one.
Our model providers are bound by business terms with no training and no retention: nothing sent is used to train a model. That commitment is signed before the first client goes live.
| Task | Sent | Never sent |
|---|---|---|
| Enriched reading of the catalogue (once) | Product designations, the category from your software, brand | Prices, stock, customers, suppliers |
| Reading a customer request | The message received: text, voice transcript, image, PDF | The catalogue, prices, stock |
| Choosing a product | One request line and at most eight candidate products | Prices, stock, cost, customer identity, the rest of the catalogue |
| Drafting a supplier request | Product descriptions, quantities, contact name | The end customer’s identity, the project, any price |
| Reading a supplier reply | The text of the reply | Our margins, our sale prices |
| An instruction in the workspace | The line summaries and the salesperson’s instruction | Purchase prices, margins |
Your customers’ names, phone numbers and email addresses; your suppliers’ contacts; your users’ accounts. We collect nothing else, and we never cross your data with another company’s.
For a walk-in customer — someone with no account in your software — the name, phone number and email address your salesperson types are stored with the quote and nowhere else. They are not written to your software, and they disappear with the draft if it is deleted.
On this website, the consultation form records what you type into it — name, company, city, phone, the software you use, rough volume — so that we can call you back. It is passed to nobody else. The site carries no analytics, no advertising tracker and no third-party script.
Three roles: the owner sees everything; the salesperson sees quotes and can send them, but not purchase prices or margins; the stock keeper sees costs and the catalogue, but does not send.
Purchase prices and margins are stripped from the server’s responses for the salesperson role. They are not merely hidden on screen: they are never sent to the browser.
Uploaded voice notes, photos and PDFs expire according to your company’s retention setting. Retention periods are agreed with you and written into your contract.
You can ask at any time for a full export of your data, in a documented format, and for its full deletion, including stored files. Backups are encrypted and expire on their own cycle, stated in the contract.
The sub-processors we use — model provider, hosting and file storage, email sending — are named in your contract.
Where your data is hosted is stated in your contract. If you ask for it to stay in a particular region, we hold to that.
Qotora AI is designed to comply with Moroccan law 09-08 on the protection of individuals with regard to the processing of personal data.
Registration obligations with the CNDP are checked with you before go-live, and the sub-processors concerned are named in your contract.
Every change to an amount, to the identity of a product or to the status of a quote is recorded with its author, its timestamp and the before and after. A manual price override requires a reason, which is kept.
Technical logs, by contrast, contain none of your table data: no customer name, no price, no connection string.
Onboarding sessions are logged: who connected, when, from where, and what was read.
For any question about your data, or to request an export or a deletion: contact@qotora.com.
To report a security vulnerability: security@qotora.com. We acknowledge within two working days. Please never test against a client’s production system.