What You Can't Say: IP, Confidentiality & Academic Freedom
Module 4 · Voice, Identity & Boundaries

What You Can't Say: IP, Confidentiality & Academic Freedom

Three real boundaries — student privacy law, employer confidentiality, and institutional IP policy — and why the right move is always to ask your specific institution, not to guess from this lesson.

This Lesson Cannot Tell You Your Institution’s Specific Rules

Every instructor teaching under this course’s model sits inside at least two, often three, overlapping sets of rules: your academic institution’s policies, your day-job employer’s confidentiality obligations, and general law around student privacy. This lesson names the three real categories of boundary and the questions you should be asking — it deliberately does not, and cannot responsibly, tell you what CityU’s specific current policy says, because that’s a fact to get from your own institution, not from a course lesson that may not reflect this week’s actual policy language.

⚠️ Common Pitfall: Assuming a Course Lesson Is a Substitute for Reading Your Actual Contract

The single most important habit this lesson can teach is: when in doubt, ask your department chair, HR, or general counsel’s office the specific question, in writing, before you publish — not “is content creation okay,” but the precise scenario (“can I use an anonymized version of a case study from my day job,” “does my faculty appointment’s IP policy cover a YouTube video I make on my own time”). A specific written answer from your own institution outranks any general framework, including this one.


Boundary One: Student Privacy

The Family Educational Rights and Privacy Act (FERPA), 20 U.S.C. § 1232g (1974) is U.S. federal law protecting the privacy of student education records, and it applies regardless of platform or good intentions. The safe practice, well within FERPA’s spirit even where exact application varies by circumstance:

  • Never share identifiable student work, grades, or specific classroom incidents publicly without explicit, informed consent — and get that consent in writing, not verbally.
  • The “repeated question” content source from Module 3 is almost always safe, because it’s about the question, generalized, not about a specific identifiable student who asked it.
  • If a real classroom anecdote is central to a piece of content, anonymize aggressively — change enough identifying detail that the student themselves wouldn’t recognize the reference, not just that a stranger couldn’t.

Boundary Two: Employer Confidentiality

If your industry expertise comes from a current employer or client relationship, standard confidentiality and IP assignment agreements — the kind most industry professionals sign as a condition of employment — typically restrict what you can say about specific:

  • Proprietary systems, codebases, internal tools, or architecture details
  • Client names, deal terms, or anything covered by an NDA
  • Non-public company data, even in “anonymized” form, if it’s specific enough to be identifiable

The safest reliable pattern used by practitioners who publish successfully: teach the pattern, not the instance. A general architecture principle, a category of bug, a class of negotiation tactic — abstracted away from the specific company, system, or client — is usually well clear of confidentiality obligations that a verbatim internal example would violate. When genuinely unsure, the correct move is asking your employer’s legal or HR contact directly, in writing, before publishing — not inferring an answer from a course lesson or a colleague’s informal opinion.


Boundary Three: Institutional IP and Academic Freedom

American Association of University Professors (AAUP). (1940, reaffirmed 1970). 1940 Statement of Principles on Academic Freedom and Tenure.

The AAUP’s foundational statement establishes the widely-adopted principle that faculty should have freedom in research, publication, and, within professional standards, in discussing their subject in the classroom — a principle most U.S. institutions reference in their own faculty handbooks, though the specific implementation varies considerably by institution and by employment type (tenure-track, adjunct, affiliate).

What this means practically for your content:

  • Academic freedom principles generally protect your right to discuss and teach your subject matter — they do not automatically resolve who owns a specific piece of content (a video, a course-derived framework) you produce, which is usually governed by a separate institutional IP policy, not the academic freedom statement itself.
  • IP ownership questions get more, not less, complicated when content is derived from material you were paid to develop for a course — a slide deck built for a CityU course and a spontaneous LinkedIn post are not obviously governed by the same rule, and institutions differ on where that line falls.
  • Adjunct and affiliate faculty, in particular, should not assume their IP situation mirrors what a tenure-track colleague has heard informally — appointment type frequently changes the specific answer.
💻 Code Lab: Three Questions to Ask Before You Publish at Scale

Before your content habit (Module 2) becomes a regular practice, get specific, written answers to:

  1. To your institution: “Does my faculty appointment’s policy address ownership of content I create independently, derived loosely from what I teach?”
  2. To your employer (if industry content is involved): “Is there a category of general, non-proprietary insight from my role I’m clear to discuss publicly, and where exactly is that line?”
  3. To yourself: “If a specific piece of content named a real student, a real client, or a real proprietary system, would I still be comfortable publishing it?” — if the honest answer is no, that’s the anonymization test from Boundary One and Two, applied before publishing, not after a complaint.
🧠 Knowledge Check

An instructor wants to make a video walking through a debugging approach they use at their day job, illustrated with a real incident from a client's system. They're unsure whether this crosses a confidentiality line. What's the evidence-aligned next step, based on this lesson?

Reveal Answer & Explanation

Ask their employer’s legal, HR, or direct manager contact the specific question in writing before publishing — and in the meantime, default to teaching the general debugging pattern rather than the specific client incident. This lesson’s core position is that neither a general framework nor an instructor’s own judgment call is a substitute for a specific answer from the party actually holding the confidentiality agreement. The “teach the pattern, not the instance” default is the safer starting point precisely because it’s very likely to be fine without needing an answer at all — but it doesn’t remove the value of getting an explicit answer once the content habit becomes a regular practice, rather than relying on an assumption that was never confirmed.


Up Next

With voice and boundaries in place, Module 5 turns to the audience-building side of the loop: what the research on parasocial relationships says about why consistency, not virality, is what actually compounds — and how much of the content-to-enrollment link is solid evidence versus plausible correlation.