ReportLog
Documentation menu

Data and privacy

Everything a ReportLog site stores, how it is protected, how long it is kept and how it is removed, for operators writing a privacy policy.

This page describes what the software does. Which providers a site uses, and how its operator set it up, decides the rest; a site's own privacy policy is its operator's to write. See Legal notices and privacy.

What is stored#

DataStored asKeptRemoved by
A report's answersSealed, in the database; published only when approved and allowedFor good: it is the recordNever deleted. Can be withdrawn from public view.
A reporter's email addressEncrypted under a key of the report's own, itself encrypted under CONTACT_KEY; stored apart from the reportUntil erasedThe reporter, from My reports or the confirmation email's link: destroys the report's key
A report filed before its address was confirmedA pending submissionUntil the confirmation link expires (90 days)The nightly sweep job
Files: the originalEncrypted under a key of the file's own, itself encrypted under FILES_KEY, in object storageUntil erasedAn administrator, by destroying the file's key
Files: the published copyRe-encoded, with metadata removedWhile publishedWithholding or refusing it, or the reporter switching off publishing their files
Reporter permissionsA log of every changeFor good, as historyNot removed: it records the reporter's own choices
List entries: the personal halfIn the database, with addresses as keyed hashesLIST_PERSONAL_DAYS (365 days unless changed, or never)The nightly lists-sweep job, or the person's erasure link
List entries: the restIn the databaseFor goodNot removed
AccountsEmail address, role, second factor, membershipsUntil deletedThe person, from their account
Sign-in codes, sessions, invitations, unlock tokensHashedUntil they expireThe nightly sweep job
Journalist alert subscriptionsAddress and chosen statesUntil removedThe person, from the link in every alert
Email update subscriptionsAddress, frequency, logbooksUntil stoppedThe person, from the link in every email
Illegal content noticesThe notice and the decisionFor goodThe sender's name and address are blanked once the decision is sent
Evidence requestsThe request and the files it broughtFor goodThe moderator's message is replaced with a fixed sentence a year after it was sent
Staff recordsWho decided what, who opened what and why, who granted whatFor goodNot removed: they are the audit trail

What is not stored#

Where data leaves the server#

ToWhatWhen
The email provider (Scaleway or an SMTP server)Every email: confirmation links, sign-in codes, notifications, alertsWhenever the site sends one
The object storage providerEncrypted backups; files, if the site takes themNightly, and as files arrive
The timestamp authority (DFN by default)The day's list of chain heads: fingerprints onlyDaily
The transparency log's git hostsThe same list and its timestamp, public by designDaily
GitHubNothing about anybody: the server fetches code from itAt deploy, and in the daily update check
Error tracking, if turned onErrors, scrubbed to an allowed list of fieldsOnly to Bugsink on the same server

Backups#

The nightly backup is the whole database, encrypted with age to the public keys in BACKUP_AGE_RECIPIENTS before it leaves the server, sent to a bucket with an upload-only key. Reporters' addresses in it are still encrypted under the contact key, which is not in the backup. Expiry of old copies is set on the bucket.

Requests from people#

See this page's source