Terms of Use
Noise or Voice is an experimental acoustic detector. These terms describe permitted use and the limits of its results.
Operator and scope
The site is operated by Cisco Caceres. Contact [email protected] about these terms. The Privacy & Data Handling notice describes the local demo, server records, pilot emails, and voluntary contributions. A separately agreed pilot contract may set additional access, service, security, and processing terms.
Experimental results
Scores are outputs of acoustic heuristics, not calibrated probabilities or proof of a speaker's identity, honesty, biological origin, or authorization. False positives and false negatives occur. The benchmarks disclose selected-corpus performance and failures. Selected sample successes do not establish accuracy for your recordings or operating conditions.
Do not use a verdict alone to authenticate a person, deny access to a service, accuse someone of fraud, make a medical decision, or take another consequential action. Validate the intended setting and arrange human review and independent evidence.
Audio, permissions, and research consent
Submit or analyze only audio you are entitled to use. Respect consent, recording, privacy, and intellectual-property requirements that apply to the speakers and your use. Do not submit sensitive or confidential material to the public prototype. Do not contribute recordings of minors.
Using the browser demo does not grant permission to retain or publish your recording. Voluntary contribution requires separate consent for storage and research evaluation. It does not grant a general right to publish or commercially reuse a contributor's voice. The deletion process and its limits are described in the contribution notice.
Public samples and attribution
The Evaluation Lab contains locally labeled examples with varying provenance. A filename, source label, or detector result does not independently authenticate a public figure or establish a generator's identity. Playback and download availability do not grant ownership, endorsement, or unrestricted reuse rights. Check the original source's permissions and applicable law before redistributing an example.
API and package availability
POST file verification is deployed at /api/v1/verify. Access, quotas, key issuance, and service configuration may change. SDK source is maintained in the project; public package distribution is not established. Streaming, WebSocket, gRPC, and telephone integrations in the docs are design proposals unless a pilot explicitly supplies them. There is no public uptime, latency, detection accuracy, certification, or cryptographic signing guarantee.
Do not bypass rate limits, obtain another user's keys or records, or interfere with the service. Responsible security reports can be sent to the operator without attaching unnecessary personal information.
Updates and mandatory rights
We may update these terms and will date changes here. Your statutory rights and obligations continue to apply. These terms do not waive rights that cannot lawfully be waived or replace a required data-processing agreement. Ask the operator about a documented pilot arrangement before operational or regulated use.