If your LEA does NOT currently have an account with SDPC, click this link to request one.
Utah law requires certain privacy protections to be included when entering agreements with third parties.
The Utah NDPA will meet these requirements. These requirements are triggered when SHARING PII or entering an agreement - CLICKING I AGREE
Is the product listed above in this column?
If so, it is either a State Contract or it has a Privacy Badge.
Adding OTHER types of agreements
Adding OTHER types of agreements
Is the product listed above in this column?
If so, your LEA can subscribe to an established agreement.
Adding an Exhibit E to your registry.
Adding an Exhibit E to your registry.
This is a walkthrough designed for 3rd party providers entering a data privacy agreement with an LEA in Utah. Useful for Data Managers who are initiating agreements with vendors who are new to Utah.
The NDPA is a 20-page document. The great part is, you only have to fill out pages 1, 2 & 3. The vendor does the rest. I often tell agencies to fill out this first part, and then save as. Put it on your desktop as your LEANAME_NDPA and forget about it for now.
On Exhibit A they will provide a detailed description of their services covered by this agreement.
On Exhibit B they will select all data collected while using their resource. These data elements also line up with the metadata dictionary components.
Exhibit C is DEFINITIONS
Exhibit D won’t be signed but is a model document to be used if the LEA needed. Our law states that you need to be in Direct Control and be able to delete data, this Exhibit is included in the agreement so that way you don't need to come up with your own way to request deletion meaning that the vendor will accept this as a formal directive.
Exhibit E: Again if you're the first one to get a DPA with a vendor you would just need to put your LEA Name and date at the top, and the vendor will do everything else. They will put their designated representative here and the representative that would be notified of subscribing LEAs here;
It’s important to remember that you will not sign Exhibit E if you are originating the agreement. You would not be originating and also subscribing onto your own agreement terms. The only time you will complete Exhibit E is if an agreement already exists in Utah and you are subscribing.
Exhibit F which is data security requirements. This will be completed by the vendor.
Exhibit G is supplemental for state terms. So, rather than each state having their own agreement, this exhibit allows for those specific changes to be made here, instead of changing the body of the agreement. You can see that this page isn’t necessary for those of us in Utah, as this standard agreement meets all of Utah’s requirements, meaning we don’t ever need to add supplemental terms.
Exhibit H is for the vendor. If they would like to make any changes, they would but anything here.
Step 1 - Teacher Requests an App/Website/Extension
Step 2 - Search the Utah Applications Menu
Step 3 - Search the National Database on SPDC
*You must be logged in
Step 4 - Send an NDPA to the Vendor
Include Model Email Language
Step 5 - Adding a new agreement
What does a complete agreement look like?
Step 6 - Renewals