Yovoca legal
Privacy Policy
This policy explains what Yovoca collects today for the waitlist, and what we expect to handle when early access calling features open.
Current state: the public site currently collects waitlist emails and optional use-case signals, runs a live translation demo hotline, and measures page-to-signup conversion with first-party, cookieless analytics. There is no full user account system on the public site yet. Full calling features may collect more data only when beta access opens.
1. Information we collect
Waitlist information
- email address;
- optional use-case segment, such as travel, cross-border sales, or personal use;
- source and campaign information, such as a referral or UTM value in the page URL;
- basic technical information, such as country or request metadata needed for security, abuse prevention, analytics-free operation, and debugging.
Live demo hotline (available now)
If you call our demo hotline, we process the call to provide live translation. Your audio is streamed transiently to our telephony provider (Twilio) and speech-translation provider (Google) and is not recorded or stored by Yovoca. To enforce daily demo limits and prevent abuse we keep a salted hash of your caller number — never the raw number — together with the call identifier, timestamps, call duration, and technical diagnostic logs. We do not store demo audio, recordings, or transcripts in our database.
Beta account data (available now)
If you create a beta account, we collect your phone number, language preferences, and — only if you claim founding membership — the waitlist email you verify. We do not collect passwords; sign-in uses one-time codes.
First-party analytics
We measure how the public site converts using first-party, cookieless analytics: a random session identifier stored in your browser's sessionStorage, the page path, interface language, coarse country derived at the network edge, and the event type (for example a page view, a click on the demo number, or a waitlist submission result). We do not store your IP address, user agent, or any device fingerprint, and analytics events are never joined with your email. To protect the waitlist from abuse we additionally keep a salted hash of the connecting IP address for up to two days; the raw IP address is never stored.
Future account and calling information
If you are invited to beta calling features, we may collect account details, phone numbers, verified caller IDs, destination numbers, call metadata, call status, usage balances, payment records, support messages, and safety signals.
When you buy a pack, payment is handled by PayPal. We receive and store the order identifier, the pack, the amount, and its status — never your card or bank details. To prevent duplicate free-credit grants, we store a salted hash of the phone number used for verification, not the number itself, for this purpose.
Future call content
Live translation may require audio streams, transcripts, translations, summaries, extracted details such as times or addresses, and temporary processing by AI or telecom providers. If voice cloning is offered, it may require voice samples, voice embeddings, verification recordings, and related consent records.
2. How we use information
- to run the waitlist and tell you when early access opens;
- to understand which use cases to prioritize;
- to provide, test, secure, debug, and improve translated calling features;
- to route calls, translate speech, generate summaries, and show call details when you ask for those features;
- to prevent spam, fraud, telecom abuse, premium-rate number abuse, impersonation, and unsafe voice use;
- to comply with legal, carrier, tax, billing, security, and platform obligations.
3. Cookies, local storage, and analytics
Yovoca does not currently add third-party analytics or advertising trackers to the public waitlist site. We may use browser storage such as sessionStorage to remember a referral or campaign source so a waitlist signup can be attributed correctly. Cloud, hosting, security, and carrier providers may process standard request logs needed to operate the service.
4. Sharing information
We do not sell personal information. We may share information with service providers and partners who help us operate Yovoca, including:
- cloud hosting, database, and security providers;
- telecom carriers and communications platforms used to place, receive, route, stream, or verify calls and messages;
- AI, speech-to-text, translation, text-to-speech, and voice providers used to process calls;
- payment processors, if paid plans open;
- email and support tools used to contact waitlist or account users;
- Supabase — hosts beta account profiles and authentication;
- Twilio Verify — delivers sign-in codes by SMS or voice call;
- legal, safety, compliance, or law-enforcement recipients when required or reasonably necessary.
5. Call and voice privacy
Calls are sensitive. We design Yovoca to process only what is needed to provide translation, routing, safety, debugging, billing, and user-requested records such as summaries. During beta, call content may be temporarily processed by providers that make live translation and voice output possible. The demo hotline described above is live today and operates under these same principles.
If voice cloning becomes available, we will treat voice samples and voice profiles as sensitive data. We may require verification and consent steps, and we may refuse or remove a voice profile when misuse is suspected.
6. Retention
Waitlist records are kept while early access is active and for a reasonable period afterward so we can manage launch communication, founding status, abuse prevention, and support. Future call metadata, transcripts, summaries, recordings, voice samples, and billing records may have different retention periods depending on the feature, your settings, carrier requirements, legal requirements, and safety needs.
Beta account data is kept while your account is active and removed within 30 days of a deletion request made in Settings.
You can ask us to delete eligible data by emailing [email protected]. We may retain limited records where needed for legal compliance, security, fraud prevention, dispute handling, tax, accounting, or telecom obligations.
7. Security
We use reasonable technical and organizational measures to protect information. No internet, telecom, or AI system is perfectly secure. Please do not send highly sensitive personal information through Yovoca unless the feature is clearly designed for that use and you understand the risks.
8. Children
Yovoca is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child provided information to us, contact [email protected].
9. International users
Yovoca may process information in the United States and other countries where our providers operate. Those countries may have data protection rules different from where you live.
10. Your choices
- You can join the waitlist with only an email address; the use-case segment is optional.
- You can ask us to remove your waitlist email.
- Future beta users may be able to control transcript, summary, recording, and voice-profile settings depending on the feature.
- You can contact us to access, correct, delete, or object to certain uses of your information, subject to legal and operational limits.
11. Changes to this policy
We may update this Privacy Policy as Yovoca moves from waitlist to beta, adds account sign-in, supports payments, or opens live calling features. We will update the effective date and, for material changes, make a reasonable effort to notify affected users.
Contact
For privacy requests, email [email protected] from the address you used for the waitlist or account.