Documentation isldata.app

Architecture and Data Security

Last updated November 16, 2026

1. Why this document exists

ISL Data was built and is managed by a core development and operations team. This statement covers:

Separate from these protocols and practices, our Terms of Service govern our assumption of risk, liability, and your rights to your data.

2. Who we are

ISL Data is built bit by bit and run by a small, dedicated team of researchers and engineers. As a user you have direct access to the people who build the system. Good data security is a shared practice: we see it as a data culture we build together with the projects we serve.

3. What ISL Data is, and where data are held

ISL Data is a data capture, cleaning, management, analysis, and reporting system. The moving parts:

ComponentWhat it doesWhere it runs (ISL-hosted)
Data Viewer applicationWeb app for access control, import, review, edit, create, analyze, and audit functionsDigitalOcean (region: SFO3)
MongoDB databaseStores records, users, views, audit log, sessionsDigitalOcean (region: SFO3)
Object storagePhotos, audio, and other binary attachmentsAmazon S3 (region: us-west-1)
Data system integrationA variety of third-party digital collection tools that feed into the database (ODK Central, ESRI Survey123, Google Forms, KoBoToolbox)Each platform runs on its own host, operated by its vendor or by you — not by ISL (see below).

Resources we integrate with. ISL Data currently facilitates automatic data retrieval from Open Data Kit (ODK), Google Forms, ESRI Survey123, and KoBoToolbox, and accepts standard spreadsheet and CSV files. The integrations retrieve data into a designated ISL Data workspace; they do not establish a live link to remove, edit, or archive anything in your data collection platform. The use of MongoDB for ISL Data allows the system to be highly flexible and source-agnostic.

The security of data before it reaches ISL Data is governed by the data collection service vendor — Google for Google Forms, ESRI for Survey123, your KoBo server's operator. We do not enforce access control, retention, or deletion inside those systems. If your data is sensitive, consider collecting with encrypted forms, which most data collection apps allow.

4. Data security

Authentication

ISL Data uses passwordless email sign-in. When you navigate to the database, the system requests an email address. If the email address matches a registered user, a single-use, signed link is sent to that email; links expire after 5 minutes. Following the link establishes an ISL Data browser session. Passwordless email sign-in means there is no password theft and no account sharing, unless via a shared email account. It ensures that users can quickly enter the system, no matter how infrequently they need it, with an email account they use every day.

For standard users, an email inbox is the credential. Anyone with persistent access to a registered user's mailbox can sign in to ISL Data as that user; however, damage is limited to that user's access: they can see and alter only objects they have been granted access to, and all their actions are recorded in the audit log that administrators can see. We highly recommend that every ISL Data user enable multi-factor authentication (MFA) on the email account associated with ISL Data.

If you require an additional password entry mechanism, please contact support at info@insitulabs.org.

A browser session stays active while you use it and ends after 5 days of inactivity; then you must sign in again. Every sign-in attempt — including attempts using email addresses that aren't registered — is recorded in the audit log with the IP address and browser used.

Authorization — workspaces and per-object access control

Data is isolated into workspaces, each presenting a separate database. A user is a member of specific workspaces and sees nothing outside them. Within a workspace, access is granted by administrators to each individual object — per source, per view, per report, per dashboard — with separate read and write permissions. A user can be given write access to exactly one data source and nothing else.

Access is default-deny: new users see nothing until granted access by a workspace administrator.

Encryption

Attachments

Photos and other media are stored in a private AWS S3 bucket and are never served from a public URL. Each request generates a short-lived pre-signed link (default 60 seconds) scoped to that one object. Copying an image URL out of the app does not create a shareable link.

Audit logging

The built-in audit system records:

The log keeps the previous value of every changed field, so any record edit or import can be undone from the audit log by an administrator. Changes to attachments (photos, audio) are the exception: edits or deletions cannot be undone in this way. Audit records are append-only through the web application; they are not editable through the user interface.

Operational practices (ISL-hosted)

5. Data retention, deletion, and portability

6. Solutions to common threats

ThreatRealistic scenarioSystem solutionsYour responsibility
Stolen or borrowed credentialsA collaborator's email account is compromised, or a shared field email is used by several peoplePasswordless links expire in 5 min and are single-use; sessions expire after 5 days of inactivity; all logins auditedMulti-factor authentication (MFA) on every user's email; one account per person; do not leave stale users on the workspace
Lost or stolen field deviceA tablet or phone with unsent form submissions is lostDigital form data already submitted is secured by the third-party collection service and additionally by ISL DataDevice passcode + full-disk encryption; submit digital forms as soon as possible
Over-broad internal accessEveryone in an organization can see and edit the data of every internal groupComplete workspace isolation; per-source/view/report read and write permissions; default-deny access for new usersGrant minimum permissions; review the user list regularly; keep the number of workspace admins small
Accidental or malicious data damageA bulk edit or import overwrites good recordsFull audit trail; imports and edits are reversible; archive-only with full restore capability; automatic backupsUse views rather than editing sources where possible; inform the ISL support team quickly
Data leaving via exportA CSV of everything ends up on a personal laptop or in a shared driveExports and downloads are logged with user and time; attachment links expireSet an internal rule for where exports are saved
Server compromise via unpatched softwareA known vulnerability in a dependency or the OS is exploitedPatch cadence, dependency scanning, minimal exposed surface, no framework version disclosure, firewalled databaseNothing, if we host. Everything, if you host — see Section 9
Temporary loss of serviceThe application is flooded and becomes unavailableProvider-level network protection; this is an availability risk, not a confidentiality oneUse of third-party collection tools means collection is unaffected; sync resumes when service is restored
Third-party source systemsData is exposed inside a collection platform we do not operate, before it ever reaches usOutside our control; however, ISL Data retains a secure copy within the controls outlined in this statementSecure those accounts under that vendor's terms; for sensitive projects, encrypt submissions if possible
Insider access by ISL staffAn ISL super administrator reads your dataSee Section 8Pick a hosting model that matches your requirements

7. Recommendations for all users

Security is a shared responsibility. Each recommendation below is in your control and will reduce risk:

8. Access by ISL system administrators

Two levels of "administrator"

When subscribed to an ISL Data hosted plan, technical staff are able to access your workspace to provide critical technical support. A system that is completely inaccessible to our team requires self-hosting; refer to Section 9 to learn about the security and risk consequences of self-hosting. Our Terms of Service (Section 4.4) define that system administrators are prohibited from reviewing, altering, exporting, or sharing any aspect of your data without data-security cause or unless expressly requested by you. In rare cases, such as a subscriber introducing malware that would compromise their workspace as well as others, system administrators will inform subscribers and take immediate safety actions in accordance with the severity of the data threat. For any other reason — e.g. poor system performance related to your workspace — system administrators must notify you and request permission to inspect and correct any issues. When granted permission, an ISL system administrator can:

These capabilities are necessary to ensure the system works reliably for you and for all other users. Except in extenuating data-security circumstances, your data are accessed only when approved, by core technical staff, at times that do not interfere with your operation, and with an issue completion report provided to you.

Functions of the system administrators

System administrators may not:

Is administrator access recorded?

All in-app actions by global administrators are recorded. Once you give approval, you will see an ISL system administrator added to your user list during an active support request, and the system will record their actions. Actions taken by an ISL administrator who is a member of your workspace are audited exactly like any other user's. This is the standard practice, with one exception: "Guest" mode.

A "Guest" mode exists for system administrators for detailed repair or system debugging without polluting project audit history. The effect is that you will not see system administrator actions while in Guest mode. Our staff will always contact you before accessing your workspace, except in extenuating circumstances (e.g. major security threats). Supplemental audit logs of system administrator activity associated with your workspace are available on reasonable request. In these instances, database and object-storage access is outside application logging but does appear in infrastructure/provider logs, which can be provided on reasonable request.

9. Self-hosting

Self-hosting may be necessary when data-sovereignty requirements, sensitive human-subjects data, or government or institutional policy does not allow external support or access under any circumstance. Self-hosting is also common for a university, agency, or other institution with its own advanced IT team. In this case, code to run the ISL Data platform is available for a one-time, single-use licensing fee.

If you are considering this option, please be aware of the following technical responsibilities — not only at installation, but also as IT environments evolve over time.

An unmaintained self-hosted instance is less secure than a maintained hosted one, and it degrades silently. If no named person at your institution owns this work with budgeted time, self-hosting is a high-risk option. Institutional IT departments with reliable capacity are an excellent reason to self-host.

Middle options (for enterprise users). On a case-by-case basis, we will consider: (a) hosting in a region or provider account you specify; (b) deploying into infrastructure you own while we operate it under agreement; or (c) splitting the hosting — for example, you self-host ISL Data while we run your data collection server, or the reverse. If neither standard option fits your institution's policy, ask.

10. Incident response and vulnerability reporting

If we have a security incident affecting your data, we will tell you what happened, what data was involved, what we have done, and what you should do — without undue delay and in any case within 72 hours of confirming it — while we remedy the situation as quickly as possible.

To report a vulnerability, email data@insitulabs.org.

11. Where we're heading

Where we are today

What we are improving next

12. Our commitment

We review our security practices at least annually, tell you when something material changes, and welcome your questions and suggestions.