VoiceSafe transparency
Privacy
This page explains how VoiceSafe thinks about submitted evidence and product privacy at the MVP stage.
What VoiceSafe processes
- VoiceSafe helps review fraud-risk signals in suspicious calls, messages, documents, links, payment requests and related evidence.
- Users may upload or submit calls, messages, documents, links, payment requests or other case context so VoiceSafe can organize the evidence and support review.
- Uploaded or submitted content may be processed to provide fraud-risk review, risk signals, recommended next steps and safety disclaimers.
- VoiceSafe does not guarantee fraud detection and does not guarantee that a request is safe or unsafe.
- VoiceSafe is not legal, financial, banking, police or emergency advice.
- Users should not send money until they verify requests through trusted independent channels.
Product analytics
VoiceSafe uses Vercel Web Analytics to understand aggregate page visits and a limited set of product events such as registration starts, completed registration, case creation, evidence addition and checkout flow activity. A privacy-scoped Metricool tracker is also used on the public landing page to understand aggregate website traffic from social media.
Organic and paid social links may carry a strictly bounded, non-identifying attribution key made only from the network, campaign and creative slot. VoiceSafe may keep that key in a first-party cookie for up to 30 days so a social visit can be connected to registration and early product-use events. For versioned campaign links, VoiceSafe may also keep daily aggregate counts by that attribution key for social visits, registration starts, completed registrations, first case creation and checkout flow activity. Those aggregate counters do not contain user IDs, email addresses, case IDs, evidence IDs, payment IDs or submitted content.
VoiceSafe does not intentionally send submitted evidence, email addresses, account IDs, case IDs, evidence IDs or file names as analytics event data. Query parameters are removed and dynamic UUIDs in page URLs are redacted before analytics page views are sent.
Important note
This page is provided for product transparency and should be reviewed with legal counsel before full public launch.
Privacy questions
For privacy questions, contact support@voicesafe.ai.