A provider's record is a current, dated account of the adults it sends into your buildings: screening status, abuse-prevention training, proof of insurance, the agreements your organization requires, and a row for each instructor. Every line shows a status, the date it was current, and its source.
The provider keeps the record. It orders its own screening through its own screening partner, uploads its own certificates, signs your agreements, and decides which hosts may see the result. enrops is the software that holds the record and shows it; it is not a party to any check.
Your organization receives a read of status: what each line says, as of which date, from which source. You do not receive a background check report, any student or family data, or a promise about any person. Your packet still sets the requirements, and your office still makes the decision.
Written for general counsel, risk managers, HR and insurance pool contacts at a city, district, library or community education program.
Five kinds of line, each with an owner and a date. When every line your packet asks for is current, the record shows host-ready for your organization, as of the date shown. Host-ready is a status measured against the requirements you already wrote; it is not a certification.
Status shown with each provider's consent. enrops displays verification status from the provider's screening partner; it does not run or certify checks.
The provider. A host sees a provider's record only after that provider chooses the host. Screening is ordered by the provider through its screening partner, which handles the disclosures and authorizations with each instructor and any dispute of a result.
A provider can withdraw a host's access at any time. From then on, that host's view shows "record withdrawn" with the date, and the host no longer sees the provider's status or any update to it. The host keeps only its own notes, its provider list and the dates on which it read the record; enrops keeps a log of that access. Treat a withdrawn record the way your process treats any missing document in a packet.
Information about the provider's adult instructors only: names, and the status, date and source of each line, with the training certificate, the insurance certificate and the signed agreements. No student or family data, and never a background check report. A host reading a record sees the provider, not the families it serves.
Stripe (payments), Supabase (database and backend), Resend (transactional email) and Netlify (hosting), all in the US, as listed in the published DPA, plus the provider's screening partner, when the provider connects one. The DPA commits enrops to at least 30 days' notice, and an opportunity to object, before adding or replacing a subprocessor.
Under the DPA, enrops notifies the provider without undue delay, and within 72 hours, after becoming aware of a personal data breach affecting its data. Within the same window, enrops also notifies any host whose access to an affected record is involved.
The DPA, the parent notice, the security overview and the host terms are published on this site. To request a countersigned copy of the DPA, email hello@enrops.com.
No. The record sits alongside the checks you already run. Anything your organization runs itself, such as district fingerprinting, stays with you and is marked host-run on the record.
Reading a record does not move your organization's duties to enrops or to the provider. A current, dated record shows what was on file for each adult and when, which helps your office document the care it took. Your own packet still governs what you require and how you decide. enrops does not give legal advice; your counsel reads the record against your own requirements.
Only the host terms, and hosts pay nothing. You use a record for your own decisions about the provider who shared it, share it only with the people who need it for that purpose, and keep it confidential. Disclaimers, liability limits, Oregon law and dispute terms follow the enrops Terms of Service.
One page for your counsel, risk manager or insurance pool contact: what the record holds, who keeps each line, and what enrops never does. It arrives by email.
Prefer to walk through a record with us? Book a 30-minute briefing.
No. enrops is not a consumer reporting agency and does not furnish consumer reports. The provider's screening partner runs the screen and keeps the report; enrops displays its status, date and source.
No. A record holds information about the provider's adult instructors only. There is no student or family data in it, and a host reading it sees the provider, not the families the provider serves.
The provider's screening partner runs each check and keeps the report. Your packet and agreement say what the provider must have on file, and your office still makes the decision, alongside your own checks. A record that shows host-ready means every line you ask for is current against your packet as of the date shown, from the sources named on each line. It is a status, not a certification or a promise about any person.
From that point your view shows "record withdrawn" with the date, and you no longer see the provider's status or any update to it. You keep your own notes, your provider list and the dates you read the record. Treat it as you would any missing document in your packet and follow your own process.
A countersigned copy of the published DPA is available on request at hello@enrops.com. A host does not need its own data addendum to read a record, because it receives no personal data beyond the record's lines about the provider's adult instructors. If your policy calls for your own addendum anyway, send it to the same address.
Yes, when they need it to help you evaluate the provider who shared it and they keep it confidential. The host terms allow sharing inside your organization and with your own outside counsel, auditors and insurer or risk pool for that purpose. Republishing or sharing it beyond that is not permitted.
Respond under the law that applies to you. Where that law allows, the host terms ask you to give the provider prompt notice before releasing anything, so it can respond.
Oregon law, with disputes handled under Section 14 of the enrops Terms of Service: informal resolution first, then arbitration seated in Multnomah County, Oregon. A public body that cannot accept those terms under its own law can ask for a written agreement at hello@enrops.com before reading a record.
This page explains how the record works. The enrops Terms of Service, the Data Processing Agreement and the host terms govern. Nothing here is legal advice.
Status shown with each provider's consent. enrops displays verification status from the provider's screening partner; it does not run or certify checks.