Who Owns Your Data? — Ownership Before AI
A foundation for understanding data on Forwork: ownership, control, permission, visibility, and trust before discussing AI, indexing, or third-party crawlers.
Do not begin with what AI can read
The first question should be who owns the data, who decides how it is used, and under what conditions.
Ownership is different from storage
A platform may store data without owning your professional identity.
Framework: Ownership → Control → Permission → Visibility → Trust
Ownership — who owns the data?
Control — who can create, edit, delete, or update it?
Permission — who can access it and at what level?
Visibility — where does it appear: public, private, or selective?
Trust — can users understand and control the full flow?
Ownership should connect to portability
If users own their data, they should be able to export, move, or stop using the system without losing the identity they built.
Control should be clear for each entity
Profile, Project, Result, Evidence, Letter, and Event may require different control models.
Permission is not a single toggle
Public/Private is often not enough.
Selective sharing, team access, partner access, or machine access may be needed.
Visibility is contextual
A Project may have a public summary with private evidence.
A Result may be shared with a client but excluded from public indexing.
Trust comes from predictability
Before publishing, users should know who can see the content, whether AI can read it, whether third parties can index it, and what changes when settings change.
Applying this on Forwork
A useful model: User/Organization owns → chooses permissions → defines visibility → system enforces access → AI/third-party readability stays within the allowed scope.
Conclusion
Do not only ask, “Can Forwork AI read my data?”
Ask: “Do I clearly own, control, and decide what can be read, by whom, and in what context?”
Ownership → Control → Permission → Visibility → Trust.