Vayce has no accounts and no upload step, so there is no user record to hold. What this page describes is the data a visit produces: what the server logs to deliver a page, and what the analytics tools count in aggregate.
1. What never reaches us
The files, text, images, and audio you put into a tool are processed by your browser. They are not transmitted, so no copy exists on any server we control or rent. That applies to every tool, every workflow, and every embed.
One detail worth knowing. Tool settings are written into the page URL, which is how a setup becomes a shareable link. A URL is part of the request your browser makes, so the address of a page you load, including those settings, appears in server logs and analytics the same way any page address does. The file you were working on does not.
2. What the server sees
Vayce is hosted and served through Cloudflare, which processes technical information needed to deliver and protect the site:
- IP address
- Browser and device type
- Requested URL and timestamp
This is used for delivery, caching, error handling, and protection against attacks and abuse.
3. Analytics
Two analytics systems run on the site’s own pages, both to understand usage in aggregate rather than to identify anyone.
Umami is open-source and cookie-free. It stores no IP addresses and does not follow visitors between sites. It reports page views, referrers, device type, and country.
Google Analytics 4, deployed through Google Tag Manager, reports page views, navigation events, approximate location derived from IP, and device and browser information. The tag is served first-party through our own domain rather than from Google’s, which changes where the request goes, not who processes the data: that remains Google, on servers that may sit outside the EU under its data processing terms. GA4 is configured without personally identifiable information and without intentional cross-site profiling.
4. On-site engagement features
Mediavine Grow provides optional sharing and follow widgets. It may process limited technical data such as IP address, browser, device type, and interaction events, and may use cookies or local storage for functional purposes like remembering a preference or not repeating a prompt.
5. Embedded tools are not measured
Pages under /embed/ load no analytics at all. If a site embeds a Vayce tool, its readers are not counted by us, and nothing about them reaches this site beyond the request for the frame itself.
6. Cookies and local storage
Vayce sets no advertising or tracking cookies of its own. GA4 may use cookies for analytics, and Mediavine Grow may use cookies or local storage for the features above. Neither is used for personalized advertising here.
Separately, the tools use your browser’s local storage to hold saved workflow presets and remembered settings. That data stays on your device, is never sent anywhere, and disappears when you clear site data.
Your browser settings control cookies and stored data for this site.
7. What we do not do
No accounts, no personal profiles, no selling of data, no tracking across unrelated sites, and no advertising cookies.
8. Third parties
- Cloudflare, hosting, security, and delivery: privacy policy
- Umami, cookie-free analytics: documentation
- Google (Analytics and Tag Manager), aggregate analytics: privacy policy
- Mediavine Grow, engagement features: privacy policy
Each processes only what its service needs and is not permitted to use it for unrelated purposes.
9. Your rights
If you are in the EU or UK, the GDPR gives you rights of access, correction, deletion, and objection over personal data held about you.
Because Vayce keeps no accounts and holds nothing that identifies you, there is usually no personal record to retrieve or erase. Requests about data held by the processors above, particularly Google, are best directed to them as well as to us.
Questions about any of this: contact@vayce.app.
10. Updates
New features can change what is processed. When that happens this page is updated, and the effective date at the top changes with it.