BA Internet · Five commitments
A principle is not a fine sentence. It says what a system must not do and which human rights it must protect.A principle names what a system must not do and which rights it must protect.
BA Internet Principles are not ethical labels added after a product is built. They are commitments made from the beginning: do not reduce a person to a user, data to ownerless material, a model to a judge, an interface to a neutral screen or privacy to a setting.
People · Data · Models · Interfaces · Privacy
Why principles?
Tools and brands change. The questions that protect human rights and responsibility remain.
Today we may use a chat model; tomorrow another agent or device. A principle neither blesses a product nor rejects every innovation. It helps us ask again how a tool sees people, what data it takes, what it recommends, how it shapes attention and who remains accountable when it fails.
A stable principle does not stop thought as tools change; it helps us remain dynamic in the right direction.
A useful distinction
A principle is not a badge of approval. It is a commitment carried throughout use and production.
Mechanical compliance
A condition added at the end
- Checked only after the product is finished
- Left entirely to technical or legal teams
- Closed by a one-time approval
- Hidden from the people who use the system
BA Internet
A shared commitment from beginning to end
- Asked while the purpose is chosen
- Shaped with the people who will be affected
- Revisited as tools and settings change
- Explains appeal, correction and exit
Five commitments
Each principle stops a different reduction; together they protect the human place in digital life.
A person is not a user
A person is more than clicks, a profile or system input. People carry purpose, speech, objection, judgement and responsibility.
Read the human principleData concerns privacy and rights
Data is not ownerless raw material. It requires a real need, a clear purpose, minimum collection, permission, limited retention, access and deletion rights.
Read the data principleA model cannot speak on anyone’s behalf
A model produces outputs and estimates. It does not judge on behalf of a person, institution, library or truth. Sources and human review remain visible.
Read the model principleInterfaces carry attention and decision
Showing, hiding, ranking and recommending are not neutral. An interface should make choices and consequences clear rather than manipulate people.
Read the interface principlePrivacy is not a setting
Protection should not be buried in long menus. A system begins with minimum data, safe defaults, limited access and a clear way out.
Read the privacy principleWho are these principles for?
The same principle opens different responsibilities for the person using a tool, the Builder and the institution.
The person using the tool
Should understand why something is recommended, what data is taken, where an output ends and how to leave—and should be able to object and seek correction.
The Builder making it
Should define purpose, sources, data permission, model authority, interface effects, error ownership and maintenance from the beginning.
Schools, households, institutions and partners
Do not transfer responsibility simply by buying a tool. They set limits, oversight and clear accountability for children, families, workers and people receiving a service.
How do the principles work together?
A learning tool for a child needs all five principles, not only one.
This everyday example shows why the five commitments are not separate checkboxes.
01 People
The child’s curiosity, growth and own voice remain central; the tool does not reduce the child to a score, profile or source of engagement.
02 Data
Only necessary learning records are kept; child and household data do not quietly move into unrelated uses.
03 Models
A model may offer answers and exercises; it does not replace a teacher, parent, friend or religious guide.
04 Interfaces
The interface does not capture attention through endless use or variable rewards; it supports the child in stopping, thinking and asking a person.
05 Privacy
Safe defaults, household visibility, limited access, clear deletion and a way to end the relationship exist from the start.
For any new digital project
Test the five principles through six shared questions.
What real need does it serve?Is the need described by people and the field, rather than by technical possibility alone? Who is affected, and where do they have a voice?Are children, families, workers, professionals or communities merely data sources—or participants in the decision? Which rights and data must be protected?Are purpose, permission, minimum data, retention, access, transfer and deletion clear? What may the machine recommend or change?Are the model’s limits, authority to act, human approval and the path of reversal understandable? What does the interface bring forward?Are choice, attention and consequence clear? Is there fear, dependency or hidden manipulation? Who carries maintenance and correction?Is someone responsible for errors, appeals, updates, restricted access, deletion and ending the system?
A promise shared as a MİLLET
Principles are not an internal document for a technical team. They are an open promise among the people who share a digital space.
Native-language circles, professionals, child and family guides, young Builders, designers, data stewards and affected people examine the principles together. No single application is the final representation for every place and time; it is reviewed and corrected as real consequences appear.
Constants protect direction; tajdid keeps searching for the right application as the field changes.
Review the principles
Would you like to examine a digital project through these five commitments?
Shared BA Internet review circles are still being prepared. You may tell us about the real need, the people affected and the principle at stake. This is not yet an active compliance service, certificate or programme offer.