Getting started: from recording to transcript

1. Sign up

Register at the app — an email address and a password, that's it. Every paid tier has a 30-day free trial, no card required. When the trial ends nothing is deleted — access returns to the free tier (300 minutes a month).

2. Upload a file

Drag your file onto the upload screen — or pick it straight from your phone. Any audio or video file, from any device, no format list and no length limit: AMR, 3GP, OGG, WhatsApp, PBX recordings. If ffmpeg can read it, we can transcribe it.

The original file is kept bit-for-bit with a cryptographic hash — it is never edited and never deleted. Every processing step creates a derivative copy and is recorded in the audit log.

3. Work on the transcript

Within minutes you get an accurate transcript — Hebrew-first, any language — with speaker detection and timestamps. In the editor:

• A word-synced player — click any word to play that exact moment in the recording
• Text fixes, segment splits and speaker names — with keyboard shortcuts
• Every save creates a documented version, and exports always use the latest one

4. Export

Export to Word (DOCX), TXT, SRT, VTT or JSON — perfect RTL. On the Free tier Word and VTT exports are watermarked; on Pro and up exports are clean.

Security: an organisation admin must use two-factor authentication

Whoever opened the account is the organisation's admin — and an admin can do irreversible things (erase recordings, pay, mint API keys). An admin account therefore requires two-factor authentication (TOTP) with an authenticator app such as Google Authenticator. Until it is set up, the account page shows only the setup screen and every admin action (invitations, payments, keys, erasure) is blocked; viewing files and the editor stays open.

Regular team members do not need two-factor authentication. A team invitation is always as a member; promotion to admin is possible only after the invitee has set up two-factor authentication themselves.

• Account page → Two-factor authentication → scan the key in the app → type the 6-digit code → confirm.
• Keep your backup codes! When you enable 2FA, 10 one-time codes are shown once — each replaces a code from the app once (at sign-in or when confirming an action). Save them in a password manager or print them. Using a code is audited and mailed, and afterwards you should set up 2FA again and generate new codes.
• Lost the phone with no backup codes? In an organisation with more than one admin, another admin can request a reset of your two-factor authentication: it applies after 24 hours, both sides get an e-mail, and you can cancel it at any time until then (takeover protection). In a single-admin organisation without backup codes the account stays locked; that is deliberate — nobody can vouch for the identity on the other side. So: backup codes, and a second admin.

Display adaptations and accessibility

At the top of every page — on the site and in the app — there are three switches: high contrast, larger text, and reduced motion. The choice is stored in your browser only and is never sent to the server. The switches need JavaScript; without it the default display is shown.

The full accessibility statement, the contact channel and the remedy procedure (up to 60 days) are behind the "Accessibility statement" link at the bottom of every page.

The legal documents

The privacy policy, terms of service, data processing agreement (DPA) and subscription terms are published on the site's "Legal" page and linked from the footer of every page. Version and date appear at the top of each document; until launch most are marked as drafts (the accessibility statement is final).

The recording announcement on the Comply track

By default every Comply call opens with a recording announcement — in the organisation's language, followed by a short English version. The announcement (text + hash), the time it was played and the caller's response (continued / keypress / hang-up) are written to an immutable audit log and included in the recording's sidecar file and the monthly compliance report. Without a documented announcement the recording does not start.

The profile follows the organisation's country (the strictest bar in that country), never the carrier, the branch or the caller's state; the caller's prefix only selects the announcement language. Where the law requires the announcement (e.g. Spain, Germany, the US) the switch is locked. On the Israeli profile only an admin can disable it — after re-authentication and a documented warning — and the switch-off is recorded with the warning text and the terms version, with a reminder every 90 days (Terms 4.4, DPA 2.3).