Sensitive evidence handling

What you upload

• Event logs, sign-in exports, endpoint alerts, email and pasted text. Each file is hashed with SHA-256 as it arrives and stored under an identifier NEMUQU generates, never under its filename.
• Files are read as data, never executed. Archives are refused rather than extracted; formats NEMUQU does not read are named as such.
• Parsed events keep the text of each original record alongside the normalized fields, so a finding can always be traced to what the log said.
• Before pasted text is sent, the browser checks it for recognizable secrets such as API keys, tokens and private keys. The check can miss secrets and is not data-loss prevention.

Personal data and credentials inside evidence

Logs routinely contain user names, email addresses, IP addresses, host names and sometimes passwords or tokens typed into command lines. NEMUQU stores them as part of the case because the investigation depends on them. It does not scan for or mask personal data in uploaded files. Upload only what you are authorized to share, and remove what the investigation does not need. Do not upload classified information, Controlled Unclassified Information or health records.

Who can see a case

• Only members of the organization that owns it. Access is checked in the same database query that loads the case; another organization's case answers as if it does not exist.
• Owners see every case. In restricted mode, other members need a read or edit grant for the case's client. In legacy mode, every member can see organization cases.
• Row-level security is switched on in the database but is not a second tenant boundary: the API's database role is privileged, and isolation is enforced by the API.
• PastePile Labs LLC has no support tool for viewing customer cases. Operators with infrastructure access can reach the database directly; the application does not restrict that access.

What leaves NEMUQU

• Hosting, storage and email providers process data to run the service. They are listed on Subprocessors.
• AI prioritization, only when a member asks: finding and observation text, never files. See AI use.
• Enrichment lookups, only when a member asks: the single indicator shown in the preview. Internal addresses and host names are refused.
• Delivery to your own systems, only when your organization turns it on and a member approves one handoff note.
• Exports and reports you download.

Integrity

Every original file is hashed with SHA-256 when it arrives, and each case can export an integrity bundle that pairs its JSON report and evidence manifest with SHA-256 digests. That lets you check later that a report and its manifest have not changed. It does not prove who wrote them or what they conclude, and it is not a forensic chain-of-custody record: NEMUQU does not attest to how the files were collected before upload.

Removing evidence

• Ephemeral cases remove the original files right after processing; the parsed records stay until the case window ends.
• Owners, and members with edit access to a case, can delete it. Storage is cleared first; if that fails, the case stays and the deletion is reported as incomplete.
• Retention windows remove cases and original files automatically. Backup copies follow their own schedule.

Details: Data retention and deletion.

Last updated 2026-10-15.