Privacy Policy
Updated: 25 серпня 2026. Цей документ описує реальні механізми системи — кожне твердження можна перевірити в коді або в базі на демо.
What data we process
- Account: name, email, password hash (scrypt), last login time.
- Conversations: call transcripts, recognized utterances, extracted facts (value + verbatim customer quote + confidence).
- Audio recordings: ONLY if you turn them on. By default only text is stored. Audio is kept in your own storage (S3 / MinIO / Cloudflare R2), not on our servers.
- Customer data: name, phone, email, country, call language — from what the customer said on the call or what you entered.
- Technical data: call duration and outcome, per-stage latencies (STT/model/TTS), provider costs, the audit log of critical actions.
Why we process it
The legal basis is performing the contract with you: providing the call processing service. Specifically: running the conversation, collecting facts for the manager, showing analytics, keeping the platform secure.
We do not use your data to train models, do not sell it, and do not use it for advertising. The application has no advertising trackers.
Who has access during a call
For a call to happen, audio and text pass through the telephony and AI providers. We pass the minimum each stage needs:
- Telephony: your SIP carrier (Twilio / Telnyx / Vonage / your own PBX) — the call audio channel.
- Speech recognition: Deepgram — audio to text.
- Conversation model: OpenAI or Anthropic (configurable route) — conversation text for the reply.
- Speech synthesis: Deepgram / ElevenLabs / OpenAI — reply text to voice.
- Recording storage: your own S3-compatible bucket — audio is not stored on our infrastructure.
The active providers for your workspace are visible in settings and in the analytics of every call (per-stage breakdown with cost).
Isolation & security
- Each organization's data is isolated at the database level: FORCE ROW LEVEL SECURITY on every data table — not a query filter, a database policy.
- Database access runs under limited roles (api_service, voice_worker) without superuser rights.
- Provider keys are encrypted with AES-256-GCM and released to the voice worker only for the duration of a call.
- Passwords are stored as scrypt hashes only; verification uses constant-time comparison.
- Critical actions (human handover, qualification completion, configuration changes) are written to an append-only audit log.
- Sessions are httpOnly cookies; the access token lives 15 minutes and refreshes automatically.
How long data is kept
- Transcripts and facts: 365 days by default; the period is configurable per organization.
- Audio recordings: the period is fixed at the moment recording STARTS (not retroactively). After it expires the file is destroyed, and the deletion is confirmed by a database record.
- Audit log: longer than business data — it is the proof that requirements were met.
Your rights
Access, correction, deletion, portability — via your manager or hello@cc.fisher.tech. The system has a dedicated request workflow: each request has a status, an owner and a 30-day deadline from receipt. Overdue ones are visible on the privacy screen.
Deleting an organization removes all of its data by cascade (leads, conversations, facts, tasks, knowledge base) — a property of the storage, not a “we’ll clean it up someday” procedure.
About call recordings
Audio recording is off by default — and that is a decision, not a precaution: voice is personal data, and keeping it “just in case” is a call for the company to make, not for the platform.
Коли запис увімкнено, агент повідомляє про це першою фразою розмови — це вбудовано в його поведінку, а не залишається на сумління оператора. Клієнт проти запису — розмова передається людині без продовження збору даних.
What we don't claim today
We hold no SOC 2 or ISO 27001 certifications — and we won't write them into the policy until they exist. There is no separate service status page yet. These will appear with the real grounds, not sooner.
Contact
Privacy questions and data-subject requests: hello@cc.fisher.tech. Every request is recorded in the system with a deadline and an owner.
See also: Terms of Service · Security