How Resumi handles account information, resume drafts, Google Sign-In, and support messages.
Last updated: September 14, 2026
If you create an account with email and password, Resumi stores your email, display name, plan status, and account identifier through Supabase. If you choose Google Sign-In, Resumi receives the basic identity information you approve, such as your name, email address, profile image, and Google account identifier.
Resumi requests only openid, email, and profile for Google authentication. Resumi does not receive or store your Google password or Google OAuth credentials. Google and Supabase handle the authentication exchange.
Signed-in users can store profile details, resumes, selected templates, section order, and download activity in Supabase so the product can save, restore, and manage their work. Profile photos are stored in private, user-scoped storage and are served through short-lived access links.
When you use the guest builder, Resumi may save a device-specific session identifier, your resume draft, selected template, completion progress, ATS score, download status, and basic device, browser, referral, and campaign details. If your resume contains a name, email, phone number, location, or links, those details may be included in the server-side draft. Guest photos remain in the local browser draft and are excluded from anonymous server sync.
When you submit the Contact form, Resumi stores the name, email address, subject, and message you provide so the team can review and respond to your request.
Resumi uses this information to provide authentication, save and recover work, render resumes, enable downloads, secure access, respond to support requests, diagnose reliability problems, understand product completion, and improve the service.
Account records and saved resumes are retained while needed to provide the service or until deletion is requested, subject to security, legal, and backup constraints. Anonymous drafts may also be retained for draft recovery and product improvement. To request access or deletion, use the Contact page and provide enough identifying information for Resumi to locate the relevant account or draft.
Payments are disabled during the current free launch. Resumi does not currently collect payment-card details through the product. If paid features are introduced, this policy will be updated before payment processing is enabled.
Resumi uses service providers such as Supabase to host authentication, database, and storage functions. Information is not made public by default. Technical controls include row-level access rules for account data and private owner-scoped photo storage, but no online service can promise absolute security.