Privacy and analytics choices

Draft preview notice — operator/contact details and the final policy review must be completed before public launch. These notices describe the selected product behavior; they do not establish a completed deployment or legal review.

Resume content stays local

The editor, imports, previews, JSON backups and PDF/print preparation process resume content in your browser. Resume fields, imported files and generated documents are not uploaded to ResumeFree or a third-party PDF service. We do not use your resume for product feedback, public examples or AI training.

Your browser stores the current draft and a last-good copy under an opaque product-local partition. They are not encrypted against someone using the same browser profile. Clearing site data, using private browsing, changing devices or browser policies can remove them. Keep a JSON backup if you need a portable editable copy. Clear all resume data removes the current and last-good copies for this product account in this browser; downloaded files and copies on other devices must be removed separately.

Identity and sessions

Common Funtoolio Auth handles sign-in and its provider choices. ResumeFree maps the validated issuer/subject to a local product user and stores only the product state, a random storage partition key and bounded session information. It does not automatically put sign-in profile details into the resume. Product session cookies are host-scoped, Secure/HttpOnly and expire after at most eight hours without indefinite sliding renewal. Antiforgery cookies protect signed-in actions. They are separate from optional analytics.

Voluntary feedback

If you send feedback, we store your submitted text/category, safe source-area code, local submitter reference, notice version, server version, retry key and timestamps, together with private review notes. Only the minimal committed acknowledgement is returned. The form is private; there is no public board or user conversation history. Please do not paste a resume, secrets or confidential data. The feedback permission in Terms is separate from privacy processing and does not make feedback or identity public.

Retention and deletion

• Local drafts remain until you clear them, clear browser data, or select removal when signing out. The server cannot erase browser copies on another device.
• Product deletion immediately revokes product sessions. Product user, session and linked feedback records are purged within seven days by bounded hourly cleanup.
• A minimal exact issuer/subject deletion block lasts thirty days to prevent automatic recreation. Disabled accounts remain blocked until authorized reactivation.
• Expired session records are cleaned after seven days. Closed feedback is removed after 180 days from closure; open feedback after 365 days from submission, or earlier through account purge.
• The proposed deployed backup window is up to thirty days, with deletion records reapplied after restore. Actual encrypted backup/restore setup and the published processing/provider details must be verified before launch. This local preview is not evidence of a production backup.

Optional public-page analytics

Optional Umami analytics can measure visits only on the homepage, template gallery and two public guides. It is off unless the operator configures it and you explicitly allow it. Sign-in, editor, account, feedback, privacy/security routes and exports have no public tracker. The integration does not send resume content, account identifiers, filenames, URL queries/fragments or raw referrers, and does not use identify, session replay or heatmaps. DNT takes precedence when available.

Your analytics choice is stored in this browser for up to 180 days. Allowing it here applies to later eligible public-page visits, with no backfill. Withdrawal stops later sends, including in other open public tabs through their before-send checks. Essential session/security storage remains independent.

Optional analytics is off unless a valid saved choice allows it.

Operational processing and requests

Hosting and authentication necessarily process network/request information. Product logging is bounded and excludes resume fields, feedback bodies, tokens and raw identity claims. The deployment plan limits operational logs to fourteen days; actual proxy/provider logs and processing arrangements need confirmation in the final notice. Data is not called anonymous merely because an identity field is absent.

For access, correction, deletion, privacy complaints or a security report, use the monitored route on Contact. Do not create an account solely to make a rights request. The operator must confirm applicable legal bases, recipients/processors, locations/transfers, rights and contact details before publishing this notice.