Privacy policy

Purpose

MiConnects helps approved testers turn the job posting they are viewing into a reviewed, personalized recruiter outreach email sent through their Gmail account only after explicit confirmation.

Data we handle

• Identity and authentication: Google ID, email, display name, picture, OAuth authorization data, MiConnects session, beta access, and credits.
• Current-page job content: URL, title, company, description, location, experience, salary, skills, metadata, and scan time.
• Candidate data: name, email, phone, role, experience, skills, notice period, summary, resume filename/content, and selected evidence.
• Recruiter and company data: domain, company context, recruiter identity/title/public profile, and business email status.
• Communications: generated drafts, recipient, subject, body, optional resume attachment, send result, and optional credit-request note.
• Operations: authenticated server-request outcomes, coarse timestamps, credit state, provider outcome categories, errors, and standard service/network logs. The Store client contains no direct analytics SDK and sends no separate UI-step telemetry.

We do not intentionally read passwords, cookies, complete browser history, banking data, health data, or content unrelated to detecting a job posting on the current page.

Connected Gmail and LinkedIn activity

With your authorized connection, MiConnects reads relevant Gmail delivery reports and replies to keep job activity current. LinkedIn connection and message activity use Unipile when connected. Messages require your explicit approval.

How data is used

Data is used only to admit testers, maintain sessions, scan the visible job page, resolve companies, find and rank contacts, analyze a user-selected resume, create editable drafts, deliver a user-confirmed Gmail message, enforce credits, prevent abuse, recover workflows, provide support, and measure beta reliability.

We do not sell user data or use it for personalized advertising, creditworthiness, or lending.

Current-page access

The packaged parser runs automatically on supported LinkedIn and Naukri job pages. On other HTTP or HTTPS career pages, Chrome grants temporary current-tab access only after the tester invokes MiConnects. Current-page job content is used only for the visible scanning and outreach workflow. Page scanning remains dormant until the tester accepts the prominent first-use disclosure.

Local Chrome storage

The extension persistently stores its session token, Google profile, credits, settings, candidate profile, full uploaded resume, parsed evidence, jobs, recruiter cache, generated drafts, and pipeline state in Chrome. Logout clears the session identity and credit display but intentionally retains resume, profile, job, recruiter, draft, and workflow data. Clearing extension storage or uninstalling deletes data from that Chrome profile.

Server storage and retention

The account database stores approved tester identity, Google ID, profile fields, beta state, credits/events, and an encrypted Gmail refresh token. Resume files, job pages, and email bodies are processed for the requested feature and are not intentionally stored in the account database. Operational analytics contain the event metadata described above.

• Local data remains until the tester clears it or uninstalls.
• Account, credit, and encrypted Gmail authorization data remains until verified deletion, access revocation, or beta shutdown.
• Analytics and service logs remain until verified deletion or service-retention cleanup, subject to security and backup schedules.

Verified deletion requests are completed within 30 days except for information retained temporarily for security, fraud prevention, legal obligations, or provider backups.

Service providers and sharing

• Google Identity and Gmail: sign-in, OAuth authorization, and user-confirmed messages/attachments.
• Render: authenticated API requests and operational logs.
• Neon: account/credit records and encrypted Gmail refresh tokens.
• Apollo, Apify, and Logo.dev: employer, role/location, and public recruiter/company lookup data.
• Google Gemini, OpenAI, and DeepSeek: resume/job context or candidate, job, company, recruiter, and evidence data when used for analysis or drafting.
• PostHog: bounded server-side beta account/event metadata and basic pageview metadata on these public information pages.
• Beta administrator: identity, credit state, and note only after an explicit credit request.

Sharing is limited to providing, securing, or measuring the disclosed extension purpose, complying with law, or investigating abuse.

Security and user choices

Extension-to-server data uses HTTPS, Gmail refresh tokens are encrypted before database storage, and provider credentials remain server-side. Users can edit drafts, omit a resume attachment, cancel before send, log out, clear local data, uninstall, revoke Google access, or request server deletion.

Deletion and contact

Email hello@miconnects.in from the affected Google email to request correction, revocation, or deletion. Step-by-step instructions are on the support page.

Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Changes and children

This private job-search beta is not directed to children under 13. Material data-practice changes will be published here and prominently disclosed before updated collection begins.