Aramis:Build employer terms
2026-10-17
These terms cover every Aramis:Build employer tool: the Requisition Compiler, the workforce planner, and team capability campaigns. You use them on behalf of an organization. Nearshore Cyber keeps the requisitions you compile, keeps no workforce plan, shows your organization Free campaign results only in aggregate, and may contact you about Aramis:Build. Where Team is enabled, its recorded manager sees only the named information described below and in the participant notice. None of it is a hiring decision.
The agreement
By accepting these terms you agree to them on behalf of the organization you represent, and you confirm that you may do so. If you cannot, do not use Aramis:Build.
Aramis:Build is operated by Nearshore Cyber USA, LLC ("we"). These terms are between your organization and us. The individual Aramis:Insight terms continue to apply to your own account and to any assessment you take yourself.
Who can use Aramis:Build
Every Aramis:Build tool requires a signed-in account with a verified business email address. Personal and temporary email services are not accepted; a company address is accepted whoever hosts its mail. A business address does not, by itself, give access to any organization or show that you may act for one.
If your business address is refused, you can ask for a review. We keep the request and any note you add, and a member of Nearshore Cyber staff decides it. A request grants nothing until a decision is recorded, and an approval applies only to the address or domain it names.
What the Requisition Compiler is, and what it is not
The Requisition Compiler turns a draft requisition into a Requisition Contract: its individual requirements, the official NIST NICE Framework v2.2.0 statements you confirmed, ownership and timing decisions, an assessment plan, and the decisions still open. Suggestions come from matching the words in your text against the official framework text. A suggestion becomes a mapping only when you confirm it.
It does not grade a requisition, declare a job impossible, evaluate candidates, or validate a selection procedure. Alignment with the NICE Framework is not evidence that a selection procedure is valid.
What we keep from the Requisition Compiler
We keep the requisition text you paste, the title and outcome you enter, every decision you record, and the Requisition Contract compiled from them, tied to your account. We keep them so you can return to them and so we can prepare a conversation with you about the position.
Do not paste personal data about candidates or employees into the Requisition Compiler, nor secrets, incident details, customer data, or other information your organization has not authorized you to share. The tool is for describing a position, not for evaluating a person.
You can see everything we hold about your account through a data subject request, and deleting your account deletes your compiled requisitions with it.
The workforce planner
The workforce planner compares the hours a team's responsibilities need with the hours its resource groups have, and the options for closing the difference. It runs in your browser. Nothing you enter in it is saved on Aramis servers: a reload clears the plan, and the file you export is the only record of it. We cannot recover a plan you did not export.
The planner describes work and resource groups, not people. Do not enter employee names, pay, candidate data, incident details or customer data. Its figures are arithmetic on the numbers you enter: a closed workload gap is not adequate staffing, hours removed are not payroll savings, and the help request it drafts is not sent to anyone.
Free aggregate campaigns
For Free aggregate campaigns, Nearshore Cyber sets up an Aramis:Build organization and names its administrators. An administrator creates campaigns over published Aramis roles and invites people to take the assessment for a role. Aramis does not email the invitations: the administrator shares each invitation link with the person it was created for.
For Free aggregate campaigns, your organization and Nearshore Cyber are independent controllers of the personal data in a campaign. Your organization controls its decision to invite people and its own invitation list. Nearshore Cyber controls the assessment and computes the campaign aggregate on each participant's own consent, which the participant gives to Nearshore Cyber directly. Apart from the status of its own invitations, your organization receives aggregate output only. Nearshore Cyber does not process personal data on your organization's behalf, and the two are not joint controllers.
In a campaign, the invitation list is the only information about other people that you enter: one work email address per person. Enter nothing else about them. Nearshore Cyber keeps each address with its invitation so that the invited person can accept it.
What your organization undertakes in a campaign
When your organization runs a campaign, it undertakes to:
- Invite only people it works with, at their work email address, and only with their knowledge.
- Treat participation as voluntary. Declining an invitation, not finishing the assessment, or withdrawing later carries no consequence for the person.
- Use campaign results only to plan team capability, such as training, hiring, and how work is covered.
- Never try to identify a person or work out any person's result from the totals, including from a change in the totals after someone finishes or withdraws, and never combine the totals with other data to do either.
What your organization sees in a Free campaign
In a Free aggregate campaign, your organization's administrators see:
- Which invitations are still waiting to be accepted, with their links.
- For each role, how many people were invited and how many have completed the assessment.
- For each area of a role, once enough participants are counted in it to reach the campaign's minimum, the team's average result and the number of people it is based on.
What your organization does not see in a Free campaign
In a Free aggregate campaign, your organization does not see any person's individual result, answers or score. Aggregates are computed when the page is read, from the people whose consent stands at that moment.
An area stays hidden until it reaches the campaign's minimum. That minimum keeps thin results off the page; it does not make the totals anonymous, which is why the undertaking not to identify anyone or infer anyone's result from them matters.
What Free campaign participants are told and agree to
Before taking part in a Free aggregate campaign, each participant sees what your organization will and will not see. A participant's agreement is recorded with Nearshore Cyber as separate consents: a required consent to have their result counted in your organization's aggregate and, only if the participant ticks a separate box, consent to be contacted by Nearshore Cyber about your organization's invitations. Each can be withdrawn on its own at any time. A person who withdraws from the aggregate is not counted in any aggregate shown after the withdrawal.
A participant sees their own full results in their Aramis account, as with any Aramis assessment.
Consented named results in Aramis:Build Team
Team is separate from Free aggregate campaigns. Where Team is enabled, the recorded manager of a group, with current administrator membership in that organization, sees each participant's name, invited email address and assessment progress. Teammates and other administrators do not receive that view.
While a participant shares results under the current Team notice, the recorded manager also sees the participant's completed assessment self-ratings, per-area results and missed-statement list, and team summaries built from the results participants share. Older permissions do not expand to include self-ratings. Questions, individual answers, item identifiers and answer keys are not disclosed.
Permission applies to the recorded manager role of that one group in that organization. If the recorded manager changes, the successor has the same view under the participant's current permission and the same access requirements; no fresh acceptance is needed solely for that change. The former manager loses access. This creates no permission across groups, organizations, purposes or tiers.
Before joining, a participant reads and acknowledges the Team notice. They can withdraw the manager's view of their results from My Team at any time. The manager then sees that the view was withdrawn and continues to see assignment progress, but no longer sees the shared results. Participants keep access to their own results.
Team results are not anonymous. They are evidence about the work the assessments cover, not a measure of job performance. The organization's voluntary-participation and capability-planning undertakings above still apply. Accepting these employer terms does not give participant permission or broaden an existing grant.
Contact about Aramis:Build
By accepting these terms you agree that Nearshore Cyber may contact you, at the email address on your account, about Aramis:Build and about any requisition you compile. We record this consent separately, as its own purpose, and you can withdraw it from your dashboard or from the Requisition Compiler page at any time; withdrawing it does not delete your compiled requisitions. Accepting a later version of these terms does not restore a contact consent you withdrew; you can restore it from your dashboard.
To follow up on a requisition, we record you as a contact in RecruiterFlow, the applicant tracking system Nearshore Cyber uses for its own recruiting, hosted in the United States. What is transferred is your name, your account email address, the organization implied by that address, and the working title of the position you compiled. The requisition text and the Requisition Contract are never transferred. The transfer happens only for a contract you export, only while your contact consent stands, and at most once per contract; withdrawing consent stops any further transfer, and you can ask us to remove the contact record at contact@project-aramis.com.
We do not sell contact data and we do not add you to marketing lists on the strength of this acceptance. Marketing mail has its own separate opt-in.
Your responsibility
Your organization remains responsible for the positions it defines, the requirements it publishes, the plans it adopts, the selection procedures it runs, and the employment decisions it makes. A Requisition Contract and a workforce plan are working drafts you author; we provide the method and the framework text.
Aramis is measurement, not certification. Any hiring verdict is made by people.
Changes
If we change these terms in a way that matters, we will ask you to accept the new version before you use Aramis:Build again. Acceptances are dated and kept.