Security & trust
So here is exactly what we do, and exactly what we do not yet do.
Every event is written once and chained to the one before it. A correction is never an edit — it is a new entry that references the original, and the original never changes.
The chain proves that a record has not been altered since it was written. It does not, on its own, prove that the physical event occurred independently of the device that reported it.
We publish that limitation because it is true, and because a system that overclaims its guarantees is worth less than one that states them precisely. TallyCord makes tampering evident. It does not make false reporting impossible — no system can, and any vendor who says otherwise is selling you something that will not survive a courtroom.
| Standard | Status | Note |
|---|---|---|
| TLS 1.3 in transit | In place | |
| Encryption at rest | In place | |
| Hash-chained, append-only event log | In place | |
| Device-bound operator signing keys | In place | |
| SOC 2 Type II | Not held | Not held. Roadmap item, not a current claim. |
| ISO 27001 | Not held | Not held. |
| Nigeria NDPR / NDPC | To state | [state honestly] |
| EU/UK GDPR | To state | [state position if you have EU/UK data subjects] |
| Penetration test | To state | [state date if done, or 'not yet performed'] |
We are a young company and we will not pretend otherwise. If a SOC 2 report is a hard requirement for your procurement, tell us now — we would rather disqualify ourselves early than waste your time. For buyers whose requirement is evidence integrity rather than a certificate, we are stronger than most vendors twice our size.
Reporting a security issue: security@tallycord.com — we acknowledge within [N] business days and will not pursue legal action against good-faith researchers.