Security

Security and data handling

For teams deciding whether to trust us with their evaluation data: what protects it, who can see it, and what we don’t do yet.

Last updated

The short version

  • Hosted in India, on Google Cloud in Mumbai. No web ports are open; all traffic arrives through a Cloudflare Tunnel over TLS.
  • Raters and reviewers see only their own project. Project managers see only the projects they manage.
  • Passwords are hashed with bcrypt; payout details are encrypted with AES-256-GCM and every full view is logged.
  • Sensitive actions go to an audit log only admins can read. We list exactly what it covers, and what it doesn’t.
  • No third-party scripts or analytics. Report a vulnerability to [email protected].

This summary is here to help you read the document, not to replace it. Where the two differ, the full text below applies.

01Where your data lives

Cicada runs on Google Cloud in Mumbai, India. The application, its database (PostgreSQL) and its web server run as containers on that machine, and all evaluation data, ratings and account records are stored there.

Uploaded batch files are read in memory and turned into database rows; the files themselves are never saved to disk or to object storage.

02Network and encryption in transit

  • No open web ports. All public traffic reaches the server through a Cloudflare Tunnel, an outbound-only connection. The only port open on the machine is SSH, for administration.
  • TLS everywhere. Connections are encrypted with TLS, terminated at Cloudflare, and plain HTTP is redirected to HTTPS.
  • Security headers on every response: HSTS for one year including subdomains; X-Content-Type-Options: nosniff; X-Frame-Options: DENY, so the app can’t be framed by another site; Referrer-Policy: strict-origin-when-cross-origin; a Permissions-Policy that allows only screen capture, and only on our own origin; Cross-Origin-Opener-Policy: same-origin; and no Server header.

03Passwords and sign-in

  • Passwords are hashed with bcrypt and must be at least 8 characters.
  • Sign-in takes the same time whether or not the username exists, so it can’t be used to find accounts.
  • Password-reset links are single-use, expire after one hour, and are stored only as a SHA-256 hash. The reset form never reveals whether an account exists.
  • Changing your password or bank details requires your current password, with the same lockout as sign-in.

04Sessions

A session is a signed token in one cookie, access_token, marked HttpOnly, Secure and SameSite=Lax, lasting seven days. Signing out, changing or resetting a password, and deactivating an account all revoke every session for that account, on every device, at once.

The API accepts requests only from our own origins (no wildcard), and every action that changes data is a POST, PUT or DELETE request, which the cookie’s SameSite setting withholds from other sites.

05Who can see what

Access is decided by role and, below admin level, by project:

  • Role
    Rater
    Can see
    Tasks on their own project only, and their own work, earnings and payout records.
  • Role
    QA reviewer
    Can see
    Completed ratings on their own project. Can’t review their own work.
  • Role
    Project manager
    Can see
    Only the projects they manage. Can’t assign people to projects, change pay, delete batches, mark payouts paid, see full bank details or read the audit log.
  • Role
    Admin
    Can see
    The whole platform, including the audit log. Every view of full bank details is logged.

Nobody can change their own role, or delete or deactivate their own account. Only the owner-level account can manage other owner-level accounts. Email addresses aren’t shown on any screen in the app.

06Payout details

Raters’ bank details (account number, IFSC, optional UPI ID) are encrypted at rest with AES-256-GCM. On screen they are masked to the last four digits. Only admins can see them in full, to make a payment, and each view is written to the audit log. A rater gets an in-app notification whenever their bank details change.

07The audit log

Sensitive actions are written to an audit log with who did it, when, and what changed. Only admins can read it, and the application has no way to edit or delete entries. What is logged today:

  • Role changes, and level changes (including automatic ones)
  • Accounts created, deleted, deactivated or reactivated
  • Users added to or removed from projects
  • Project settings changes, including pay rate, and project deletion
  • Batch deletion
  • QA edits to a rating, with what the rating said before
  • Gold answers set or cleared
  • Manual balance adjustments and bonuses, with the reason
  • Payout decisions: approved, rejected, marked paid
  • Appeal decisions
  • Changes to a rater’s bank details (last four digits only)
  • Every view of a rater’s full bank details
  • Password reset requested and completed
  • Offline work packets exported and imported

Separately, every money movement (task payment, QA reversal, appeal restoration, bonus, adjustment, payout) is an entry in an append-only ledger, and every failed rating leaves a rejection record with the reviewer and their reason.

Not logged today: sign-ins, QA pass and rework verdicts (they are stored on the rating itself), batch uploads and edits, guideline and rubric-template edits, and in-app password changes. We would rather say so than claim to log everything.

08Rate limiting

  • Sign-in: five wrong passwords for one username locks it for five minutes from that address; thirty failures from one address locks that address for ten minutes.
  • Sign-up, password reset and the contact form: five requests an hour from one address.
  • Password and bank-detail changes: five wrong passwords locks the account’s changes for five minutes.

09Exports

  • CSV exports neutralise spreadsheet formulas: any cell that starts with =, +, -, @, a tab or a carriage return is prefixed with an apostrophe, so a prompt or response can’t run as a formula when the file is opened.
  • The JSONL preference-pair export contains no rater identity.
  • Exports can be produced only by project managers (for their projects) and admins.

10Hardening

  • Containers run as non-root users on read-only file systems, with Linux capabilities dropped and privilege escalation disabled.
  • The application connects to the database with a restricted role, not as the database owner.
  • Interactive API documentation is switched off in production.
  • The servers keep no request logs, so IP addresses and browser details aren’t recorded. IP addresses are used only in memory, for rate limiting.

11Third parties

The site and app load no third-party scripts: no analytics, no advertising, no error tracking. Fonts are served from our own domain. Emails are plain text, with no tracking pixels.

Three providers process data for us:

  • Google Cloud (Mumbai): hosting and database.
  • Cloudflare: network, TLS, the tunnel, and routing of email to [email protected].
  • Resend: transactional email (password reset links and confirmations).

12What we don’t have yet

So you can judge for yourself: Cicada doesn’t yet offer two-factor authentication or single sign-on, holds no third-party certification (such as SOC 2 or ISO 27001), and doesn’t delete data on a schedule; deletion is done on request (see the Privacy Policy). If any of these matters for your project, tell us.

13Reporting a vulnerability

If you find a security problem, email [email protected] with “Security” in the subject. Tell us what you found, how to reproduce it and what it could expose.

While you investigate, please:

  • use only your own accounts, and don’t access, change or keep anyone else’s data;
  • don’t run denial-of-service, spam or social-engineering tests;
  • give us reasonable time to fix the problem before you tell anyone else.

If you do that in good faith, we won’t take legal action against you for the research, and we will keep you updated as we fix it. We don’t run a paid bug bounty.