What we don't have to keep secret, because we don't have it.

Rapifile is a local-first browser extension. Your résumé, profile, and captured answers live on your device. We don't run a server that stores your data, we don't have analytics, and we don't have a user account system. This page exists because the Chrome Web Store requires a privacy policy — not because there's a complicated story to tell.

Last updated: May 25, 2026

1. What Rapifile stores

Rapifile saves the following to your browser's chrome.storage.local (which is local to your device — not synced to Google's servers):

Your profile fields: name, email, phone, location, work authorization, EEO answers, and any free-text fields you fill in during onboarding.
Your résumé PDF, if you upload one.
Custom answers that Rapifile "captures" while you fill out forms (only after you explicitly approve them).
Per-site preferences such as "hide on this page" choices.
If you have multiple profiles, each profile owns a separate copy of all of the above.

2. What Rapifile explicitly never stores

Rapifile runs a sensitive-field deny list. It refuses to read, fill, or capture the following — even if a form mislabels them:

Passwords and password-reset codes
Social-security numbers and other government IDs
Credit-card numbers, CVVs, and cardholder data
Bank account / routing numbers
Security questions and security answers
One-time codes, OTPs, and two-factor authentication tokens

3. What Rapifile sends over the network

Almost nothing. Filling forms, parsing your résumé, and saving your profile all happen entirely on your device — there is no analytics SDK, no error reporting, no telemetry, and no cloud sync of your data. You can verify this in your browser's DevTools network tab.

The only request Rapifile makes is to validate a Pro license key, if you have one. When you activate Pro — and once a day afterward to confirm the subscription is still active — the extension sends your license key to our server at rapifile.com. That request contains only the license key itself: never your profile, your résumé, your answers, or what sites you've used Rapifile on. Free users with no license key trigger no network requests at all.

4. Permissions Rapifile requests, and why

storage — to save your profile and résumé to chrome.storage.local on your device.
unlimitedStorage — to allow PDFs larger than the default 5 MB quota.
activeTab — to read the form fields on the page you're currently on, so it can find what to fill, and to write your data into those fields when you ask it to.
alarms — to run a once-daily background check that revalidates a Pro license key, if you have one.
Host access to https://rapifile.com — so the extension can validate your Pro license key against our server. Only the license key is sent; never your profile data.
Content scripts run on <all_urls> so the pill can appear on any job application site, including custom careers pages.

5. Third parties

Rapifile itself does not share, sell, or transmit your data to any third party. The extension is self-contained.

If you purchase a Pro license, payment is processed by Stripe. Stripe receives the information required to process a payment (your name, email, billing address, and card details) per their own privacy policy. We receive a webhook from Stripe confirming a successful payment so we can issue a license key — we do not receive your card details.

6. Your data, your control

You can delete everything Rapifile has stored at any time by removing the extension from chrome://extensions. Uninstalling clears all per-extension storage. There is no account to delete because there is no account.

7. Changes to this policy

If we change how Rapifile handles data, we'll update this page and note the change in the changelog. Material changes (anything that adds network requests or changes what's stored) will also be called out in the extension itself on the first launch after the update.

8. Contact

Questions, concerns, or "wait, is that allowed?" — email info@minovaweb.com.