Privacy
How resume data is handled
This page explains the current privacy model in plain language: local-first storage, optional sync, and explicit sharing choices.
Local storage first
Resume data is meant to stay on the user's device unless they use optional sync or sharing features.
Optional sharing
Public links are intentionally public. Users should only share content they want others to view.
Minimal tracking
The product is built to avoid unnecessary tracking and to keep the public site easy to inspect.
Third-party services
If a user connects external services, those services may process data under their own terms.
Your control
You decide where your data lives
- By default, your resume is stored locally in your browser.
- You can use the builder without creating an account.
- Sharing and cloud sync are optional and only happen when you choose them.
- You can export your resume anytime and keep full control over your data.
What this means in practice
- Your local resume data should remain under your control.
- Sharing is a deliberate action, not a background behavior.
- You should review any synced or connected service separately.
- Public pages exist to describe the product, not to collect profile data.
Caveat
This summary is informational, not legal advice.
The privacy posture can evolve with new features, so the safest approach is to review the current app behavior, policy pages, and the repository before relying on any assumption.
Data usage
No selling. No profiling.
VeriWorkly does not sell resume data or use it for advertising or profiling. Product analytics are minimal and focused only on improving reliability and usability.