MAYAThis document describes what we do with the data you entrust to MAYA Enterprise, where it sits, who touches it, and how you get it back or make it disappear. It states only what the product actually does. TW MICRONICS SARL (Yaoundé, Cameroon) is the publisher; any question goes to [email protected].
1. Roles
You are the controller of your workspace data: your contacts, customers, employees and documents. You decide what goes in and what is done with it.
TW MICRONICS SARL acts as processor: we process this data to provide the service, on your instructions, and for nothing else.
We NEVER use one workspace data to train a model, nor to feed another workspace. Isolation is physical: a separate database per customer.
2. Purposes
- run the modules you have opened (sales, purchasing, accounting, HR, projects, websites…);
- receive and send your conversations on the channels you connected (WhatsApp, Telegram, Messenger, email);
- produce assistant answers from your data, according to the autonomy levels you set;
- build your documents (quotes, invoices, certificates, cards);
- run the service: backups, monitoring, and support when you write to us.
3. Categories of data
Depending on the modules you activate: identity and contact details of your contacts and customers, messaging exchanges, commercial and accounting documents, employee data (including, if you enable payroll, pay data), attachments and files you upload.
⚠️ You decide what you put in. The product requests no sensitive data and infers none.
4. Location
Data is hosted in the NETHERLANDS (Meppel, province of Drenthe), on infrastructure rented from Hostinger International Ltd.. Backups are kept on the same server.
⚠️ We say it plainly: an encrypted off-site copy is not yet in place. Current backups protect against a handling error, not against the loss of the server. This page will change the day that is done, not before.
Some processing leaves this infrastructure when you use the features concerned: they are listed on the sub-processors page.
5. Security measures
- physical isolation: one database per customer, never shared logical filtering;
- two-factor authentication required for administration and management roles;
- secrets encrypted at rest with dedicated keys: channel tokens, mailbox secrets, external service keys, social tokens;
- no secret inside export archives: those columns carry a marker and are listed in the manifest;
- partitioning by entity and by role, enforced at every route of the product;
- daily backups that are RE-READ (a written file is not a readable file), kept fourteen days and eight Sundays;
- automatic task log and public status page, which tells a failed task from one that runs and produces nothing.
6. Sub-processors
The full list, with the purpose and country of each, is published on the sub-processors page. It is updated before any new use.
A sub-processor only receives what the feature requires, and only if you use that feature.
7. Retention
Your data is kept as long as your workspace exists: you decide what you erase inside the product.
Social media comments are purged beyond twenty-four months, and revoked social accounts beyond twelve months.
An export archive stays seven days on our servers, then it is deleted: it is a clear copy of your whole workspace.
8. Your rights, and how to exercise them yourself
Access and portability: the "Export my data" screen gives you, without asking us, a complete and reloadable archive.
Erasure: the same screen opens the closure of your workspace, with a thirty-day grace period and a deletion certificate at the end.
Rectification: it happens inside the product, screen by screen.
For a request from a person whose data you hold (one of your customers, one of your employees), you are the one who answers: we assist you on request, at [email protected].
9. Security incident
In the event of an incident affecting your data, we notify you without undue delay, with what we know: what is affected, since when, and what we are doing.
We will never tell you an incident is closed before having verified it.
10. End of contract
At the end of your subscription, your data remains available as long as you have not requested its deletion: a payment default makes the workspace read-only, it erases nothing.
Your export archive remains available throughout.