Privacy policy for “HH Letter Assistant”
Updated: November 6, 2026.
“HH Letter Assistant” is an independent Averliq browser extension for preparing cover letters on hh.ru. It compares the selected vacancy with the profile you provide and connects to OpenAI using your own API key. The extension is free to install and use; you pay for OpenAI API usage under the terms of your OpenAI project.
This policy applies to the extension. It is not an official product of hh.ru or OpenAI.
Data the extension handles
The extension handles:
- Your OpenAI API key, which you enter to connect your own project.
- Your profile and writing preferences, such as your experience, skills and projects. The extension does not automatically download your résumé from your hh account.
- The selected vacancy: its title, description, identifier and page address, together with the employer information needed for that vacancy.
- Available public company information: the company name and description, rating, review count and source links, when hh provides them.
- Generated results: a draft and reviewed cover letter, or a vacancy analysis with supporting quotations.
- Preferences: the selected model, generation settings, letter length and enabled modes.
The extension does not collect your general browsing history, hh password, email contents or data from unrelated websites. It contains no advertising trackers, usage analytics or diagnostic reporting to the developer.
Where data is sent
OpenAI. After you give consent, requests go directly from your browser to api.openai.com. Letter generation sends your profile, writing preferences, the selected vacancy and available employer description. If review is enabled, a second request also contains the first draft. A separate vacancy analysis sends the profile, vacancy and the employer’s name, description and industry. The company rating, review count and verification indicator are not sent to the model. Your key authenticates requests to OpenAI, and the selected model and generation parameters form part of the request. The connection check contacts OpenAI without generating a letter.
By default, the extension removes recognizable URLs, phone numbers, email addresses and Telegram handles from the profile before sending it. If you enable contact details, they may be sent and included in the letter. The filter may miss unusual formats; review your profile and writing preferences before saving them.
Generation requests use store: false. This setting limits storing the response as an API object. It does not cancel request processing, safety measures, possible logging or other OpenAI retention practices. Your project settings and OpenAI API data controls ↗ apply.
hh.ru. To obtain a description, the extension may load the selected vacancy or employer page on the same hh domain, using your existing website session. If the vacancy description cannot be obtained, it may make a fallback request to api.hh.ru without cookies. These requests never contain your OpenAI key. Raw page HTML is not sent to OpenAI; only the relevant text is extracted.
The generated letter and analysis are displayed on the hh page. Like other page content, they may be accessible to website scripts. The extension does not submit an application: you decide whether to send it and press the website’s application button yourself.
Averliq. The extension does not send your key, profile, writing preferences, settings or generated results to an Averliq server. Generation does not use a developer-operated proxy.
Storage and retention
Your key, profile and writing preferences are held only in the current extension session’s memory through chrome.storage.session. The extension does not write these fields to persistent settings storage or synchronize them across devices. The hh page and content scripts cannot access this storage.
Session storage is cleared when Chrome restarts or when the extension is disabled, reloaded or updated. You then need to enter your key and profile again. Closing a single hh tab or the settings window does not end this session.
Letters and analyses may be cached in the same session storage for reuse. The cache is limited to 50 results. Letters can be reused for up to 24 hours, and analyses for up to 15 minutes. Expired entries are removed during subsequent cache cleanup; expiry is not a separately scheduled deletion timer. The entire session cache disappears when the session ends.
Non-sensitive preferences, such as the model, letter length and enabled modes, remain locally in your Chrome profile until you change them or remove the extension. Chrome synchronization is not used. Public vacancy and employer information may also be cached briefly in the memory of an open tab or the background process.
The extension uses HTTPS for network transfers. Session storage does not guarantee protection against malware or someone who has access to your device.
Your controls
By default, you start generation by pressing a button. You explicitly agree to the necessary transfer to OpenAI before connecting. If you separately enable generation when an application form opens, a request may start when an empty letter field appears.
In settings, you can edit your profile, disable automatic generation or contact details, remove the key, clear cached results or clear the session. Removing the extension removes its local preferences. Text already inserted into an hh form remains there; delete it separately if needed.
Clearing the session does not revoke your key in OpenAI, cancel a request already sent or delete information a provider has already received. Manage your API key and OpenAI data settings in your OpenAI account.
The extension uses data only for its stated cover-letter and vacancy-analysis functions. The developer does not sell it or use it for advertising, credit decisions or model training. Use and transfer of data are limited to the extension’s purpose in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Contact and changes
For questions about the extension or this policy, contact Averliq ↗. Do not include your API key in a support message. This policy will be updated when data practices change; material changes will also be disclosed within the extension.