Trust
Every learning moment can create information.
A book opened. A note written. An assignment submitted. A teacher’s comment. A question answered incorrectly. A pattern that may show where a student needs more support.
That information can make education more connected and responsive. It can also carry real responsibility.
READTYCH is being designed to handle student and institutional information with purpose, restraint, transparency, and appropriate human oversight.
Schools should understand what information is collected, why it is needed, who can access it, how long it is retained, and what happens when it is no longer required.
Students should be able to learn without becoming products.
Educators should be able to use technology without surrendering their judgment.
Institutions should remain informed and involved throughout the relationship.
That is the foundation of the READTYCH approach to privacy and student data.
Privacy in education is not simply a consent form, a paragraph in a contract, or a setting hidden inside an administrator dashboard.
It is a series of choices made throughout the life of a product.
What information does the platform truly need?
Could the same educational purpose be achieved with less?
Who should be able to see it?
What controls does the institution require?
How should the information be protected?
When should it be deleted?
What role, if any, should it play in AI-assisted features?
READTYCH is building privacy considerations into the development of its Digital Book and connected education platform.
The goal is not to collect every piece of information a system can produce.
The goal is to use the right information, for the right educational purpose, with the right safeguards around it.
Student information should be collected or used only when there is a clear educational, operational, security, support, or legal reason for doing so.
Before information becomes part of the READTYCH environment, its purpose should be understood.
More data does not automatically create better learning.
READTYCH is being designed around data minimization. That means limiting collection to information reasonably required to provide, secure, support, evaluate, and improve the services used by an institution.
Schools and districts need enough information to evaluate how the platform handles student data before adoption.
READTYCH aims to provide clear explanations of data categories, purposes, access, retention, service providers, security practices, and institutional responsibilities.
A student, educator, school administrator, district leader, support specialist, and technology administrator should not automatically see the same information.
Access should reflect a person’s role, responsibilities, and institutional authorization.
READTYCH is being designed as an education platform, not an advertising platform.
Student personal information should not be sold or used to create behavioral advertising profiles. Educational information should support learning, administration, security, and approved institutional purposes.
Data can provide context. It cannot fully explain a student.
Academic decisions, interventions, evaluations, and meaningful interpretations should remain under appropriate human oversight.
Information should not remain in a system simply because it can.
Retention should reflect the educational purpose, institutional agreement, operational need, security requirement, and applicable legal obligation connected to the information.
Privacy is not a one-time product feature.
READTYCH intends to review and improve its privacy practices as the platform develops, institutional requirements evolve, and new capabilities are introduced.
The information involved will depend on the product capabilities used, the institution’s configuration, and the nature of the educational program.
This may include a person’s name, institutional email address, student or employee identifier, assigned school, grade level, class, role, and account credentials.
This information helps connect the right user with the right institution, courses, content, permissions, and learning environment.
Depending on the services selected, the platform may process information connected to:
This information should remain connected to a defined educational purpose.
The READTYCH Digital Book is being developed to support handwriting, annotation, diagrams, calculations, written assignments, and other student-created work.
When enabled, this content may be stored, organized, submitted, reviewed, or processed through the READTYCH education platform.
Handwriting recognition capabilities may help convert written work into searchable or structured digital content. Such processing should occur within the permissions and purposes established for the relevant educational program.
READTYCH may need information about the device, software version, account activity, connectivity, performance, diagnostics, security events, and errors.
This information can help maintain service reliability, troubleshoot problems, manage devices, protect accounts, and improve the product.
When an educator, administrator, student, or authorized representative contacts READTYCH, the company may receive contact details and information about the question, issue, or support request.
Support teams should access only the information reasonably needed to understand and resolve the matter.
If an institution uses learning intelligence capabilities, READTYCH may process academic activities and patterns to help authorized users understand progress, incomplete work, recurring difficulties, or possible areas for support.
A pattern is a signal for consideration, not a final judgment about a student.
Information within READTYCH should serve a defined function.
Depending on the services selected by an institution, student information may be used to:
READTYCH should not quietly turn information collected for education into information used for an unrelated commercial purpose.
If a materially different use is introduced, it should be assessed, documented, and communicated appropriately.
The READTYCH platform is being designed around role-based access.
That means access should depend on who the person is, what responsibilities they hold, and what the institution has authorized them to do.
Students should be able to access their own books, notes, assignments, feedback, grades, course information, and relevant learning insights.
They should not receive unrestricted access to the information of other students.
Educators may need access to the students, classes, assignments, submissions, feedback, and academic information connected to their teaching responsibilities.
Their view should support instruction without exposing unrelated institutional information.
Authorized administrators may require broader access for account management, deployment, academic oversight, support, reporting, security, or institutional planning.
The scope of access should reflect their role and the permissions established by the institution.
Access for parents or guardians may depend on the educational setting, student age, institutional policy, applicable requirements, and the capabilities enabled by the school.
Where such access is provided, institutions should determine what information is appropriate to share.
Authorized READTYCH personnel may require limited access for support, security, maintenance, implementation, or other legitimate operational purposes.
Such access should be restricted according to role and business need.
READTYCH may work with carefully selected providers that support areas such as hosting, infrastructure, security, communication, analytics, or technical operations.
These providers should receive only the access necessary to perform their approved service and should be subject to appropriate contractual and security requirements.
An institution should not have to hand over information and hope it is handled correctly.
Schools and districts need meaningful participation in how an education platform is configured and used.
Depending on the product and institutional agreement, READTYCH intends to support controls related to:
The right configuration may differ between an elementary school, high school, university, school district, research program, and government education initiative.
Privacy controls should reflect the environment in which learning actually takes place.
Artificial intelligence may help educators recognize patterns that are difficult to see across hundreds of assignments, handwritten responses, assessments, and classroom activities.
It may also create new questions about accuracy, bias, transparency, privacy, and responsibility.
READTYCH is exploring AI-assisted capabilities that may support:
These capabilities should not turn an automated suggestion into an unquestioned academic decision.
Where AI contributes to grading suggestions, feedback, recommendations, or learning insights, an authorized educator should remain able to review the result.
Educators should be able to correct, question, reject, or report an AI-assisted output.
Student information should not be used for an AI-assisted function simply because it is available. The intended educational purpose should be established first.
Schools should understand which AI-assisted capabilities are available, what information they use, what they are designed to do, and where human review remains necessary.
A learner is more than a grade, a response pattern, an engagement score, or a prediction.
AI may help reveal context. It should never become the entire context.
A connected education platform can help schools see more than a final score.
It may reveal that a student performs well in discussion but struggles with written assessments. It may show that a particular concept is creating difficulty across an entire class. It may help an educator notice incomplete work before it becomes a larger problem.
These insights can be valuable.
They also need boundaries.
READTYCH is developing learning intelligence to support authorized educators and institutions, not to create permanent labels around students.
A learning insight should:
The purpose is to help educators ask better questions sooner.
Not to let a system answer every question for them.
Privacy is often discussed after information has already been collected.
READTYCH aims to begin earlier.
During product development, every proposed information flow should raise practical questions:
Do we need this information to provide the feature?
Could we achieve the same result with less?
Does the user understand why it is needed?
Who requires access?
How should it be protected?
How long should it remain?
What happens if the information is incorrect?
What happens when the student leaves the institution?
These questions help turn privacy from a policy statement into a product discipline.
Student information should not remain indefinitely without a clear reason.
Retention periods may depend on:
When an account, pilot, or institutional relationship ends, READTYCH and the institution should understand what happens next.
Depending on the applicable arrangement, this may include:
The exact process should be defined through the agreement and product capabilities applicable to the institution.
Privacy and security are closely connected.
A clear privacy purpose means little if the information cannot be appropriately protected.
READTYCH is developing its security approach across the Digital Book, user accounts, education platform, integrations, applications, and operational environment.
The security direction may include:
Specific controls, validated assessments, and assurance documentation should be communicated when they are complete and applicable.
READTYCH will distinguish between a planned safeguard and a verified one.
Schools already use learning management systems, student information systems, identity platforms, digital libraries, educational applications, and administrative tools.
Integrations can reduce duplication and make the school day easier to manage. They can also create additional information flows that institutions need to understand.
Before an integration is enabled, schools should be able to evaluate:
An integration should not become an invisible doorway into student information.
It should be an understood and authorized connection.
A pilot is a learning opportunity for both the institution and READTYCH.
It is also a real educational environment involving real people and potentially sensitive information.
Before a pilot begins, READTYCH and the participating institution should establish:
A pilot should begin with clarity, not assumptions.
Institutions should know what they are testing, what information is involved, and what happens when the evaluation is complete.
Questions about student information may come from different people for different reasons.
A student may want to understand what the platform knows about their work.
A parent may want to know how information is being used.
An educator may need help correcting a record.
A technology administrator may need to review permissions.
A school district may need documentation for privacy, legal, security, or procurement review.
READTYCH aims to route these questions appropriately.
In many educational settings, the school or district manages the student relationship and determines how the platform is used. Requests involving access, correction, account management, or educational records may therefore need to begin with the institution.
READTYCH can support institutions in understanding the relevant product capabilities and responsibilities.
READTYCH is progressing through product development and preparing for pilot-focused institutional opportunities.
Privacy practices, contractual commitments, technical controls, product settings, and supporting documentation will continue to develop alongside the platform.
Schools participating in evaluation can help READTYCH understand:
The future of educational technology should not be designed without the institutions responsible for protecting students.
The information will depend on the READTYCH services selected by an institution. It may include account details, classes, assigned materials, notes, annotations, assignments, assessments, teacher feedback, grades, device information, support records, and authorized learning activity. READTYCH aims to limit processing to information connected to a defined educational, operational, security, support, or legal purpose.
READTYCH is being built as an education platform, not an advertising business. READTYCH does not intend to sell student personal information or use it to create behavioral advertising profiles. Specific commitments will be reflected in the privacy notices and institutional agreements applicable to each service or program.
Ownership and control should be addressed clearly in the agreement governing the institution’s use of READTYCH. READTYCH does not intend to claim ownership of student-created educational work merely because that work is stored or processed through the platform.
READTYCH is being designed around role-based access. Students, educators, school administrators, district leaders, support personnel, and other authorized users should receive access appropriate to their responsibilities and institutional permissions.
Where enabled, relevant information may support capabilities such as handwriting recognition, grading suggestions, feedback preparation, learning pattern identification, and resource recommendations. These capabilities should have a defined educational purpose, appropriate access controls, institutional awareness, and meaningful human oversight. Educators remain responsible for academic decisions.
The process will depend on the institution’s agreement, product configuration, and applicable obligations. It may include restricting access, returning or exporting authorized information, deleting information that is no longer required, and retaining limited records where a legitimate obligation remains.
The next page starts here
Schools deserve more than broad promises.
They deserve understandable answers about what information is collected, how it supports learning, who can access it, how AI may use it, how long it remains, and what happens when the relationship ends.
Students deserve technology that recognizes the difference between supporting their education and turning their education into a product.
Educators deserve useful information without losing professional judgment.
Institutions deserve a partner willing to answer difficult questions before deployment, throughout implementation, and as the platform evolves.
READTYCH is building a connected learning environment.
Protecting the people inside that environment is part of the work.