Section 7 of the protocol asks where the data will be stored. That answer was settled months earlier, in the data use agreement the district signed: student records remain on university-controlled equipment, and identifiable data may not be transferred to any third party. Nobody argued about the clause at the time. It read like boilerplate.
Then comes the afternoon you actually have the file. 1,842 rows of eighth-grade survey responses, an attendance column merged in from the district system, and a report due to the superintendent in two weeks. The obvious next move is to upload the file somewhere and start working. That move is the one the agreement ruled out before you ever opened the CSV.
The Clause Was Never Boilerplate
Institutional language about data storage tends to turn on one word: transfer. Sending a file to a server your institution does not control is a transfer, and most IRB offices read it that way whether the destination is a research platform, a transcription service, or a general-purpose tool with a free tier. The file does not have to be published or breached. Sending it is the event.
De-identification helps less than researchers expect. A restricted-use dataset often carries its own terms, separate from the consent form, and those terms frequently name the storage location directly. An indirect identifier such as school, grade, and disability status can also re-identify a small subgroup, which is why the agreement covers the whole file rather than the name column.
None of this makes cloud analysis forbidden. Plenty of universities hold enterprise agreements that cover exactly this, and if yours does, the path is legitimate and already paved. What changes is the cost of the question. Without that coverage, using an outside service means a protocol amendment, a security review with campus IT, and possibly a business associate agreement. Three weeks of calendar time, for a step that was supposed to take an afternoon.
What the Machine on Your Desk Already Satisfies
A university-issued Mac with FileVault turned on is, in the plain language of most agreements, the controlled equipment the clause describes. Full-disk encryption, hardware keys held in the Secure Enclave, and device management your IT office already approved. Nothing new to review, because the review happened when the machine was issued.
For years the tradeoff was speed. Local analysis meant waiting, so people uploaded. Apple Silicon closed that gap. A reliability analysis across 1,842 rows and 24 items finishes before you look up from the keyboard, and a full afternoon of recoding, subgroup comparisons, and table building never touches a network.
Analysis That Stays Where the Agreement Says
Quanta is our statistics app for the Mac, written in Swift for Apple Silicon and checked against NIST reference datasets. Open the CSV, run the analysis, read the output. Alpha arrives with item-total correlations and assumption notes in plain language, and the table comes out in APA 7 format. The data stays on the disk it was already on. No account, no upload, no sync.
Quala does the same for interviews. Transcription runs on-device, so a recording of a teacher describing a student by name never leaves the machine. Coding, memos, themes, and the audit trail live in the same local file. ReliCheck Intelligence suggests codes drawn from your own codebook and never applies one on its own, which keeps the coding decisions attributable to a person when a reviewer asks who made them.
Neither app thinks for you. What either removes is the translation between your question and your evidence, and that is the only thing it removes. Choosing the model, defending the design, deciding whether a theme is real: still yours.
Local storage also moves responsibility onto you, and that deserves saying plainly. Encrypted backups, a device you do not leave in a car, and a plan for what happens if the drive fails. Working locally is not automatically safer. Being answerable is the point.
One Sentence in the Protocol
Section 7 becomes short. All analysis will be conducted locally on an encrypted, university-issued Mac; no participant data will be transmitted to external servers. Reviewers stop reading at that line because there is no vendor to evaluate and no transfer to justify.
The practical win is the calendar. No amendment, no security review, no waiting on a signature from a company that has never heard of your study. You had the answer in hand the day the agreement was signed. The software just has to agree with it.
Quanta and Quala are available for the Mac at relicheck.com and on the Mac App Store, with a free 30-day trial.