Privacy and data
What is public, what your account stores, what the browser extension can read, and when data reaches another service.
This page explains product behavior in plain language. The Privacy Policy is the binding and more complete source.
Public job data
Job postings, company facts, source information, and public job discussions are shared catalogue data. You can browse jobs without an account.
Anonymous API responses may withhold employer application URLs while retaining the job facts. Comments and reactions are public user-generated content and are shown with the user's display name.
Data attached to your account
| Data | Why it is stored |
|---|---|
| Identity and sign-in methods | Account access and sessions. |
| Profile and résumé | Matching, CV generation, and form filling. |
| Search history and alerts | Reuse searches and deliver new jobs. |
| Viewed and saved job state | Hide viewed jobs and keep notes, tags, and status. |
| Saved answers and profile gaps | Reuse application answers safely. |
| Application records | Show destinations, outcomes, and field-value snapshots. |
| Application profiles | Keep targeting rules and targeted CVs. |
| Telegram links and destinations | Deliver alerts to the place you chose. |
| API keys and credit ledger | Authenticate MCP use and account for operations. |
Profile-editor drafts may be stored locally and mirrored to your account so an unfinished edit can survive a reload. A draft does not update matching until you save the profile.
What the extension accesses
The extension needs access to job sites because application forms can live on many domains. When you start a fill or enable automatic applying, it can read the form's field labels and questions, enter approved values, open tabs, and store parts of its local queue.
It reads the Remotera session state so the panel can use your account. It does not read login cookies for other sites or collect a general browsing history.
When data leaves Remotera systems
Limited data reaches another service when the feature requires it:
- approved application values go to the employer or ATS when you submit;
- relevant profile text and a question can go to the configured AI provider to generate an answer or targeted résumé text;
- account email goes through the email delivery provider;
- alert content goes through Telegram when you choose Telegram delivery;
- product analytics and diagnostics go to the analytics provider when enabled.
Remotera does not use your profile or application content to train AI models, sell it, rent it, or use it for advertising.
Shared alert destinations strip personal match data. Webhook destinations should be marked shared whenever their output can be read by other people.
CV-specific behavior
The free CV check evaluates the uploaded bytes and discards them; it does not create a stored résumé or profile. Choosing Save this to my profile is a separate, explicit account action.
A résumé uploaded to My profile is stored because it is meant to be reused and attached to applications. Remove or replace it from the profile page.
Control and deletion
You can remove many items directly:
- delete or pause an alert;
- remove an alert destination;
- revoke an API key;
- delete an application profile;
- clear profile fields or remove the stored résumé;
- delete recent searches and private job notes.
For account deletion, access, correction, portability, or another privacy request, use the contact address in the Privacy Policy. Legal retention requirements may apply to a limited subset of records.
Safer defaults
- Keep webhook secrets outside source control.
- Mark shared destinations honestly.
- Review generated screening answers before submission.
- Do not put secrets or identity documents into public comments.
- Revoke old API keys and remove extension access when you no longer use it.