Security and data

What we hold, who can touch it, and what we do not claim.

Written from what the system actually does. Where something is not true yet, this page says so rather than leaving it out.

Where your data lives

  • Where it sits

    The application and the database run on one AWS region in Mumbai, India, and files sit with Cloudflare R2. We cannot keep a company's data inside another country today, so we do not offer it — if your rules require that, tell us before you sign up.

  • Files

    Documents, CVs and Drive contents are held in object storage separate from the database. Nothing in Drive is served by a public link — every download goes through a signed URL that expires, so a copied address stops working.

  • Signing in

    There are no passwords. Sign-in is a one-time code to your email, so there is no password database to leak and nothing to reuse from another breach. Sessions are cookies scoped to the application's own origin.

  • In transit

    Everything travels over TLS. Writes carry a double-submitted token, so a request forged by another site cannot borrow your session. Public endpoints are rate limited per address.

Who inside your company can see what

  • Permissions are separate, not bundled

    Seeing salaries, handling billing, assigning support tickets and administering the workspace are four different permissions. Being senior does not grant them; being granted them does.

  • An employee is not shown their score

    Reviewers rate out of ten. The employee sees a letter grade — and the API does not send the number to them at all, so it cannot be read out of the browser.

  • Project access is a grant, not a blanket

    Somebody on a project can see that project. There is no company-wide read that comes free with having an account.

  • Changes are attributable

    Edits to a person's record keep who made them and when. Deletion is soft, confirmed, and kept for thirty days before it goes.

What happens to a CV

This is the part people ask about first, so here is the whole path.

  1. 1Somebody applies through your careers page. The file lands in your workspace's own storage.
  2. 2Its text is sent to the model together with that job posting — and nothing else. No other candidate, no other posting, nothing from the rest of your workspace.
  3. 3The model returns a score, a summary and one line per requirement, each quoting the sentence it judged that requirement on.
  4. 4All of it is written onto the application, including what the call cost, so you can check the working later.
  5. 5The model keeps nothing and trains on nothing. The CV stays in your workspace until you delete it.

Nothing is ever auto-rejected. The score orders the field. Every decision about a person is taken by a person, and screening can be switched off entirely.

Who else touches it

The services tewo relies on, what each one does, and what reaches it.

ServiceWhat it doesWhat reaches it
Google (Gemini)Reads a CV against the posting it was sent to, extracts an applicant's details, reads lead form answers into columns, sums up recorded calls and suggests acceptance criteriaOnly what that feature needs — the CV and posting, the form's answers, the transcript, the task. Not retained beyond the request or used for training, under its terms with us.
Anthropic (Claude)Reads an uploaded CV to fill in a record, reads a pasted enquiry into a lead, and drafts text where you ask it toThe document's or message's text, and whatever you typed into the writing prompt.
Groq (Whisper)Transcribes a call recording, when somebody turns transcription onThe audio of that call. Off unless asked for.
Cloudflare R2Stores files, documents and Drive contentsWhatever is uploaded.
Amazon Web ServicesRuns the application and the databaseEverything in the workspace.
HostingerDelivers sign-in codes, invitations, invoices and notifications from noreply@tewo.inThe address and the message.
LiveKit CloudCarries video and voice calls between the people in them, through the region nearest the callThe call's audio and video while it happens. Recorded only if somebody in the call starts a recording.
RazorpayTakes payment for the plan and storageThe billing contact and the amount — never workspace records.

What we do not claim

Every security page in this category is a wall of ticks. Here is the other list — it is short, it is specific, and it is the one worth reading.

  • No SOC 2, ISO 27001 or any other certification. None is in progress. If your procurement requires one today, this is not yet the product for you.
  • No independent penetration test has been commissioned.
  • No contractual uptime guarantee. There is no SLA on the Start or Run plans.
  • Backups are taken, but we do not yet publish a tested recovery time — so do not treat tewo as your only copy of a legal record.
  • tewo does not run payroll and holds no bank or card details of your employees. Subscription payments are handled by the payment provider, not by us.

Need this in a document?

Send us your security questionnaire and we will answer it in full, including the questions where the answer is no. Data questions go to hello@amionyx.com.