Legal
Data Processing
These terms describe how Amnen Suite processes personal information on behalf of a customer that subscribes to the hosted Service. They apply together with the SaaS Terms of Service and the Privacy Policy. If a signed data processing agreement is in place for your organization, that signed agreement controls where it differs from this page.
1. Roles
The customer is the controller of the personal information it puts into its workspace, or it processes that information on behalf of its own client. Amnen Suite is the processor. We process that information only to provide, secure, and support the Service, and as the customer’s administrators instruct through the product.
For our own website accounts, billing contacts, and marketing enquiries, we act as controller. That activity is described in the Privacy Policy, not in this page.
2. What we process
Customer Data may include names, work contact details, identification numbers the customer chooses to store, invoices, payments, stock records, attendance, leave, payroll inputs, and files the customer uploads. The exact categories depend on the products the customer enables. We do not require special-category data. If a customer chooses to store it, the customer is responsible for having a lawful basis.
We also process limited account and log data needed to run the workspace: user identifiers, sign-in events, IP address, and diagnostic logs. Those records help us authenticate users and investigate faults.
3. Instructions and purpose
Our instructions are the customer’s configuration of the Service, the actions its users take, and the subscription agreement. We do not sell Customer Data, and we do not use it to train public models or to advertise third-party products. We may use aggregated, de-identified statistics about how the Service performs, provided those statistics cannot identify a person or a customer.
4. People who handle the data
Access inside Amnen Suite is limited to staff and contractors who need it to operate, support, or secure the Service, and who are bound to confidentiality. Support staff open a workspace only when the customer asks for help or when we must investigate a security incident.
We use infrastructure, email, and payment providers as sub-processors. They process Customer Data only under written terms that require confidentiality and security. We will give a customer a current list of sub-processors on request to [email protected], and we will tell subscribed customers before we add a sub-processor that will handle Customer Data in a new way.
5. Security
We protect Customer Data with access control, encryption in transit, network separation appropriate to the hosting environment, backups, and logging. We review access when roles change. These measures are designed for a multi-tenant business application. The customer remains responsible for the strength of its own user passwords, for who it invites, and for the devices its staff use.
6. International transfers
Customer Data may be stored in the region agreed for the workspace and may be accessed from other countries where our support or infrastructure providers operate. Where a transfer is restricted by law, we use a lawful transfer tool, such as standard contractual clauses, and additional safeguards where those are required.
7. Retention and deletion
We keep Customer Data for the life of the subscription. After the subscription ends, the customer can export it for 30 days, unless a shorter period is required by law or the customer asks us to delete it sooner. We then delete the workspace data from active systems and from backups as those backups expire on their normal cycle.
Billing records that identify the customer’s organization, rather than its end customers or employees, may be kept longer where tax or accounting law requires it.
8. Requests from individuals
If a person asks us for access, correction, or deletion of information that a customer stores in the Service, we will direct that person to the customer unless the law requires us to respond ourselves. We will help the customer answer the request by providing the export and admin tools in the product, and by reasonable additional assistance.
9. Incidents
If we become aware of a personal-data breach affecting a customer’s workspace, we will notify that customer without undue delay, describe what happened as far as we know it, and describe the steps we are taking. The customer is responsible for notices to its own users and regulators, except where the law places that duty on us directly.
10. Audits and contact
Once a year, or after a documented incident, a customer may ask for a summary of the security measures that apply to its subscription. We will provide that summary, or a relevant third-party report if we have one, rather than unrestricted access to multi-tenant systems. Requests and questions go to [email protected].
