Armbrain Security Incident and Breach Notification Terms
What Armbrain will do if a security incident affects data a customer stores in Armbrain.
These terms describe what Volacci Agency, LLC, which provides Armbrain (“Armbrain,” “we,” “us”), will do if a security incident affects data a customer stores in Armbrain. They form part of the agreement between Armbrain and the customer (“Customer,” “you”), including the Armbrain Terms of Service. If these terms conflict with the Terms of Service on the subject of security incidents, these terms control.
Definitions
Customer Data means any information Customer or its authorized users put into Armbrain or connect to Armbrain, including notes, meeting transcripts, email and calendar content Customer authorizes, files, and information Customer stores about its own clients.
Security Incident means a confirmed breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Data while it is stored, sent or processed by Armbrain or a Subprocessor. Unsuccessful attempts that do not compromise Customer Data, such as pings, port scans, blocked sign-in attempts or denial-of-service attacks, are not Security Incidents.
Subprocessor means a third-party service provider that processes Customer Data on Armbrain’s behalf to provide the service.
Discovery means the time Armbrain confirms that a Security Incident has occurred.
Notice to Customer
Armbrain will notify Customer of a Security Incident without undue delay, and in any event within 72 hours after Discovery.
Armbrain will send notice by email to the account owner’s email address on file and to any security contact Customer names in writing. If the Security Incident may affect email delivery, Armbrain will also make reasonable efforts to reach Customer by phone. Customer is responsible for keeping its contact details current.
What the notice will include
To the extent known at the time, the notice will describe:
- what happened, including the date it occurred (if known) and the date of Discovery;
- the categories of Customer Data involved, and the approximate number of records, client Brains and users affected;
- whether a Subprocessor was involved;
- the likely consequences of the Security Incident;
- the steps Armbrain has taken, and plans to take, to contain and fix it and to reduce harm;
- any steps Armbrain recommends Customer take; and
- a named contact at Armbrain for questions.
If some of this information is not yet available, Armbrain will not delay the notice. It will send what it knows and provide the rest as it becomes available.
Updates and final report
Until the Security Incident is contained, Armbrain will update Customer at least every 72 hours, or sooner when there is material new information. Within 30 days after containment, Armbrain will provide a written summary of the root cause, the Customer Data affected, and the measures taken to prevent a repeat.
Containment and remediation
After Discovery, Armbrain will promptly take reasonable steps to contain and investigate the Security Incident, reduce its effects, restore the security of Customer Data, and preserve relevant records and evidence.
Cooperation with Customer
Armbrain will reasonably cooperate with Customer so that Customer can meet its own legal and contractual obligations, including any duty to notify its clients, affected individuals or regulators. Customer decides whether and how to notify its own clients and any individuals about Customer Data. Armbrain will not notify Customer’s clients, affected individuals or regulators about Customer Data on Customer’s behalf without Customer’s prior written approval, unless the law requires Armbrain to do so. If the law requires it, Armbrain will tell Customer first where the law allows.
Subprocessors
When a Subprocessor notifies Armbrain of an incident that is a Security Incident under these terms, the 72-hour notice period runs from Armbrain’s Discovery.
The current list of Subprocessors is published at armbrain.io/legal/sub-processors.
Customer’s duty to report
If Customer suspects unauthorized access to its Armbrain account or Customer Data, Customer will notify Armbrain promptly at security@armbrain.io.
Records
Armbrain will keep a record of each Security Incident, including the facts, its effects and the actions taken, for at least three years, and will give Customer a summary of the records that relate to Customer on request.
Costs and liability
Armbrain will bear its own costs of investigating, containing and fixing a Security Incident. Any other liability arising from a Security Incident is governed by the limitation of liability in the Armbrain Terms of Service.
No admission of fault
Armbrain’s notice of, or response to, a Security Incident is not an admission of fault or liability.
Governing law
These terms are governed by the laws of the State of Texas, without regard to conflict of law principles, consistent with the Armbrain Terms of Service.
Contact
Security questions and incident reports: security@armbrain.io