Privacy Policy

When you sign up, we collect your name, email, password (cryptographically hashed by our authentication system — we never see the plaintext), and any profile data you enter (job history, education, skills, target role, contact info).

If you sign in via LinkedIn, we receive your name, email, profile picture, and locale from LinkedIn's standard sign-in flow. We do not request any other LinkedIn permissions.

We log basic technical information for every authenticated request: a timestamp, your user ID, and an IP-derived approximate region so we can debug issues and enforce rate limits.

We measure how the site is used: pages visited, where visitors come from, and product actions such as signing up or generating a CV. Visit statistics do not include your name, e-mail, phone number or the content of your CV. For signed-in members, product usage is linked to your account (e-mail, name, plan and language) and stored in the United States. We also receive error reports when a page crashes, and we measure how our own adverts perform with an advertising tool that receives which Maseera pages are opened and when someone signs up or pays for a plan. The Cookies Policy explains what is kept in your browser.

We do NOT collect: precise location, contacts list, your browsing outside Maseera, or advertising IDs.

When you click "Generate" on a CV, photo, banner, LinkedIn pack, LinkedIn posts, or language-practice turn, we send the relevant data from your profile to our AI through a server-side proxy. No credentials ship in your browser.

AI inputs are processed transiently and are not retained for model training under our AI provider's commercial terms.

Outputs (your generated CV, photo, etc.) are stored in your encrypted account so you can come back to them later.

When you import a LinkedIn PDF, the file is parsed locally in your browser. Only the extracted text is sent to our AI for structuring — the file itself never leaves your device.

LinkedIn analytics screenshots are sent once to our AI for reading, then discarded. We persist only the numbers, not the image.

Account data and generated content are stored in secure encrypted cloud storage with multi-region redundancy.

Payments are processed through a licensed regional payment partner. We never see or store your card number — only the order ID and outcome.

We do not sell or rent your data. Your CVs and everything you generate are never shared with advertisers, brokers or affiliates. An advertising service receives which Maseera pages are opened, when a sign-up or a payment happens (with the plan and the amount), and contact details typed into forms in scrambled form, as the Cookies Policy describes.

A business-visit tool reads the network (IP) address of each visit to name the company it comes from, such as an employer browsing Maseera for Business. We use the company name only, never who you are, to offer Maseera for Business to companies that show interest. It runs only where advertising tools are allowed.

You can export every piece of data we have on you by emailing contact@maseera.ai — we'll send a JSON archive within 7 days.

You can delete your account at any time. Deletion is permanent and removes your user doc, all generated CVs/photos/banners, and your usage logs from our active database within 24 hours, and from backups within 30 days.

Two things are kept after deletion. Records of payments you made stay, because we need a record of the money we received. A record that a free trial or a one-time code was used also stays, with a scrambled form of your email that cannot be read back, so a deleted account cannot claim the same free allowance again. Neither holds your CV, your photos or your profile.

If you're in the EU or UK and exercise GDPR rights (rectification, objection, restriction), email us and we'll respond within 30 days.

Maseera is built for working professionals and is not directed at anyone under 16. We don't knowingly collect data from children. If you believe a minor has signed up, email us and we'll remove the account.

When we change anything material, we'll bump the "Last updated" date above and notify signed-in users in-app at least 14 days before the change takes effect.