Security and data
Built for institutions that cannot afford a leak
This page lists the controls that are in place today. Certifications will be listed here once they are obtained.
01Controls in place
| Data handling | To build a record, Editorrah stores the writing-process events from a capture session, such as keystroke and clipboard events. This data is not sold and is not shared with third-party advertisers. |
|---|---|
| Encryption | Data is encrypted in transit and at rest. Passwords are stored as salted hashes, and stored credentials are encrypted at the application layer. |
| Record integrity | Records are cryptographically signed. The underlying event log is hash chained, so a later alteration is evident on verification. |
| Access controls | Access is role based, so authors and reviewers see only what their role allows. Requests are rate limited, and security-relevant actions are written to an audit log. |
| Deletion | Personal data can be deleted on request once evaluation is complete. Write to privacy@editorrah.com. |
| Questions | For a security review or a data processing question, write to rahul.ceo@editorrah.com. |