Agreements and Data Protection

You can view the End-User Agreement on the FORT Robotics website.

You can view the OEM Supply and License Agreement on the FORT Robotics website.

You can view the Data Processing Agreement on the FORT Robotics website. The Data Processing Agreement sets out how FORT Robotics handles personal data on your behalf when you use FORT Manager.

The rest of this appendix summarizes what personal data the Pro Series and FORT Manager hold, and what you can do about it. It is a summary for integrators and administrators. The agreements above are the binding documents; where this appendix and an agreement differ, the agreement governs.

Personal Data in FORT Manager

FORT Manager holds account information for the people in your organization. When you add someone to your organization you supply their email address and choose a role, and FORT Manager records their membership of your organization.

Table 1. Personal Data Held by FORT Manager
Data	Where It Comes From
Email address	You supply it when you add the person to your organization.
User Role	You choose one of Admin, Config Manager, Device Manager, or Operator.
Organization membership	Recorded when the account is created.

The following list outlines the different user roles:

Admin: Manage all aspects of FORT Manager, including users.
Config Manager: Create, edit, and delete both configurations and devices; Apply firmware and configurations to devices.
Device Manager: Enroll, edit, and delete devices; Apply firmware and configurations to devices.
Operator: View and apply firmware and configurations to devices.

On the Users page, roles are colour-coded so you can scan access levels at a glance, and the role chips above the list filter to one role at a time.

Who is responsible for what

Your organization decides who gets a FORT Manager account and what role each person holds. Under data protection law that makes your organization the controller of your users' personal data. FORT Robotics operates the platform on your behalf, which makes FORT the processor. The Data Processing Agreement sets out the terms of that relationship, including how FORT assists you when one of your users exercises their rights.

Where the Data is Held

FORT Manager runs in the hosting region.

Note:

FORT Robotics uses other companies to help operate FORT Manager. Before adding or replacing one of them, FORT tells you. For more information, see Sub-processor Change Notifications

Personal Data on the Devices Themselves

Pro Series devices do not hold FORT Manager account information. Personal data reaches a device only where you put it there, in fields whose contents you choose:

Configuration names and device names.
Custom Display Text Line 1 through Line 4, the text an application sends to an SRC Pro screen. For more information, see SRC Pro User Display Text String Message.

Important:

Text you send to a device travels over the machine's CAN bus or serial link as part of a control message. Those links are internal to the machine and are not protected in the way that the safety radio link is. Do not put a person's name or other personal data in a device name, a configuration name, or custom display text.

API Key Expiry

On the Organization page, each API key shows its expiry state. A key with an expiry date set is shown in green; a key that never expires is shown in red.

Note:

A key that never expires is a standing credential. If it is disclosed it stays valid until someone notices and revokes it. Set an expiry on every key, and treat a never-expiring key that holds the Admin role as something to fix rather than something to note.

Use the search box and the role filter above the list to find keys in a large inventory.

Note:

An expired key stops working. If a script or a CLI login that worked yesterday is refused today, check the key's expiry state before anything else. For more information, see Logging In.

API Key Roles

An API key carries a role that determines what it can do, set with PUT /v1/organizations/{orgId}/apiKeys/{keyName}/role. The role set for API keys is wider than the role set for users:

Table 2.
Role	Users	API Keys
Operator	Yes	Yes
Device Manager	Yes	Yes
Config Manager	Yes	Yes
Admin	Yes	Yes
Service	No	Yes
Key Manager	No	Yes

Note:

Because the two sets differ, the role filter on the Users page and the role filter on the API keys list do not offer the same choices.

Sub-Processor Change Notifications

FORT Robotics uses other companies — sub-processors — to help operate FORT Manager, for example to host it. Before FORT adds a new sub-processor or replaces an existing one, FORT notifies its customers, so that you have the opportunity to review the change and object to it before it takes effect.

To receive these notifications, subscribe to the sub-processor notification list on the FORT Robotics website.

FORT gives at least X days' notice of a change.

If you object to a change, follow the process in the Data Processing Agreement. Your rights on objection, including any right to terminate, are set out there.

Note:

Make sure the person who receives these notifications is someone who can act on them. The notification period only helps if it reaches your data protection contact rather than the engineer who set up the devices.

Removing a User

When someone leaves your organization, or asks you to erase their personal data, remove their FORT Manager account using the steps outlined below.

Log in to FORT Manager. If you're using the FORT Manager Desktop App, confirm you have online connectivity.
Navigate to the Users tab on the left navigation.
Select the FORT Manager account targeted for removal.
To find an account in a long list, filter with the role chips above the list.
Note:
An invitation that has not been accepted is not an account. Outstanding invitations are counted by the badge on the Pending tab and are withdrawn from there, not through this procedure.
In the Actions column, select Delete. Alternatively, you can select the FORT Manager account and navigate to that account's page containing the name, profile image, email address, and user role. Select Delete in the top, right corner to remove the account from FORT Manager.

To remove a FORT Manager account using the FORT Manager API interface, use DeleteAUser. For more information, see FORT Manager API: DeleteAUser.

Note:

FORT retains all account information indefinitely when it is deleted via FORT Manager desktop app, web app, or FORT Manager API. For more information, contact FORT support at support@fortrobotics.com

Note:

Removing a user from FORT Manager has no effect on data you have already exported. Downloaded log files, configuration files, and support ticket attachments stay wherever you put them

Information You Send to FORT Support

When you file a request on the Customer Support Portal, or email support@fortrobotics.com, you typically send some or all of the following:

Device serial numbers and model numbers.
Configuration names and device names, which you chose.
Log files retrieved through the FORT Manager Desktop App. For more information, see Using Logs
Screenshots, which may show account names or email addresses.

FORT handles what you send under the Data Processing Agreement. Even so, review an attachment before you send it. Device logs are designed to be shared whole — they are sized to attach to an email or a support request — so send the complete log rather than an extract, and apply the smallest-amount principle to screenshots and other material instead.

Note:

If a support request needs data you would rather not attach to a ticket, say so in the request and ask support how to send it.