Privacy Policy

ApplyBOLD is a product of Mivaantech, a proprietorship based in India.

This policy explains what information ApplyBOLD collects when you build a resume, why we hold it, and how to reach us about it. We have tried to keep it short and readable rather than exhaustive.

Information you provide

The resume you build is the main information we hold. That includes whatever you choose to enter — your name, contact details, work history, education, skills and anything else you type into a section. You decide what goes in, and you can leave any field blank.

Using ApplyBOLD without an account

You do not create an account to use ApplyBOLD. Your browser is given an anonymous session so your work can be saved and restored when you come back. That session is not linked to your name or email address, and we do not use it to identify you personally.

Because the session lives in your browser, clearing your browser data or switching to a different browser or device will generally mean your earlier draft is no longer available to you.

How your resume is stored

Your draft is kept in your browser and on our servers so that it survives closing the tab. It is stored against your anonymous session, and is not readable by other people using the service.

AI features

Some features can rewrite a bullet point or draft a professional summary. When you choose to use one of these, the relevant text from your resume is sent to a third-party AI provider (Google) to generate the suggestion, and the suggestion is returned to you for review. These features are optional — ApplyBOLD works fully without them, and nothing is changed in your resume unless you accept a suggestion.

Payments

Payments are processed by Razorpay. When you choose to pay, Razorpay's own checkout opens and you enter your payment details — card, UPI or banking information — directly into it. Those details go to Razorpay, not to us: ApplyBOLD never receives, sees or stores your card number, UPI ID or bank details. Razorpay handles that information under its own privacy policy and the rules that apply to payment providers in India.

What we keep is the record of the purchase itself: the order and payment references Razorpay gives us, the amount, the currency, when it was paid, and which resume it was for. We need that to know you are entitled to your download, and to investigate if a payment goes wrong. If you enter contact details into Razorpay's checkout, those belong to that payment and are not added to your resume or to your ApplyBOLD session.

Analytics

We use Google Analytics to understand how ApplyBOLD is used — which pages people visit, and which steps of building a resume they reach. This tells us where the product is confusing so we can fix it. Google sets its own cookies and may record technical details such as your approximate location, device and browser.

Your resume never goes to Google Analytics. We send only a small, fixed list of non-identifying measurements: the page path, which template was chosen, which step you reached, whether an action succeeded, and — when a purchase completes — the amount charged and the order reference. Your name, contact details, work history, the text of any section, your photo, your card or UPI details and your anonymous session identifier are never included, and the system that sends these measurements can only send values from that fixed list.

The order reference is the identifier the payment system gives the transaction. It lets us count one purchase once rather than several times; it is not a name, an email or a session, and it cannot be used to look you up.

For Google Analytics, we do not give Google an identifier for you, and we have switched off Google's advertising and cross-device signals, so this measurement data is not used to build an advertising profile of you. You can also block analytics with a browser setting or extension; ApplyBOLD works normally without it.

Advertising measurement (only if you allow it)

If you allow it, we use the Meta (Facebook) Pixel and Meta's Conversions API to measure which advertisements bring people to ApplyBOLD, so that a small advertising budget is spent on what actually works. This is advertising measurement and attribution — it is separate from the analytics described above.

This is off unless you choose to turn it on. We ask once, with Accept and Reject offered equally — neither is preselected and neither is harder to find. Until you accept, Meta's Pixel is never loaded, no Meta cookie is set, and nothing is sent to Meta from your browser or from our server. If you reject the question, or simply ignore it, it stays that way.

What events we share, if you allow it. That a page of a certain kind was viewed (a guide, a template, or the builder), that a “build your resume” button was pressed and which one, that a resume was completed, that a checkout was opened, and that a purchase completed — with the amount in rupees, the currency, the order reference and the template name.

Meta can see your IP address and browser information. If you accept, your browser loads Meta's Pixel script from Meta's own servers. Like any request your browser makes to another company's server, that request carries your public IP address and your browser's user-agent string, and Meta can see them. Meta's script also runs on the page, so it can read the address of the page you are on and the referring page your browser reports — the page you came from. That is how the web works, and it is not something ApplyBOLD can switch off while the Pixel is running — so we say it plainly here rather than leaving you to assume otherwise. Meta may also set and read its own browser identifiers, including the cookies it calls _fbp and _fbc, and use them to connect your visit to an advertisement you clicked.

About the addresses themselves. A page address can carry extra information after a ? — advertising click identifiers such as fbclid, or campaign tags such as utm_source — and these are usually added by whoever linked to you, so they most often appear when you arrive from an advertisement or an external link. ApplyBOLD does not put anything of yours into its own addresses: our pages are addressed by template and article names, and we do not use query parameters anywhere in the product. We do not remove what someone else added, and we do not control what Meta's script collects from the address — so we make no claim to strip any of it. We have not independently verified which parts of an address Meta's script transmits, and we would rather say that than imply a protection we have not confirmed.

Separately, we set a strict-origin-when-cross-origin referrer policy on ApplyBOLD. That limits what your browser puts in the referrer header when it makes requests to other sites — those get our domain rather than the full address of the page you were reading. It does not restrict what a script already running on the page can read, which is why the paragraph above says what it says.

We also confirm completed purchases to Meta from our own server, so that a sale is counted even if your browser could not report it. In those server messages we deliberately do not include your IP address: Meta offers a field for it and we leave it empty. Where your browser has Meta's own _fbp or _fbc identifier, we include that and your user-agent string so the purchase can be matched to the right advertisement, and nothing else. We do not add contact details to improve that matching.

What we never send Meta: your resume, or anything in it. Not your name, your email address, your phone number, your education, your employment history or your skills — not in plain text, and not hashed or otherwise encoded. We do not give Meta an account identifier for you. The list of things we are able to send is fixed in our code, and anything outside it is discarded before any request is made, so this is a property of how ApplyBOLD is built rather than only a promise about how we behave.

Changing your mind. Use the Privacy Choices link in our footer at any time to reject tracking or withdraw permission you gave earlier. When you withdraw it we stop sending events from your browser, stop sending them from our server, and clear Meta's _fbp and _fbc cookies where your browser lets us. We cannot undo requests your browser already made while permission was in place, and we do not control what Meta retains from them.

Meta sets its own cookies and decides for itself what it does with what it receives. You can read Meta's own description of that in their Privacy Policy and their Cookies Policy.

Service providers

We use a small number of third-party providers to host the service, to process payments, and to power the AI features described above. They process information only to provide those services to us.

What we do not do

• We do not sell your information.
• We do not use your resume content for advertising.
• We do not send your resume content to Google Analytics.
• We never send your resume content, name, email or phone number to Meta.
• We do not require an account, a password, or a phone number.

Keeping and removing your information

We keep your draft so you can return to it. If you would like your resume data removed, contact us at applybold.info@gmail.com and we will action it.

Children

ApplyBOLD is intended for people seeking work and is not directed at children.

Changes to this policy

If the service changes in a way that affects this policy — for example if we add a new provider or start collecting something we do not collect today — we will update this page to describe it.

Contact

For any privacy question, write to applybold.info@gmail.com.

Grievance contact

Gaurav — applybold.info@gmail.com