Skip to main content
PRIVACY & TERMS
AUDIO: OPTIONALSTATUS: EXPERIMENTAL
Noise or Voice PRIVACY
Spectrogram DemoArchitectureThreat ModelBenchmarksEvaluation LabAPI & SDKsEarly Access
Navigation Menu
Home OverviewSpectrogram DemoAcoustic ArchitectureThreat Model & ResilienceEmpirical BenchmarksSample Evaluation LabAPI & Integration DesignsPrivacy & Data HandlingTerms of UseRequest Early Access

Engineered by Cisco Caceres

Privacy & Data HandlingUpdated October 5, 2026

Privacy & Data Handling

Browser analysis, server verification, and voluntary research contributions have different data flows. This notice describes each one and how to ask for removal.

Who operates this site

Noise or Voice is operated by Cisco Caceres. For privacy questions, access, correction, or deletion requests, email [email protected]. Include the type of request and any relevant receipt ID; do not email a recording or API key unless we arrange a suitable transfer method.

1. Browser demo

The spectrogram demo decodes and analyzes audio on your device. Selecting a local file or using the microphone does not upload that audio to the verification API. The application keeps working audio buffers and recordings in browser memory while you use it. Reloading or closing the page ends that session; downloaded reports remain on your device until you remove them.

Loading a public sample makes a request to this site's hosting provider. Loading an audio URL makes a request to the source host, which may see your network address. Uploading a research contribution is a separate, explicit action described below.

2. Server verification API

POST requests to /api/v1/verify send audio to our Cloudflare-hosted function for processing. The handler processes audio in memory and does not write the submitted recording to its audit table. The audit record can contain the audio SHA-256 digest, verdict, decision score, threshold, duration, API-key prefix, timestamp, and an optional signature. A digest may link a known recording to its result; it is not a guarantee of anonymity.

New audit records leave client-IP and user-agent fields empty; historical records from earlier versions may contain those identifiers. A separate rate-limit record uses the request's IP address. Hosting infrastructure can also process request metadata. There is no scheduled deletion period for verification audit records in the current application. A pilot needs agreed retention and processing terms before sending sensitive material.

3. Voluntary voice contributions

If you select Submit Contribution and consent, the browser sends a short WAV excerpt, your selected issue category, optional notes, and the limited acoustic telemetry shown in the form. These are stored in Cloudflare D1 for research evaluation. A voice recording or free-text note can identify a person. Submit only audio you have permission to share; do not include confidential conversations, health information, or recordings of minors.

The contribution record includes a random receipt ID, submission time, and, for submissions under this notice, the accepted consent version, wording, and time. It does not include your IP address or user agent. The endpoint does not publish contributions or automatically add them to the public sample corpus. This consent authorizes storage and research evaluation; it does not authorize public release or commercial reuse of your voice.

No automatic deletion period is configured. A contribution remains stored until it is removed. Keep the receipt ID: it authorizes deletion, so treat it as private. The confirmation screen's Delete This Recording button removes the contribution's active database row. To withdraw consent or request removal later, email the operator with your receipt ID. Earlier contributions may not have a stored consent version.

Current contribution submissions are not sent through email notifications. Earlier false-positive submissions could have sent notes, telemetry, and a receipt through the configured notification service. Database deletion does not remove those older emails, any separately retained research copies, if they exist, or provider recovery copies; ask the operator to investigate those copies as part of a removal request. Deletion and recovery behavior of infrastructure backups must be confirmed separately.

4. Pilot access and contact email

The pilot form sends your email address to /api/waitlist. We store the normalized email, site source, and submission time to review your request and contact you about access. When email delivery is configured, a notification can be sent through Resend or a Cloudflare notification queue to the operator. Messages you email us are also handled by the recipient's mail service.

There is no automatic waitlist deletion period or self-service email-removal button. To cancel your request or ask us to remove your email, contact the operator from that address. Ask the operator to investigate removal of the active waitlist record and relevant correspondence; provider backups require separate handling.

5. Service providers and request metadata

Cloudflare hosts the site, runs the API functions, and stores server records in D1. It can receive IP addresses, request headers, timing, security, and traffic metadata. Traffic and security analytics may be processed under the hosting configuration. Resend is the configured email-delivery integration for pilot notifications when enabled; a notification queue may also be used. An operator's email provider receives correspondence and delivered notifications.

See Cloudflare's privacy policy and Resend's privacy policy. Provider location, logs, recovery retention, and international-transfer arrangements depend on the deployment and applicable contracts. This notice does not promise a particular processing country, backup expiry, or transfer safeguard.

The application uses IP addresses to limit abusive requests. Cleanup attempts to remove rate-limit windows older than 24 hours during subsequent traffic, in bounded batches. This is not a guaranteed 24-hour deletion deadline. Provider security settings may use cookies or similar browser storage; the site's application does not implement advertising trackers.

6. Purposes, consent, and your choices

Local analysis is optional. Research storage requires the form's explicit consent, which you can withdraw by requesting deletion. Pilot email processing responds to your access request. Hosting and rate limiting support delivery and abuse prevention. These purposes are separate; agreeing to research storage is not required to use local analysis.

Depending on the law that applies to you, you may have rights to access, correct, delete, restrict, or object to processing, request portability, withdraw consent, or complain to your data-protection authority. Email the operator to exercise a right or ask about the legal basis for a particular pilot. We may need information to confirm that a request concerns your data. A deployed pilot must establish its applicable legal basis and contracts; this notice is not a GDPR, HIPAA, or SOC 2 assurance.

We will date material changes on this page. A new consent version is required when contribution terms change. Review the Terms of Use and pilot documentation before using the service.

Noise or Voice

Experimental acoustic analysis of complete recordings. Results are uncalibrated decision scores with documented evaluation limits.

Navigation

  • Home Overview
  • Live Spectrogram Demo
  • Acoustic Architecture
  • Threat Model & Resilience
  • Academic Citations
  • Empirical Benchmarks
  • Sample Evaluation Lab
  • API & SDK Reference

Resources & Specs

  • Privacy & Data Handling
  • Terms of Use
  • llms.txt (LLM Summary)
  • llms-full.txt (Full Technical Grounding)
  • sitemap.xml
  • Contact Engineering
© 2026 Noise or Voice. All rights reserved.
Engineered by Cisco Caceres