Provenance, scoring and data, in the open.

Provenance, scoring and data, in the open

Trust in a record comes from being able to check it. This page sets out how 7Analytica proves where information came from, how scores are made, and how your own data is protected.

Every record can be traced back

Provenance is not a feature added to 7Analytica. It is how it is organised.

One origin, the repeats that relay it, then capture and seal

• Reference numbers

  Every dispatch, source, report and note has an identifier. It is printed in full and never reused.

• One time zone

  All times are shown in your local time with the zone written out, so a record can be compared with another without converting.

• Origin before repeat

  Each claim is followed to its first appearance. Reports that only repeat it are marked as repeats.

• Captured pages

  Cited pages are captured with the time they were seen. When a page changes, both versions are kept and the difference is shown.

• Seals

  A record can be sealed. A seal fixes its content and time, and any later change is recorded as a new entry rather than a rewrite.

A score is its inputs, shown

Confidence in a claim is built from five named inputs. Each one is displayed beside the score, so you can see which input moved it and weigh it differently if you disagree.

A score is an estimate, not a verdict. It shows the state of the evidence at a given time, with the sample behind each source stated. It does not say that a claim is true.

• Weights are stated

  Each input has a weight, and the weights are shown next to the score they produce.

• Samples are stated

  A source’s reliability shows how many claims it rests on and when it was last reviewed.

• Changes are dated

  When a score moves, the entry that moved it is listed with its time.

• Scores can be wrong

  A score estimates how well the evidence stands. New evidence changes it, and the earlier value is kept.

• Source reliability

  Example
  82

  The source’s measured record: claims later supported, corrections made, sample size and last review.

• Corroboration

  Example
  64

  How many independent origins stand behind the claim, as distinct from how many outlets repeat it.

• Recency

  Example
  91

  How recent the reporting is relative to the event it describes.

• Primary documents

  Example
  55

  Whether a document a reader can open supports the claim directly.

• Framing neutrality

  Example
  71

  How far the wording departs from how other reports describe the same event.

Your data is handled as carefully as the record

This is a summary. The binding terms are in the Privacy Notice and the Terms of Use. Our security programme is designed with recognised standards in mind. We do not claim a certification we do not hold.

• What we collect

  Account details you give us, the notes and preferences you create, and the technical data needed to run and protect 7Analytica. The Privacy Notice lists each category, the reason and the legal basis.

• In transit and at rest

  Data is encrypted in transit using TLS and encrypted at rest. Passwords are stored only as salted, one-way hashes.

• Who can see it

  Access is role-based and limited to what each person needs. Multi-factor authentication is required for administrative access, and access is logged.

• How long we keep it

  Account data is deleted or anonymised within thirty days of closure unless the law requires us to keep it. The Privacy Notice gives the full schedule.

• Your choices

  You can ask to see, correct, export or delete your personal data. Write to us and we will respond as the law requires.

Found a vulnerability? Tell us first

Write to bhuvanchandra@7analytica.com with the details. Good-faith research that follows the rules here is welcome. Please do not include other people’s personal data in a report.

• What to send

  What you found, the steps to reproduce it, the address or page where it occurs and what you think the impact is. A short note is enough.

• What to avoid

  Reading, changing or deleting other people’s data, degrading 7Analytica, and social engineering of staff or users.

• What happens next

  We read every report and replies to the address it came from. We tell you what we found and, when it is fixed, that it is fixed.

• Credit

  If you would like to be credited once an issue is resolved, say so and how you would like to be named.

Have a question about how this works?

Write to bhuvanchandra@7analytica.com for anything that is not a vulnerability report, or use the form.

Contact us · Privacy Notice