Privacy Policy

This describes exactly what Resumu stores, why, and who else can see it. Resumu is operated by Wasut Panyawiphat, an individual in Thailand, who is the data controller for everything described here. Questions or requests: admin@resumu.me, and a postal address on request.

Using Resumu without an account

If you are not signed in, your resume never reaches our servers. It is held in your browser's local storage, and clearing your browser data deletes it permanently — we cannot recover it.

Exporting is the one exception. A PDF or DOCX export sends the resume to our server so it can be rendered, then returns the file. The content is processed in memory and is not written to our database or kept afterwards.

What we store when you have an account

• Your email address and, if you sign in with Google, the name and avatar Google provides.
• The resumes you save, stored as structured data.
• Which path you publish to, and whether it is currently published.
• Your plan, its status, and identifiers issued by Stripe. We never see or store card details.
• Any one-time template purchases.

Photos

Adding a photo is optional. If you upload one it is resized in your browser and stored on Cloudflare R2, and the file is public to anyone who has its address — as it must be, for it to appear on a published page. Replacing your photo overwrites the previous file. Removing it from a resume stops it being shown; email us if you want the stored file deleted outright.

Published pages are public

Publishing puts your resume at a public address that anyone with the link can open and that search engines may index. Include only what you are willing to make public — a published resume is not a private link. Unpublishing removes the page; search engines may take time to drop it from results.

View counts on published pages

For published pages we record a daily count of visits so you can see whether your link is being opened. This is a count and nothing else: no IP address, no browser or device details, no location, and no identifier for the visitor. We cannot tell you who viewed your page, only how many times it was opened. Counting happens in the visitor's browser, so most automated crawlers are not included.

Abuse prevention

Exporting is rate limited to keep the service available. To do that we briefly hold a counter against your account, or against your IP address if you are signed out. These counters expire automatically within an hour and are deleted; they are never used for analytics or profiling.

Cookies

We set a cookie to keep you signed in. We do not use advertising or third-party tracking cookies, and there is no analytics script on the site. Your browser also stores a short-lived marker so a published page is not counted twice in one visit.

Who else processes your data

• Supabase — database, authentication and storage. Data is hosted in the United States (us-east-1).
• Stripe — payment processing. Stripe handles card details directly; we receive only the subscription status and identifiers.
• Netlify — application hosting and content delivery.
• Cloudflare — DNS, and R2 storage for uploaded photos.

We do not sell your data, and we do not share it with anyone else.

How long we keep things

Saved resumes stay until you delete them or close your account. Deleting a resume removes its published page and its view counts at the same time. Billing records are kept as long as tax and accounting rules require, even after an account closes.

Your rights

You can export any resume as JSON at any time, delete individual resumes from My Resumes, and unpublish a page whenever you like. To delete your account and everything in it, use Delete account on your profile page; for a copy of everything we hold, email admin@resumu.me. Depending on where you live you may also have rights to correct or restrict how your data is used, and to complain to a data protection authority.

Children

Resumu is not intended for use by anyone under 16.

Changes

If this policy changes in a way that affects you, we will say so on this page and update the date above before the change takes effect.