Support and data deletion

Contact

Email hello@miconnects.in. Include the extension and Chrome versions, job-site hostname, visible error, and workflow step. Do not send passwords, MiConnects session tokens, Google authorization codes, raw API responses, or a resume unless support explicitly requests it and you consent.

Common recovery

1. Confirm that the Google email is an approved beta tester.
2. Reopen the job page and MiConnects side panel.
3. Use New Job to request a fresh parse.
4. If the backend is waking, wait briefly and retry the same non-send step.
5. Never repeat Send unless the UI clearly reports no provider-accepted send.

Logout versus deletion

Logout removes the MiConnects session and account display but intentionally retains the saved resume, profile, jobs, recruiter cache, drafts, consent record, and workflow state. It does not delete server data or revoke Google authorization.

Delete local data

1. Open chrome://extensions and choose MiConnects.
2. Clear its extension data if Chrome exposes that control, then remove the extension.
3. Repeat for any other Chrome profile or device where it was installed.

Uninstalling stops page scanning and removes local extension storage from that Chrome profile.

Delete server data

Email from the Google account used for the beta with subject MiConnects data deletion request. Request access revocation, Gmail authorization removal, account/credit/analytics deletion, or all three. We verify ownership and complete data under our control within 30 days, subject to security, legal, fraud-prevention, and provider-backup exceptions.

Separately revoke MiConnects from the Google Account third-party access page if you want Google to invalidate authorization immediately.

Tester-group removal

Removing a tester from the private Google Group stops Store availability but does not itself delete local data, the backend account, or Google OAuth authorization. Use the deletion steps above during offboarding.