Security & Privacy
Review how information is handled, who is responsible for it, and the evidence your school needs. Keep implemented safeguards, formal documents, and your evaluation questions clear.
Verified public-website controls
These controls describe the public marketing website and inquiry form. Evaluate operational application controls separately with current product evidence.
Additional operational control details
[PLACEHOLDER — VERIFIED SECURITY CONTROL COPY PENDING OWNER APPROVAL]
Formal security, privacy, procurement and contractual materials are being prepared for customer review.
Start with your school
Identify the workflows you want to support, the people who need access, and the information those workflows require. Involve your technology, privacy, and operational stakeholders before introducing student records. Initial product conversations can use fictional examples.
Identify who needs to submit information, review records, manage work, or administer the workspace. Discuss role permissions, school and district boundaries, sensitive-record access, and how access is changed or removed.
Ask to see evidence for the access controls your use requires. A role label or interface screenshot is not a substitute for verification.
Establish the information needed for each approved workflow and the purposes for which it may be used. Include entries, attachments, support interactions, and any additional services involved in handling that information.
Define unnecessary or particularly sensitive information that should stay outside the proposed deployment.
Request the relevant details about hosting, processing locations, service providers, authentication, data protection, and attachment handling.
Match each important requirement to current documentation or other appropriate evidence.
Discuss retention, correction, export, deletion, and the handling of information when service ends. Clarify responsibilities, any record-preservation requirements, and the process your school would follow.
Agree on what your school needs to retain, retrieve, or remove before deciding how to use the service.
Include security incident contacts, notification arrangements, backup and recovery practices, support access, and the agreements needed for the proposed use.
Record unresolved questions, the evidence needed, and who will resolve them.
Bring school leadership, technology staff, privacy or legal reviewers, procurement, and the people responsible for the workflows into the conversation. Use your existing district requirements as the starting point.
Keep product fit, technical evidence, and contractual approval visible as separate decisions.
Before the next step
Explore the product while keeping your school's review process in view.
Yes. Use fictional scenarios to explore the product, and bring any requirements that could affect whether it is suitable for your school. A demonstration does not replace your approval process. Prepare for a Lindenmark Ops demo.
Do not submit student names, incident details, medical information, credentials, or other sensitive records through the public inquiry form or general inquiry email. Describe your question without identifying an individual.
No. Those documents must describe the actual service, information practices, and responsibilities that apply. Use the documentation status above when planning your review.
