Legal

Privacy Policy

Last updated 13 September 2026

Pending legal review

Drafted against the current system. Every bracketed placeholder must be filled and the whole page reviewed by a qualified lawyer before accounts open.

1. Who is responsible

Controller
CodeHarbor OOD, trading as VocalVault
Registered seat
[registered address, city, postcode, Bulgaria]
UIC / EIK
[9-digit company number]
Privacy contact
Data protection officer
[Name, or: not appointed — see 1.1]

1.1 On the DPO. A DPO is mandatory under GDPR art. 37 where core activities involve large-scale regular and systematic monitoring, or large-scale processing of special categories. Hosting customers' voice recordings at scale may cross that line as the service grows. Reassess before launch and again at each growth stage, and record the reasoning either way.

2. Controller or processor

Our role differs by data, and that difference decides who you go to about it:

Account and billing data
We are the controller
Website visits
We are the controller
Audio signed through the service
We are a processor for the customer organisation
People heard in a recording
The customer organisation is the controller

If you were recorded by an organisation using VocalVault and want your recording accessed or deleted, that organisation decides — we act on their instruction. Our Data Processing Agreement governs that relationship. Tell us anyway and we will pass the request on and tell you who holds it.

3. What we hold, and on what basis

Account data
Name, work email, organisation, role, sessions — art. 6(1)(b), performance of the contract
Authentication
Password hash, two-factor secret — art. 6(1)(b) and 6(1)(f), account security
Recordings
Encrypted audio and its signatures — processed on the customer's instruction
Device metadata
Public keys, assurance level, last seen — art. 6(1)(b)
Audit log
Hash-chained record of every action — art. 6(1)(c) and 6(1)(f), integrity and accountability
Server logs
IP address, timestamp, request — art. 6(1)(f), security and abuse prevention
Billing records
Invoices and usage — art. 6(1)(c), accounting and tax law
Private signing keys
Never. They are generated in your device's hardware and cannot be exported

We collect nothing beyond this. There is no analytics, no tracking, no advertising and no profiling anywhere on this site — see the Cookie Policy, which also explains why no consent banner appears.

Where we rely on legitimate interests, the balancing test is available on request.

4. Voice recordings and biometric data

A voice recording is personal data about everyone audible in it. It is not automatically biometric data under GDPR art. 9: it becomes so when processed specifically to identify a person, through technical means such as a voiceprint.

We do not do that, and the system is not built to. VocalVault binds a signature to the audio using a key held in the signing device. The content fingerprint it computes is a coarse spectral summary used to detect re-encoding and editing — it identifies the recording, not the speaker. We build no voiceprints, run no speaker identification or verification, and derive no biometric templates.

Customers must not use the service to do so either, and doing so would also take them outside their own lawful basis — see the Terms. If we ever add a feature that identifies speakers, art. 9 would apply, explicit consent would normally be required, and this policy would change before the feature shipped.

5. Recording other people

Recording a conversation engages more than the GDPR, and the rules differ by country — several EU states require every participant to agree, and some treat covert recording as a criminal matter. The customer organisation, not VocalVault, is responsible for having a lawful basis and for telling participants. The service provides a consent gate before recording; using it is not a substitute for obtaining consent.

6. Who else sees it

We do not sell personal data, and we do not share it for anyone else's marketing. Data reaches a third party only where a supplier is needed to run the service, each under a GDPR art. 28 contract. Current suppliers are listed on the Subprocessors page, which is the authoritative list.

We may also disclose data where the law requires it. Where we are permitted to tell you about such a request, we will.

7. Where it is stored

In the European Union by default, and we intend to keep customer recordings inside the EU. Should any transfer outside the EEA become necessary, it would rely on an adequacy decision or on Standard Contractual Clauses with a transfer impact assessment, and would appear on the Subprocessors page before it began.

8. How long we keep it

Recordings
The retention period the customer organisation sets
Account data
While the account is open, then [X] days
Billing records
[As required by Bulgarian accounting and tax law — confirm the exact period with your accountant]
Server logs
[X] days
Audit log
Retained as the integrity record — see below

Deletion is by crypto-shredding. The per-recording data key is destroyed, leaving ciphertext that no one can decrypt.

The audit log is append-only and hash-chained, so entries cannot be rewritten or removed without breaking the chain that makes the log worth having. This limits erasure under art. 17: the audio goes, but the record that an action occurred remains. We keep it under art. 17(3)(b) and (e) and art. 6(1)(c) and (f). We consider this justified and defensible, and you should know about it before you sign up rather than discover it during a deletion request. Audit entries are minimised to the identifiers needed to make the chain verifiable.

9. Security

Recordings are encrypted, signing keys are generated inside device hardware and are non-exportable, access is authenticated with a second factor, and every action is written to a hash-chained log. No system is perfectly secure, and we do not claim otherwise. A personal data breach meeting the art. 33 threshold is reported to the Commission for Personal Data Protection within 72 hours, and to affected people without undue delay where art. 34 requires it.

To report a vulnerability, write to security@vocalvault.io. We will acknowledge within two working days and will not pursue researchers acting in good faith.

10. Your rights

Under the GDPR you may request access, rectification, erasure, restriction, portability, and object to processing based on legitimate interests. There is no automated decision-making with legal effect under art. 22 anywhere in the service.

Write to privacy@vocalvault.io. We respond within one month, extendable by two where a request is complex, and we will say so if we extend. Exercising these rights is free unless a request is manifestly unfounded or excessive.

If you are unhappy with how we handled it, you can complain to the Bulgarian supervisory authority — the Commission for Personal Data Protection (Комисия за защита на личните данни), 2 Prof. Tsvetan Lazarov Blvd, Sofia 1592, www.cpdp.bg — or to the authority where you live or work.

11. Children

VocalVault is a business service and is not directed at children. We do not knowingly create accounts for anyone under 18. A recording may of course capture a child's voice; that processing is the customer organisation's responsibility and demands particular care.

12. Changes

The date at the top changes whenever this policy does. Material changes will be notified by email to account holders before they take effect. Previous versions are available on request.