Skip to main content
Security and privacy

Built so that even we can't read a report

Each company's reports are encrypted with its own key, reporter identities are sealed with another, and SpeakUpSafe's own tools can only count. Here is how, and where the data goes.

The case list: anonymous reports are marked and never show who filed them
The case list in the demo company, where anonymous reports never show who filed them, and how the audit log shows a change made outside the app.

What it does today

A key for every company

Report content, messages and files are encrypted with AES-256-GCM, using a separate key for each company, itself wrapped by a master key.

Identities sealed apart

Who reported is kept in a separate vault, sealed with its own key. A confidential name opens only with a second person's approval, and the reporter is told.

An audit log that shows any change

Every action on a case, in admin and by automation goes into an append-only log where each entry carries the fingerprint of the one before. The chain can be checked at any time.

SpeakUpSafe sees counts only

Our console reads through a database role that can only return counts. Support can open a company's settings only with its admin's consent, for a set time, with every action logged, and never a case.

Files handled with care

Each upload is checked by its content, stripped of hidden details such as location, fingerprinted, kept in private storage, and every download is logged.

Kept only as long as needed

Retention per company and per category (7 years by default), then anonymised or deleted. A legal hold pauses it. Data requests have their own register with the legal due dates.

The law

The law it helps with

DPDP Act 2023

What it asksReasonable security safeguards, erasure once the purpose is served, and the rights of the people the data is about.

What the product doesEncryption per company, retention per category, a register of data requests with their due dates, and an employee's data exported or erased from admin.

EU Directive 2019/1937, Art. 16 to 18

What it asksThe reporter's identity kept confidential, personal data handled under the GDPR, and records kept no longer than needed.

What the product doesSealed identities, need-to-know access inside the case team, and retention that runs by itself.

GDPR, Art. 32

What it asksSecurity suited to the risk, including encryption and the ability to show it works.

What the product doesEncryption at rest per company, the audit chain check, and a controls register mapped to ISO/IEC 27001 and SOC 2.

CERT-In directions, 2022

What it asksLogs kept, and cyber incidents reported within 6 hours.

What the product doesCase team sign-ins are logged for this, and referrals carry the CERT-In deadline. Reporters' internet addresses are never kept.

A summary, not legal advice. Your lawyers will know which rules apply to your company.

Where the data goes, said plainly

  • Reports, files and backups are stored in the Mumbai region of India.
  • Pages reach people through Cloudflare's network, which sees visitors' internet addresses, as any such network does. SpeakUpSafe doesn't keep a reporter's.
  • Notification emails go through an email service. They carry an address and a short sentence, never report content.
  • If a reporter chooses the browser's online speech service, Google or Apple hears that speech. Speech on the device, or typing, sends nothing anywhere.
  • AI on the server is off unless a company switches on a model it chooses. Saathi, the assistant on every page, runs in the browser and never sees a report.
  • Controls are mapped to ISO/IEC 27001 and SOC 2. That is not a certification, and we don't claim one.

See it with your own questions

A walkthrough of the screens on this page, set up around your company.