Privacy Policy

Privacy Policy

What personal data Cicada holds, why, who else touches it, how long it stays and what you can ask us to do with it. Specific to how the platform actually works.

Last updated · Version 2026-10-28

The short version

  • We collect only what running the platform needs: a username, an email address, a password hash, your work and, for raters, earnings and payout details (bank account, the name on it and PAN) to pay you.
  • Raters also fill in an application profile (contact details, education, work, expertise, languages and availability) so we can match them to projects. Only Cicada admins see it.
  • When you accept our terms and policies we record the version, the time, your IP address and browser, as evidence of what you agreed to. Copies are under Settings, Agreements.
  • Screen sharing during rating sessions stays in your browser. We log only when a session ran and what kind of screen was shared; nothing is recorded.
  • Join the waitlist with just an email address. We write only after you confirm it, and every role email has an unsubscribe link.
  • One sign-in cookie, no analytics, no tracking, and no selling of data.
  • Data is stored in India (Google Cloud, Mumbai). Cloudflare carries traffic and Resend sends our emails.
  • Email [email protected] to see, correct or delete your data. Payment records are kept as the law requires.

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

01Who we are

Cicada (cicadaevals.com) is a human-evaluation platform run by Cicada (“we”, “us”). AI teams send us prompts with model responses; vetted raters compare and score them; QA reviewers check the work; raters are paid per rating.

For the personal data described in this policy, Cicada is the Data Fiduciary under India’s Digital Personal Data Protection Act, 2023 (the “DPDP Act”), and the controller under the EU and UK GDPR where those laws apply to you. You can reach us at:

Cicada

Email: [email protected]

This policy covers the public website, the Cicada app (everything under /dashboard), the waitlist and the contact form. It is written to the DPDP Act, and it also sets out the rights people in the EU and UK have.

02What we collect

What we hold depends on how you use Cicada. We have listed it exactly, by role. If something isn’t listed here, we don’t collect it.

Everyone with an account

  • Username (3 to 64 characters, chosen by you or by the admin who created the account).
  • Email address. Required when you sign up yourself. Accounts created by an admin start without one; you can add or change it in account settings, which asks for your password. We send a link to confirm it, valid for 48 hours, and we record when you confirm it. You need a confirmed address to apply for a role.
  • Password, stored only as a bcrypt hash. We can’t read it.
  • Your role, level, the project you are on, whether the account is active, and a counter we use to end your sessions when you sign out or change your password.
  • In-app notifications sent to you (for example a QA result, an exam result, a payout update, being added to a project, or a change to your bank details).
  • Agreement records: each time you accept our Terms of Service, Rater Agreement or Privacy Policy, which document you accepted, its version, the time, and the IP address and browser details (user agent) you used.

Raters

  • Your application profile, which you fill in after signing up and can edit at any time: your full name, your mobile number if you choose to give it, the city and state you live in, your education (level, subject, institution, years and, if you give it, your grade), your work history (job titles, organisations, dates and what you did), any certifications, links you add (such as LinkedIn or GitHub), the subjects you know and your years of experience, programming languages, the languages you speak, read and write and how well, when and how much you can work, whether you have a laptop or desktop, and anything else you choose to tell us. We don’t ask for documents or files.
  • Work records: which tasks you claimed, when you started and finished, and the time each took.
  • Ratings: your scores, written justifications and rubric answers.
  • Quality records: results on known-answer (gold) tasks, exam attempts and scores, QA verdicts and comments on your work, rejection records, and your quality score and level.
  • Appeals you file, with the reason you wrote and the outcome.
  • Earnings records: every credit, reversal, bonus, adjustment and payout on your ledger, and your payout requests.
  • Payout details: the name on your bank account, account number, IFSC code, PAN and, if you add one, a UPI ID. These are encrypted (AES-256-GCM), and your account number and PAN are shown back to you masked. When you request a payout we keep a masked copy (last four digits) and an encrypted full copy with that request, so we know where that payment was meant to go even if you later change your details.
  • Your signature and declarations: the full name you type to sign the Rater Agreement at the end of the onboarding course; your screen-sharing consent, with its version; and the declaration you tick when you save payout details, with the account-holder name.
  • Screen-share session logs, described in the next section.

QA reviewers

  • The verdicts you give, the reasons you write, and any edits you make to a rating (we keep what the rating said before your edit).

Project managers and admins

  • A record of the sensitive actions you take, such as changing a role, resolving an appeal or processing a payout (see the audit log).

Clients

  • Your account, if we have created one for you, and the task content you send us (prompts and responses). Task content is yours; we process it to run your project. Please don’t include personal data in task content unless the evaluation needs it, and tell us if it does.

People who join the waitlist

  • Your email address and, if you give them, your name, the languages you work in and a note.
  • When you joined, and when you left if you do. The waitlist section explains how it works.

People who use the contact form

  • Your name, email address, organisation, whether you are a client, a rater or neither, your message, and any extra answers you give (data volume, languages, availability).
  • The form is not stored in our database. It is sent as an email to our team inbox, and that email includes the IP address the message came from, which helps us spot abuse.

What we don’t collect

We don’t ask for your postal address, date of birth, Aadhaar or other government ID or photograph, and we don’t track your location. The only identity details we hold are the name on your bank account and your PAN, which raters give us to be paid, the full name a rater types to sign the Rater Agreement, and the name, mobile number (if given), city and state a rater puts in their application profile. The only IP addresses and browser details (user agents) we store in our database are the ones in your agreement records, and our servers don’t keep request logs. We don’t record your screen.

03Screen sharing during rating sessions

To start a rating session, the app asks your browser to share your entire screen. This is the only place screen sharing is used; exams don’t use it.

The video never leaves your browser. It is not uploaded, recorded, streamed to anyone, watched or stored, and no screenshots are taken. What we log for each session is:

  • when the session started and ended, and how it ended (for example, you stopped sharing, you ended the session, or we stopped hearing from your browser);
  • what your browser reported you shared (whole screen, a window or a tab);
  • a “still running” signal from your browser every 30 seconds while the session is open;
  • how many tasks you submitted during the session.

Admins can see these logs for every project, and project managers for the projects they manage. We use them to check that rating work was done in a session, and to look into quality problems.

04The waitlist

Anyone can join the waitlist to hear when a role opens. You give us your email address and, if you like, your name, the languages you work in and a note. We use them only to tell you when a role opens.

  • Joining sends you nothing. We email you only when a role opens, and only because you ticked the box asking us to.
  • Every role email has an unsubscribe link.
  • Admins can see and export the waitlist, and erase an entry when you ask. Email [email protected] to have yours erased.
  • We keep your entry until you unsubscribe or ask us to delete it.

05Why we use it, and on what basis

Under the DPDP Act we process your personal data with your consent, which you give when you create an account, join the waitlist or send the contact form and can withdraw at any time (see your rights), and for the legitimate uses the Act allows, such as meeting our legal obligations. For people in the EU and UK, the legal basis for each purpose is shown below.

  • Purpose
    Running your account and signing you in
    Data used
    Account details, session cookie
    EU/UK legal basis
    Contract
  • Purpose
    Giving raters work, recording it and paying for it
    Data used
    Work records, ratings, earnings records, bank details
    EU/UK legal basis
    Contract; legal obligation for financial records
  • Purpose
    Matching raters to projects that suit their education, experience, expertise, languages and availability, and contacting them about it
    Data used
    Application profile
    EU/UK legal basis
    Contract; legitimate interests (giving each project raters who can do its work)
  • Purpose
    Measuring quality, setting levels and handling QA and appeals
    Data used
    Ratings, quality records, appeals
    EU/UK legal basis
    Contract; legitimate interests (delivering reliable data to clients)
  • Purpose
    Checking that rating work happened in a screen-shared session
    Data used
    Screen-share session logs
    EU/UK legal basis
    Legitimate interests (integrity of the work)
  • Purpose
    Keeping the service secure and investigating misuse
    Data used
    IP address (in memory only), audit log, account details
    EU/UK legal basis
    Legitimate interests (security)
  • Purpose
    Recording what you agreed to, and keeping it as evidence
    Data used
    Agreement records, signature and declarations
    EU/UK legal basis
    Contract; legitimate interests (being able to show what was agreed)
  • Purpose
    Confirming your email address and sending account and application emails
    Data used
    Email address
    EU/UK legal basis
    Contract
  • Purpose
    Telling people when a role opens
    Data used
    Email address, waitlist entry
    EU/UK legal basis
    Consent; legitimate interests (filling open roles)
  • Purpose
    Sending news, new roles and offers to people who said yes at sign-up
    Data used
    Email address
    EU/UK legal basis
    Consent
  • Purpose
    Replying to the contact form
    Data used
    What you put in the form, IP address
    EU/UK legal basis
    Consent; legitimate interests

We don’t sell or rent personal data. The emails we send are:

  • a link to confirm your email address, when you sign up;
  • a password-reset link when you ask for one, and a confirmation after a reset;
  • updates on a role you applied for (application received, shortlisted, accepted or declined, your exam result, and when you can start), sent only to a confirmed address;
  • a copy of each agreement you accept, sent to your confirmed address;
  • an email when a role opens;
  • news, new roles and offers from Cicada, if you left that box ticked when you signed up. Turn it off any time under Settings, Email.

Every role email has an unsubscribe link. Everything else (QA results, payouts, appeals) appears as an in-app notification.

Automatic level changes

On projects where automatic tiering is switched on, a rater’s level is recalculated each time QA reviews their work, from their accuracy on gold tasks and their QA pass rate. A level decides which batches a rater can claim; it doesn’t change their pay. If you think an automatic change was wrong, email us and a person will review it.

06Who can see it

  • Admins can see account details (but not email addresses, which no screen in the app shows), all work and quality records, screen-share session logs, payout requests and the audit log. Only admins can see full bank details, and every time they do it is recorded in the audit log. Admins can also see and export the waitlist, and erase an entry from it.
  • Project managers can see the same work, quality, session and payout records for the projects they manage, with bank details masked to the last four digits.
  • Application profiles are seen only by Cicada admins. Project managers, other raters, QA reviewers and clients never see them.
  • QA reviewers see completed ratings on their own project, with the rater’s username.
  • Other raters on your project see your username, level and task count on the project leaderboard.
  • Clients receive exports of their batches. The full CSV export includes the username of the rater who did each task; the JSONL preference-pair export contains no rater identity.
  • Our service providers, listed in the next section, process data on our behalf.
  • Authorities, if the law requires us to disclose data.

07Service providers we use

These companies process personal data on our behalf, only to provide their service to us:

  • Provider
    Google Cloud
    What they do for us
    Hosts the application and its database, where all account and work data is stored
    Where
    Mumbai, India
  • Provider
    Cloudflare
    What they do for us
    Carries all traffic to the site and app, handles encryption in transit (TLS), and routes email sent to [email protected]. Sees IP addresses and browser details as part of carrying traffic.
    Where
    Global network
  • Provider
    Resend
    What they do for us
    Sends our emails (email confirmation, password reset and password-changed, role application updates, copies of agreements, waitlist emails, and contact-form messages to our inbox)
    Where
    United States

Our source code is built and tested on GitHub; no personal data is sent there. We don’t use analytics, advertising, error-tracking or payment-processing services.

08International transfers

Your account and work data are stored in India. Cloudflare and Resend may process some of it outside India (for example, an email address passing through Resend in the United States, or traffic passing through a Cloudflare data centre near you). The DPDP Act allows this except to countries the Government of India restricts; we will stop using any route that becomes restricted.

If you are in the EU or UK, your data is transferred to India, which does not have an adequacy decision. We rely on the data processing terms of our providers, including standard contractual clauses where they offer them, and on transfers being necessary to perform our contract with you.

09Cookies and browser storage

We set one cookie, access_token, which keeps you signed in for up to seven days. Inside the app we also keep a few small flags in your browser’s local storage, on that device only. They contain no personal data; they remember that you finished or skipped the guided tour, hid a getting-started checklist, or dismissed the “how to rate” tips, and the code on the link you arrived from (like ?ref=linkedin) for 30 days. That code is sent to us only if you sign up, and is saved with your account so we know which post or channel brought you. That’s all. There is no analytics or advertising cookie, and no tracking. Details are in our Cookie Policy.

10How long we keep it

We don’t yet delete anything automatically. In practice:

  • Account, work, quality and notification records are kept while your account exists, and afterwards for as long as we need them to account for work done and money paid.
  • Earnings records, payout records and the audit log are kept for as long as the law requires us to keep financial and accounting records, even after an account is closed.
  • Bank details stay on your account until you change them; the copy kept with each payout request is kept with that financial record.
  • Screen-share session logs are kept with your work records.
  • Agreement records, your signature and your declarations are kept as evidence of what you agreed to, for as long as your account exists and afterwards for any period the law requires.
  • Application profiles are kept while your account exists, and deleted with it. Ask us and we will delete yours sooner.
  • Waitlist entries are kept until you unsubscribe or ask us to delete them.
  • Contact-form emails stay in our team inbox until we delete them.
  • IP addresses used for rate limiting are held in memory only and are lost within hours, or whenever the server restarts.

You can ask us to delete your data at any time by email (see your rights). An account with work or payments on record is deactivated rather than erased, so that those records stay intact; we delete what we are not required to keep.

11How we protect it

In short: passwords are hashed with bcrypt; bank details are encrypted with AES-256-GCM and masked on screen; all traffic is encrypted; the servers accept no direct web traffic; access inside the app is limited by role and project; and sensitive actions are written to an audit log. The full list is on our Security page.

If a breach of personal data happens, we will tell the Data Protection Board of India and the people affected, as the DPDP Act requires.

12Your rights and how to use them

Under the DPDP Act (everyone)

  • to get a summary of the personal data we hold about you and what we do with it;
  • to have it corrected, completed or updated;
  • to have it erased, except what we must keep by law;
  • to withdraw your consent, as easily as you gave it;
  • to have a grievance dealt with by us, and then to complain to the Data Protection Board of India;
  • to nominate someone to exercise these rights if you die or become unable to.

If you are in the EU or UK

You also have the rights to access, rectification, erasure, restriction of processing, data portability and to object to processing based on legitimate interests, and the right to complain to your local data protection authority (in the UK, the ICO).

How to use them

Email [email protected], ideally from the email address on your account, and tell us your username and what you want. We may ask you to confirm it is you. We aim to reply within one month. Withdrawing consent or asking for erasure means we will close your account, because we can’t run it without the data.

Some things you can do yourself: change your email address and password in account settings, edit your application profile, update your bank details on the Earnings page, and read your own ledger, task history, payouts, appeals and rejections in the app. You can see copies of what you agreed to under Settings, Agreements. To leave the waitlist, use the unsubscribe link in any role email; to have your entry erased, email us.

13Grievance officer

If you have a complaint about how we handle your personal data, write to our grievance officer. We will acknowledge it and respond as the DPDP Act and its rules require.

Swastik Tripathi, Grievance Officer

Email: [email protected]

If you are not satisfied with our response, you can complain to the Data Protection Board of India.

14Children

Cicada is for people aged 18 and over. We don’t knowingly collect data from anyone younger. If you believe someone under 18 has an account, tell us and we will close it and delete their data.

15Changes to this policy

When we change this policy we will update the date and version at the top of this page. If you have an account, we ask you to accept the new version; raters can’t take more work until they do. If a change affects how we use data you have already given us, we will tell you in the app before it takes effect, and ask for your consent again where the law requires it.